Kraken builds crypto-native fintech OS

Kraken is trying to turn exchange liquidity into the base layer for a crypto native fintech stack. Reap adds the missing workflows that B2B fintechs actually sell, cards, cross border payouts, virtual accounts, and expense flows, so Kraken can move from earning mainly trading fees to earning on day to day business money movement, especially for fast growing fintechs in Asia, LatAm, and other dollar hungry markets.

• Reap was already building the toolbox these fintechs need. Its customers use stablecoins in the back end for supplier payments, payroll, card settlement, and wallet to bank flows, while the end user sees a familiar neobank or payments product. That makes Reap a natural app layer on top of Kraken’s exchange and liquidity engine.
  1 sacra 5 sacra 6 sacra
• The closest fiat world analog is Airwallex, which expanded from cross border payments into cards and multi product financial infrastructure, with cards and payments driving over half of gross profit. Kraken is now pursuing the same bundling logic, but with stablecoin rails underneath instead of mainly bank and FX rails.
  1 sacra 2 sacra 3 sacra
• Stripe shows the other path. Bridge plugs stablecoins into a very broad payments middleware stack, while Kraken starts from crypto liquidity and builds outward. That gives Kraken an edge with fintechs that need deep on and off ramps and 24 by 7 settlement, but it also pulls Kraken into direct competition for the same global fintech customers.
  1 sacra 3 sacra 6 sacra

The next step is a stablecoin network where cards, payouts, treasury, and FX all reinforce one another and every new fintech customer adds more flow through Kraken’s rails. If that works, Kraken becomes less like a brokerage with add ons and more like crypto’s version of a cross border financial operating system for fintechs.