Skip to main content

Stripe's AWS for Money: How Bridge, Privy, and Tempo Form the Stablecoin Stack

· 11 min read
Dora Noda
Dora Noda
Software Engineer

When Stripe's crypto chief told CoinDesk on April 18, 2026 that the company wants to become "AWS for money," it wasn't a slogan — it was a confession. Stripe has been quietly assembling the most aggressive stablecoin stack in fintech: a $1.1 billion acquisition (Bridge), 75 million embedded wallets (Privy), and a purpose-built Layer 1 blockchain (Tempo) valued at $5 billion before its first full quarter of mainnet life.

The play is simple to state and brutal to execute. Stripe wants every stablecoin flow on the planet — merchant settlement, creator payouts, cross-border B2B, agent-to-agent commerce — to terminate on its rails without anyone noticing. Just like AWS, where developers don't pick "Amazon" so much as build on services that happen to run on it, Stripe is engineering a world where the next generation of money movement runs on Stripe by default.

Here's how the three-layer stack fits together, why it threatens Visa, PayPal, and even Circle simultaneously, and what could still go wrong.

The Three-Layer Stack: Bridge + Privy + Tempo​

Stripe's stablecoin strategy isn't one product. It's three complementary infrastructure layers that, taken together, span the entire lifecycle of a stablecoin payment.

Layer 1: Bridge — the issuance and on/off-ramp engine. Stripe closed the Bridge acquisition in February 2025 for $1.1 billion, the largest crypto M&A deal in history at the time. Bridge handles stablecoin issuance, custody, and the unglamorous plumbing of converting between fiat and digital dollars. By the end of 2025, Bridge volumes had more than quadrupled. In a quieter but strategically important move, Bridge won a bidding war to issue USDH, the native stablecoin of Hyperliquid's perp DEX — proof that Stripe's stablecoin infrastructure is now competitive at the protocol level, not just the merchant level.

Layer 2: Privy — the embedded wallet layer. Stripe announced the Privy acquisition in June 2025. Privy's calling card is invisibility: it powers more than 75 million wallets across over 1,000 teams, including OpenSea, without those users ever needing to manage seed phrases. By bolting Privy onto Bridge's rails, Stripe gives every Shopify merchant, every SaaS subscription product, and every consumer fintech app a wallet primitive they can deploy in days, not quarters.

Layer 3: Tempo — the merchant-optimized settlement chain. Tempo, jointly incubated with Paradigm, went live on mainnet in March 2026 after a three-and-a-half-month testnet phase. It's a Layer 1 designed exclusively for stablecoin payments — dedicated blockspace, predictable costs, instant settlement, and rich payment metadata baked into the protocol. Launch partners include Mastercard, UBS, Klarna, Visa, and DoorDash, which is using Tempo to settle merchant payouts across more than 40 countries. Tempo raised $500 million at a $5 billion valuation before mainnet.

Bridge moves the dollars in and out. Privy gives every developer a wallet. Tempo runs the settlement underneath. That's the AWS-for-money flywheel.

Why "AWS for Money" Is Different from "Crypto for Merchants"​

The framing matters. Plenty of fintechs have rolled out crypto features — accept-USDC checkboxes, BTC on/off-ramps, branded stablecoins. Almost all of them treat crypto as a feature added on top of fiat. Stripe is doing the opposite: treating fiat as a settlement option on top of stablecoin rails.

Read the data carefully. Stripe processed $1.9 trillion in payment volume in 2025, up 34% year over year. Across the broader market, stablecoins moved $9 trillion in adjusted payment activity between October 2024 and October 2025 — up 87% YoY, growing more than twice as fast as Stripe's already-blistering pace. Some Stripe customers report that 20% of their payment volume has already shifted to stablecoins, with transaction costs roughly cut in half compared to card networks.

If those curves continue, the dominant rail for online payments by 2030 isn't Visa or ACH — it's a stablecoin rail. Stripe is betting that the developer experience for that rail will be the deciding factor, and that whoever owns the developer experience owns the economics.

This is the AWS playbook. AWS didn't win because EC2 was cheaper than running your own server. It won because spinning up an EC2 instance took five minutes and a credit card. Stripe wants Tempo + Bridge + Privy to feel like the same thing for money: five minutes and a Stripe API key, and you have a global, programmable, low-cost dollar.

How Stripe's Strategy Compares to Visa, PayPal, and Apple​

Three competing visions are now racing to define how stablecoins get distributed at scale, and they barely overlap.

Visa is hedging. Visa's annualized stablecoin settlement volume reached $4.6 billion as of Q1 2026, up from a $3.5 billion run-rate in late 2025. That sounds large until you compare it to Visa's $14+ trillion in annual card volume. Visa is integrating stablecoins into existing card flows (Visa Direct, USDC settlement for issuers) rather than challenging the underlying rail. It's defensive. Crucially, Visa doesn't own a chain, an issuer, or a wallet — it has to partner for every layer Stripe builds in-house.

PayPal is consumer-first. PYUSD has expanded to 70 markets with a $4.3 billion supply, and PayPal CEO Alex Chriss has made it the centerpiece of the company's 2026 wallet strategy. But PayPal is optimizing for distribution to its 400 million existing consumers, not for merchant infrastructure. PYUSD is a coin in search of an ecosystem; Stripe is building the ecosystem in search of more coins.

Apple is rumored, closed, and slow. Reports of Apple Pay stablecoin integration have circulated for months, but Apple's pattern is closed-system: stablecoins inside the Apple wallet, settling between Apple's pre-approved partners. That's a powerful distribution channel for the iOS user base, but it's not infrastructure other developers can build on — which is exactly the gap Stripe is racing to fill before Apple commits.

The strategic gap should be obvious. Visa is partnering, PayPal is distributing, Apple is gating. Only Stripe is trying to be the substrate.

The Circle Tension and the Tempo Bet​

Stripe's three-layer stack carries one obvious internal contradiction: it competes with Circle while depending on Circle.

Circle's own platform, the Circle Payments Network (CPN) — and its Managed Payments service launched April 8, 2026 — is a direct rival. Both Stripe and Circle are pitching the same thing to banks and PSPs: an abstracted, fully managed stablecoin settlement layer. CPN handles the USDC mint/burn, payment orchestration, and compliance plumbing so partners interact only in fiat. Stripe wants to be the merchant-facing version of exactly that.

Yet USDC remains the dominant settlement asset for most of Bridge's enterprise flows, and Tempo has to support USDC in production to be credible. So Stripe is partnered with Circle on USDC issuance and competing with Circle on the network layer above USDC.

That tension resolves in one of three ways. Either Tempo scales fast enough that Stripe can route around Circle by promoting Bridge-issued stablecoins (USDH being the early test case). Or Circle locks in CPN distribution faster than Tempo can onboard merchants, forcing Stripe to pay Circle's settlement tax forever. Or — most likely — they coexist as parallel rails, each owning different segments of the market: Circle for institutional and bank flows, Stripe for merchants, developers, and AI agents.

The DoorDash partnership is the most important early signal here. DoorDash generated nearly $75 billion in local merchant sales last year, and chose to settle cross-border merchant payouts on Tempo rather than on existing rails. That's the proof point Stripe needs that a payments-native L1 outcompetes a general-purpose stablecoin network for real merchant volume.

What This Means for Crypto Infrastructure Builders​

If Stripe captures the "developer default" position for stablecoin payments, the implications cascade through every part of the crypto infrastructure stack.

For RPC and indexing providers, Tempo is now a chain you cannot ignore. It's not just another L1 — it's the L1 that sits underneath Mastercard, UBS, Klarna, DoorDash, and increasingly Visa. The indexing surface is unique: payment metadata, merchant identifiers, and compliance hooks are first-class protocol primitives, not bolted-on application data. Anyone who serves stablecoin-native dashboards, treasury tools, or B2B reconciliation systems will need Tempo coverage by Q4 2026.

For wallet and developer-tools startups, the Privy precedent matters. Stripe paid up to acquire embedded-wallet distribution, which means embedded-wallet distribution is the moat. Standalone wallet SDKs without distribution are now harder to monetize than they were 12 months ago.

For chains competing with Tempo, the message is harsher: a payments-only L1 with merchant distribution and a pre-integrated PSP is a different category from a general-purpose L1 hoping merchants show up. Solana, Polygon, and Base have stablecoin volume; Tempo has stablecoin volume with merchant intent baked into the metadata. That distinction will matter when AI agents start settling autonomously and need to verify that a payment was for a coffee, not a money-laundering layer.

BlockEden.xyz operates production-grade RPC and indexing infrastructure across 27+ blockchains, and we're tracking emerging stablecoin-native L1s like Tempo as they move from announcement to merchant-volume reality. Explore our API marketplace to build on rails designed for the next decade of programmable money.

The Three Risks That Could Break the Thesis​

The "AWS for money" pitch is elegant, but Stripe is making three big bets that could each go wrong.

Risk 1: Multi-vendor preference. Big merchants and banks have been burned by single-vendor lock-in before. They may explicitly want multi-rail setups: USDC on Solana, PYUSD on Ethereum, RLUSD on XRPL, and only some flows on Tempo. If that fragmentation persists, "AWS for money" becomes "one of several clouds for money," and Stripe loses the substrate position.

Risk 2: Regulatory whiplash. The GENIUS Act, MiCA, and the OCC's prudential rulemaking are all still in motion. A single bad ruling — particularly one that treats stablecoin issuers as systemically important banks — could pull Bridge's economics out from under it. Stripe is now exposed to stablecoin policy in a way it wasn't 18 months ago.

Risk 3: The Visa counter-attack. Visa has the distribution, the brand, and the regulatory relationships. If Visa decides to stop hedging and build its own stablecoin chain — or aggressively co-opt Tempo as a partner-of-convenience — Stripe's substrate ambition could be capped at "best fintech-native rail" rather than "default rail for everyone."

None of these are fatal. But they explain why Stripe is moving so fast: every additional merchant on Tempo, every developer on Privy, and every dollar on Bridge makes the next attack harder.

The Quiet Revolution​

The most interesting thing about Stripe's strategy isn't any single component — it's the framing. By calling itself "AWS for money," Stripe is signaling that it intends to disappear into the background, the way AWS disappeared into every consumer app you use. You don't think about the cloud powering Netflix. You won't think about the rails moving your DoorDash payout from Manila to São Paulo.

If Stripe wins, the average internet user will move dollars on stablecoins for the rest of their life and never know it. The merchants will save 50% on payment costs. The developers will ship in hours. And the chain underneath, the wallet on top, and the issuer in the middle will all be Stripe.

That's a very large bet. It's also, three-layers-deep, already half-built.

Sources:

Share on Twitter