Money that has moved is hard to bring back, so a payment company's programme must centre on held actions at depth 4. It should include a common grounding for everyone, reviewer tracks for payments operations, disputes and financial crime, practice on the company's own held payouts and alerts, drills on withheld actions, and sign-off that expires and is renewed.
What makes payments training different?
Most of the work is fast, high in volume and irreversible. A payout sent to the wrong account, or a refund issued twice, may never come back. That puts more weight on the person who releases a held payment than in almost any other business.
Payment companies also sit under several regimes at once. PSD2 strong customer authentication applies in the EU, the EU Instant Payments Regulation requires payment service providers to verify the payee's name, PCI DSS v4.0 governs card data, and the FATF Recommendations set the standard for customer due diligence and suspicious transaction reporting. Training does not need to teach the law. It needs reviewers who know which of their decisions those regimes touch. This is an explanation of the rules, not legal advice; confirm how they apply to you with counsel.
Who takes which track?
| Team | Agent work they review | Track |
|---|---|---|
| Payments operations | Payouts, returns, failed payment repairs | Reviewer track, practicum on held payouts |
| Disputes and chargebacks | Evidence packs and representment drafts | Reviewer track, practicum on past disputes |
| Financial crime | Alert summaries and draft dispositions | Reviewer track, plus drills on what stays with an investigator |
| Merchant onboarding and risk | Business verification checks, draft decisions | Reviewer track |
| Product and engineering staff who build agents | Agent design and certification | Builder track |
| Leadership and the compliance officer | Limits, red lines, the record | Common grounding |
What may the agent do, and what stays with a person?
- Depth 1 to 2: read transactions and merchant files; draft alert summaries, dispute responses and merchant emails.
- Depth 3: repair a failed payment's formatting or chase missing onboarding documents within set rules.
- Depth 4: send a payout, issue a refund or release a held transaction; held for a named person unless the agent has earned that depth for that capability and the amount sits inside the company's own limit.
- Withheld: some actions are refused for every agent at every depth at the platform floor, such as reversing a settled payment on Pryme's own rail. Reviewers should learn that no setting changes this.
- Stays with a person: filing a suspicious transaction report, offboarding a merchant, and any exception to the risk policy.
An example: a payout with a name mismatch
Take a payments firm that pays out to marketplace sellers. The agent prepares a payout of 4,000 to a seller whose bank details changed yesterday, following an email from the seller's address. The email is external provenance, and an external claim cannot authorise a payment, so the payout is held. The payee name check also returns a partial match.
A trained operations analyst reads both signals, contacts the seller through the details on file and holds the payout until confirmed. An untrained analyst sees a known seller and a routine amount and approves. The practicum should include dozens of cases like this, drawn from the company's own payout history.
How should sign-off and renewal work?
Sign-off should be by someone outside the reviewer's team, against a fixed standard with no missed red line. Renewal should be yearly, with an update whenever an agent gains depth 4 for a new capability. Agent certificates lapse after 90 days and a run that clears no depth drops an agent to depth 1 the same day; operations teams must rehearse releasing payouts by hand when that happens.
Logistics companies face the same carrier payment risk on a smaller scale. For scheduling, use the AI agent training plan template for payment companies, and read what payment companies get wrong about AI agent training before you start. To train across several hubs, run a train-the-trainer programme. The general method is in training teams for AI agents.
Where the Academy fits
Pryme Intelligence Academy's Operator track ends with a practicum of two weeks of real review decisions, 95 in every 100 correct and no missed red line, signed off by a Pryme assessor. A payment company can make the right to release payouts at depth 4 depend on a current certificate, so expiry removes the right automatically.
Questions people ask
Should financial crime investigators be certified as reviewers?
Yes, if they act on agent summaries. The filing decision stays with them, but they must know what the agent read and what it could not see.
How many certified reviewers does a payout team need?
Enough to cover every shift on which payouts are released, with at least one spare. Held payouts that wait for the morning become a service failure.
Does card data change the training?
It adds a red line. Reviewers must recognise when agent output exposes card data it should not, and report it at once.