Why payments need multiple statuses

Payment Series | Episode 14

Why does a payment need so many statuses?

Why not just:

Received → Completed → Failed?

Because every status tells the payment engine — and sometimes the customer — two things:

Where is the payment?

What happens next?

An illustrative flow:

Received → Validated → Compliance Passed → Fraud Passed → Balance Checked → Routed → Processed → Booked / Settled

These aren’t just labels.

Each status can trigger the next event.

Take a payment that has cleared compliance and fraud.

The engine now checks the execution date:

📅 Future-dated?

→ Move to Warehoused

→ Wait for execution date

→ Scheduler triggers the next step

⚡ Current-dated?

→ Balance check ✅

→ Route

→ Continue processing

(Exact sequences vary by bank architecture. The principle doesn’t.)

Statuses also drive customer transparency.

Through payment-status reporting, the customer may see:

Accepted · Processing · Awaiting execution · Rejected · Completed

But one distinction matters:

Intermediate status ≠ Final status

Accepted means the payment entered the journey.

Processed means a stage was completed.

Booked / Settled represents a later lifecycle stage — but whether the payment is truly final depends on which status was received, who sent it and the applicable payment scheme.

💡 The Insight

Payment status is not just reporting. It is orchestration.

A well-designed status answers:

Where is the payment now? What happens next?

❓ In your bank, which status causes the most confusion for customers or Operations?

One episode. One practical example. One insight.

#Payments #PaymentProcessing #ISO20022 #PaymentStatus #PaymentOperations