
You pressed “send” on a large company payment. What happens next? Before the money leaves your bank, it passes through a series of checks, and each one can stop it. Knowing these steps helps you understand the status you see, and why a payment can be delayed.
The journey at a glance
Read the five columns from left to right: initiation, processing, clearing, settlement and, in gray, exceptions. Each column lists the statuses you may see at that stage. The dark bar is the happy path a normal payment follows: created, approved, sent, credited and settled. The gray column shows what can go wrong: rejected, returned, recalled or disputed.
The 7 checks before a payment leaves the bank
| # | Stage | What the bank checks | What can delay it |
|---|---|---|---|
| 1 | Initiation | The instruction arrives from online banking, an API (a way for two systems to talk to each other), a file or the company’s finance and accounting system (its ERP) | Missing or badly formatted data |
| 2 | Validation | Correct format (such as ISO 20022), valid account numbers, no duplicates | Format errors, duplicate payments |
| 3 | Account checks | Enough balance, credit limits, the right currency, before the cut-off time | Low balance, missed cut-off |
| 4 | Compliance and risk | Sanctions screening (checking the government’s lists of banned people and countries), anti-money-laundering checks, country risk | A possible sanctions match needing manual review |
| 5 | Pricing and FX (foreign exchange: changing one currency into another) | Exchange rates and fees applied | Rate approval for large amounts |
| 6 | Accounting | Your account is debited and the funds are reserved | System or booking errors |
| 7 | Approval and routing | Maker-checker approval for big amounts (a bank operations clerk enters it, and a payments operations manager approves it), then the right payment system (the “rail”) is chosen: wire, ACH (bank-to-bank transfers in the US), RTP (instant payments run by The Clearing House), FedNow or Swift | Waiting for an approver |
Only after all seven checks does the payment leave the bank. Then the network and the receiving bank do their own checks.
The status codes you’ll see
With ISO 20022 (a newer, richer format for payment messages), banks report progress with standard status codes, usually in a payment status report (pacs.002 or pain.002):
| Code | Meaning, in plain English |
|---|---|
| ACTC | Accepted: the message passed the technical checks |
| ACCP | Accepted: the customer and account checks passed |
| ACSP | Accepted: settlement (the moment money actually moves between banks) is in progress |
| ACSC | Accepted: settlement is complete. The money has moved. |
| PDNG | Pending: waiting for something, such as a review or approval |
| RJCT | Rejected: always comes with a reason code, for example AC04 (account closed) |
How to track a payment after it leaves
- Cross-border (Swift, the secure network banks use to send payments abroad): every payment carries a unique tracking number called a UETR, which every bank on the way uses to track it end to end.
- US wires (Fedwire): each wire gets a unique reference that both banks can use to trace it.
- Instant payments (RTP, FedNow): you get an accepted or rejected answer within seconds.
Tips for payments product teams
- Show customers simple, honest statuses: “Being checked”, “Sent”, “Completed”, “Needs your action”.
- Map your internal statuses to the ISO 20022 codes so every channel tells the same story.
- When a payment is rejected, show the reason in plain English and what the customer can do next.
- Track how long payments sit in each stage. Long waits point to the step that needs fixing.
My take
A payment isn’t “instant magic”. It’s a series of careful checks that protect your money. Clear statuses turn that hidden journey into something customers can see and trust.
Working on a payments project?
I help banks and fintechs deliver real-time payments, ISO 20022, and AI-driven AML and compliance change, from strategy to go-live.
Connect on LinkedInSee how I can help