Crypto Payment Settlement Speed: Which Gateway Is Fastest

Every crypto payment gateway advertises instant settlement. Almost none says which part is instant. The blockchain is rarely the slow part: on the fastest rails a payment is irreversible in under a minute, and even Bitcoin is done in an hour. What varies by days is what happens after the chain finishes — whether your money sits in a processor’s account waiting for the next business-day payout batch, and whether you still have to convert it into the currency your suppliers invoice in.

So compare settlement speed by splitting the journey into five stages and asking each vendor about each stage separately. Stages 1 to 3 run in seconds and minutes and are mostly set by the chain. Stage 4 is where the real spread lives, and it is a function of custody rather than technology. Stage 5, fiat conversion, usually takes longer than stages 1 through 4 combined, and most comparison pages leave it out.

We sell a non-custodial gateway, so read this accordingly: stage 4 is zero for us by construction, which is architecture rather than a marketing claim — and the cost of that architecture is that we cannot do stage 5 for you at all. Every competitor figure below links to the vendor’s own public documentation, checked 21 September 2026. Where a vendor publishes no number the table says not published rather than an estimate, including in our own row.

The five stages between “Pay now” and money you can spend

These stages are sequential and independent. A gateway can be excellent at one and terrible at another, which is how two providers both truthfully claim “instant” and deliver results a week apart.

Stage	What happens	What controls the duration	Typical elapsed time
1. Broadcast	Buyer’s wallet signs and pushes the transaction to the mempool	The fee the buyer’s wallet attaches, plus current congestion	Seconds — but open-ended if underpriced
2. First confirmation	The transaction is included in a block	The chain’s block interval	Sub-second to ~10 minutes
3. Gateway calls it paid	The provider fires the webhook you fulfil on	The provider’s confirmation policy, sometimes scaled by order value	0 to ~60 minutes
4. Funds reach a balance you control	The asset becomes yours to move	Custody model. Custodial providers run payout batches; non-custodial ones have no such step	Zero, or one to two business days
5. Local currency in your bank	Crypto is sold and fiat is wired	Exchange or OTC desk, then banking rails	1–3 business days, longer on a first withdrawal

What to do with this: make every vendor answer for stage 3 and stage 4 separately. A provider quoting “10 minutes” is describing stage 3 and omitting stage 4; one quoting “next business day” is describing stage 4 and omitting that stage 3 finished 24 hours earlier. For who controls the asset at each point, see our note on stablecoin checkout versus stablecoin settlement.

Stages 1 and 2: what the chain actually costs you in time

This part is public, verifiable and identical for every gateway on the same network. Nobody has a faster Ethereum.

Network	Block interval	First confirmation	Practical finality
Bitcoin Lightning	Off-chain	Sub-second	Immediate within channel capacity
Tron (TRC-20)	~3 seconds	~3 seconds	~1 minute — solidifies once 19 of 27 Super Representatives build on it
Ethereum (ERC-20)	12-second slots	~12 seconds	~13–15 minutes — two epochs to full finality
Bitcoin (on-chain)	~10 minutes on average	~10 minutes	~60 minutes at the conventional six confirmations

Sources: TRON consensus documentation and ethereum.org on finality, both checked 21 September 2026. Bitcoin’s ten-minute target is a protocol parameter; real intervals vary widely around it.

What to do with this: if chain-layer speed is your binding constraint, enable Lightning for small digital orders and Tron for everything else — Tron reaches irreversibility roughly twelve times faster than Ethereum. If your orders are large and infrequent, one minute versus fifteen is noise, so choose on cost instead.

Fast and cheap are separate axes, and 2026 broke the old pairing

The standard advice — “use TRC-20, it is cheap and fast” — now gets one of those two backwards. In our September 2026 measurement, a USDT or USDC transfer cost about $0.02 on ERC-20 and $2.11 to $4.36 on TRC-20. Tron is now roughly a hundred times more expensive per transfer than Ethereum, the reverse of its position for years, driven by falling Ethereum gas prices alongside a higher TRX price feeding Tron’s resource pricing. Method and raw figures are in our measured ERC-20 versus TRC-20 fee comparison.

So in 2026 the cheap rail is the slower one and the fast rail is the expensive one. That matters because fees and speed get conflated constantly. They are unrelated: a fee buys priority into the mempool, not a shorter block interval. Paying triple gas on Ethereum does not produce a nine-second block.

When stage 1 stalls

Nobody budgets for the mempool stage, and it is the usual cause of a customer insisting they paid an hour ago. Three recurring reasons: the wallet attached a fee below the current floor and the transaction is simply waiting; the buyer paid from an exchange, so that exchange’s withdrawal queue — often 10 to 30 minutes, sometimes manually reviewed — runs before anything is broadcast; or the right asset went out on the wrong network, where waiting never helps. That last case has a recovery procedure in our underpaid, overpaid and wrong-network payment SOP.

Stage 3: the confirmation policy is the biggest published difference

This is the first stage where vendors diverge, because each decides for itself how much reorganisation risk to absorb before telling you the order is paid. Some make it configurable; some publish no number at all.

Gateway	Signal you fulfil on	Confirmations required	Time to that signal
BitPay	Invoice status confirmed	Configurable via transactionSpeed: high = received but not yet validated on-chain; medium = 1 BTC confirmation; low = skips confirmed, reaching complete at 2 confirmations	~0 / ~10 min / ~20 min for BTC
Coinbase Commerce	Charge status PENDING	Transaction included in a block; COMPLETED adds reorg protection	2–10 seconds to PENDING, ~15 minutes to COMPLETED
NOWPayments	confirmed, then finished	No per-asset count published; its blog describes value tiers — 1 confirmation under $1,000, 3 up to $10,000, 6 up to $1M, 60 above	~60 minutes at six BTC confirmations
CoinPayments	Payment marked complete	Not published in the public FAQ	Not published
Aurpay	succeed callback	Not published as a fixed count in public API docs	Not published

Sources, all checked 21 September 2026: BitPay invoice states, Coinbase Commerce payment status, NOWPayments on payment statuses, and the CoinPayments FAQ.

Our own row is the uncomfortable one and we are leaving it in. Aurpay’s public API documentation defines the terminal order states and the callback that fires on payment, but publishes no per-asset confirmation threshold. If your fulfilment policy depends on that exact number — and for anything shipped physically it should — ask for it in writing before you integrate rather than inferring it from test orders. That is a documentation gap on our side, not a feature.

What to do with this: BitPay is the only one of the five that hands you the dial, so if you want a configurable per-store risk setting out of the box, it wins this stage outright. Everyone else, us included, gives you a fixed policy to work around in your own order state machine.

Why fewer confirmations is not simply better

A confirmation threshold is a bet, not a performance metric. Below finality the block holding your payment can be reorganised out of the chain, and the payment goes with it. That is why BitPay’s documentation flags the high setting as making you more susceptible to fraudulent payments, and why Coinbase Commerce separates PENDING from COMPLETED instead of treating block inclusion as final.

Size the threshold against what a reversal costs you. A $12 software licence delivered on first confirmation is rational even at a one-in-a-thousand reversal rate; a $9,000 order where you pay freight at dispatch is not. The right answer scales with order value, which is what NOWPayments’ tiered model encodes and what most merchants should build regardless of gateway. Anyone selling “zero-confirmation instant settlement” as an unqualified benefit is selling you their risk.

Stage 4: the withdrawal cycle nobody puts in the headline

Here is where a one-minute chain becomes a three-day wait. Once a custodial provider has been paid, the funds sit in their account, and moving them to yours is a separate scheduled process with its own calendar.

Gateway	Who holds the funds after payment	Route to a balance you control	Delay this stage adds
BitPay	Custodial — credited only at invoice status complete	Automatic settlement every business day, to a crypto address or bank account	Crypto: daily batch. Fiat: +1 business day for EUR via SEPA, +2 for USD, GBP, CAD, AUD, NZD, CHF and MXN
Coinbase Commerce	Custodial balance, migrating onto the onchain payment protocol and Coinbase Business	Account withdrawal, or direct onchain receipt under the newer protocol	See the migration note below
NOWPayments	Custodial in transit, then auto-forwarded	Payout to your nominated wallet	Minutes, per its published payout timings
CoinPayments	Custodial wallet balance	Manual or API withdrawal; minimum is twice the network fee	Not published
Aurpay	Nobody. Funds never enter an Aurpay account	None — the payment lands at your own address	Zero

BitPay’s figures come from its settlement documentation, checked 21 September 2026: settlements run automatically every business day, and fiat lands one or two business days later depending on currency and rail. NOWPayments’ figure comes from its own payout guide, which puts standard wallet payouts at one to three minutes.

The zero in our row is not a performance claim and we optimised nothing to achieve it. In a non-custodial design the buyer’s transaction is addressed to a wallet you already control, so there is no intermediate balance, no payout batch, no business-day calendar, no minimum withdrawal and no counterparty that could freeze the transfer. The step does not exist — which is also why the price is a flat 0.8% per transaction rather than settlement tiers.

The cost is equally structural. You hold the keys, so a lost seed phrase is unrecoverable and nobody can reverse a mistake for you. And because we never touch the money, we cannot convert it — which is the stage that actually takes days.

What to do with this: if your cash-flow problem is waiting on someone else’s payout calendar, a non-custodial gateway removes the stage entirely and is the right choice. If you would rather a provider held the keys and absorbed that operational burden, accept the batch delay and pick on settlement currency instead — but price the delay explicitly rather than reading “instant” off the homepage.

One caution on Coinbase Commerce: it is being folded into Coinbase Business and the onchain payment protocol, with third-party migration guides citing a 31 March 2026 cut-off for the legacy Commerce portal for merchants outside the United States and Singapore. We could not fetch Coinbase’s own notice to confirm the scope, so verify your status with Coinbase before planning around Commerce timings.

Stage 5: if you need local currency, the chain was never your bottleneck

A non-custodial gateway puts USDT or USDC at your address within a minute or two, then stops. If your suppliers, payroll and tax authority work in dollars, euros or Singapore dollars, you still have to sell the stablecoin and get a wire. That leg runs through an exchange, an OTC desk or a crypto debit card and typically takes one to three business days, longer on a first withdrawal because identity verification happens here rather than at checkout. Our guide to crypto on-ramps and off-ramps covers the routes.

Two consequences follow. First, Aurpay does not convert crypto to fiat and does not settle into bank accounts. If you need local currency on a fixed schedule you will run that conversion yourself, and it should be set up before you integrate. Getting an off-ramp with verified business accounts approved is a week of onboarding you want behind you, not ahead of you in the week a supplier needs paying.

Second, a competitor quoting next-business-day fiat settlement is performing stage 5 for you, and can only do so by taking custody first. That is a legitimate trade — convenience for control, plus whatever spread sits inside their conversion rate — but it means their headline number and ours measure different things. Ours ends at stage 4; theirs starts there. The gateway fee comparison is where that spread shows up.

For cross-border e-commerce, do the arithmetic explicitly. A SWIFT payment takes two to five business days end to end. A stablecoin payment collapses stages 1 through 4 into under fifteen minutes, then spends one to three business days in stage 5 — but only if you convert. Merchants who keep a working balance in stablecoin and pay overseas suppliers from it skip stage 5 entirely. That is where the real cross-border advantage lives, and it is a treasury decision rather than a gateway feature.

What makes real settlement slower than any table

Four failure modes absent from every vendor’s timing claims:

Congestion. Block intervals are averages. Under heavy on-chain activity, a transaction priced at yesterday’s fee level can sit unconfirmed for hours. Bitcoin is most exposed: longest block interval, most volatile fee market.

Lightning channel capacity. Lightning settles in under a second and is the fastest option here, but it is bounded: a payment only routes if enough inbound liquidity exists along the path, so large amounts fail outright rather than arrive slowly. Aurpay accepts Lightning through its plugins, hosted checkout, Payment Button, invoices and REST API, but provides no node hosting, liquidity provision or channel management, so inbound capacity is your side of the arrangement. Treat Lightning as a fast lane for small orders, not a rail for high-ticket checkout.

Exchange-originated payments. When a buyer pays from an exchange rather than a self-custody wallet, that exchange’s withdrawal queue runs first, entirely outside your visibility. It is the largest source of stage-1 variance in practice.

Weekends and holidays. Stages 1 to 3 ignore them. Stages 4 and 5 do not, at every custodial provider and every bank. A Friday evening order on a business-day cycle is a Tuesday morning deposit.

Choosing by the deadline you actually have

Your situation	Fastest workable setup	Reasoning
Digital goods, instant delivery, low ticket	Lightning, or Tron with fulfilment on first confirmation	Reversal exposure is smaller than the order margin
Physical goods dispatched same day	Stablecoin on Tron, ship at solidification (~1 minute)	Freight and label costs are real losses on a reversal
Orders above roughly $5,000	Wait for full finality; six confirmations on Bitcoin	Reorg tail risk outweighs an hour of delay
You need local currency on a schedule	Any gateway — the off-ramp sets the clock, not the checkout	Stage 5 dominates; optimise the conversion route
Cross-border B2B, paying overseas suppliers	Stablecoin direct to a wallet you control, held not converted	Skipping stage 5 is the only way to genuinely beat SWIFT
Running Shopify or WooCommerce	Compare stage 3 and 4 behaviour, not marketing copy	See the Shopify gateway comparison and the WooCommerce plugin comparison

The summary judgement: no gateway beats the chain, several add days to it, and the only route to zero added delay after confirmation is for the payment never to leave your control. Aurpay is non-custodial for that reason — funds arrive at your own wallet at a flat 0.8% per transaction, with no payout schedule and no minimum withdrawal. If you also need local currency in a bank on a fixed day, you are adding stage 5 yourself, so choose your off-ramp provider with the scrutiny you gave the gateway. Take these timings to your current provider and make them answer stage by stage. See whether “instant” survives the split.