Kraken acquired Reap to own stablecoin APIs

Diving deeper into

Why Kraken acquired Reap for $600M

Document
created developer APIs on top of underlying stablecoin issuers
Analyzed 6 sources

The real product was not the stablecoin itself, it was the software layer that made stablecoins usable like modern fintech. Companies like Bridge, Rail, BVNK, and Reap hid the messy parts, picking the issuer, chain, banking partner, and liquidity route in the background, then exposing simple APIs so a fintech could add wallets, payouts, card spend, and FX-like transfers without stitching together Circle, Tether, Solana, Lead Bank, or market makers one by one.

  • In practice, a customer wanted one API that could open a stablecoin account, accept fiat, convert into USDC or USDT, send funds across borders any time, and off-ramp back into a bank account. The infrastructure company handled orchestration across blockchains, banks, and liquidity providers, then charged on payment volume.
  • This is why these businesses looked more like Stripe than like Circle. Circle and Tether issue the dollars onchain, but the API layer owned the developer relationship and the workflow, which is where the higher value sits. Reap described its own job as building the toolbox for cards, payments, and virtual accounts on top of one programmable money movement stack.
  • Cards made the model especially powerful because they turned stablecoin balances into normal spend at any Visa or Mastercard merchant. Rain showed the pattern, stablecoins stay in the background, the user taps a card for SaaS, travel, or payroll expenses, and the provider makes money from interchange, subscriptions, and transaction services.

The next phase is more bundling and more vertical integration. Exchanges, card networks, and payment platforms are buying the API layer because whoever controls this orchestration layer can turn stablecoins from a treasury asset into a full money movement stack, with accounts, payouts, cards, and programmable payment logic all in one system.