M1, M9 and M4

Payments and Transactions

The hard part of payments is the ones that do not arrive. Any system handles a payment that works. This page is mostly about the ones that do not: the instruction held for review, the rail that stops answering, the credit that arrives with no name on it. That is the part you will live with.

14 instruction statesSuspense and releaseInbound and outbound

Every state has a deadline and a consequence.

An instruction cannot sit in limbo waiting for somebody to notice. Each non-terminal state carries a timeout and a named thing that happens when it passes, so a stall is an event rather than an absence.

LiveInstruction lifecycleWaiting
RECEIVEDAccepted from the API. Cancellable.5 min
VALIDATEDShape, account and currency check. Cancellable.5 min
APPROVEDControls satisfied, or a case resolved. Cancellable.5 min
RESERVEDFunds held on the wallet. Cancellable.5 min
SUBMITTEDHanded to the rail. No longer cancellable.1 day
SETTLEDThe entries are posted and the transaction is final.terminal

Where else it can go

HELD_REVIEW1 daySUBMITTED_UNKNOWN15 minHELD_BY_PROVIDER1 dayOPERATIONS_CASE1 dayREJECTED_BY_RAILterminalBLOCKEDterminalCANCELLEDterminal

Every non-terminal state carries a deadline and a named consequence. A rail that stops answering becomes SUBMITTED_UNKNOWN, which is queried rather than resent, because the one thing worse than an unknown payment is two of them.

The one that matters at three in the morning.

A rail that stops answering is the failure mode that costs real money, and it is the one most systems get wrong by being helpful.

StateWhat the machine does
SUBMITTED_UNKNOWNThe rail was handed the instruction and did not confirm. After fifteen minutes the machine raises a query.It never resends. The only thing worse than one payment you cannot account for is two of them, so the recovery path is to ask rather than to retry.
HELD_BY_PROVIDERThe rail has it and is holding it. A day's deadline, then a stall.
OPERATIONS_CASESomething needs a person who is not in compliance.Deliberately separate from a compliance case. The queues are different people with different authority.
REJECTED_BY_RAILTerminal, and distinct from our own rejection.Whose decision it was changes what you tell the customer and what you do next.

Money that arrives without a name on it.

Inbound is its own machine, because an unattributed receipt is not an outbound payment running backwards.

StepWhat happens
RECEIVEDA credit lands from the rail or the statement.
PARSEDThe remittance information is read for something to match on.
SUSPENSENothing matched, so it is booked to a suspense account rather than guessed at.Suspense is a real ledger account with a real balance, which is why it is part of the safeguarding requirement rather than a holding pen outside the books.
ATTRIBUTEDA party was identified and the money is theirs.
CREDITEDPosted to the wallet.
CREDITED_ON_HOLDPosted, and not spendable.The customer can see it, which prevents the support ticket, and cannot move it, which is the point.
RETURNED_TO_SENDERNobody owns it and it goes back.

Which is why you can go live without a rail.

The ledger does not know what triggered a movement. An officer books it today; a rail webhook books it later; the entry is identical. Going live before an integration becomes a sequencing decision rather than a rewrite.

LiveInstruction, outbound transferManual
What triggered it
SourceOfficer, admin portalRail webhook, M4
ActorA. Patelsystem
Recorded asmanual_bookingprovider_event
The resulting ledger entry
DebitClient wallet, Northwind
CreditSettlement, safeguarded
Amount24,500.00EUR

Identical entry, either way

What it guarantees.

Each of these is enforced rather than intended, and each is something you can sit down and try to break on a call. We would rather you did.

  • Every non-terminal state carries a deadline and a named consequence. An instruction cannot sit in limbo waiting for somebody to notice it.
  • A rail that stops answering is queried, never resent. The one thing worse than a payment you cannot account for is two of them.
  • Money that arrives without a name on it lands in a real suspense account with a real balance, which is counted in the safeguarding requirement rather than parked outside the books.
  • Whose rejection it was is recorded distinctly. Ours and the rail’s are different facts, and they lead to different conversations with the customer.

Ask us when the first rail lands.

It is the question we get first and the one we would ask. The answer depends on which rail and which institution, and we would rather give you a real one.