Teach what the agent can never do before teaching what it can. A payment company should give everyone the four verdicts and provenance classes first, certify the operations, disputes and screening reviewers who will approve held work, and keep every money-moving capability at drafting until the agent, the reviewers and the risk owner all have evidence for depth 4.
Why start with verdicts and provenance?
Payments is the sector where a single wrong approval moves real money that may not come back. Reviewers must understand, before anything else, why an action is held, refused or withheld. Some actions are withheld at the platform floor for every agent at every depth, such as reversing a settled payment on the company's own rail; no setting in the business can switch that on. Others are refused or held because the company's own limits say so. A reviewer who cannot tell these apart will escalate the wrong cases and approve the wrong ones.
Provenance is the other foundation. A settlement record from the company's own rail is sealed. A payee's verified name match is signed. A merchant's stated turnover is declared. An emailed request to change a beneficiary is external, and an external claim cannot authorise a payment. Almost every payment fraud relies on a reviewer treating an external or declared fact as stronger than it is.
What order should training follow?
- Everyone: verdicts, depth and provenance. A few hours, including executives and engineers.
- Payments operations reviewers. Repairs, returns, exceptions and settlement breaks. The full reviewer path with a practicum on held drafts during shadow.
- Disputes and chargebacks. The same path, with red lines specific to evidence deadlines and card scheme rules.
- Screening and financial crime analysts. How the agent prepares sanctions and transaction monitoring alerts, what it may close, and what must stay with an analyst under a risk-based approach consistent with FATF standards.
- Merchant onboarding. Reading the agent's due diligence drafts against registry and ownership records.
- Builders and the risk owner. Writing the brief, reading certification results, signing depth decisions.
What must payments reviewers learn specifically?
Payee verification. In the EU, the Instant Payments Regulation requires payment service providers to verify the payee's name. When the check returns a mismatch, the agent should hold. The reviewer must decide with the customer's verified instruction, not with whatever explanation the customer volunteers.
Card data boundaries. If the agent touches card data, the company's PCI DSS scope applies. Reviewers should know which views mask data and must never paste full card numbers into a note or a draft reply.
Screening discipline. An agent can gather the facts for an alert and draft a disposition. Closing a true sanctions match, or deciding to file a suspicious activity report, stays with a trained analyst.
What stays with a person?
| The agent may | Stays with a person |
|---|---|
| Read transactions, settlement files and alerts (depth 1) | Releasing any payment with a payee name mismatch |
| Draft repairs, dispute responses and alert dispositions (depth 2) | Closing a potential sanctions match |
| Repair routine formatting failures within limits, once certified (depth 3) | Filing suspicious activity reports |
| Prepare refunds and returns for release (depth 2) | Releasing refunds and payouts above the company's limit (depth 4) |
What should be proven before depth 4?
Before any agent moves money on its own, a payment company should hold four pieces of evidence: the agent certified at depth 4 for that capability on the company's own transactions; reviewers on that queue certified with no missed red line in their practicum; a risk owner's trace of a sample of filed verdicts; and a sponsor bank or auditor able to check reviewer certificates at source. Most companies will keep depth 4 narrow for a long time, perhaps to refunds below a small amount on the original payment method.
An example
Take a hypothetical merchant acquirer. All 90 staff take the vocabulary course in the first fortnight. Twenty payments operations analysts take reviewer certification while the agent drafts repairs in shadow for three weeks. Twelve disputes analysts follow. Only after both groups pass and the agent is certified does the company let it repair formatting failures at depth 3. Refunds stay at depth 2 for another quarter.
Logistics companies meet a similar question on carrier payments, covered in how logistics companies should train staff. The AI agent training plan template for payment companies puts the steps into weeks.
Where the Academy fits
Pryme Intelligence Academy's Operator practicum requires two weeks of real review decisions with no missed red line, signed off by a Pryme assessor. For payments teams, that is the evidence a sponsor bank asks for. A business can also make approval rights depend on a current certificate, depth by depth.
Questions people ask
Can a payment company use agents before reviewers are certified?
At depth 1 and 2, with a person releasing everything, yes. See can payment companies use AI agents before staff are trained.
Do engineers need reviewer training?
Engineers who build agents should spend time on the held queue first. They write better bounds afterwards.
What do payment companies get wrong?
Training operations and forgetting screening. More in what payment companies get wrong about AI agent training and the guide to training teams for AI agents.