Payment Investigation Agent · Use case
How can a bank use an AI agent to answer payment investigation queries on its own infrastructure?
A payment investigation agent takes a query about a payment, from a customer or from another bank. It finds the payment in the payment hub, lines up its messages in order and drafts the reply. An investigator sends the reply, and nothing is recalled, amended or returned without a person's approval.
One query. Several screens.
A deadline.
- ✗ 01To answer one query an investigator opens the payment, its message history and the earlier correspondence. Most of the time goes on finding the facts and putting them in order.
- ✗ 02Payment data cannot be pasted into a public AI service, and the customer or the other bank expects an answer that can be evidenced.
Where it stops for a person
Before a reply is sent, and before any recall, amendment or return.An investigator checks and sends every reply. A recall, an amendment or a return is prepared by the agent and waits for a person's approval.
It traces the payment.
An investigator replies.
Step · 01
An investigator gives the agent the query: a customer asking where a payment is, or another bank asking about one it sent or received.
Step · 02
The agent finds the payment in the payment hub and reads its status and history.
Step · 03
It lines up the messages on that payment in order, with the time of each.
Step · 04
It drafts the reply, with the record each statement came from beside it.
Step · 05
The investigator checks the draft and sends it. If the case needs a recall, an amendment or a return, the agent prepares the request and it waits for approval.
Reads from · connectors
Your own APIs
Your payment hub, through its own API. You give Katonic the API's OpenAPI description and each operation becomes a tool.
Acts through · your own APIs
The same API's operations for a recall, an amendment or a return. Each one is a separate tool, held for a person's approval.
What you set up
- Import the payment hub's API description.
- Choose the operations the agent may call.
- Leave every operation that changes a payment held for approval.
Where it runs
The agent, its knowledge store and the model run on infrastructure you own or control. You choose the model and serve it yourself, so questions, documents and answers are not sent to a public AI service. Payment data stays inside the bank.
How you get it today
This page is labelled Use case: the agent is built in Katonic Studio. You describe the job, connect what is named above, add test questions and release the agent once it passes them. When the Catalog holds a tested template for this job, this page will carry the Template label and show how to take it.
Can the agent recall or return a payment?
Not on its own. It prepares the request, and a person approves it before anything goes to the payment hub.
Does it work with our payment hub?
It works through the hub's own API. You supply the API's description, so no ready-made connector has to exist for your product.
What does the investigator see?
The draft reply with the record behind each statement, so every line can be checked before it is sent.