Payment company directors govern the one thing agents must never get casual about: money that cannot be called back. The board needs tested literacy on depth, the difference between held, refused and withheld actions, how certification earns and removes authority, what the record reconstructs, and who releases each payment. Finality should frame every part of it.
Why is finality the centre of a payment board's training?
Most businesses can reverse a mistake with an apology and a credit. A payment company often cannot. Once a payment settles, recovering it depends on the recipient, the rail and sometimes the courts. That makes depth 4, the depth for moving money and hard-to-undo actions, the most important line on the board's map.
It also explains withheld actions. Some actions exist and work, yet are refused on purpose at the platform floor for every agent at every depth. Reversing a settled payment on Pryme's own rail is one. Directors should understand that this is a platform decision, not a company setting, and that it protects them: no configuration change, however urgent the request, lets an agent do it.
What do directors need to understand?
- Depth (per agent), and the depth each action needs: 1 read, 2 draft, 3 routine work within bounds, 4 money or hard-to-undo actions, 5 coordinating other agents.
- The minimum chain: role scope, certificate, sources, the company's own limits and platform guardrails all apply at once, and the lowest wins.
- Provenance: a fact sealed by the settlement rail or ledger outranks a merchant's declared claim; an external email cannot authorise a payment.
- Expiry: certificates lapse after 90 days, and a lapse or a run that clears no depth drops an agent to depth 1 the same day.
- The record: every verdict is filed append-only, so a disputed payment can be traced to its facts, its bound and its approver.
Which payment work stays with people?
| Work | Agent | Stays with a person |
|---|---|---|
| Merchant onboarding checks | Reads and drafts a risk summary at depth 1 to 2 | Accepting the merchant |
| Payee name checks | Runs the check and holds mismatches | Deciding on mismatches |
| Chargeback responses | Drafts at depth 2 | Submitting |
| Refunds and payouts within limits | Prepares and holds at depth 4, if certified | Releasing above the company's limits |
| Suspicious activity | Flags and summarises | Deciding whether to report |
| Reversing a settled payment on Pryme's own rail | Withheld for every agent | Handled outside the agent |
Which external rules shape the board's oversight?
Several cross-border standards bear directly on agents that handle payments. PSD2 strong customer authentication applies in the EU. The EU Instant Payments Regulation requires payment service providers to verify the payee's name, which an agent can run but a person should resolve when it fails. The FATF Recommendations set the international AML standard, including customer due diligence and suspicious transaction reporting. PCI DSS v4.0 governs card data. DORA applies to financial entities' ICT risk in the EU.
None of these mentions agents by name. Each assumes that the people overseeing controls understand them, which is a training requirement in all but name.
What should the board ask for?
A short, regular report on agent capabilities at depth 4, failed certification runs, payments released by uncertified staff (which should be none), and one disputed payment reconstructed from the record. Use a readiness assessment in the payment company to set the baseline and a plan to roll out AI agent training across the company to close gaps. A bank board and a logistics company board face related payment questions. The full model is in AI literacy and certification for people who work with agents.
Where the Academy fits
Pryme Intelligence Academy's Foundations track gives directors the concepts in about four hours. Payment operations approvers take Operator, whose practicum requires 95 correct decisions in every 100 and no missed red line. Executives leading regulated deployments take Architect, ending in a board review with two Pryme assessors.
Questions people ask
Can a payment company let agents release payouts automatically?
Within the company's limits, at depth 4, yes. Above those limits the payout is refused: the agent may only draft it, and a certified person makes the payment. Where payee details came from an external source, the payout should be held for a certified person.
Why can't the company switch on reversals for its own agents?
Because withheld actions are set at the platform floor for every agent. The company can narrow authority through its own limits, not widen it past the floor.
What should directors read before approving depth 4?
The agent's certification evidence, the list of approvers and their credentials, and a reconstructed payment from the record.