Skip to main content

18 posts tagged with "Payment Infrastructure"

Payment systems and infrastructure

View all tags

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:

Lightspark and Visa Bring Self-Custodial Bitcoin and Stablecoin Debit Cards to 100+ Countries

· 11 min read
Dora Noda
Dora Noda
Software Engineer

For most of the last decade, "spending crypto in the real world" meant handing your coins to an exchange, waiting for them to issue you a Visa or Mastercard, and accepting that the spending balance was no longer yours in any meaningful sense. The Coinbase Card, the Crypto.com card, the BVNK-powered programs — all of them solved the merchant-acceptance problem by re-introducing a custodian.

That model just cracked.

On April 29, 2026, Lightspark and Visa announced a partnership to issue stablecoin- and Bitcoin-backed Visa debit cards across 100+ countries, plugged directly into Lightspark's Grid platform. The same week, Lightspark's Grid Global Accounts launched at Bitcoin 2026 Las Vegas, and a new wave of issuers — including a self-custodial multi-asset wallet called Avvio — began onboarding to the rails. The pitch is blunt: a Visa swipe at any of 175 million merchants, funded by a balance the user actually holds the keys to.

If the architecture sticks, this is the first global Visa product where "your card, your coins" stops being a slogan and starts being a default.

What Lightspark and Visa Actually Shipped​

The headline number is 100+ countries, but the more important detail is what Grid is. Lightspark Grid is an API platform that lets any fintech, neobank, or app behave like a global financial institution without becoming one. Through a single integration, a partner can offer:

  • Branded dollar accounts backed by stablecoins
  • Visa debit cards, virtual and physical, that swipe at 175 million merchants in 33 countries at launch
  • Real-time payouts to bank accounts and mobile money providers in 65+ countries, across 14,000 banks
  • Instant Bitcoin/fiat conversion routed over Lightning or the new Spark protocol
  • Stablecoin support including USDC on Solana, Base, and Spark

According to Lightspark, the network as configured already reaches roughly 5.6 billion people across an aggregated $93 trillion in GDP. The first phase rolls out in the United States and Europe, with planned expansion into Asia Pacific, Africa, and the Middle East later in 2026.

For Visa, this is a continuation of a clear 2025–2026 strategy. The card network now captures more than 90% of on-chain card volume through partnerships with crypto-native infrastructure providers, and its on-chain stablecoin settlement for issuers reached an estimated $3.5 billion annual run rate by late 2025. Lightspark gives Visa something it didn't have before: a partner whose entire stack is built around Bitcoin and Lightning settlement, not just stablecoins.

The Avvio Wedge: Self-Custody as a Product, Not a Compromise​

The Lightspark–Visa announcement on its own would already be a big payments story. What pushes it into "architectural shift" territory is the type of issuer now showing up on Grid.

Avvio is one of the first card-issuing wallets to launch on the Lightspark+Visa stack as an explicitly self-custodial, multi-asset product. The pitch is unusually direct for a consumer payments app: real USD and EUR accounts, payouts into 120 countries, and a spending balance collateralized by self-custodial Bitcoin, gold, and tokenized-stock exposure. The wallet keys never leave the user's device, and the Visa rail sits on top.

This matters because every prior attempt at a "real" crypto debit card has eventually hit one of two walls:

  1. Custodial issuers (Coinbase Card, Crypto.com Card, the original BVNK pilots) had to take ownership of user funds to authorize merchant pulls in real time. Convenient — but the user is back to trusting an intermediary, with all the failure modes that implies.
  2. Pseudo-self-custodial wrappers typically required moving funds into a centralized intermediate balance the moment you swiped. Self-custodial in marketing copy, custodial at the moment of truth.

A Lightspark+Visa+Avvio-style stack threads the needle by separating roles. The user holds the keys. The wallet authorizes a draw against a verified balance. Lightspark Grid handles the conversion and settlement to Visa in real time over Lightning or Spark. The merchant gets dollars. Visa gets a clearing event. Nobody in the chain ever needed sole custody of the asset.

That is a meaningfully different security model from anything that has shipped at this scale before.

How This Stacks Up Against BVNK, MoonPay, and Coinbase​

To understand how big a shift this is, it helps to look at where the other three contenders sit in May 2026:

  • BVNK + Visa Direct (2025–2026): BVNK's stablecoin payments infrastructure powered Visa Direct payouts to issuers in select markets, handling roughly $30 billion in annual stablecoin volume. The model was issuer-locked and operated through custodied balances. In a notable plot twist, Mastercard acquired BVNK for around $1.8 billion in March 2026, effectively migrating that infrastructure off Visa's roadmap.
  • MoonPay MoonAgents Card (May 1, 2026): MoonPay launched a stablecoin debit card aimed at AI agents and consumers, on the Mastercard network via Monavate. It links a self-custodial wallet to a virtual Mastercard, with revocable approvals and no transfer of custody at issuance. It is genuinely closer to self-custodial than older custodial-card products, but it lives on Mastercard rails and on a single chain.
  • Coinbase Cards and Base App: Coinbase still operates one of the most widely held crypto cards in the U.S., funded from the centralized exchange wallet. The Base App, launched as a self-custodial consumer wallet, points in the same direction as Avvio — but Coinbase has not yet plugged Base directly into a Visa-issuing path that bypasses the exchange custody layer.

Stack those four side by side and a clear pattern emerges. Mastercard's bet is on acquiring custodial stablecoin infrastructure (BVNK) and licensing it to AI-agent and fintech use cases (MoonAgents). Visa's bet, via Lightspark, is on building a programmable global rail where the issuer can be self-custodial by default. They are not the same architecture, and within 12–18 months one of them is going to start to look obviously correct.

The Numbers Behind the Inflection​

The market context makes the timing less surprising. The total stablecoin market capitalization crossed $317 billion in early 2026, with USDT at roughly $187 billion and USDC at around $75.7 billion — and USDC growing 73% year over year, faster than USDT for the second consecutive year. Crypto card spending hit an $18 billion annualized run rate by January 2026 as everyday payments shifted on-chain. Some analysts now project stablecoins to settle more than $50 trillion in transactions during 2026, a figure that would put on-chain dollar transfers comfortably ahead of the legacy card networks on raw transfer volume.

What was missing from those numbers was a credible self-custodial spending experience at global scale. Card programs were either niche, custodial, or both. The Lightspark+Visa launch is the first piece of infrastructure that lets that $317 billion of dollar-pegged tokens, plus Bitcoin, plus tokenized assets like gold and equities, become spendable in 100+ countries without forcing the user to hand over the keys.

It also reframes the agent economy story. MoonPay positioned MoonAgents around AI agents that need to spend. Lightspark and Avvio are quietly building the same capability for humans first, with agent-callable controls bolted on top via Grid's "agent permissions" layer. Both groups are converging on the same insight: the spending experience and the custody decision should be decoupled.

What This Means for Web3 Infrastructure​

For builders sitting one layer below the card network, the Lightspark+Visa launch reshapes demand in three concrete ways:

1. Continuous balance attestation becomes the new hot path. A self-custodial card has to verify "the user has X dollars of spendable balance" in milliseconds, every swipe, often across multiple chains and assets. That is not a one-shot RPC pattern. It looks much more like a high-QPS read workload — eth_call, getBalance, oracle lookups, and Lightning channel state — sustained 24/7 against millions of wallets. RPC providers are about to feel this.

2. Multi-asset price feeds move from analytics to settlement-critical. When the spending balance is collateralized by BTC, gold, USDC, and tokenized stocks at once, the price feed that values that basket is no longer a UX detail. It is part of the authorization flow. Latency, freshness guarantees, and feed redundancy become payments-grade requirements rather than dashboard features.

3. Lightning/Spark settlement attestation becomes a queryable surface. For Bitcoin-backed swipes, the issuer needs to prove that a Lightning payment cleared, that a Spark transfer is finalized, and that a USDC swap settled — all in time to authorize the Visa transaction. Every one of those is a new RPC pattern that today's Ethereum-shaped infrastructure was not designed for.

The shape of all this is different from how centralized exchange wallets generated load. Exchange wallets concentrated traffic at a few endpoints. Self-custodial spending wallets fan out load across millions of independently keyed addresses, each polling for balances, each requiring its own authorization checks, each potentially live across multiple chains.

What to Watch Next​

Three open questions will decide whether this becomes the new template or a well-funded experiment:

  • Does MiCA and the GENIUS Act compliance overhead force self-custodial issuers like Avvio back behind a custodian for licensing reasons in Europe and the U.S.? The technical architecture is ready. The regulatory architecture for self-custodial card programs is genuinely unclear.
  • Does Mastercard counter with a self-custodial Visa-style stack of its own, or double down on the BVNK-MoonPay custodial agent thesis? The two networks are now visibly diverging on architecture for the first time in years.
  • Do other issuers — BVNK successors, Bridge, regulated neobanks — follow Avvio onto Grid, or do they wait for the regulatory dust to settle? The first 90 days of issuer onboarding will be telling.

Either way, the era where "spending Bitcoin" required surrendering Bitcoin is ending. The infrastructure to keep the keys and swipe the card now exists, in 100+ countries, on the world's largest card network.

BlockEden.xyz provides enterprise-grade RPC and indexing infrastructure for the chains powering this new self-custodial payments stack — including Solana, Base, and the Bitcoin-adjacent Lightning ecosystem. If you're building wallets, card programs, or agent-callable financial services on top of this architecture, explore our API marketplace to ship on rails designed for the workload.

Sources​

OKX's Agent Payments Protocol Just Made the x402 vs AP2 vs TAP War a Three-Way Race

· 11 min read
Dora Noda
Dora Noda
Software Engineer

On April 29, 2026, OKX shipped the broadest day-one coalition the agent-payments standards war has ever seen — and quietly redefined what the war is actually about.

While Coinbase's x402, Google's AP2, Visa's TAP, and PayPal's Agent Ready spent the last 90 days fighting over who owns the moment an AI agent moves money, OKX's Agent Payments Protocol (APP) walked onto the field with a bigger thesis: payment is the easy part. The hard parts — quoting, negotiating, escrowing, metering, settling, and disputing — are the bottleneck. And on day one, AWS, Alibaba Cloud, the Ethereum Foundation, Solana, Sui, Aptos, Base, Optimism, Paxos, Uniswap, MoonPay, Sahara AI, Nansen, and QuickNode all signed on to say so.

That coalition breadth is the news. Every previous "agent commerce standard" launched with one company's logo on it. APP launched with the spec sheet of a neutral consortium.

The Stablecoin Orchestration Layer Race: Conduit, Circle, and the $200B Cross-Chain Question

· 12 min read
Dora Noda
Dora Noda
Software Engineer

When Circle quietly flipped on its native USDC Bridge across seventeen networks in mid-April 2026, it did more than ship a feature. It detonated a market structure question that the stablecoin industry has been dancing around for two years: who owns the customer when value moves between chains?

The answer, increasingly, is whoever owns the orchestration layer. And that fight is now wide open.

Conduit, the Boston-based stablecoin payments startup that closed a $36M Series A led by Dragonfly Capital and Altos Ventures last year, has spent the intervening months turning a single thesis into a product roadmap: developers do not want to choose between Circle's burn-and-mint, LayerZero's omnichain messaging, Wormhole's general-purpose attestation, or DEX-aggregator routing. They want one API call that picks the right rail and gets the money there. The company now processes more than $10 billion in annualized transaction volume across nine countries and 5,000 merchants — a base it built before Circle, Stripe, and Mastercard each declared the stablecoin orchestration layer their next strategic priority.

That collision — between Conduit's developer-API simplicity thesis and the vertically integrated stacks now racing to subsume it — is the most interesting structural question in stablecoin infrastructure today.

The Three-Tier Stack That Wasn't Supposed to Exist​

For most of 2024, the stablecoin world had two layers: issuers (Circle, Tether, Paxos) and bridges (LayerZero, Wormhole, Axelar, Stargate). The bridge layer competed on chain coverage, security model, and fee.

By early 2026, a third tier had crystallized in between: the orchestration layer. Eco Routes, Across, Relay, LiFi — and Conduit, with a payments-flavored variant — sit above the rails and route across them. A developer integrating one orchestration provider inherits CCTP, Hyperlane, and LayerZero simultaneously, without writing rail-specific code or maintaining gas-on-destination logic for every supported chain.

The architectural rationale is straightforward. No single rail is optimal across every chain pair. Circle's CCTP delivers the cleanest experience for native USDC moving between EVM chains, but it does not handle USDT, EURC issued by other parties, or non-EVM destinations consistently. LayerZero's OFT pattern offers the broadest chain coverage and supports any token, but introduces messaging-layer trust assumptions. DEX-aggregator routing through Jupiter or 1inch handles cross-chain stablecoin movement via swaps, picking up slippage at every hop. The orchestration layer's job is to make those tradeoffs invisible to the developer.

Conduit's pitch — "deposit USDC on Ethereum, receive USDC on Solana, Base, Arbitrum, or Polygon without users touching bridge contracts" — is a payments-shaped expression of the same logic. Where general orchestrators target DeFi flows, Conduit targets payouts, payroll, and merchant settlement, the use cases where the user is a treasury operator or a fintech platform, not a yield farmer.

Why Circle Just Made This Harder​

The April 2026 USDC Bridge launch is the development most Conduit competitors did not adequately price in. Until that point, Circle's CCTP existed as a developer protocol, not a consumer-facing product. To move USDC across chains using CCTP, an application or wallet had to integrate it, handle the burn-mint flow, manage attestations, and pay destination-chain gas. Most users got their cross-chain USDC through third-party bridges that wrapped CCTP or used different infrastructure entirely.

USDC Bridge collapses that. A user connects a wallet, picks source and destination chains, sees the fee upfront, watches a live tracker, and lands native USDC on the other side with destination-chain gas handled automatically. It supports Ethereum, Arbitrum, Base, Optimism, Polygon PoS, Avalanche, Sei, and Monad at launch, with more coming. Circle now competes directly with the orchestration layer for routine consumer-grade USDC transfers, while CCTP V1 sunsets on July 31, 2026 — a forced migration that incentivizes developers to revisit their bridging stack anyway.

The market data hints at how much volume is in play. LayerZero processed roughly $4.965 billion in cross-chain transactions in a recent thirty-day window, accounting for nearly half of total cross-chain volume; CCTP came second at $3.8 billion. Wormhole has shipped over $60 billion in lifetime volume. If even a quarter of that flow rotates toward Circle's first-party bridge, every orchestration provider — Conduit included — will need to articulate why developers should pay for an abstraction that Circle is now offering for free at the source.

The Dragonfly Thesis: Stablecoins Are a Stack, Not a Token​

Dragonfly's check into Conduit makes more sense in the context of the firm's broader portfolio than in isolation. The fourth fund — $650 million, closed February 2026 — is heavily concentrated in stablecoin and payments infrastructure. Plasma, the Bitfinex-backed Layer 1 that launched mainnet beta in September 2025 with $1 billion in pre-launch deposits and zero-fee USDT transfers via authorization-based logic, sits in the chain layer. Stable, the separate Bitfinex-backed L1 that uses USDT as gas token, occupies an adjacent niche. Rain, which raised $58M in August 2025 for emerging-market payroll on stablecoin rails, takes the application slot.

The firm's bet is not that any single layer wins; it is that 2026 produces a coherent stack — purpose-built stablecoin chains at the bottom, orchestration in the middle, payments and consumer apps at the top — and that early ownership of every layer pays out regardless of which chain or which application captures the largest share. Conduit fits that bet as the orchestration entry, the company that does for cross-chain stablecoin movement what Stripe did for card payments: turn a fragmented, infrastructure-heavy problem into one API call.

Rob Hadick, the Dragonfly partner who joined Conduit's board, has been one of the loudest voices in the firm on the thesis that compliance-native stablecoin infrastructure is the multi-decade trade. His presence on the board signals that Dragonfly intends to use Conduit as the connective tissue between its chain investments and its application investments.

The Acquisition Multiples Are Already Setting the Comp Set​

The price tags on adjacent stablecoin infrastructure deals in the past eighteen months frame the stakes. Stripe paid $1.1 billion for Bridge.xyz in February 2025 to acquire stablecoin orchestration and issuance, then shipped that capability as Bridge APIs and Stripe stablecoin financial accounts in 2026 — covering on/off-ramp, wallet-as-a-service, and issuer-grade minting. Mastercard followed in March 2026 with the largest stablecoin acquisition to date: $1.5 billion plus a $300 million earnout for BVNK, a London-based platform that processed over $30 billion in stablecoin payments in 2025.

The Mastercard deal is illuminating because Mastercard could have built it. The company has a global merchant network, regulatory relationships in 200+ markets, and the engineering resources to ship an orchestration layer in twelve months. It chose to acquire instead, paying roughly six times BVNK's transaction volume, because the talent and the regulatory licenses were worth more than the time. That pricing implies Conduit, currently at a tenth of BVNK's volume but with similar regulatory positioning, sits in a band that strategic acquirers will find affordable as orchestration-layer consolidation accelerates.

The exit ladder for stablecoin infrastructure has therefore inverted. In 2023, the assumption was that infrastructure companies would IPO into a maturing market. By 2026, the realistic exit is acquisition by a card network, a fintech platform, or an issuer trying to vertically integrate. Bridge went to Stripe. BVNK went to Mastercard. The remaining independent orchestration providers are now valued against that ceiling.

What Conduit Has That Circle Does Not​

The strongest case for Conduit's continued independence is the part of the stack Circle is structurally unable to own. Circle's USDC Bridge moves USDC. It does not move USDT, USDP, EURC issued by third parties, RLUSD, USDe, or any of the dozens of yield-bearing wrapped variants — and it cannot, because Circle does not control those tokens' minting infrastructure. The current stablecoin supply sits at $224.9 billion, of which USDC is roughly 24%. The other 76% — Tether's USDT dominance, the GENIUS Act-spawned bank-issued stablecoins, the regional EUR and SGD stablecoins — flows through paths Circle cannot service.

A general orchestration layer that handles USDC, USDT, EURC, and emerging-market local-currency stablecoins through a single integration captures a meaningfully larger surface area than any first-party bridge. Conduit's specific edge is the fiat layer attached to the crypto layer: 14 fiat currencies and on/off-ramp coverage in the United States, Mexico, Brazil, Nigeria, and Kenya. A US fintech that wants to pay a Brazilian contractor in BRL using USDC as the settlement medium can use Conduit's API and never touch a bridge contract, never source destination-chain gas, and never integrate a separate FX provider. That composite — orchestration plus fiat rails plus regulatory coverage — is what made Circle, DCG, and Commerce Ventures all sign the same Series A.

The 2026 Stablecoin Orchestration Bracket​

Five distinct models now compete for the stablecoin orchestration role, and they are differentiating along axes that did not exist in 2024:

Issuer-vertical (Circle USDC Bridge, Tether's USDT0 on Plasma). Best UX for the issuer's own token, free at the point of use, locked to the issuer's chain coverage list.

Generalized rails (LayerZero, Wormhole, Axelar, Hyperlane). Broadest chain coverage, multi-token, but expose developers to messaging-layer security and require orchestration on top to be developer-friendly.

Pure orchestration (Eco Routes, Across, Relay, LiFi). Route across multiple rails based on price, speed, and security; primarily DeFi-flow shaped.

Payments-shaped orchestration (Conduit, Bridge inside Stripe, BVNK inside Mastercard). Combine cross-chain stablecoin movement with fiat on/off-ramp, regulatory licensing, and merchant settlement primitives.

Purpose-built stablecoin chains (Plasma, Stable, Tempo). Vertically integrate the chain layer with the stablecoin layer, eliminating cross-chain movement for flows that originate and terminate on the chain itself.

The five categories are not mutually exclusive — Conduit can route through Circle's USDC Bridge for USDC flows and through LayerZero for USDT flows on the same API call — but the strategic positioning matters for who captures the developer relationship. Whoever owns that relationship owns the routing decision, which owns the economics.

The Next Eighteen Months​

Three signals will tell us whether Conduit's bet on the orchestration layer is structurally durable or whether the issuer-vertical and acquired-by-platform paths consume the category.

First, watch USDC Bridge volume share. If Circle captures 40% or more of cross-chain USDC volume within six months, the economic value of an independent USDC orchestration layer compresses meaningfully, and Conduit's defensibility narrows to non-USDC stablecoins and fiat-attached use cases.

Second, watch the next strategic acquisition in the space. Coinbase, PayPal, Visa, JPMorgan, and Worldpay all have public or rumored stablecoin orchestration ambitions. Any one of them moving on a Conduit-shaped target at a $500M+ valuation re-rates the category and forces remaining independents to either run faster or position for sale.

Third, watch whether GENIUS Act implementation produces a fragmentation of bank-issued stablecoins. If a dozen US banks each issue their own stablecoin under OCC trust charter — and Treasury Department and Federal Reserve guidance suggest several are queued for 2026 launches — the case for an orchestration layer that abstracts which bank-stablecoin a payment uses becomes existentially important, because no developer wants to integrate twelve regional stablecoin APIs.

Conduit's $36M is, in the scheme of the stablecoin infrastructure capital that has flowed in 2025-2026, a modest check. But the position is not modest. The company is one of perhaps four serious independent orchestration providers in a category that the largest payment networks in the world have just declared strategic. The question for the next eighteen months is whether that position translates into the $1B-$2B exit valuations that Bridge and BVNK already established as the floor — or whether Circle's decision to stop being a protocol and start being a product leaves the orchestration layer to be slowly absorbed from above.

The race has started. The starting gun was Circle's bridge.

BlockEden.xyz provides enterprise-grade RPC and indexing infrastructure across 27+ chains, including Ethereum, Solana, Base, Arbitrum, Polygon, and Avalanche — the same networks Conduit and the broader stablecoin orchestration layer route across. Explore our API marketplace to build cross-chain payment flows on infrastructure designed for institutional reliability.

Sources​

MoonPay's Open Wallet Standard: Why the Agent Economy Just Got Its First Real Wallet Layer

· 13 min read
Dora Noda
Dora Noda
Software Engineer

When MoonPay open-sourced its Open Wallet Standard on March 23, 2026, it did something the rest of the agent-economy stack had quietly avoided: it admitted that AI agents need a wallet purpose-built for machines, not a sandboxed copy of MetaMask. The launch came with backing from PayPal, Circle, the Ethereum Foundation, the Solana Foundation, Ripple, OKX, Polygon, Sui, Base, Arbitrum, LayerZero, and roughly a dozen other organizations spanning every major chain. Within two months of launching MoonPay Agents in February, the company had pulled together what looks more like an industry consortium than a product release.

The thesis is simple and uncomfortable for incumbents: the wallet UX that took crypto a decade to refine — seed phrases, hardware confirmations, per-transaction approvals, browser extensions — was designed for humans who can think about risk. None of those primitives translate cleanly to a process running inside an LLM context window, where any data can leak into a prompt, a log line, or a tool call. If the next trillion dollars of crypto volume comes from autonomous agents transacting on behalf of users, the wallet layer needs a hard reset.

Western Union Picks Solana Over SWIFT: Inside the USDPT Stablecoin Pivot Reshaping the $905B Remittance Map

· 14 min read
Dora Noda
Dora Noda
Software Engineer

A 174-year-old company that helped invent the wire transfer just told the wire transfer it is finished. On April 24, 2026, Western Union CEO Devin McGranahan stood on a Q1 earnings call and confirmed what had been telegraphed for months: USDPT — a U.S. dollar stablecoin built on Solana, issued by Anchorage Digital Bank — launches in May. The company that has run on SWIFT and correspondent banking since the era of dial telegraphy is now choosing a public blockchain to settle with its own agents.

Rakuten's $23B Loyalty-to-XRP Bridge: How Japan Just Leapfrogged Every Web3 Rewards Experiment

· 9 min read
Dora Noda
Dora Noda
Software Engineer

On April 15, 2026, a quiet line in a Rakuten Wallet press release did what five years of Web3 loyalty experiments could not: it handed 44 million Japanese consumers a working bridge from traditional points to a public blockchain. With a single listing, Rakuten converted roughly 3 trillion yen — about $23 billion — of loyalty points into XRP-convertible value, and plugged the asset directly into 5 million merchant locations across Japan via Rakuten Pay.

To put that in perspective: the entire U.S. spot XRP ETF complex holds around $1 billion in assets. Rakuten just opened a consumer-facing utility pool more than 20 times larger — and, unlike an ETF, every yen of it can actually buy a sandwich at 7-Eleven.

Circle's $0.000001 USDC Nanopayments: The Invisible Rail Powering the Robot Economy

· 12 min read
Dora Noda
Dora Noda
Software Engineer

A robot dog walks up to a charging station, plugs itself in, and pays for electricity. No human swipes a card. No merchant account is touched. The entire transaction costs less than the kilowatt it buys.

This is not a concept video. In February 2026, OpenMind's robot dog "Bits" did exactly that using Circle's new nanopayments rail — settling USDC transfers as small as $0.000001 with zero gas fees to the developer. On March 3, 2026, Circle pushed that capability to public testnet, making it the first stablecoin infrastructure genuinely engineered for the economics of machines.

For a decade, "micropayments" has been the blockchain industry's most over-promised and under-delivered use case. Circle Nanopayments is the strongest evidence yet that the math has finally closed.

Why Sub-Cent Transfers Broke Every Existing Rail​

Talk to a payments engineer about micropayments and they will sigh. The dream — pay-per-article, pay-per-API-call, pay-per-second-of-streaming — has collided with a simple truth: fees eat the payload.

Visa's effective floor on card transactions sits around 1.4 cents after interchange and processing. PayPal's minimum is closer to 5 cents. Stripe's standard rate of 2.9% plus 30 cents makes anything below roughly $5 economically pointless. These networks were designed to move dollars, not fractions of pennies.

Blockchain was supposed to fix this. It mostly did not.

  • Ethereum mainnet gas, even at post-Dencun lows, rarely drops below a few cents per transfer — orders of magnitude more than the payload in any real micropayment.
  • Solana gets close with sub-cent fees and sub-400ms finality, but a machine making a million calls a day still pays meaningful overhead, and gas volatility breaks budgeting.
  • Lightning Network can do sub-cent Bitcoin payments, but requires dedicated liquidity in channels and has never solved the UX for autonomous agents.
  • Stripe's x402 HTTP payment protocol, while elegant, still rides underlying chain economics — its $28,000 daily on-chain volume as of March 2026 shows demand has not materialized at scale.

The missing piece was a payments primitive where the fee structure is not proportional to the payload. Circle's answer is brutally simple: aggregate everything off-chain, settle in batches, and have Circle itself absorb the on-chain cost.

What Circle Actually Built​

Circle Nanopayments enables USDC transfers as small as $0.000001 — one ten-thousandth of a cent — with zero gas fees passed to the developer. The mechanism is not new cryptography. It is disciplined engineering:

  • Off-chain aggregation: Thousands of micro-transfers are accumulated in a signed ledger off-chain.
  • Delayed, batched settlement: Those aggregated balances are settled on-chain in a single transaction at intervals.
  • Circle-subsidized gas: On-chain settlement fees are paid by Circle at the batch layer, not the developer or the machine making the transfer.

The architectural trick is recognizing that machine-to-machine flows do not need instant finality for every single payment. A robot charging its battery does not need a six-confirmation settlement for a $0.04 electrical bill before it unplugs. It needs a signed receipt, a revocation-resistant ledger entry, and a mechanism that guarantees eventual settlement. That is exactly what batching provides.

As of February 2026, Circle supports Nanopayments on testnet across Arbitrum, Arc, Avalanche, Base, Ethereum, HyperEVM, Optimism, Polygon PoS, Sei, Sonic, Unichain, and World Chain — a 12-chain footprint that matches USDC's native issuance and leaves competitors dealing with a bridged liquidity problem.

The Robot Dog That Bought Its Own Electricity​

The most compelling demo for the new rail came from Circle's partnership with OpenMind, a robotics software firm building OM1, a decentralized operating system for autonomous machines.

In February 2026, OpenMind's quadruped robot "Bits" executed a closed-loop autonomous workflow:

  1. Internal sensors detected a low battery.
  2. Bits navigated to the nearest charging station.
  3. The station advertised a per-kilowatt rate via the x402 protocol.
  4. Bits plugged in, initiated a USDC nanopayment stream, and charged.
  5. Payment was acknowledged near-instantly; actual on-chain settlement happened later via Circle's batch layer.

No human authorized the transaction. No merchant account was involved. No card network fee ate the margin. The robot held its own USDC wallet, authenticated via x402, and paid exactly what it owed — down to fractions of a cent per watt-hour.

This is the kind of loop that the machine economy has been promising for years. Circle's own blog framed it as the "core primitive for agentic economic activity," and that is not marketing language. Before this, every robot-payment demo had to hand-wave the settlement layer or lean on a prepaid voucher system. Nanopayments collapses the gap between autonomous decision-making and autonomous settlement.

Where This Fits in the 2026 Agent Stack​

Circle is not building nanopayments in isolation. The surrounding infrastructure is unusually dense for a market still years from mainstream penetration:

  • x402 protocol (Coinbase-led, joined Linux Foundation April 2, 2026 with backing from Stripe, Cloudflare, AWS, American Express, Ant International, Visa, and Microsoft) — the HTTP-native payment standard that lets agents pay for API calls using blockchain rails.
  • Stripe + Tempo's Machine Payments Protocol (MPP) — a competing agent-first standard launched March 2026, co-developed by Stripe and Paradigm-backed Tempo, also built on HTTP 402 semantics.
  • Coinbase Agentic Wallet — a "wallet as callable service" architecture where agents never hold private keys; wallet actions are invoked through MCP tool calls.
  • BNB Chain BAP-578 — the proposed token standard for treating AI agents themselves as on-chain assets.

Circle Nanopayments sits below all of these as the money layer. x402 and MPP are how an agent signals "I want to pay." Agentic Wallet is who signs the transaction. BAP-578 is what an agent is as an asset. Nanopayments is what actually moves the money at a price per transaction that makes the math work.

Notably, Circle's rail is the only one among these that has squarely solved the per-transaction fee problem rather than deferring it. x402 today runs mostly on Solana or Base at native gas rates; it inherits whatever chain economics its users pick. Circle batches the problem away at the issuer layer.

The Numbers Behind the Machine Economy Bet​

Why is Circle investing engineering effort in a rail whose volume may be tiny for years? Because the addressable market is structurally different from human commerce.

  • The DePIN sector, the closest public proxy for machine-economy activity, sat at roughly $9–10 billion in tracked market cap in early 2026, with some industry forecasts projecting scenarios from $50 billion to $800 billion by the end of the decade depending on adoption pace.
  • Helium's IoT network runs over 900,000 active hotspots, each of which is a potential endpoint for sub-cent machine payments.
  • OpenMind-style autonomous robotics are moving from research labs into warehouses, last-mile delivery, and industrial inspection.
  • Every one of Anthropic's, OpenAI's, and Google's agent frameworks is converging on HTTP-402-style "pay-per-call" economics.

If an AI agent makes 10,000 API calls at $0.0001 each, that is $1 in aggregate value — but 10,000 transactions. On Ethereum, Solana, or any current L1, the gas alone dwarfs the payload. On Circle Nanopayments, the developer pays zero. That delta is not a feature; it is a market-creation event.

Tether has already shown stablecoins can compete with Visa on volume — USDT processed over $10 trillion in 2024 transactions against Visa's $16 trillion. But that volume is human-scale, merchant-scale, and remittance-scale. The nanopayment tier is a different universe: machine-scale, API-scale, per-kilowatt-hour-scale. It is the volume Visa cannot physically serve.

The Moat Is Regulatory, Not Just Technical​

Batched settlement is not a novel idea. Stripe, PayPal, and every ACH processor have batched payments for decades. What makes Circle's version defensible is the combination with USDC's regulatory footprint.

Under the GENIUS Act's "payment stablecoin" classification, USDC has a clearer compliance path than competing micropayment rails. That matters when an agent is paying a real merchant, a real utility, or a real cloud provider — parties who cannot accept funds that might later be deemed unregistered securities or unlicensed money transmission. Lightning-native USDC exists, but fragmentation between USDC variants on different L1s and L2s has kept institutional issuance narrow.

Circle's positioning advantage:

  1. USDC is issued by a US-regulated entity with audited reserves.
  2. Nanopayments batches settle on public chains, preserving auditability and transparency for compliance.
  3. The 12-chain testnet footprint means a developer does not have to pick a chain to pick Circle's rail.
  4. Circle already has integrations with Visa, Stripe, and Coinbase — the three companies most likely to distribute agent payment rails to mainstream merchants.

Competing rails — Lightning USDT, Solana Pay, chain-native micropayment schemes — all solve the fee math, but none assemble the full regulatory + distribution + multi-chain stack that Circle is shipping.

What Still Has to Go Right​

The testnet launch is not a finish line. Several things have to resolve before nanopayments becomes the default machine-economy rail:

  • Mainnet migration: Circle has not publicly committed to a mainnet date. The on-chain settlement mechanics still need production-grade operational maturity.
  • Real demand: CoinDesk reported that x402 itself processes only about $28,000 in daily on-chain volume, much of it test traffic. Agent-economy demand is still largely speculative.
  • Batch-layer risk: If Circle's off-chain aggregator is the single point of settlement, it becomes a bottleneck and a counterparty. Decentralization of that layer is a separate, unresolved problem.
  • Chain selection: With 12 supported networks on testnet, Circle will have to decide which chains get first-class mainnet support and which remain second-tier, with liquidity implications for developers.
  • Regulatory clarity on machine payments: GENIUS Act classification helps, but "an autonomous agent paying without human authorization" has never been litigated in US payments law.

Any of these could slow the rollout by quarters. None of them undermines the fundamental architectural insight.

Why This Moment Matters​

Every prior micropayment primitive asked the user to accept a tradeoff: lower fees for worse UX, better speed for weaker settlement guarantees, cheaper gas for thinner regulatory cover. Circle Nanopayments is the first attempt at removing the tradeoff entirely — native stablecoin, multi-chain, sub-cent, zero-gas, regulator-adjacent.

If the rail works at mainnet scale, the downstream effects compound fast:

  • DePIN networks price compute, bandwidth, and storage per second rather than per month.
  • AI agents pay for data on a per-query basis, breaking the current "buy an API subscription" model.
  • Robotics transitions from centrally-funded fleets to autonomous revenue-generating units.
  • IoT finally gets economic incentives for individual sensors to monetize their output.
  • Content experiments with pay-per-paragraph and pay-per-second models that have failed for 20 years due to transaction costs.

None of those outcomes is guaranteed. But for the first time, the rail underneath them is not the blocker.

Bottom Line​

Circle's nanopayments testnet is a quiet, technical release with loud implications. By solving the fee math through batching, subsidizing on-chain settlement, and riding USDC's multi-chain and regulatory footprint, Circle has shipped the first stablecoin infrastructure that takes the machine economy seriously on economics rather than aspiration.

The robot dog paying for its own electricity is the headline moment. The real story is that every autonomous agent, IoT device, and API-paying script now has a rail where the transaction fee does not exceed the transaction value. That has never been true before.

Machines are about to become first-class economic participants. The rails they will pay on are being laid this year.

BlockEden.xyz provides enterprise-grade blockchain API infrastructure across 27+ chains — including the networks Circle Nanopayments supports. If you are building agent-driven applications or machine-economy services, explore our API marketplace for the low-latency, high-reliability endpoints autonomous workflows require.

Sources​

Visa Just Became a Blockchain Operator: Inside the Tempo Anchor Validator Playbook

· 9 min read
Dora Noda
Dora Noda
Software Engineer

On April 14, 2026, something quietly radical happened in payments. Visa — the company that built the modern card economy — flipped a switch on a production blockchain node it engineered in-house and began earning stablecoin rewards for packaging other people's transactions. Together with Stripe and Zodia Custody (majority-owned by Standard Chartered), Visa became one of the first three external validators on Tempo, the Paradigm-incubated, payments-first Layer 1 that raised $500 million at a $5 billion valuation before a single block was produced on its mainnet.

The headline story is easy: card network joins blockchain. The real story is harder and more interesting. For the first time, a Tier-1 global card network is not paying fees to crypto rails — it is charging fees on them. And it built the infrastructure itself, not through a validator-as-a-service vendor. That shift reframes a decade of "banks versus blockchains" debate into something closer to a merger.