You can describe a rail by its speed, its cost, or its message format. None of those tell you how to build on it. The property that does is finality: the moment a payment stops being a claim that can be unwound and becomes a settled fact. Get this wrong and you build a refund flow that the rail does not support, or you assume a fraud loss is recoverable when the money left days ago.
We covered the rails themselves in the previous modules. This module is about the one axis that cuts across all of them.
Two kinds of finality
Finality is not a single event. It has a legal dimension and an operational dimension, and practitioners conflate them at their peril.
Operational finality is mechanical. It is the point in the clearing and settlement process where the system stops accepting an instruction to undo the transfer. After this point there is no message you can send that the rail will honor as a cancellation.
Legal finality is the harder guarantee. It is the point at which the transfer is irrevocable as a matter of law, including against the claims of an insolvency administrator if a participant fails between submission and settlement. This is the protection that keeps one bank's collapse from clawing back settled payments across the whole system.
The distinction matters most under stress. A payment can look operationally complete and still be legally exposed if the governing rules do not protect it against an insolvency unwind. That gap is precisely what settlement finality law exists to close.
Where each rail sits
Every rail occupies a position on a spectrum from irrevocable to reversible. The position is fixed by the rail's rules, not by your preference.
Wires and instant rails: irrevocable
Under UCC Article 4A, the legal basis for domestic wires in the US, a funds transfer is accepted and final once the beneficiary's bank accepts the payment order. After acceptance the sender cannot cancel without the receiving bank's consent, and the bank has no obligation to give it. Under section 4A-406 the originator's underlying debt is discharged at acceptance to the same extent as if cash had changed hands. The framework was built to make high-value transfers predictable, which means built to make them final.
RTP and FedNow inherit the same posture by design. Both are credit-push and both are final and irrevocable the moment the payment is submitted and the receiving institution accepts it. A sending institution cannot recall the payment. What both networks provide instead is a Request for Return of Funds: a message asking the receiver to send the money back voluntarily. That is not a reversal. It is a polite request that depends entirely on the receiver cooperating and the funds still being there.
This is the trap for anyone migrating volume to instant rails expecting an ACH-style safety net. There is none.
ACH and cards: reversible
ACH is reversible by return. A standard return such as insufficient funds moves back within two banking days of settlement. An unauthorized consumer debit can be returned for up to 60 calendar days from settlement under Nacha rules, via codes including R05, R07, and R10. The money can move forward in a day and still come back two months later.
Card payments are reversible through the chargeback. The cardholder disputes a transaction with their issuer, and the network rules pull the funds back from the merchant, often months after authorization. Chargebacks are a card-network mechanism and are legally distinct from ACH returns, but the product consequence is the same: settlement does not mean the money is safe to spend.
Why finality dictates everything downstream
Once you know where a rail sits, three product decisions follow almost mechanically.
Fraud exposure. On an irrevocable rail, the loss lands the instant the payment leaves and the funds are gone. There is no return window to catch a mistake. This is why authorized push payment fraud is so damaging on wires and instant rails: the victim authorizes a real, final transfer to a fraudster, and the rail did exactly what it was told. Your fraud controls have to live before submission, because nothing after submission can help you.
Refund mechanics. You cannot reverse a final payment. You can only originate a second, separate payment in the opposite direction. A refund on an instant rail is a new credit transfer, not an undo, and it carries its own fraud and finality properties. On reversible rails the system itself provides the unwind, which is why card refunds and ACH returns feel different from wire refunds. They are different mechanisms, not different speeds of the same thing.
Funding and credit design. Reversibility is a liability that sits on your balance sheet. If you give a merchant access to card or ACH funds before the return and chargeback windows close, you are extending credit against money that can be pulled back. A later module turns this into a funding model. For now the rule is simple: on a reversible rail, settled is not the same as safe, and your reserve and hold policies should track the return window, not the settlement timestamp.
The legal floor: settlement finality law
The protection that makes any of this dependable is statutory, not contractual. In the US, UCC Article 4A supplies finality for wires. In the EU, the Settlement Finality Directive (98/26/EC) does the systemic work: it makes transfer orders and netting irrevocable from a defined moment within a designated system, and it enforces that irrevocability even after insolvency proceedings open against a participant. The directive exists to stop one participant's failure from cascading through the system by unwinding settled payments, which is the systemic risk we name as Herstatt risk in the next module.
The practical reading: a rail's finality is only as strong as the law that protects it against an insolvency unwind. Operational finality without legal finality is a guarantee that holds right up until the moment you need it.
Takeaway
Finality is the first question to ask about any rail, before speed or cost. Irrevocable rails (wires, RTP, FedNow) push all your fraud control to before submission and make every refund a fresh payment. Reversible rails (ACH, cards) give you a return window but turn settlement into a liability you have to fund. The rule that ties it together: settled and final are not the same thing, and the gap between them is where fraud losses and funding risk live.