Payment Investigations demo

What the demo shows

Payment ops work wire inquiries, cancellations and non-receipt claims as cases, with replies

A Reading agent reads each request, structured ISO 20022 or free text, and extracts the case with a confidence on every field. A Research agent finds the payment in the payments hub, the SWIFT tracker, the Fedwire gateway, the core banking system and the general ledger, citing each record. A Rules agent decides what the facts mean under UCC Article 4A, Regulation J and the correspondent agreement, and marks any reply that admits liability, moves money or pays a claim. A Drafting agent writes the camt.111, camt.029 and customer notices, a Correction agent drafts the entries, a Deadline agent watches every client deadline, and a Trends agent summarizes repeat issues by correspondent. The analyst sends routine replies; a team lead approves the rest on the same thread.

Transcript

1. 0:00Payment Investigations works wire inquiries, cancellations and non-receipt claims as cases.
2. 0:09Corvane works 3,400 a month; a non-receipt claim took three days.
3. 0:17Halberd Bank asks why 48,250 dollars never reached its customer.
4. 0:25Agents trace it in the payments hub, tracker and ledger, each step cited.
5. 0:31It went to a similarly named account; the name check scored 0.81.
6. 0:38The drafting agent writes the correction and both replies.
7. 0:44Dana asks why not return the funds; the agent cites the agreement.
8. 0:50It admits a mistake and moves money, so it needs a checker.
9. 0:56Team lead Marcus Oyelaran approves on the same evidence, and the case closes.
10. 1:03Halberd's six mismatches reach the relationship manager in a drafted note.
11. 1:10Every action is on the audit trail, with export packs for examiners.
12. 1:15The result: closed in forty minutes, every liability reply signed twice.
13. 1:23Built on Botminds: agents, data, screens and governance on one platform.

The narration as written for the film. Captions are on the player.