The nine parties behind one blockchain payment, from sender and on-ramp to issuer, network, off-ramp, and bank. Who does what, and who fixes failures.
A blockchain payment usually involves nine parties: the sender and its bank, an on-ramp, the stablecoin issuer, a wallet holder, the blockchain network, liquidity providers, an off-ramp, the recipient's bank and local rail, and compliance checks throughout. A payment API often coordinates most of them, so the sender and recipient only see bank accounts.
Knowing who does what tells you who to ask when something breaks, and where the fees come from.
Key takeaways
Definition: A blockchain payment is a transfer that settles on a public blockchain, usually as a dollar stablecoin, often converted from and back into bank money at each end. See blockchain payments vs crypto payments for how this differs from paying in a crypto asset.
Nine roles, listed in the order money meets them. Some companies play several roles at once, and a payment API can bundle most of them behind one integration.
| Role | What it does | What it is responsible for | Typical failure |
|---|---|---|---|
| Sender and sender's bank | Starts the payment and funds it | Correct amount, recipient details, source of funds | Deposit late, missing reference, rejected by the bank |
| On-ramp | Converts bank money into stablecoins | KYC or KYB of its customer, the buy rate, delivery | Deposit held for review, amount mismatch |
| Stablecoin issuer | Mints and redeems the token against reserves | Reserves, redemption, freezing sanctioned addresses | Depeg, frozen address |
| Wallet holder or custodian | Holds the tokens and signs transfers | Key security, authorizing the exact amount | Lost key, wrong network, wrong address |
| Blockchain network and validators | Records and finalizes the transfer | Ordering and finality | Congestion, higher fees, slower confirmation |
| Liquidity providers | Supply the local currency and price the trade | The rate behind the quote, depth for large amounts | Wide spread, thin liquidity in a currency |
| Off-ramp | Converts stablecoins into local currency | The sell rate, the local payout, its own compliance | Payout rejected, review hold |
| Recipient's bank and local rail | Credits the recipient's account | Name and account checks, crediting funds | Invalid account, closed account, name mismatch |
| Compliance functions | Check people, businesses, wallets, and transfers | KYC, KYB, sanctions, wallet screening, Travel Rule data | Hold, request for information, rejection |
The banking terms vs blockchain terms table maps each of these roles to the bank job it replaces.
A different party at almost every step. That is the most useful question you can ask a provider, because custody decides who owes you the money if something goes wrong in the middle.
Here is the flow as a simple diagram, left to right:
A design team can draw this as five boxes with arrows, with a label under each box naming the party that holds funds. Custodial vs non-custodial off-ramps covers what each custody model means if a provider fails.
The ramps and the liquidity behind them. The blockchain network charges a network fee, but it does not set any exchange rate. Converting dollars into stablecoins, and stablecoins into reais or pesos, is where the price is made.
That matches what the Federal Reserve said in March 2026: on-chain costs are likely small, but there may be greater on-ramp and off-ramp costs when exchanging payment stablecoins for fiat currency (Federal Reserve, 2026). So compare providers on the amount the recipient receives.
Market makers are the quiet party here. They quote the rate a ramp passes on, and their depth decides whether a large payout gets the same rate as a small one. What is a market maker in stablecoin payments? explains how that works.
It creates tokens when someone deposits dollars and destroys them when someone redeems. Circle issues USDC and Tether issues USDT. The issuer does not touch each payment: tokens move wallet to wallet without asking it.
Its job is to keep the token worth one dollar. In the US, the GENIUS Act framework requires payment stablecoins to be backed by relatively safe assets with low credit or valuation risk, per the same Federal Reserve note. Issuers can also freeze tokens at specific addresses, which is why sanctioned or stolen funds can get stuck.
Every regulated party, for its own customers. The ramp or payment provider runs KYC on individuals and KYB on businesses, screens the wallets involved, and checks sanctions lists. Banks at each end run their own checks, and transfers between virtual asset service providers carry Travel Rule data.
Central banks watch this layer closely. The Bank for International Settlements wrote in 2025 that stablecoins perform badly against its integrity test at the system level, pointing to risks from transfers between unhosted wallets (BIS, 2025). Regulated ramps are where that gap gets closed in practice. Travel rule for stablecoin off-ramps covers the data that travels with a transfer.
If you run a platform that pays your own users, you are part of this chain too. A provider can verify your end users, but your own obligations as a business with customers stay with you.
The party at the stage where it failed. A late deposit is between the sender's bank and the on-ramp. A wrong address is usually the sender's problem. A rejected local payout belongs to the off-ramp and the recipient's bank.
What matters is the refund path. Before you integrate, ask each provider three things in writing: where funds go if a payout cannot be delivered, whether the refund is automatic, and how long a review can take. Are stablecoin payments safe? lists the other risks to check.
BlindPay plays the payment API role and runs the ramp, liquidity, and payout steps behind one integration. A business can fund with a bank deposit, and the recipient gets local currency over ACH, wire, SWIFT (POBO/COBO), RTP, Pix, SPEI, Transfers, ACH COP, or SEPA (overview).
On custody, BlindPay operates as a non-custodial payment processor for payout flows from customer-controlled wallets: you authorize the exact amount and BlindPay executes that single transaction. If a payout cannot be delivered after the stablecoins are collected, BlindPay refunds them to the quote's refund wallet, or to the sending wallet when none is set. On Pix and other non-USD local rails the refund is automatic, while USD payouts and payouts whose review times out are refunded after an operator review. Optional BlindPay-managed wallets (beta) are custodial when you choose that path.
Draw your own payment as the five-box diagram above and write a name under each box. Any box without a clear name, or with "we think the provider handles it", is the first question for your next vendor call.
If you would rather skip the blockchain roles entirely, see do you need a crypto wallet for stablecoin payments?.
To see each stage of a BlindPay payout and the webhook it fires, read the payouts documentation.
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.