Most payments cannot be called back once they settle. A payments operations approver authority matrix therefore states which payment actions an AI agent may complete, which it holds, which it is refused and which are withheld for every agent, and names who approves each held action up to what value, with second approvers above set amounts.
What makes payments approvals different?
Most payments cannot be called back. Once a payment settles, recovery usually depends on the receiving bank and the recipient's goodwill. So the matrix leans heavily on holding actions before they become irreversible, and on making sure the approver has sealed evidence, not just a convincing story.
Payments also involve all four verdicts more clearly than any other area. Allowed: an agent repairs a missing field from the original instruction at depth 3. Held: a release from a screening hold waits for a named analyst. Refused: a beneficiary change requested by email is outside the agent's bounds, because an external claim cannot authorise a payment. Withheld: reversing a settled payment on the firm's own rail is refused on purpose at the platform floor, for every agent at every depth. People may still have a manual route for exceptional cases under the firm's own controls, and the matrix should say who.
How do you fill it in?
- List each payment action.
- Write the verdict the agent normally gets for it: allowed, held, refused or withheld.
- Name the approver for held actions and their limit.
- Set the second approver threshold.
- Name the person who handles refused and withheld actions manually, if a manual route exists.
- Record the certificate approvers must hold, if your firm links approval rights to certification.
The template
| Payment action | Agent depth | Usual verdict | Approver | Limit | Second approver above | Manual route owner | Certificate |
|---|---|---|---|---|---|---|---|
| Repair invalid field | |||||||
| Release from screening hold | |||||||
| Release after payee name mismatch | |||||||
| Enter a manual payment | |||||||
| Return an incoming payment | |||||||
| Request a recall | |||||||
| Change beneficiary details | |||||||
| Reverse a settled payment on own rail |
A worked example
A hypothetical payment institution's operations team: twelve analysts, three seniors and a payments operations manager. Values are illustrative.
| Action | Agent depth | Verdict | Approver | Limit | Second above | Manual route owner | Certificate |
|---|---|---|---|---|---|---|---|
| Repair field | 3 | Allowed within bounds | None | Source instruction only | n/a | n/a | n/a |
| Screening hold release | 2 | Held | Senior | All | Possible true match, manager and compliance | n/a | Operator |
| Payee mismatch release | 2 | Held | Analyst | 10,000 | 10,000, senior | n/a | Operator |
| Manual payment | 4 | Held | Senior | 50,000 | Always, manager | n/a | Operator |
| Return incoming | 2 | Held | Analyst | All | None | n/a | Operator |
| Recall request | 2 | Held | Senior | All | None | n/a | Operator |
| Beneficiary change by email | none | Refused | n/a | n/a | n/a | Senior via call-back, with manager check | Operator |
| Reversal on own rail | none | Withheld | n/a | n/a | n/a | Manager, under the exceptional reversal procedure | Operator |
Payee mismatch releases sit with analysts up to 10,000. The EU Instant Payments Regulation requires payment service providers to verify the payee's name, and a mismatch is a signal, not proof of fraud. The analyst checks the context, contacts the payer through a known channel if needed, and records the decision.
The withheld row has no approver because no approval changes the verdict. That is the point of the platform floor. A manager may still follow the firm's exceptional reversal procedure by hand, outside the agent, with its own controls and record.
Repairs at depth 3 are allowed only from the original sealed instruction. If the agent would need to guess a value, the repair is held.
Operational decisions about queues and pauses sit in the approver authority matrix for the operations team. Legal holds on funds follow the approver authority matrix for the legal operations team. Thresholds belong in the approver rule for the payments operations team. Market rules shape the details, as the brief on training payments operations staff in Hong Kong shows.
Where the Academy fits
Pryme Intelligence Academy's Operator track trains payments analysts on how a governed agent decides, including the difference between refused and withheld. Its practicum requires two weeks of real review decisions with no missed red line, signed off by a Pryme assessor, and the certificate is valid for 12 months.
Questions people ask
Why can't a manager approve the agent reversing a payment?
Because withheld actions are refused at the platform floor for every agent at every depth. No customer setting or approval changes it. The manual procedure exists for people, under the firm's own controls.
Should analysts release screening holds?
In this model, seniors do, because a wrong release could breach sanctions. Analysts may prepare the evidence. The skills each role needs are in AI agent skills by role.
What does the matrix look like during a lapse?
The same, except that repairs move from allowed to held. Analysts absorb them until the agent is recertified, so plan cover for the lapse date.