Routing number, cut-off, UETR, recall, nostro: what each bank payment term maps to on a blockchain, and where the analogy breaks. A payments team table.
Most blockchain payment terms have a banking twin. A wallet address is an account number, a gas fee is a wire fee, a transaction hash is a UETR or trace number, and finality is settlement. The analogies hold until they don't: there is no recall, no cut-off, and no correspondent bank in the middle.
This page is the translation table. Use it when your finance team, your bank, and your engineers are using different words for the same thing.
Key takeaways
Definition: A blockchain payment moves value as a token, usually a dollar stablecoin, over a public ledger instead of through a chain of bank accounts. The blockchain payments vs crypto payments guide explains how this differs from paying in a crypto asset.
Because the same payment gets described three ways. Treasury talks about value dates and nostro balances, engineers talk about confirmations and gas, and the provider's API talks about payins, payouts, and quotes. Mistakes happen in the gaps.
A shared vocabulary fixes the boring problems first: the wrong network in a payout request, a recipient asking for a "reference number" that is really a transaction hash, or an approval policy written for wires that does not cover token approvals.
Most map cleanly. The right column is where your controls and expectations need to change.
| Banking term | Blockchain equivalent | Where the analogy breaks |
|---|---|---|
| Bank account | Wallet (address) | Whoever holds the private key controls the funds, with no bank to call |
| Account number + routing number or BIC | Wallet address + network | The same address can exist on several networks; the network is part of the destination |
| Bank | Wallet provider or custodian | You can also hold your own keys, which no bank equivalent allows |
| Currency (USD) | Token (USDC, USDT) | A stablecoin is a claim on an issuer's reserves, not a bank deposit |
| Payment rail (ACH, Fedwire, SWIFT) | Blockchain network (Ethereum, Solana, Stellar) | Networks are open around the clock and settle each transfer individually |
| Correspondent bank | None on-chain | Liquidity providers still sit at the on-ramp and off-ramp |
| Wire fee or per-item ACH fee | Gas fee (network fee) | Paid to validators, often in the network's native token |
| Settlement | Finality | Comes in seconds to minutes and cannot be unwound by an operator |
| Cut-off time, business day | None | Bank legs at each end still follow their own calendars |
| UETR, trace number, reference | Transaction hash | Public and checkable by anyone, but covers only the on-chain leg |
| Payment tracker, bank statement | Block explorer | Shows the transfer; does not show who the addresses belong to |
| Recall, ACH return | None (a new transfer back) | The recipient has to send the money back |
| Chargeback | None | No card-style dispute process exists on-chain |
| FX desk, currency conversion | On-ramp and off-ramp | Conversion happens at the edges, at a quoted rate |
| Direct debit mandate | Token approval (allowance) | Lets a contract pull up to an approved amount from a wallet |
| Online banking login and 2FA | Private key signature | A signature is final authorization; there is no password reset |
| Nostro account, pre-funding | Stablecoin float | Held in a wallet, available on weekends |
| KYC and KYB | KYC and KYB, plus wallet screening | Addresses are screened for risk exposure too |
| Travel Rule for wires | Travel Rule for virtual asset transfers | Applies between virtual asset service providers; transfers to self-hosted wallets are handled differently |
The blockchain payments glossary defines each blockchain term on its own. This table is about the mapping.
A wallet, identified by an address. The wallet holds tokens on a specific network, and whoever controls its private key can move them. There is no bank in between that can freeze, reverse, or reissue access, unless a custodian holds the key for you.
That changes one habit. In banking, the routing number tells you which bank. On a blockchain, the network tells you which ledger, and an EVM address on Ethereum looks identical to one on Polygon or Base. Sending USDC on the wrong network is the blockchain version of a wire to the right account number at the wrong bank, except the money may not come back. BlindPay's supported chains reference shows which token exists on which network for exactly this reason.
Finality replaces settlement, and there are no cut-offs. A blockchain transfer is final once the network will not reorganize it, and networks produce blocks all day, every day.
How fast depends on the chain. Ethereum divides time into 12-second slots grouped in 32-slot epochs, and finality comes from checkpoints between epochs (ethereum.org). Bitcoin retargets its difficulty so that 2,016 blocks take about two weeks, which works out to roughly one block every 10 minutes (Bitcoin developer guide).
The catch is the bank legs. A stablecoin payment that starts with an ACH deposit and ends with a SEPA credit still waits for those rails. The network never closes; the banks at the edges do. Stablecoin API SLAs and settlement finality covers how providers word this in contracts.
Gas, or network fees. Each transfer pays validators to include it in a block. It is the closest thing to a per-item wire or ACH fee, and on most chains used for payments it is small per transfer.
Do not stop there, though. A cross-border stablecoin payment has two currency conversions, and that is where most of the cost sits. The Federal Reserve noted in March 2026 that on-chain costs are likely small but on-ramp and off-ramp costs can be greater (Federal Reserve, 2026). Compare quotes on the amount delivered, not on gas.
With the transaction hash. Paste it into the network's block explorer and you see the amount, both addresses, the block, and the confirmation status. No phone call to a correspondent bank needed.
It is a partial view. The hash covers the on-chain leg only. If the payment ends in a bank account, the bank leg has its own reference, and a good payment API returns both and fires a webhook when each stage changes.
No. There is no recall message, no ACH return code, and no chargeback. Once a transfer is final, only the recipient can send funds back, as a new transfer.
That is why controls move earlier in the flow. Address checks, quote approvals, and amount limits happen before anything is signed. Are stablecoin payments reversible? explains what protections exist instead.
Four: correspondent banks, cut-off times, recalls, and chargebacks. Each one exists in banking because settlement passes through several institutions on business hours. A single shared ledger removes the need for most of them.
The Federal Reserve's March 2026 note puts numbers on the old structure: over 60% of wholesale payments are routed through one or more intermediaries, and the number of active correspondents has declined by about 30% over the last decade, per the same FEDS note. Fewer hops is the core of the blockchain pitch. Fewer safety nets is the trade-off.
At the ramps. An on-ramp turns a bank deposit into stablecoins and an off-ramp turns stablecoins back into a bank credit. Everything a bank person cares about happens there: FX rate, fees, compliance checks, and the local rail.
BlindPay's docs use both vocabularies on purpose. The Abstracted flavor describes payments in bank terms (deposits, virtual accounts, bank payouts), and the Advanced flavor describes the same flows in blockchain terms (wallets, networks, token authorization). Same API, two lenses (overview).
Pick one payment your team runs today and write it out in both columns. Where a banking control has no blockchain twin, like a recall, decide what replaces it before you go live.
For the step-by-step view of what happens on the ledger, read what happens on-chain in a stablecoin payment.
To see the bank-side and chain-side vocabulary for the same payout in one place, open the BlindPay overview and switch between the Abstracted and Advanced flavors.
Seven places blockchain payments beat bank rails: contractor payroll, remittances, B2B suppliers, marketplaces, 24/7 treasury, bill pay, and PSP payouts.
Push means the payer sends an ACH transfer. Pull means you debit a connected account. How each funds a USD to USDC on-ramp, the fees, and the return risk.
AP2, ACP, and x402 each verify that an AI agent had permission to spend. Here is what every protocol covers, who backs it, and the reconciliation gap none of them close.