Tempo: Payment Lanes

Stripe and Paradigm's payments-focused chain dedicates blockspace to payment transactions, ensuring sub-second finality even under heavy load.

TempoStripe / Paradigm · Payments-focused stablecoin L1 · Simplex BFTA-302 · TEMPO SECTION CUTCOMPLIANCE DEPTH →L5 APPLICATIONWallets, dApps, UIL4 MIDDLEWAREAPIs, bridges, oraclesL3 EXECUTIONSmart contracts, VML2 CONSENSUSBlock production, finalityL1 NETWORKP2P transport, gossipSTATE CHANGESimplex BFTInvited validatorsT6 · S2Payment LanesDedicated payment blocksT3 · S6TIP-403 Policy RegistryWhitelist/blacklist ACLsT1 · S7Enshrined DEXStablecoin AMMT2 · S4Stripe KYC/AMLIdentity verificationT6 · S2ChainalysisTransaction monitoring— · S4–S7MPPMachine Payments ProtocoT5 · S5Commerce RuntimeAI agents, merchant SDK— · S1STRIPE / PARADIGMIntentIdentityCross-ChainAccountTokenReservesGate (pre-condition)Monitor (concurrent)Obligation (post-settlement)Solid = code-enforcedDashed = policy-enforced

Payment Lane Architecture

50%
PAYMENT LANE
<1s
Guaranteed
Reserved blockspace for payment txns
GENERAL COMPUTE
1-2s
Congestion dependent
Shared blockspace for general txns

TIP-403 Policy Registry

DISABLED
Transaction Results
Submit a payment to see lane performance
TIP-403 Policy Registry: Issuers can register blacklist rules at the protocol level. All transactions are checked against active policies before confirmation, regardless of lane.