Why blockchain payments still need rails

The pitch that "blockchain payments" replace traditional rails has aged unevenly. What has aged well is the more careful claim that blockchain settlement can sit inside a broader payment architecture, replacing some steps while requiring the others.

Written October 2024 from a review of production integrations.

What blockchain settlement does well

• Final, non-reversible settlement in minutes rather than days.
• Programmable execution — conditional payments, escrow, streaming.
• Cost efficiency for high-value transfers.
• Interoperability across institutional boundaries.

What it doesn't do

• On-ramp and off-ramp. Getting fiat in and out is where most of the operational cost lives.
• Merchant discovery and acceptance. A stablecoin is settlement; the merchant still needs a checkout flow, a POS integration, a customer relationship.
• Compliance and identity. Travel rule, KYC/KYB, sanctions screening — all off-chain, all required.
• Dispute resolution. No chargeback mechanism; disputes need a designed process.
• Consumer protection. Reversibility and consumer rights are absent from the base layer; they have to be added at higher layers.

The architecture that works

• Application layer: merchant checkout, wallet, invoice.
• Compliance layer: KYC, screening, travel rule.
• Payment initiation layer: which rail, which token, which amount.
• Settlement layer: on-chain finalisation.
• Reconciliation layer: matching on-chain events with off-chain business records.

Blockchain settlement replaces the settlement layer. The rest of the stack still needs to exist, and building it is where the actual product work happens.

What this means for a merchant

Choosing to accept blockchain-based payments is not choosing a rail. It's choosing to extend your existing payments stack with one more settlement option, with its own operational and compliance implications. Merchants who understand this ship stable products; merchants who don't ship things that break.