Stripe Building Own Blockchain for Cross-Border Payments

Stripe is developing its own blockchain to improve the speed and cost of cross-border payments and support stablecoin settlement. The initiative aims to create programmable money rails, signaling a strategic move toward integrating blockchain technology for global financial settlement. This development suggests a growing need for backend engineers in fintech to build API abstraction layers for event-driven payment flows on-chain.

This isn't Stripe's first foray into crypto; the company initially enabled Bitcoin payments in 2014 before discontinuing the service in 2018 due to rising costs and slow transaction times on the Bitcoin network. The firm later re-entered the space by enabling USDC payouts on its Connect platform and launching a fiat-to-crypto onramp for Web3 companies in 2023. This history signals a long-term interest in digital assets, culminating in the development of its own blockchain infrastructure. The new blockchain, named Tempo, is designed to provide sub-second settlement finality, a direct challenge to legacy payment rails. It aims to support enterprise-grade reliability, moving far beyond Bitcoin's sub-10 transactions per second (TPS) to address network congestion that can cause delays of over 12 hours. The long-term vision is to support an AI-driven agent economy, which Stripe anticipates could require infrastructure capable of handling over 1 million transactions per second. On the testnet, Tempo is already being utilized by major players like Visa, Nubank, and Shopify for use cases including global payouts and remittances. Klarna has also launched a bank-issued stablecoin on the platform to facilitate cheaper cross-border settlement. This pre-launch adoption by established financial and e-commerce companies indicates strong market validation for Stripe's new infrastructure. This strategic move toward proprietary blockchain infrastructure is underpinned by the dramatic growth in B2B stablecoin transactions, which doubled to $400 billion in 2025. With 60% of that volume now representing B2B flows, Stripe is positioning Tempo to capture a significant share of the market by offering a lower-cost alternative to traditional correspondent banking. The system will initially support USDC on networks like Solana, Ethereum, and Polygon, settling transactions instantly on-chain before converting to fiat. For backend engineers, this signals a shift toward event-driven architectures for payment systems, enabling asynchronous, real-time processing instead of traditional batch-based methods. Building abstraction layers on top of blockchains allows for decoupled components and greater system resilience, which is critical for handling high-volume, concurrent transactions in fintech and insurtech. This architectural pattern is essential for integrating with legacy insurance systems, which often operate in data silos and hinder the adoption of advanced AI for tasks like claims processing and underwriting. The rise of agentic AI, capable of autonomous, multi-step reasoning and execution, is a key driver behind the need for such high-throughput payment rails. In insurance, AI agents are already automating claims intake and triage, while in finance, they are being used for everything from algorithmic trading to risk management. These multi-agent systems require robust, scalable infrastructure to coordinate complex, high-speed transactions between different autonomous entities. For technical founders, this landscape underscores the importance of a strong go-to-market strategy and a deep understanding of venture finance. Investors look for a clear plan on how capital will be used to achieve specific milestones and a financial model that demonstrates how the business scales. Building relationships with potential investors early and maintaining momentum through regular updates is crucial for a successful fundraising process. The path to Principal Engineer requires a blend of deep technical expertise and strategic leadership, focusing on influencing without direct authority. This involves guiding high-level architecture decisions, mentoring other engineers, and bridging the gap between technical teams and business objectives. A key responsibility is to drive process improvements and establish technical standards that elevate the entire organization's output.

Get your own daily briefing

Scout delivers personalized news, insights, and conversations tailored to your role and industry.

Download on the App Store

Shared from Scout - Be the smartest in the room.