Skip to main content

Payment Rails

What happens when the gap between payment intent and settlement finality collapses to zero?

The same Three Flows architecture governs how payments settle:

INTENT → ROUTE → INFRASTRUCTURE → SETTLE → FEEDBACK

The Shift

FromTo
5-day correspondent hopsSub-second finality
Hidden FX spreads (2-4%)Transparent on-chain fees
Card networks as gatekeepersProgrammable settlement
Human-initiated transactionsAgent-initiated transactions
Monthly billing cyclesReal-time micropayments

Settlement Layers

LayerTechnologySpeedCostBest For
TraditionalCorrespondent banks3-5 days1-3%Legacy B2B
Card networksVisa, Mastercard1-3 days1-2%Consumer checkout
Modern stablecoinEthereum~12 min$5-50High-value, low-frequency
Fast stablecoinSolana~400ms$0.01-0.25Consumer, DeFi
Machine-tempoSui~390ms + PTB batching<$0.01Agent commerce, DePIN

Agent Commerce Protocols

Three protocol families competing to become the default rails for agent transactions:

ProtocolSettlementWho
ACPCard rails via StripeOpenAI + Stripe
AP2Multi-rail (card + stablecoin)Google, with Sui as launch partner
x402Stablecoin on-chainCoinbase + Google + Ethereum Foundation

See Agent Commerce for the full standards war.

Platform Providers

ProviderRoleConnection
StripePayment processing, ACP co-author, Bridge acquisitionCEO on Meta board. Bridge received OCC national trust charter.
Coinbasex402 protocol, Base L2, crypto on/off-rampCommerce SDK for agent-native payments
ShopifyUCP co-developer with GoogleMerchant-side agent commerce

The ABCD Stack

Payment rails operate across the full ABCD stack:

LayerFunction in Payments
AIRoute optimization, fraud detection, agent intent
BlockchainSettlement, proof, immutable receipts
CryptoIncentive alignment, tokenized coordination
DePINPhysical infrastructure settlement (sensors, devices, energy)

Context