Transaction and arrival status

“Has it arrived?” Check the status before answering.

Connect your read-only transaction API so customers can ask about a transfer in the same conversation. Explain the status, reason, and expected arrival reported by your system.

Start free trial

Sample data · fictional

Payments and fintech

Customer

¿Ya llegó la transferencia DEMO-TX-028?

Read-only tool

get_transfer({ transfer_id: "DEMO-TX-028" }) → status: "en proceso", reason: "pendiente de confirmación", expected_by: "próximo día hábil"

AI reply

La transferencia está en proceso, pendiente de confirmación. El sistema indica que se espera para el próximo día hábil; todavía no figura como completada.

Identity comes from the authenticated session and is injected by the server. Status lookup only; no transaction changes.

A transfer-status lookup tied to the session

Tool name: get_transfer
Description: Read the transfer status, reason, and expected arrival for the authenticated customer.
Endpoint URL: GET https://api.example.com/transfers/{transfer_id}
Authentication: Authorization: Bearer {{TRANSFER_API_SECRET}}
Input mapping: transfer_id ← input.transfer_id customer_id ← server.session.customer_id
Output mapping: status ← $.transfer.status reason ← $.transfer.reason expected_by ← $.transfer.expected_by

Example configuration for your read-only transaction API. No native payment connector is implied.

Only transfer_id comes from the question. The server injects customer identity from the authenticated session; your endpoint must verify ownership.

Read the status your system reports

Configure get_transfer for transaction and arrival-status queries. Return status, reason, and expected_by from your API. If your system has no expected time, say so instead of inventing one.

Use the authenticated session’s identity

Customer identity is injected by the server from the session, not supplied in the chat. Your endpoint must verify that the requested transfer belongs to that customer before returning data.

Explain a pending result clearly

Use the returned reason to explain a pending or completed status in the customer’s language. Show expected arrival as an estimate from the source, never as confirmation that funds have arrived.

Give your team the context for follow-up

If the status needs investigation, hand the conversation to your team. Tools only read transaction status; they do not initiate, cancel, or reverse a transfer.

Questions before you connect

Which data can the assistant read?

The status, reason, and expected arrival fields exposed by your configured read-only API. Ouviro does not gain access to a payment system simply by being embedded on your website.

Can someone supply another customer’s ID in the chat?

A chat message is not an identity source. The server injects identity from the authenticated session, and your API must check authorization for the requested transfer.

Can the assistant move money or change a transaction?

No. These tools query transaction and arrival status only. Requests that need action must be handled by your team through its existing process.

What if the transfer has no expected arrival time?

The answer should state that the source provides no estimate. The conversation can be handed to your support team for follow-up without inventing a deadline.

Let customers ask. Let AI check your system.

Connect your knowledge and read-only APIs for orders, transfer status, invoices, or plans. Answer in your customer’s language.

Start free trial