# Tempo Tempo is a purpose-built blockchain for stablecoin financial products. Build global payments, stablecoin accounts, and institutional settlement. --- ## Move money at internet speed > Source: https://tempo.xyz/ > Language: en # Move money at internet speed Tempo is a purpose-built blockchain for stablecoin financial products. [Talk with our team](/contact/) [For agents](/solutions/agentic-payments/) ## Scale your business with stablecoins on Tempo Solutions ### [Cross-border payments](/solutions/cross-border-payments/) Move money across the globe with fast, inexpensive and predictable payment flows. ### [Stablecoin accounts](/solutions/embedded-finance/) Launch financial accounts in 100+ countries with rewards and card spending. ### [Institutional settlement](/solutions/institutional-money-movement/) Issue and settle stablecoins 24/7 with banks, card networks, and financial institutions. ## Build on Tempo’s powerful financial primitives Tempo Products ### Earn Earn up to 7% APY on stablecoins with enterprise-grade strategies built on US Treasuries, private credit, and collateralized lending on Tempo. [Tempo Earn](/earn/) ### Routes Move stablecoins across chains and currencies in a single API. [Tempo Routes](/routes/) ### Zones Keep your business and customers payments private while using the best features of Tempo. [Tempo Zones](/zones/) ## Businesses grow revenue faster with Tempo Customers - [DoorDash pays its merchants instantly with stablecoins on Tempo](/customer-stories/doordash/) - [Deel lets contractors in 80+ countries get paid and earn up to 4%](/customer-stories/deel/) - [Stripe helps businesses across 100+ countries hold and spend money](/customer-stories/stripe/) - [Meow gives startups global banking with 24/7 stablecoin payments](/blog/meow-and-tempo-stablecoin-native-banking/) - [Felix powers 5% of all US to Mexico remittances with stablecoins](/customer-stories/felix-pago/) [All customer stories](/customer-stories/) ## Access global liquidity on Tempo Built for scale - **$36+ billion** — Annualized stablecoin payment volume on Tempo - **$700+ million** — Stablecoins and tokenized asset value on Tempo - **95 currencies** — Available through on and offramps on Tempo > Tempo is now Stripe’s default blockchain for new features. > — Patrick Collison, CEO, Stripe ## Payments that work for AI agents Agentic Payments ### MPP A protocol for machine payments that gives agents the ability to pay for API services. [Explore MPP](https://mpp.dev) ### Mercator A discovery layer and tool-router for agentic workflows. [Explore Mercator](https://mercator.sh) ## Transform your business with stablecoins Stablecoin basics ### [What are stablecoins? A guide for financial teams](/learn/what-are-stablecoins/) Stablecoins Stablecoins settle instantly, 24/7, across borders. For treasury teams, that means less trapped cash and faster access to working capital. ### [Tokenized deposits and stablecoins for corporate treasury](/learn/corporate-treasury-tokenized-deposits/) Treasury Stablecoins change how cross-border payments work. Instead of relying on correspondent banks, the flow is simpler. ### [Stablecoins for business: a practical guide for finance teams](/learn/stablecoins-for-business/) Enterprise Stablecoins enable faster payroll funding, cheaper cross-border payouts, and new revenue streams for payroll providers. ## Take your stablecoin strategy into production Start using Tempo ### Design your stablecoin product Enterprises Build on Tempo with payments specialists, forward-deployed engineers, and global banking experts. [Talk to our team](/contact/) ### Start building Developers Build on the blockchain engineered for payments, with the tools and docs to bring your product to life. [Build on Tempo API Platform](https://api.tempo.xyz) --- ## About Tempo – A blockchain built for payments > Source: https://tempo.xyz/about/ > Language: en # A blockchain built for payments Overview ## Purpose-built for stablecoins Stablecoins enable instant, borderless, programmable transactions, but most blockchain infrastructure isn't designed for them. Tempo is built to move stablecoins across borders, between businesses, and between machines with the speed, cost, and reliability that real-world payments demand. Tempo is incubated by [Stripe](https://stripe.com) and [Paradigm](https://www.paradigm.xyz), combining deep experience in global payments with leading crypto and blockchain engineering. The result is infrastructure purpose-built for stablecoins rather than retrofitted from a general-purpose chain. - **Network** Payments-first Layer 1 blockchain - **Focus** Stablecoin payments: cross-border transfers, global payouts, embedded finance, and machine-to-machine payments - **Incubated by** Stripe and Paradigm - **Designed with** Category-defining fintechs, banks, and commerce platforms serving billions worldwide - **Settlement** Near-instant settlement, with no re-orgs - **Fees** Paid in USD stablecoins, with no volatile gas token Use cases ## Designed for real-world use cases at scale 1. ### Cross-border payments Move money between countries and currencies with the speed and finality of an onchain settlement layer. 1. ### Global payouts Pay contractors, sellers, and partners anywhere with stablecoins instead of slow, fragmented banking rails. 1. ### Agentic and machine payments Give software agents and automated systems a native way to transact using stablecoins. 1. ### Embedded finance Build stablecoin balances, transfers, and payouts directly into products and platforms. 1. ### Institutional settlement Settle high-value flows between financial institutions with programmable, always-on infrastructure. ## Designed with global payment leaders Tempo was shaped with input from category-defining fintechs, banks, and commerce platforms serving billions worldwide. - ![Visa](/content/partners/visa.svg) - ![Deutsche Bank](/content/partners/deutsche-bank.svg) - ![Klarna](/content/partners/klarna.svg) - ![OpenAI](/content/partners/openai.svg) - ![Shopify](/content/partners/shopify.svg) - ![Nubank](/content/partners/nubank.svg) - ![Revolut](/content/partners/revolut.svg) - ![Mastercard](/content/partners/mastercard.svg) - ![UBS](/content/partners/ubs.svg) - ![DoorDash](/content/partners/doordash.svg) - ![Anthropic](/content/partners/anthropic.svg) - ![Standard Chartered](/content/partners/standard-chartered.svg) ## Explore Tempo [Solutions ### Stablecoin payment solutions Cross-border payments, global payouts, embedded finance, and agentic payments built on Tempo. Read more](/solutions/cross-border-payments/) [Ecosystem ### Payments infrastructure partners The wallets, on and off ramps, custodians, and infrastructure providers building on Tempo. Read more](/ecosystem/) [Customer stories ### Who builds on Tempo How companies like DoorDash, OnePay, and MoneyGram use Tempo to move money. Read more](/customer-stories/) [Documentation ### Tempo documentation Technical documentation for integrating with Tempo's payment infrastructure. Read more](/developers/) [Blog ### News and updates Product announcements, ecosystem launches, and research from the Tempo team. Read more](/blog/) [FAQ ### Frequently asked questions Clear answers about Tempo, MPP, validators, fees, and the technology behind the network. Read more](/faq/) ## Take your stablecoin strategy into production Start using Tempo ### Design your stablecoin product Enterprises Build on Tempo with payments specialists, forward-deployed engineers, and global banking experts. [Talk to our team](/contact/) ### Start building Developers Build on the blockchain engineered for payments, with the tools and docs to bring your product to life. [Tempo API Platform](https://api.tempo.xyz) --- ## Blog – Tempo > Source: https://tempo.xyz/blog/ > Language: en # News, updates, & resources from Tempo ## [Tempo Earn now supports Hastra’s PRIME and wYLDS](/blog/tempo-earn-hastra-prime-wylds/) Tempo Earn now supports Hastra-minted PRIME and wYLDS, giving platforms more ways to embed real-world yield into treasury, card, and payment products. 2026-10-16 ## [Privacy is live on Tempo](/blog/privacy-is-live-on-tempo/) Tempo Zones let enterprises keep customer stablecoin balances and payments private, with built-in compliance controls and full access to Tempo's global liquidity. 2026-10-14T13:00:00Z ## [Anchorage Digital adds custody support for assets on Tempo](/blog/anchorage-digital-adds-custody-support-for-ousd-on-tempo/) Anchorage Digital Bank, N.A. now supports custody, withdrawals, and transfers for assets on Tempo, including OUSD, USDT0, USDC.e, and pathUSD. 2026-10-13 ## [zerohash joins Tempo as a validator and infrastructure partner](/blog/zerohash-joins-tempo-as-a-validator-and-infrastructure-partner/) zerohash is joining Tempo’s validator set and partnering to give enterprises a practical path to build stablecoin payment flows on Tempo. 2026-10-06 ## [OUSD is live on Tempo](/blog/ousd-is-live-on-tempo/) Open USD (OUSD) launches on Tempo with $400M+ in liquidity for enterprise payments and no-cost minting and burning through supported providers. 2026-09-30 ## [Knova and Tempo help institutions launch tokenized products without rebuilding systems](/blog/knova-tempo-tokenized-products/) Knova and Tempo help financial institutions launch tokenized payment products while keeping their existing systems, custody providers, and payment workflows. 2026-09-21 ## [Wirex is now live on Tempo for enterprise stablecoin card programs](/blog/wirex-is-now-live-on-tempo/) Wirex enables its partners to use Tempo as a settlement layer for enterprise stablecoin card programs. 2026-09-10 ## [Chainlink Data Feeds are now live on Tempo](/blog/chainlink-data-feeds-on-tempo/) Chainlink Data Feeds are live on Tempo, giving businesses, institutions, and developers industry standard onchain pricing infrastructure. 2026-09-03 ## [Tempo and Privy launch limited-time Earn boost program](/blog/tempo-and-privy-launch-limited-time-earn-boost-program/) Tempo and Privy Earn boost program | Apply here 2026-09-02 ## [Daya expands cross-border payments for African businesses with Tempo](/blog/daya-expands-cross-border-payments-for-african-businesses-with-tempo/) Daya gives African businesses one place to collect locally, access FX, manage balances across currencies, and pay suppliers around the world. 2026-08-27 ## [Ondo’s USDY is now live on Tempo](/blog/ondo-usdy-is-now-live-on-tempo/) The integration gives platforms a Treasury-backed asset they can use in Earn products, treasury balances, and payment flows where funds may otherwise sit idle. 2026-08-24 ## [Unlock new revenue streams with Tempo Earn](/blog/introducing-tempo-earn/) Tempo Earn puts idle stablecoin balances to work: end users earn on balances they already hold and platforms control how rewards are split. 2026-08-12T12:00:00Z ## [The Settlement Gap Banks Can Own By Adopting Stablecoins](/blog/off-hours-cash-stablecoin-settlement-gap/) How banks can use wholesale deposits to back an off-hours stablecoin sleeve and own the weekend settlement market. 2026-08-10 ## [Tempo plans to support BlackRock's new GENIUS-compliant money market fund BRSRV](/blog/blackrock-brsrv/) The final prospectus for BlackRock's BRSRV names Tempo as a supported blockchain for OnChain Shares. 2026-08-03 ## [Creating More Liquidity Mobility in Markets](/blog/creating-more-liquidity-mobility-in-markets/) Why liquidity mobility is the primary lens for evaluating tokenized settlement infrastructure. 2026-07-29 ## [Tempo expands onchain yield offering with BlackRock’s BUIDL fund](/blog/tempo-expands-onchain-yield-offering-with-blackrocks-buidl-fund/) BlackRock’s BUIDL fund is now available on Tempo, expanding access to institutional-grade onchain yield for eligible investors. 2026-07-29 ## [Coupang and Woori Bank complete Korea's first end-to-end KRW stablecoin payment on Tempo](/blog/coupang-woori-bank-krw-stablecoin-payments/) Coupang and Woori Bank have completed Korea's first end-to-end proof of concept for KRW stablecoin payments and settlement in a consumer-facing commercial service. 2026-07-27 ## [Meow and Tempo partner to bring stablecoin-native banking to global businesses](/blog/meow-and-tempo-stablecoin-native-banking/) Meow is bringing payments-grade stablecoin infrastructure to its business banking platform on Tempo. 2026-07-15 ## [Introducing Receive Policies](/blog/receive-policies/) Receive policies on Tempo let exchanges, custodians, and payment platforms decide which tokens and senders their accounts accept, and recover anything they don't. 2026-07-09 ## [Open USD is coming to Tempo](/blog/open-usd-ousd/) Open USD will be issued natively on Tempo from day one, giving enterprises and developers another stablecoin option for payment, settlement, treasury, and distribution flows. 2026-07-01 ## [AllUnity's Swiss franc stablecoin CHFAU is now live on Tempo](/blog/allunity-chfau-live-on-tempo/) AllUnity's CHFAU, a regulated Swiss franc stablecoin, is now live on Tempo, giving businesses a trusted CHF instrument for cross-border payments, treasury operations, and regulated settlement flows onchain. 2026-06-17 ## [Introducing MPP Credits: fund your agent with a card](/blog/mpp-credits/) MPP Credits are a new way for developers and agents to pay for MPP services using a credit or debit card. 2026-06-17 ## [What Are Tokenized Deposits? A Guide for Banks and Institutions](/blog/tokenized-money-for-banks/) What are tokenized deposits? Learn how banks use tokenized deposits, first-party stablecoins, and third-party stablecoins under new Basel rules. 2026-06-13 ## [Flutterwave and Tempo partner to expand stablecoin settlement options to African payments](/blog/flutterwave-and-tempo-partner-to-expand-stablecoin-settlement-options-to-african-payments/) Flutterwave, one of Africa's largest payments companies, is partnering with Tempo to expand stablecoin settlement options to cross-border payments across the continent. 2026-06-04 ## [Kraken and Tempo partner to bring institutional stablecoin infrastructure to payments](/blog/kraken-and-tempo-partner-to-bring-institutional-stablecoin-infrastructure-to-payments/) Kraken is the first U.S. centralized exchange to support Tempo, giving builders access to liquidity, custody, on/off-ramps, execution, and listings support in one unified stack. 2026-06-04 ## [Deel launches stablecoin wallet for global contractors, exclusively on Tempo](/blog/deel-launches-dlusd-stablecoin-wallet-for-global-contractors/) Deel launched DLUSD, a dollar-backed stablecoin, and the Deel stablecoin wallet for its global contractor base, exclusively on Tempo. 2026-06-02 ## [Stablecoin Opportunity for Sponsor Banks](/blog/stablecoin-opportunity-for-sponsor-banks/) Sponsor banks already power fintechs with bank accounts, virtual accounts, and payments. The same fintechs now need stablecoin wallets, transfers, and cards. Sponsor banks that build for this can defend their customer base and grow revenue per relationship. 2026-06-02 ## [Kraken adds native support for USDT0 deposits and withdrawals on Tempo](/blog/kraken-adds-native-support-on-tempo/) Kraken now supports deposits and withdrawals of USDT0 on Tempo, making it the first U.S. exchange to natively support the network. 2026-06-01 ## [Morpho is now live on Tempo](/blog/morpho-is-now-live-on-tempo/) Morpho is now live on Tempo, enabling enterprises and apps to add onchain yield to their services. 2026-05-22 ## [Coinbase Wrapped BTC is now live on Tempo, powered by Chainlink CCIP](/blog/cbbtc-on-tempo/) Coinbase Wrapped BTC (cbBTC) is now live on Tempo, made available through Chainlink CCIP so enterprises and institutions can use Bitcoin alongside stablecoin payments. 2026-05-15 ## [KAST is bringing its stablecoin earn product onto Tempo and joining as design partner](/blog/kast-stablecoin-earn-product-tempo-design-partner/) KAST, a financial platform available in 170+ countries and built on stablecoin rails, plans to launch its stablecoin earn product on Tempo. 2026-05-13 ## [RedotPay integrates MPP to bring agentic payments to its 7.5 million users](/blog/redotpay-integrates-mpp-to-bring-agentic-payments-to-its-users/) RedotPay is integrating the Machine Payments Protocol (MPP) so AI agents can transact on behalf of its 7M+ users, with settlement on Tempo. 2026-05-06 ## [Now live on Tempo: CADD, Canada's first CAD-backed stablecoin issued by a financial institution](/blog/cadd-now-live-on-tempo/) CADD, a payment stablecoin backed 1:1 by Canadian dollars, is now live on Tempo. 2026-05-04 ## [New features on Tempo for enterprise payments](/blog/new-features-for-enterprise-payments/) New features on Tempo close the gaps in enterprise payment workflows on stablecoins: subscription billing and auto pay through enhanced access keys, plus per-customer deposit attribution, invoice-level reconciliation, and multi-tenant wallet structures through virtual addresses. 2026-04-27T12:00:00Z ## [Subscriptions on Tempo: Onchain Billing Made Easy](/blog/subscriptions-on-tempo/) Enable subscription billing onchain with Tempo's access keys, supporting periodic spending limits for human subscribers and AI agents alike. 2026-04-27T12:00:00Z ## [Virtual addresses for stablecoin deposits](/blog/virtual-addresses/) Virtual addresses on Tempo give exchanges, ramps, neobanks and financial institutions unique deposit addresses for every customer without the overhead of sweep transactions. Funds sent to a virtual address are credited directly to a registered master wallet at the protocol layer. 2026-04-27T12:00:00Z ## [OKX launches as Tempo's first international exchange partner](/blog/okx-launches-as-tempos-first-international-exchange-partner/) OKX is the first international exchange to support Tempo at launch, with deposits and withdrawals on Tempo mainnet and native support in OKX Wallet from day one. 2026-04-24 ## [Karta is building its self-custody money app on Tempo](/blog/karta-is-building-its-self-custody-money-app-on-tempo/) Karta, a self-custody money app with 25,000+ cardholders across 150+ countries, is building its payment infrastructure on Tempo. Treasury live today. 2026-04-23 ## [Felix brings instant remittance settlement on Tempo](/blog/felix-brings-instant-remittance-settlement-on-tempo/) Felix Pago, the WhatsApp remittance product serving 1M+ users across Latin America, is adding Tempo to its settlement infrastructure for payments at scale. 2026-04-22 ## [ARQ is building cross-border payment infrastructure on Tempo](/blog/arq-is-building-cross-border-payment-infrastructure-on-tempo/) ARQ is moving its cross-border payment infrastructure onto Tempo, bringing settlement for $10B+ in annualized transaction volume onto a payments-first chain. 2026-04-21 ## [Coastal Bank partners with Tempo to build stablecoin-settled cross-border payments](/blog/coastal-bank-partners-with-tempo-to-build-stablecoin-settled-cross-border-payments/) Coastal Financial Corporation (Nasdaq: CCB) is building stablecoin-settled cross-border payment infrastructure on Tempo for its fintech partners. 2026-04-21 ## [DoorDash partners with Tempo to bring stablecoin payments to its global marketplace](/blog/doordash-partners-with-tempo-to-bring-stablecoin-payments-to-its-global-marketplace/) DoorDash is building stablecoin-powered payment infrastructure on Tempo for marketplace payments across merchants and Dashers in 40+ countries. 2026-04-21 ## [DoorDash, Stripe, Coastal, ARQ and others bring payment operations onto stablecoins on Tempo](/blog/enterprise/) DoorDash, Stripe, Coastal, ARQ, and more are moving payment operations onto Tempo. Today, Tempo is also launching Stablecoin Advisory to help enterprises bring payments onto stablecoin rails. 2026-04-21 ## [Stripe and Tempo: stablecoin settlement for global money movement](/blog/stripe-and-tempo-stablecoin-settlement-for-global-money-movement/) Stripe's money management now supports stablecoin transfers on Tempo. Businesses in 100+ countries can hold, send, and receive stablecoins in under a second. 2026-04-21 ## [Introducing Tempo Zones](/blog/introducing-tempo-zones/) Tempo Zones bring privacy and scalability to Tempo. Private EVM-compatible chains running in parallel to mainnet, with seamless cross-zone transfers. 2026-04-16T12:00:00Z ## [Privacy on Tempo](/blog/privacy-on-tempo/) Tempo Zones bring private stablecoin payments to public rails, without giving up interoperability, liquidity, or issuer-defined compliance controls. 2026-04-16T12:00:00Z ## [Stripe, Visa, and Zodia Custody by Standard Chartered join as validators on Tempo](/blog/stripe-visa-zodia-join-as-validators/) Stripe, Visa, and Zodia Custody by Standard Chartered have joined as validators on Tempo, the blockchain built for payments at enterprise scale. 2026-04-14 ## [Stablecoins for Neobanks](/blog/stablecoins-for-neobanks/) Explore how stablecoins help neobanks launch new products and expand into new markets, backed by Tempo's growing partner ecosystem. 2026-04-07 ## [MPP Sessions: Web-Scale Payments for AI Agents](/blog/mpp-sessions/) MPP Sessions let AI agents pay for services in real time with just two onchain transactions. Learn how sessions use escrow, offchain vouchers, and onchain settlement to scale machine payments. 2026-04-02 ## [Tempo Mainnet is live](/blog/mainnet/) Start building on Tempo now that mainnet is live, using public RPC endpoints and the new Machine Payments Protocol co-authored with Stripe. 2026-03-18 ## [Account Abstraction on Tempo](/blog/account-abstraction/) Account abstraction removes the friction of onchain accounts: seed phrases, gas tokens, and repeated confirmations. Tempo builds it into the protocol with passkey accounts, native gas sponsorship, access keys, and batch transactions. 2026-03-12 ## [Issuing Stablecoins on Tempo](/blog/stablecoin-issuance/) Issuing your stablecoin on Tempo gives you distribution into enterprise payment flows, structural demand through network economics, and native compliance infrastructure. 2026-03-10 ## [Stablecoins for Payroll](/blog/stablecoins-for-payroll/) Payroll providers are starting to take stablecoins seriously. The three distinct use cases build on each other: faster payroll account funding, cheaper cross-border payouts, and embedded wallets that turn payroll into a financial services platform. 2026-02-25 ## [Stablecoin Compliance and Regulatory Controls on Tempo](/blog/compliance-controls/) Explore stablecoin compliance and regulatory controls on Tempo. Discover native features for stablecoin issuers, wallet providers, and enterprises. 2026-02-19 ## [How stablecoin remittances work and what are the key benefits](/blog/remittances/) Explore key benefits of stablecoin remittances, how the process slashes transfer fees below 1%, and the current regulatory challenges facing implementation. 2026-02-10 ## [Tempo × Merkle](/blog/tempo-x-merkle/) The Tempo team is excited to welcome the Merkle team. Together, we will build the infrastructure for payments at scale 2026-02-09 ## [Stablecoin Fees on Tempo](/blog/stablecoin-fees/) Tempo enables users to pay transaction fees in any stablecoin, no volatile gas tokens required. Stablecoin Fees are native to the protocol and deliver transparent, predictable costs and simpler accounting. 2026-02-05 ## [ACH vs wire vs stablecoins: A guide for finance teams](/blog/ach-vs-wire-vs-stablecoins-a-guide-for-finance-teams/) Stablecoins offer instant settlement, low transaction costs, and programmable controls. For finance teams, they function as payment instruments useful for supplier payouts, treasury management, and cross-border settlement. 2026-01-27 ## [Stablecoins for Global Payouts](/blog/global-payouts/) Stablecoins settle instantly, 24/7, across borders. For companies that run global payouts, that means faster delivery, lower fees, and fewer steps to pay recipients. 2026-01-14 ## [TIP-20: Tempo's Token Standard for Payments](/blog/tip20/) Explore TIP-20, Tempo's native token standard built for stablecoins, extending ERC-20 with transfer memos and compliance controls. 2026-01-06 ## [Stablecoins for Corporate Treasury](/blog/corporate-treasury/) Stablecoins settle instantly, 24/7, across borders. For global treasury teams, that means less trapped cash and faster access to working capital 2025-12-18 ## [Introducing Tempo Transactions](/blog/tempo-transactions/) Tempo Transactions are a new, native transaction type that enables paying gas fees in any stablecoin, concurrent and batch transactions, passkey authentication, and unlocks use-cases like payroll, payouts, and subscriptions. 2025-12-17 ## [Tempo's testnet is live](/blog/testnet/) Start building on Tempo today with the newly launched public testnet, now open for developers to explore and test. 2025-12-09 ## [Tempo × Commonware](/blog/tempo-commonware/) Announcing Tempo's partnership with Commonware 2025-11-08 ## [Tempo x Ithaca](/blog/tempo-x-ithaca/) Announcing Tempo's partnership with Ithaca 2025-10-17 ## [Meet Tempo's infrastructure partners](/blog/infra-partners/) Announcing Tempo's infrastructure partners who are helping build the payments blockchain. 2025-09-23 ## [Introducing Tempo, the payments-first blockchain](/blog/introducing-tempo/) Tempo is a payments-first blockchain incubated by Stripe and Paradigm. 2025-09-04 --- ## Account Abstraction on Tempo > Source: https://tempo.xyz/blog/account-abstraction/ > Language: en **_Account abstraction removes the friction of onchain accounts: seed phrases, gas tokens, and repeated confirmations. However, in most cases it requires smart contracts and third-party infrastructure. Tempo offers this natively._** [_Reach out_](https://tempo.xyz/contact) if you're building consumer wallets or enterprise payment products on Tempo. The promise of instant, low-cost stablecoin payments is held back by the default user experience of blockchains. Users deal with seed phrases and gas tokens. Developers stitch together smart contract wallets, paymasters, and bundlers. The result is unnecessary friction for users and unnecessary complexity for developers. Tempo addresses this at the protocol level. Account abstraction is built into the chain, with no middleware or workarounds required. ## The blockchain dilemma Today, building a consumer application on a blockchain often means choosing between two bad options: a poor user experience or unnecessary complexity for developers. For users, interacting with a blockchain usually means writing down 12 or 24 random words, or the seed phrase, and storing them somewhere safe. Then buying a token you’ve never heard of just to pay transaction fees. Account abstraction can improve this experience. However, existing approaches to account abstraction require a stack of infrastructure: bundlers, paymaster contracts, relayers, and custom delegation programs. Tempo takes a different approach. It provides account abstraction features directly through native primitives. ## How Tempo fixes onchain accounts Tempo supports a range of account abstraction features through its native transaction type, [Tempo Transactions](/developers/docs/guide/tempo-transaction). These capabilities, such as passkey accounts and fee sponsorship, help developers build applications without relying on additional smart contracts or middleware. ![image1-color-light](/images/blog/image1-color-light.png) ### Passkey accounts [Passkey accounts](/developers/docs/protocol/transactions/AccountKeychain) let users sign up and authenticate with their fingerprint, Face ID, or Touch ID. Passkeys are stored in the device's secure enclave and sync across devices through iCloud Keychain or Google Password Manager. Users get strong security with an experience they already understand. ![image2-color-dark](/images/blog/image2-color-dark.png) ### Native fee sponsorship [Native fee sponsorship](/developers/docs/guide/payments/sponsor-user-fees) lets your application pay transaction fees on behalf of users. This happens at the protocol level with a single transaction field. Users can also pay fees directly in any stablecoin. Either way, no one needs to hold a volatile gas token. ![image3-color-dark](/images/blog/image3-color-dark.png) ### Access keys [Access keys](/developers/docs/protocol/transactions#access-keys) let users create short-lived, scoped keys that sign transactions on their behalf. This means your app can execute transactions in the background without prompting for biometric confirmation each time, while maintaining controls on what those keys can do. ![image4-color-dark](/images/blog/image4-color-dark.png) ### Batch and scheduled transactions Tempo natively supports [batch and scheduled transactions](/developers/docs/protocol/transactions#batch-calls). Batching bundles multiple operations into a single atomic transaction: for example, you can run payroll for 500 people in one call. Scheduled transactions execute within a future time window for subscriptions, recurring invoices, or deferred settlements. ![image5-color-light](/images/blog/image5-color-light.png) ### Parallel transactions [Parallel transactions](/developers/docs/guide/payments/send-parallel-transactions#send-parallel-transactions) let your application submit multiple transactions from the same account at the same time. This means that, for example, a payment processor can run hundreds of concurrent settlements from a single wallet without any additional infrastructure or management overhead. ## What this unlocks When wallets, seed phrases, gas tokens, and middleware are no longer part of the equation, new product categories become practical: - **Embedded finance:** Stablecoin accounts with passkey signup, sponsored fees, and background transfers through access keys. - **Payroll and payouts:** Batch hundreds of payments into a single atomic transaction. All succeed or all fail, with no need to find and retry the ones that did not. - **Consumer checkout:** Embed a wallet into your checkout flow with passkey authentication. Your app sponsors the fees, and users confirm payment with a fingerprint. - **Loyalty and rewards:** Put your loyalty program onchain with passkey accounts and gasless transactions. Points become tokens your customers can transfer, trade, or use across any app that supports them. - **Agentic payments:** AI agents with their own wallets that pay in stablecoins autonomously. Access keys let humans set spending limits and authorization rules. ## Start building on Tempo Whether you're building consumer wallets or enterprise payment products, we can help you get started: ### Learn the fundamentals Visit the Learn section of the Tempo documentation to understand stablecoins, how they work, and the payment use cases they enable. [Learn](/learn) ### Start building If you're familiar with blockchain development, head to our docs to connect to Tempo, access test funds, download SDKs, and start building with Tempo Transactions. [Read the docs](/developers/docs/protocol/tip20/overview) ### Move faster with partners You can also work with our infrastructure partners including Crossmint, Fireblocks, Privy, and Turnkey, who are rolling out Tempo Transactions and can help accelerate your development timeline. Visit the Ecosystem section to explore Tempo's growing network of partners. [Explore ecosystem](/ecosystem) _For guidance on implementing account abstraction for your use case, [reach out](https://tempo.xyz/contact) to our Enterprise Team._ --- ## ACH vs wire vs stablecoins: A guide for finance teams > Source: https://tempo.xyz/blog/ach-vs-wire-vs-stablecoins-a-guide-for-finance-teams/ > Language: en **_Stablecoins offer instant settlement, low transaction costs, and programmable controls. For finance teams, they function as payment instruments useful for supplier payouts, treasury management, and cross-border settlement. Following the GENIUS Act in 2025, banks are integrating these rails directly, giving enterprises a new option alongside ACH and wire._** For decades, B2B payments have forced finance leaders to choose between two imperfect options: speed (wires) or cost (ACH). If you wanted to move money at low cost, you accepted a multi-day delay and limited visibility. If you needed money to move instantly, you paid a premium. There was no middle ground. Stablecoins eliminate this tradeoff. They are instant, 24/7, low-cost, and programmable. While early adoption was driven by cross-border arbitrage, regulatory standardization in 2025 has turned US Dollar stablecoins into a viable alternative rail for domestic money movement. ## How ACH, wires, and stablecoins compare To understand the value of stablecoins, we have to look at the "plumbing" we currently use. ACH and Fedwire handle domestic US transfers. For cross-border payments, businesses typically rely on SWIFT and correspondent banking, which are slow and expensive. Stablecoins work in both contexts, offering advantages over legacy rails domestically and internationally. ### ACH (Automated Clearing House) **ACH** is a batch-based interbank system offering same-day or T+2 settlement. Banks collect transactions and process them at specific cutoff times. The hidden cost is the settlement gap: ACH is not final immediately, and transactions can be reversed days after you release goods. ### Wires (Fedwire) **Wires (Fedwire)** are the US domestic real-time gross settlement system. Messages settle individually and instantly at the Federal Reserve. The hidden cost is price and manual overhead. Wires are expensive and often require manual intervention. Fedwire operates 22 hours per day, Monday through Friday. ### Stablecoins (USDC/USDT) **Stablecoins** are digital representations of fiat currency issued on blockchain networks, backed 1:1 by liquid assets like US Treasury Bills held in segregated accounts. They function as a T+0 settlement layer, moving value instantly outside traditional banking hours. The hidden cost is that bank and ERP support is still early, and there is a learning curve. Stablecoins combine wire-level finality with ACH-level cost. Two additional benefits worth noting: - **24/7 settlement.** Merchants can receive payment from their PSP as soon as their customer completes a transaction. - **Programmable transactions.** Corporations could issue smart invoices where payment is held in escrow and released upon delivery confirmation. ## Choosing the right payment rail For CFOs, the opportunity is selecting the optimal rail for each need based on cost, speed, and finality risk: |Feature|ACH|Wires (Fedwire)|Stablecoins| |-|-|-|-| |**Cost**|Low (less than $0.50)|High ($3 - $5 domestic $40+ international)|Negligible (less than $0.01)| |**Speed**|T+1 to T+2|Instant (business hours only)|Instant (24/7/365)| |**Finality**|Reversible (clawback risk)|Final|Final| |**Operating hours**|Business hours with cutoffs|22 hours, M-F|24/7/365| |**Programmability**|None|None|High (smart contracts, escrow)| |**Best for**|Payroll, subscriptions, routine payments|High-value treasury, legal settlements, cross-border|Cross-border, mass payouts, emergency liquidity| **ACH** remains essential for high-volume, routine payments where timing is not critical. Low cost is unmatched for payroll and recurring billing. **Wires** are necessary for high-value transactions requiring absolute finality within business hours. The cost is justified for large treasury transfers and legal settlements. **Stablecoins** are most valuable where the speed-cost tradeoff matters most: cross-border transfers (bypassing SWIFT complexity), mass payouts (eliminating $15-$40 fees on hundreds of daily payments), and emergency liquidity (instant settlement outside banking hours). ## The stablecoin sandwich: Using stablecoins without holding crypto A common misconception is that using stablecoins means holding crypto on the balance sheet. It does not. To most banks, stablecoins are simply another rail to support—this integration is driven by client demand. Financial institutions adapt to where money flows. If corporate clients demand instant settlement, banks build the bridges. The GENIUS Act (2025) has de-risked integration, allowing correspondent banks to offer stablecoin services within existing treasury platforms. For most businesses, the practical model is the stablecoin sandwich. You start with fiat and end with fiat. The stablecoin moves the value. - **Fiat in.** Your ERP triggers a payment. Your bank debits your USD account and converts it to a regulated stablecoin like USDC. - **Transfer.** The stablecoin moves over a blockchain network in 2-6 seconds, costing fractions of a penny. - **Fiat out.** The recipient's provider converts it back to USD (or local currency) and deposits it into their bank account. The result: wire-speed settlement at ACH-level cost, without either party managing keys or worrying about volatility. ## Which suppliers will accept stablecoins? A common objection: "I cannot ask my paper-supply vendor to open a Coinbase account." You do not have to. The sandwich model ensures backward compatibility via virtual accounts. Three supplier types see immediate value, with examples: - **International manufacturers.** You pay a factory in Vietnam. They want USD, but your bank charges $45 and takes days. Using a stablecoin rail, funds arrive in their local USD account in minutes. They ship faster; you save the wire fee. - **High-velocity affiliates.** You need to pay 500 marketing affiliates $200 each. A $15 wire fee on a $200 payment is a 7.5% tax. Stablecoins allow you to batch these payments for pennies. - **Emergency purchases.** It is Friday at 6 PM. You need rush inventory for the weekend. Banks are closed. Blockchains run 24/7. You settle instantly; the vendor releases goods Friday night. ## Get started with stablecoins Stablecoins are now regulated, bank-supported, and increasingly accessible through existing treasury platforms. Whether you're just starting to explore stablecoins or already use them in your payment stack, we can help you get started: --- ## AllUnity's Swiss franc stablecoin CHFAU is now live on Tempo > Source: https://tempo.xyz/blog/allunity-chfau-live-on-tempo/ > Language: en **_AllUnity's CHFAU, a regulated Swiss franc stablecoin, is now live on Tempo—giving businesses a trusted CHF instrument for cross-border payments, treasury operations, and regulated settlement flows onchain._** [_Explore the Tempo ecosystem_](https://tempo.xyz/ecosystem) [AllUnity](https://allunity.com/) is a regulated European stablecoin issuer and licensed e-money institute, established by DWS, Flow Traders, and Galaxy. CHFAU is AllUnity's MiCAR-compliant Swiss franc stablecoin. The first Swiss franc stablecoin live on Tempo, it’s built for institutions that need the efficiency of onchain settlement without giving up regulatory grounding. ## The case for Swiss franc liquidity onchain Switzerland and the EU trade [more than CHF 1 billion](https://allunity.com/articles/why-a-swiss-franc-stablecoin-and-why-now) every working day. Most of that money still moves on infrastructure that settles in days, only operates during banking hours, and adds cost at each intermediary. Access to a regulated, onchain Swiss franc instrument has been limited. CHFAU brings trusted CHF liquidity onto rails that settle in seconds, around the clock. For businesses operating between Switzerland and the rest of Europe, that means faster settlement, lower cost, and access to Swiss francs that isn't tied to banking hours. ## What businesses can do with CHFAU on Tempo CHFAU supports a range of institutional payment flows, including: - 24/7 cross-border settlement between Switzerland and the EU - Real-time corporate treasury operations - Regulated settlement between financial institutions Learn more at [https://allunity.com/chfau](https://allunity.com/chfau). ## Why Tempo Tempo is a payments-first Layer 1 blockchain incubated by Stripe and Paradigm, built for the requirements of enterprise payment operations. Transactions finalize in under a second with deterministic settlement, so payment operators get the same settlement certainty they expect from existing financial systems. Each transfer can carry structured metadata for invoice numbers and cost centers, which makes reconciliation against existing treasury and accounting systems straightforward. For institutions moving regulated currency at scale, that combination of settlement certainty and clean reconciliation is what makes onchain settlement practical. > "By bringing CHFAU to Tempo, we are enabling faster and more efficient access to Swiss franc-denominated liquidity for a broad range of use cases, from payments to treasury operations. Together with Tempo, we are delivering infrastructure that combines the stability of traditional finance with the efficiency of blockchain technology." > > — Peter Großkopf, CTO and CCO, AllUnity ## What's next AllUnity is expanding its lineup of regulated European currency stablecoins, with new currencies becoming available on Tempo as they launch. For businesses integrating stablecoins into cross-border payments, embedded finance, and institutional settlement flows, that means a growing set of compliant local-currency instruments available on Tempo. > "We're excited for AllUnity to bring CHFAU, a regulated Swiss franc stablecoin, to Tempo. Businesses on the network now have a trusted CHF instrument to settle cross-border payments, treasury flows, and regulated settlement in, natively onchain." > > — Eric Kang, GTM, Tempo ## Get started If you're evaluating stablecoins for cross-border payments, treasury operations, or institutional settlement, [get in touch](https://tempo.xyz/contact). [Browse the ecosystem](https://tempo.xyz/ecosystem) · [Learn about stablecoins](https://tempo.xyz/learn/what-are-stablecoins) --- ## Anchorage Digital adds custody support for assets on Tempo > Source: https://tempo.xyz/blog/anchorage-digital-adds-custody-support-for-ousd-on-tempo/ > Language: en **_Anchorage Digital Bank, N.A. now supports custody, withdrawals, and transfers for assets on Tempo. This gives institutions an institutional custody path for stablecoins on the network, including OUSD, USDT0, USDC.e, and pathUSD, and TIP-20 support designed to shorten the path for additional assets as they go live. If you are an issuer or institution evaluating Tempo, [get in touch with the Tempo team](/contact)._** As more institutions move stablecoins and tokenized assets into production, custody becomes part of the adoption path. Institutions need more than a network that can move value quickly. They need assets held under controls that their risk, audit, and compliance teams already understand, and custody partners that can support new networks without requiring new operating models. Anchorage Digital Bank helps bridge this gap for institutions by rolling out custody support for assets on Tempo through its qualified custody entity. Institutions can now custody, withdraw, and transfer dollar-denominated stablecoins on Tempo through Anchorage Digital Bank, including OUSD, USDT0, USDC.e, and pathUSD. ## A custody path for institutions using Tempo Tempo is designed for stablecoin payments at enterprise scale, with near-instant settlement, no re-orgs, sub-cent fees, and fees paid in stablecoins. For institutions, those network-level features matter when they connect to operational requirements: treasury controls, asset custody, reconciliation, approvals, and auditability. Custody support from Anchorage Digital Bank helps make supported Tempo assets easier to hold and use within existing institutional frameworks. > "Stablecoin networks are being built for institutional scale, and institutions need a custodian that can meet them there. Supporting Tempo means clients can hold Tempo-native assets at a federally chartered bank, under the same controls they apply to the rest of their portfolio." > > **Nathan McCauley, CEO and Co-Founder, Anchorage Digital** ## TIP-20 support shortens the path for new assets Anchorage Digital has also implemented support for TIP-20, Tempo’s token standard for stablecoins and payment assets. Tempo is designed for a growing set of stablecoins and tokenized assets. With TIP-20, Anchorage Digital Bank can extend its custody solution to new tokens issued on Tempo on a significantly shorter timeline, potentially within days once standard onboarding and approval requirements are complete. For issuers, that means custody can be part of the launch path earlier. For institutions, it means new Tempo assets can be evaluated on their merits without waiting for custody infrastructure to catch up one token at a time. ## What this enables next As more issuers bring assets to Tempo, institutional custody will become an important part of distribution, adoption, and day-to-day use. Anchorage Digital’s support creates a foundation for that next phase. Issuers get a clearer path to institutional custody. Allocators get a custody option inside a familiar control environment. Enterprises evaluating Tempo get one more piece of the operational stack in place. > "As more institutions use Tempo to move stablecoins at scale, Anchorage Digital’s support gives them a custody option inside a federally chartered bank, within the compliance requirements they already operate under. With this integration, issuers can have an institutional-grade custody path for new stablecoins as soon as they go live on the network." > > **Dan Romero, Chief Business Officer, Tempo** Tempo is built for stablecoin payments at scale. Custody support from Anchorage Digital Bank helps institutions use supported assets on Tempo with the standards they already require. If you are an issuer, fintech, or institution exploring assets on Tempo, get in touch with us at [partners@tempo.xyz](mailto:partners@tempo.xyz). --- ## ARQ is building cross-border payment infrastructure on Tempo > Source: https://tempo.xyz/blog/arq-is-building-cross-border-payment-infrastructure-on-tempo/ > Language: en **_ARQ serves over 2 million customers across Latin America with dollar and euro accounts, investing, and cross-border payments, processing more than $10 billion in annualized transaction volume. Now ARQ is moving its settlement infrastructure onto Tempo._** [_Learn more in the full case study_](https://tempo.xyz/customer-stories/arq) Stablecoins already power the infrastructure behind ARQ's cross-border payment engine. More than 2 million customers across Mexico, Colombia, Argentina, and Brazil use the platform to hold and move dollars and euros, invest in international markets, and spend worldwide. ARQ processes more than $10 billion in annualized transaction volume, all settled on stablecoin infrastructure that users never see. As ARQ expands into investing, credit, and everyday spending, the demands on the settlement layer grow. Transaction volume compounds, each new product adds complexity, and the cost and reliability of the infrastructure underneath directly shapes what ARQ can build next. At this scale, the settlement layer is a strategic decision. ## ARQ and Tempo [ARQ](https://www.arqfinance.com/en-MX) is moving its cross-border payment infrastructure onto Tempo, bringing settlement for its core products onto a chain purpose-built for high-volume stablecoin payments. Sub-second deterministic finality means every transaction settles with the certainty that users and regulators expect. And built-in compliance and reconciliation tooling replaces custom engineering. The shift is invisible to ARQ's customers. What changes is the infrastructure underneath: faster, cheaper, and designed for the throughput ARQ's growth demands. > From day one, Tempo understood what we were building, moved with urgency, and offered the infrastructure, product vision, and long-term alignment we needed to scale ARQ. > > — Zach Garman, Co-founder and CPO, ARQ ## Why Tempo Tempo is purpose-built for institutional payments. For a platform processing $10 billion a year in stablecoin-settled transactions, several capabilities made the difference. Gas abstraction lets ARQ pay transaction fees in any USD-denominated stablecoin rather than a volatile native token, keeping the entire operation denominated in dollars. Protocol-level compliance controls, including allowlists, blocklists, and freeze-and-pause capabilities, are built directly into the chain. Native memo fields compatible with ISO 20022 make reconciliation against existing systems straightforward. And dedicated payment lanes guarantee throughput regardless of other network activity. Tempo's product roadmap also aligns with where ARQ is headed: on-chain FX, privacy features, and native settlement capabilities that will matter as the platform scales across more markets and product lines. ## What this means For a fintech already processing $10 billion a year on stablecoin infrastructure, building on Tempo is not an experiment. It is the next step in ensuring the settlement layer keeps pace with product ambition. Over time, the same infrastructure opens a path to native on-chain FX, direct merchant settlement, and programmable payment flows as ARQ's product suite grows. For the 2 million customers who already use ARQ across the Americas, the result is a platform where the infrastructure underneath is as modern as the product on top. [Read the full case study](https://tempo.xyz/customer-stories/arq) --- ## Tempo plans to support BlackRock's new GENIUS-compliant money market fund BRSRV > Source: https://tempo.xyz/blog/blackrock-brsrv/ > Language: en **_The final prospectus for BlackRock's BRSRV names Tempo as a supported blockchain for OnChain Shares. BRSRV is a proposed U.S. government money market fund with shares digitally represented on public blockchain networks. For eligible investors, it will connect regulated cash management to the same network used for onchain payments and settlement._** [_Read the prospectus_](https://www.sec.gov/Archives/edgar/data/844779/000119312526327203/d283147d485bpos.htm). Tempo plans to support BlackRock's BRSRV, a GENIUS-compliant money market fund with a blockchain-based share class, bringing regulated cash management closer to onchain payments and settlement. BlackRock Advisors will manage BRSRV. Securitize Transfer Agent will maintain the fund's official shareholder record through a permissioned system connected to Tempo and other supported public blockchains. OnChain Shares will be digitally represented on those networks, while transfers remain limited to approved wallets and are subject to eligibility, KYC and AML review, and the fund's transfer restrictions. BRSRV seeks current income while preserving liquidity and stability of principal. The fund will invest in cash, short-dated U.S. Treasury instruments, and overnight repurchase agreements secured by U.S. Treasury instruments. It seeks to maintain a stable $1.00 net asset value. ## A regulated cash-management product on onchain rails The prospectus states that the fund intends to operate so its OnChain Shares are eligible reserve assets for permitted payment stablecoin issuers under the GENIUS Act. That treatment remains subject to implementing rules and regulatory interpretation. For institutions using Tempo for payments, treasury management, and settlement, BRSRV can connect a regulated cash-management product to the same public network where balances can move onchain. This is a concrete step toward bringing regulated financial products and programmable payment activity into the same operating environment while preserving the investor controls expected of a registered fund. If you’re building payments products and want to explore integrating BRSRV on Tempo, [get in touch](https://tempo.xyz/contact/). **_Important information_** _BRSRV shares are securities, not stablecoins. The fund is not FDIC insured or bank guaranteed, may lose value, and cannot guarantee a stable $1.00 net asset value. This material is for informational purposes only and is not an offer, a recommendation, or investment advice. Investors should review the final prospectus and determine whether they meet its eligibility, minimum-investment, KYC, AML, and wallet requirements._ --- ## Now live on Tempo: CADD, Canada's first CAD-backed stablecoin issued by a financial institution > Source: https://tempo.xyz/blog/cadd-now-live-on-tempo/ > Language: en **_CADD, a payment stablecoin backed 1:1 by Canadian dollars, is now live on Tempo. Issued by Tetra Trust Company via its agent CAD Digital Inc., CADD is the first Canadian dollar stablecoin issued by a regulated financial institution._** [_Explore the Tempo ecosystem_](/ecosystem) CADD has received regulatory approval from Alberta Treasury Board and Finance, a national first for digital asset infrastructure in Canada. It enables Canadian dollars to move on blockchain rails under a financial services regulatory framework, and it is now live on Tempo. ## Why CADD matters Canada clears roughly $424 billion per business day, with retail payments still largely reliant on batch-based infrastructure first implemented in the 1980s. The Canadian dollar is one of the most traded currencies globally, yet there has not been a widely adopted, production-scaled, CAD-denominated digital asset payment rail. Stablecoin adoption to date has been dominated by US dollar-denominated assets, leaving Canadian businesses and institutions without a competitive domestic option. CADD is designed to address that need. All funds used to mint CADD are held in trust and dedicated exclusively to redemption, aligning the program with institutional expectations around asset protection, transparency, and compliance. The model is built for banks, payment service providers, and fintech platforms that require regulatory clarity from the outset. CADD launches with institutional scale from day one, backed by a consortium of leading Canadian financial institutions and technology companies including [Tetra Digital Group](https://tetradg.com/), Urbana Corporation, Wealthsimple, Purpose Unlimited, Shakepay, ATB Financial, National Bank of Canada, and Shopify. ## What CADD enables on Tempo CADD brings Canadian dollars onto continuous, programmable networks with near-instant settlement finality. For Canadian institutions, that unlocks use cases that were previously difficult and impractical to execute on existing Canadian rails: - 24/7 cross-border settlement - Real-time corporate treasury transfers - Programmable payments for marketplace payouts - Direct settlement between fintech partners without correspondent banking delays "This milestone reflects the strong collaboration with Alberta's government, industry partners and regulators to bring a compliant and scalable Canadian-dollar stablecoin to market," said Didier Lavallée, Founder and CEO of Tetra Digital Group. "CADD is issued by a regulated financial institution, with reserves held in Canada and compliance built in from day one by a firm with Canada's longest track record of operating regulated digital asset infrastructure. It enables faster and more efficient movement of Canadian dollars on-chain within a structure institutions recognize." ## About Tetra Digital Group Tetra Digital Group is Canada's leading institutional digital technology and financial services provider, parent company of Tetra Trust, Tetra Unity, and CAD Digital. Tetra Trust was Canada's first regulated digital asset custodian and supported the first staking-enabled Ethereum and Solana ETFs in Canada. ## Get started If you're evaluating stablecoins for global payments, treasury operations, or settlement, [get in touch](https://tempo.xyz/contact). --- ## Coinbase Wrapped BTC is now live on Tempo, powered by Chainlink CCIP > Source: https://tempo.xyz/blog/cbbtc-on-tempo/ > Language: en **_Coinbase Wrapped BTC (cbBTC) is now live on Tempo, the payments-first Layer 1 blockchain incubated by Stripe and Paradigm, made available through Chainlink's Cross-Chain Interoperability Protocol (CCIP). Enterprises and institutions building on Tempo can now use Bitcoin alongside stablecoin payments in a single environment._** We're excited to announce that Coinbase Wrapped BTC (cbBTC) is now live on Tempo. The integration is powered by Chainlink CCIP, an industry-leading oracle platform and exclusive bridging infrastructure for Coinbase's wrapped assets. There is currently $5B+ of cbBTC in circulation, and with this integration, Tempo is bringing Bitcoin, the world's largest cryptocurrency, to its ecosystem for the first time. Now, enterprises and institutions have access to cbBTC on Tempo, including in DeFi use cases for earn products, lending markets, BTC-backed credit, trading, and more. > cbBTC gives the Tempo ecosystem access to Bitcoin, the world's largest cryptocurrency and a premier collateral asset, via Chainlink CCIP. This access unlocks the next wave of innovation on Tempo, and we are excited to see how the community leverages it. > > — Lukas Staniszewski, Director, Product Management, Coinbase ## How it works ![cbBTC on Tempo diagram](/blog/cbbtc-on-tempo-diagram.png) cbBTC is made available to the Tempo ecosystem via Chainlink's Cross-Chain Interoperability Protocol (CCIP). Tempo selected CCIP because it provides the institutional-grade security it needs for advanced institutional use cases. Unlike other bridging solutions, every CCIP bridge lane is secured by a minimum of 16 independent, security-reviewed node operators to provide redundant validation of every transaction. CCIP also provides additional risk management controls, including native rate limits that act as circuit breakers. > We're excited to securely bridge Coinbase's cbBTC to the Tempo ecosystem through Chainlink CCIP. This is a massive win for institutions who want to use the world's largest digital asset in the Tempo ecosystem. Through Chainlink's secure-by-default infrastructure, Tempo is unlocking Bitcoin liquidity for its ecosystem providing institutions the reliable foundation they need to participate in DeFi. > > — Johann Eid, Chief Business Officer at Chainlink Labs The combination of CCIP's security architecture and Tempo's high-throughput payments infrastructure gives enterprises a production-grade path to use cbBTC as collateral for lending, access deep liquidity on DEXs, and earn returns on BTC balances. > At Tempo, we're seeing growing demand from enterprises looking to bring DeFi capabilities into their payments products and create more value for their users. We're excited to partner with Coinbase and Chainlink to bring cbBTC to Tempo, giving companies access to wrapped Bitcoin for DeFi use cases across earn products, lending markets, credit, trading, and more. > > — Dan Romero, GTM, Tempo --- **About Tempo** Tempo is a payments-first Layer 1 blockchain. Incubated by Stripe and Paradigm, and developed in partnership with leading fintechs and Fortune 500s, Tempo enables high-throughput, low-cost global transactions for any use case. Companies including DoorDash, Shopify, Visa, Nubank, and OnePay are building on Tempo across cross-border payments, institutional settlement, embedded finance, treasury operations, agentic payments, and more. Learn more at [tempo.xyz](https://tempo.xyz). **About Chainlink** Chainlink is the industry-standard oracle platform bringing the capital markets onchain and the market leader powering the majority of decentralized finance (DeFi). The Chainlink stack provides the essential data, interoperability, compliance, and privacy standards needed to power advanced blockchain use cases for institutional tokenized assets, lending, payments, stablecoins, and more. Since inventing decentralized oracle networks, Chainlink has enabled tens of trillions in transaction value and now secures the vast majority of DeFi. Many of the world's largest financial services institutions have also adopted Chainlink's standards and infrastructure, including Swift, Euroclear, Mastercard, Fidelity International, UBS, S&P Dow Jones Indices, FTSE Russell, WisdomTree, ANZ, and top protocols such as Aave, Lido, GMX, and many others. Chainlink leverages a novel fee model where offchain and onchain revenue from enterprise adoption is converted to LINK tokens and stored in a strategic Chainlink Reserve. Learn more at [chain.link](https://chain.link). **About Coinbase** Coinbase (NASDAQ: COIN) is on a mission to increase economic freedom in the world. The most trusted crypto platform, Coinbase stores more digital assets than any other company and is building the everything exchange: one place to access crypto, equities, derivatives, prediction markets, and more. Coinbase serves consumers through its suite of financial apps, institutions through Coinbase Prime, and developers through the Coinbase Developer Platform. Every experience runs on Coinbase's full-stack platform powering the future of finance: secure custody, deep exchange liquidity, stablecoin infrastructure, and global settlement rails, all built on a decade-plus foundation of security and compliance. --- ## Chainlink Data Feeds are now live on Tempo > Source: https://tempo.xyz/blog/chainlink-data-feeds-on-tempo/ > Language: en **_Chainlink Data Feeds are live on Tempo, giving businesses, institutions, and developers industry standard onchain pricing infrastructure. Applications can use these feeds to value collateral, compare FX reference rates, monitor risk, and automate financial workflows while eliminating the need to build and maintain custom oracle infrastructure._** [_Explore the supported feeds and contract addresses._](https://docs.chain.link/data-feeds/price-feeds/addresses?network=tempo&page=1) ## Market data for financial applications on Tempo Tempo is purpose-built for stablecoin payments at scale. Moving stablecoins is one part of a financial workflow. Businesses also need to determine what assets are worth, whether collateral is sufficient, how an FX quote compares with the market, and when a treasury position has moved outside policy. Those decisions depend on external market data that a blockchain cannot generate on its own. [Chainlink Data Feeds](https://chain.link/data-feeds) bring that data onchain for applications on Tempo. Chainlink supplies the data input, applications apply their own business logic, and Tempo provides the execution and onchain settlement layer. ## What businesses can do with Data Feeds on Tempo ### Manage collateral and credit New [Earn](/earn/) applications can use Data Feeds to value collateral, set borrowing limits, and monitor position health. For enterprises, this can support products that let stablecoin balances serve as collateral for liquidity and working capital needs. ### Add guardrails to FX and liquidity workflows Treasury and payment applications can use reference rates to compare quotes, value positions in a common reporting currency, and apply deviation or slippage limits. The feeds provide reference data, and the application on Tempo handles conversion and settlement. ### Automate treasury and asset risk controls Applications can monitor the market value of stablecoins with supported feeds, then apply policies for collateral top-ups, rebalancing, or exposure limits. The same inputs can support tokenized-asset products that need reference values for pricing, collateral, and risk management. For institutions, this creates a common onchain reference layer for applications that need to value assets, monitor collateral, apply risk controls, or reconcile positions across currencies. ## How Chainlink Data Feeds work Chainlink Data Feeds aggregate market data from multiple data providers. Independent Chainlink node operators collect and aggregate observations, then publish tamper-resistant reports that smart contracts can verify on Tempo. This reduces reliance on a single exchange, data source, or node. For developers on Tempo, the practical benefit is an industry standard data layer and no custom oracle infrastructure to build and maintain. “Payments are the starting point for stablecoins on Tempo. Financial applications built around those payments need dependable market data to value collateral, compare exchange rates, and manage risk. Chainlink Data Feeds give developers reliable data infrastructure for those applications,” said Eric Kang, GTM at Tempo. “We’re excited to see Tempo adopt the Chainlink data standard to power institutional-grade stablecoin use cases. Tempo is building a high-performance ecosystem for stablecoins, and Chainlink Data Feeds give its developers the reliable market data required to launch secure financial applications, expand the use of stablecoins as collateral, and accelerate their utility across onchain markets,” said Thodoris Karakostas, Director, Global Partnerships at Chainlink Labs. ## Available now Chainlink Data Feeds are live on Tempo. Developers can review the supported feeds, contract addresses, and integration guidance in [Chainlink’s documentation](https://docs.chain.link/data-feeds/price-feeds/addresses?network=tempo&page=1). If you’re evaluating stablecoin financial products on Tempo, [get in touch](/contact/). --- ## Coastal Bank partners with Tempo to build stablecoin-settled cross-border payments > Source: https://tempo.xyz/blog/coastal-bank-partners-with-tempo-to-build-stablecoin-settled-cross-border-payments/ > Language: en **_Coastal, one of the leading banking-as-a-service platforms in the US, is building stablecoin-settled cross-border payment infrastructure on Tempo for its fintech clients._** [_Learn more in the full case study_](https://tempo.xyz/customer-stories/coastal) Cross-border payments remain one of the most friction-heavy workflows in financial services. Transfers route through multiple correspondent banks, take days to settle, require pre-funded accounts, and operate only during banking hours. For banks that power fintech products at scale, those limitations get passed directly to their partners and end customers. Coastal Financial Corporation (Nasdaq: CCB) is building the infrastructure to change that. Through its [CCBX](https://ccbx.com/) division, Coastal provides card sponsorship, lending, deposit, and digital financial service infrastructure to fintech companies nationwide, with approximately $4.7 billion in total assets. Now, Coastal is extending that platform with stablecoin-settled cross-border payments built on Tempo. ## Coastal and Tempo Coastal and Tempo are building a cross-border payment corridor that keeps existing compliance infrastructure intact while replacing the settlement layer with stablecoins on Tempo. Messaging, KYC/AML screening, and bank-to-bank confirmations stay in place. What changes is how the value moves: instead of routing through correspondent banks over several days, funds settle on Tempo in minutes using USD stablecoins, at a fraction of the cost. Both sides of each transaction are known, regulated financial institutions with an existing relationship. Wallets are whitelisted. The flow is permissioned end-to-end. This is the kind of implementation that lets a bank adopt stablecoin settlement without rebuilding its compliance stack. > Our partners are continually raising the bar for what modern financial services should look like: faster, more flexible, and always available. By integrating stablecoin capabilities and Tempo's blockchain-based infrastructure into our platform, we're enabling our partners to build more seamless, efficient experiences for their customers while staying grounded in the trust and reliability of the banking system. > > — Brian Hamilton, President of CCBX at Coastal ## Why Tempo Tempo is purpose-built for institutional payments. For a use case like cross-border settlement between regulated banks, several capabilities made the difference. Tempo Zones provide private stablecoin payments where only the zone operator and parties to a transaction see the details, with selective disclosure to regulators. Institutions get confidentiality without giving up access to shared liquidity across the network or the ability to meet their compliance obligations. Dollar-denominated fees mean institutions pay transaction costs in stablecoins rather than a volatile native token, keeping operational budgets predictable and avoiding uncertain capital treatment. Protocol-level compliance controls, including allowlists, blocklists, and freeze-and-pause capabilities, are built directly into the chain. Native memo fields support structured payment data compatible with ISO 20022, the messaging standard used across global institutional payments. > What was particularly interesting about Tempo was here's a partner focused on a payments-first use case and focused on how we can enable the next generation of money movement. Faster payments, more efficient payments, and safer and more secure payments. > > — Ryan Hall, Chief Product Officer at Coastal ## What this means Cross-border payments are Coastal's starting point on Tempo, not the ceiling. The infrastructure the bank is building, combining institutional messaging, compliance-native controls, and stablecoin settlement, is a foundation for any payment corridor that needs to move faster and cost less. Coastal is also exploring a broader digital asset strategy that includes support for corporate accounts, wallet funding, treasury management, and interoperability with fiat rails. For the broader market, a publicly traded, regulated US bank building stablecoin settlement infrastructure signals where institutional adoption is heading. The question for most banks is no longer whether stablecoins will play a role in payments, but how to get started safely. [_Read the full case study_](https://tempo.xyz/customer-stories/coastal) --- ## Stablecoin Compliance and Regulatory Controls on Tempo > Source: https://tempo.xyz/blog/compliance-controls/ > Language: en **_Compliance is a prerequisite for institutional adoption of stablecoins. Tempo provides native compliance controls for stablecoin issuers, wallet providers, and enterprises to meet their regulatory requirements. Work with our compliance partners, including [Blockaid](https://www.blockaid.io/), [Chainalysis](https://www.chainalysis.com/), [Sardine](https://www.sardine.ai/), and [TRM](https://www.trmlabs.com/solutions/compliance-360), or start building with [our docs](/developers/docs/protocol/tip20/overview)._** Tempo was designed with input from leading financial institutions, who emphasized that compliance is a core requirement. Stablecoin issuers, banks, and fintechs operate under strict regulatory frameworks and supervision. For these institutions, compliance cannot be an afterthought. Tempo's design reflects these requirements. Rather than forcing institutions to build custom applications and smart contracts for basic compliance functions, Tempo provides these capabilities natively. Native controls mean consistent behavior and a full audit trail. ## Design principles For institutions, code must support the law. When designing Tempo's compliance capabilities, we focused on four priorities. - **AML and sanctions.** Financial institutions must comply with AML and sanctions requirements, including the ability to freeze accounts and block transactions when addresses are flagged. - **Separation of responsibilities.** Stablecoin issuers and custodians have different regulatory obligations. Issuers care about token supply integrity and controlling token circulation. Custodians care about their KYC perimeter and protecting clients from fraud. - **Operational controls.** Institutions need tools to respond to emergencies and take corrective action. Every action must be logged, creating audit trails that are complete, immutable, and readily available for examinations. - **Remediation.** When funds are proven to be stolen or sent to a sanctioned entity, institutions need a path to recovery or seizure that satisfies legal requirements. > As a high-throughput, low-cost base layer designed specifically for payments, Tempo has the potential to unlock onchain global payments at scale. We’re proud to partner with Tempo and its growing ecosystem to provide the risk management and compliance capabilities needed to support secure and trusted onchain payments. > > — Ankush Sharma, Head of Blockchain Ingestion, TRM Labs ## How compliance controls work on Tempo Compliance controls on Tempo consist of three components: TIP-20 functions, Tempo Policies, and Transfer Memos. ![TIP-20 functions](/images/blog/-__19_.png) ### TIP-20 functions Tempo's native token standard, [TIP-20](/developers/docs/protocol/tip20/overview), includes built-in functions for emergency response and regulatory compliance. All TIP-20 stablecoins on Tempo support three functions: pause and unpause to halt and resume transfers, and burn to remove tokens from blacklisted addresses. Institutions can delegate access to these functions across teams using [role-based access controls](/developers/docs/protocol/tip20/overview#role-based-access-control-rbac), providing a full onchain audit trail. ![Tempo Policies](/images/blog/-__20_.png) ### Tempo Policies [Tempo Policies](/developers/docs/protocol/tip403/overview) complement TIP-20 functions by defining transfer rules at the token level. Tempo supports two policy types: allowlist policies and blacklist policies. These policies define which addresses can or cannot interact with a token. - **Token-level policies** are managed by stablecoin issuers and apply globally across all holders. Policies can be shared across multiple tokens, enabling consistent enforcement. - Tempo will soon support **account-level policies**, enabling separation of responsibilities between stablecoin issuers and custodial wallet operators. These will be managed by institutions operating custodial wallets and will apply to individual accounts, including send and receive policies to control which addresses an account can transact with, and token policies to control which tokens an account can receive. ![Transfer Memos](/images/blog/-__21_.png) ### Transfer memos [Transfer memos](/developers/docs/protocol/tip20/overview#transfer-memos) enable Travel Rule compliance by allowing senders to attach references to messages exchanged via industry protocols. Tempo natively supports 32-byte transfer memos attached to any transfer. These can reference IVMS101 or SWIFT messages. Receivers can use these references to match onchain transfers with the corresponding compliance data. > In an exam, regulators don’t ask whether you had alerts. They ask what you did about them. Who had authority to act? How quickly did they move? Can you show a clear record of the decision? Compliance teams carry that accountability. If enforcement sits outside the asset layer, response slows down and risk compounds. Controls have to live where the value moves. That’s what makes them real. > > — Soups Ranjan, CEO & Co-Founder, Sardine ## How institutions use compliance controls Tempo's compliance controls address several regulatory and operational requirements: - **Sanctions and freezing.** Blacklist policies allow issuers to prevent sanctioned addresses from interacting with a stablecoin. When an address is added to the blacklist, it can no longer send or receive tokens, effectively freezing the funds in place. - **Custodial wallet restrictions.** Once account-level policies are available on Tempo, custodians will be able to restrict a wallet to a specific set of approved addresses, or limit which tokens a wallet can hold. For custodians, that means the ability to enforce KYC-based allowlists, block sanctioned addresses, and reject spam tokens, all without relying on the token issuer. - **KYC-gating.** Allowlist policies enable stablecoin issuers to restrict transfers to users who have completed KYC verification. Only addresses on the allowlist can send or receive the token, ensuring that the stablecoin circulates only among verified users. - **Asset recovery.** When regulators or law enforcement request the seizure of funds, issuers can blacklist an address and burn tokens from it. This maintains a clear onchain record while satisfying legal requirements. - **Emergency response.** Issuers can halt all transfers of a token in response to a security incident, regulatory request, or operational emergency using the pause function. Once the situation is resolved, the unpause function resumes transfers. > At Blockaid, we are excited to partner with Tempo to bring security & compliance to Tempo’s ecosystem. Blockaid offers a comprehensive real-time security platform that protects institutions and consumers alike from three onchain risk vectors - security vulnerabilities, sanctions / AML risk, and fraudulent transactions. > > — Ido Ben-Natan, Co-founder & CEO, Blockaid ## Start building on Tempo Whether you are issuing stablecoins or building custodial wallets, we can help you get started: ### Learn the fundamentals Visit the Learn section of the Tempo documentation to understand stablecoins, how they work, and the payment use cases they enable. [Learn](/learn) ### Start building If you're familiar with blockchain development, head to our docs to connect to Tempo, access test funds, download SDKs, and start building with Tempo Transactions. [Read the docs](/developers/docs/protocol/tip20/overview) ### Move faster with partners You can also work with our infrastructure partners including Crossmint, Fireblocks, Privy, and Turnkey, who are rolling out Tempo Transactions and can help accelerate your development timeline. Visit the Ecosystem section to explore Tempo's growing network of partners. [Explore ecosystem](/ecosystem) _For guidance on implementing compliance controls for your use case, [reach out](https://tempo.xyz/contact) to our Enterprise Team._ --- ## Stablecoins for Corporate Treasury > Source: https://tempo.xyz/blog/corporate-treasury/ > Language: en **_Stablecoins settle instantly, 24/7, across borders. For treasury teams, that means less trapped cash and faster access to working capital. Below is a practical guide on how global companies can integrate stablecoins to make their treasury operations more efficient. If you're a team evaluating stablecoins for global treasury management,_** [_get in touch_](https://tempo.xyz/contact) with our Enterprise Team. Stablecoins and tokenized deposits are gaining traction in corporate treasury operations. If your company operates globally, you're familiar with the constraints: money moves slowly across borders. A payment to a subsidiary might take days to clear. Cash collected in one region sits idle over the weekend while banks are closed. Exchange rates shift, fees accumulate, and your finance team operates on stale data. This is where stablecoins come in, offering real-time visibility into global cash positions, instant settlement between entities, and the ability to move dollars across borders at any time of day. ## How stablecoins simplify corporate treasury management Stablecoins address a common problem: cash sitting idle offshore while waiting for correspondent banks to settle payments, particularly over weekends or through slower local payment rails. They enable instant, 24/7 dollar-based money movement across currencies, including those poorly served by traditional correspondent banking. Some also offer yield-bearing capabilities. Large multinational companies are already [using stablecoins](https://techcrunch.com/2025/01/31/stablecoins-are-finding-product-market-fit-in-emerging-markets/) to move dollars between subsidiaries and offshore offices, improving cash efficiency and reducing settlement risk. One in four CFOs [expect](https://ctmfile.com/story/corporate-treasurys-2025-crypto-turning-point-ignited-by-stablecoins) their treasury departments to engage with cryptocurrencies within two years. The practical questions: How do stablecoins fit into existing treasury operations? And how do they align with cost, risk, and resilience frameworks? ## The cost of settlement delays For companies operating across multiple jurisdictions, correspondent banking can be complex. Treasury teams manage dozens of banking relationships, currencies, and cut-off times across time zones. This creates three problems: - **Higher borrowing costs.** From trapped cash that cannot be deployed efficiently. - **Suboptimal hedging.** Based on incomplete or delayed data. - **Excess bank fees.** For accounts holding idle liquidity. Despite access to real-time data elsewhere in the organization, treasury teams often rely on end-of-day reports from disconnected systems. Some banks now offer tokenization services for instant fund movement between entities, but only within their own network. Stablecoins are used across banks and function more like cash. ## Stablecoins offer 24/7, instant, global payments Stablecoins address the core problems treasury teams face: settlement speed, visibility, and global reach. They work anywhere with internet access, allowing dollar-based treasuries to move funds between legal entities without relying on correspondent banking windows. ### Faster settlement unlocks working capital Stablecoins settle 24/7/365 with T+0 finality. This simplifies cash flow forecasting, reduces counterparty risk, and allows working capital to be redeployed immediately. ![Stablecoins for Corporate Treasury](/images/blog/corporate_treasury_1.png) ### Onchain settlement simplifies reconciliation For onchain transactions, payment and settlement occur as a single event. This creates a transparent audit trail and enables automated reconciliation, replacing manual processes. ![Stablecoins for Corporate Treasury](/images/blog/corporate_treasury_2.png) ### Available in underserved markets Correspondent banking works well for G20 currencies. Stablecoins add the most value for businesses operating in currencies with limited banking infrastructure. ![Stablecoins for Corporate Treasury](/images/blog/corporate_treasury_3.png) ## How stablecoins fit into treasury operations ### Intercompany settlements Stablecoins enable real-time settlement between parent companies and subsidiaries, or between subsidiaries. Instead of initiating SWIFT transfers, treasury teams move stablecoins between entities and settle against bank accounts on their own schedule. ![Stablecoins for Corporate Treasury](/images/blog/corporate_treasury_6.png) ### Cash positioning & forecasting Stablecoins provide real-time visibility into global cash positions. Treasury teams can see liquidity across all entities regardless of time zone or banking hours, replacing end-of-day reports with current data for forecasting and liquidity management. ![Stablecoins for Corporate Treasury](/images/blog/corporate_treasury_4.png) ### International payouts Stablecoins reduce the complexity of international payouts by bypassing correspondent banks and FX conversions. This is useful for high-volume, low-value payments or payouts to regions with limited banking infrastructure. Recipients can receive stablecoins directly, or providers can convert to local currency so the stablecoin leg is invisible to the recipient. ![Stablecoins for Corporate Treasury](/images/blog/corporate_treasury_5.png) ## Current limitations Stablecoins complement bank accounts rather than replace them. Key considerations: - **Limited non-USD liquidity.** Stablecoins are predominantly dollar-denominated. EUR, GBP, and other major currency liquidity remains limited. - **Off-ramping constraints.** Off-ramping to bank accounts is not available in all markets, though coverage is expanding. - **Custody complexity.** Treasury teams must choose between self-custody and institutional custody, with implications for multi-signature controls, insurance, and internal governance. - **Limited systems integrations.** Some blockchains require custom integration with treasury systems. Provider and network selection can simplify this. - **Operational risk varies.** Risk profiles differ by asset and network. Stablecoins backed 1:1 by US Treasuries and repo have lower risk profiles. Most major blockchains maintain high uptime. ## Reconciliation & operational risk considerations Beyond speed and cost, treasury teams must evaluate how new settlement rails affect reconciliation processes and operational risk: ### Automated GL reconciliation Fast settlement has limited value if transactions do not post to the General Ledger. Unlike SWIFT ISO 20022 messages, many blockchains lack native GL integration. Standards like [Tempo's TIP-20](/developers/docs/protocol/tip20/overview) allow invoice IDs or GL codes to be embedded in transaction metadata. Funds settle and reconcile in the ERP automatically, eliminating unallocated cash. ### Managing operational risk Adding operational risk to working capital flows is not acceptable. Instead, start with a contained use case that delivers clear value (such as moving working capital in non-G20 currencies over weekends), then expand to other operations like short-term instrument allocation. ### Controls & auditability Faster rails can weaken traditional approval and audit controls if implemented poorly. The mitigation is to enforce policy at the transaction layer, using programmable approvals and role-based permissions, so each movement of funds is pre-approved, attributable, and auditable end-to-end. For multinational companies, stablecoins can deliver value now. The right provider, network, and implementation depend on your specific requirements. ## Key questions to answer Before engaging providers, answer these questions: - **What problem are you solving?** Identify your highest-value use case: reducing FX costs, accelerating intercompany transfers, or improving cash visibility in specific regions. - **Use existing stablecoins or issue your own?** USDC and USDT are liquid and widely accepted for off-ramping. Issuing your own stablecoin allows you to move value between entities while maintaining yield, without converting to money market funds. - **Manage internally or via third party?** Wallet setup, custody, and liquidity provider integration can be complex, so many companies outsource to infrastructure providers like Bridge, BVNK, or ZeroHash. Some, like Ant Group, build in-house. By answering these questions, you'll be ready to define the value more clearly and begin to meet providers. ## Getting started ### Immediate actions The future of corporate treasury is instant, global, and efficient, but getting there requires a methodical approach that fits your organization: - **Assess pain points.** Identify where cash is trapped, which corridors have the highest fees, and where settlement delays create the most friction. - **Build a business case.** Map current costs against projected savings using your actual transaction data. - **Talk to peers.** Other CFOs in your industry are evaluating stablecoins. Learn from their experience. - **Engage infrastructure providers.** Request demos. Understand custody models, compliance tooling, and integration requirements. ### Work with Tempo Our enterprise team can help you navigate the prospect of integrating stablecoins into your corporate treasury operations: - Analyze your treasury operations to identify high-value use cases - Model the business case with your transaction data - Review integration requirements for your tech stack - Design a pilot program tailored to your operational needs - Connect you with companies that have implemented stablecoin treasury operations Please [get in touch](https://tempo.xyz/contact) with us if you'd like to explore this use case with our financial services consulting and product teams. ## Frequently Asked Questions ### Do I have to hold and manage stablecoins? No. You can use stablecoins purely as a settlement rail without holding balances directly. Third parties can manage the stablecoins outside your organization, while your existing bank relationships remain central to day-to-day operations. Over time, you may choose to hold stablecoins directly and expand into other onchain assets such as tokenized treasuries. ### Will my bank support this? Many banks are actively developing stablecoin and tokenized deposit capabilities, and many more are planning to launch through the coming year. In the meantime, infrastructure providers such as Bridge and BVNK enable seamless movement between traditional bank accounts and stablecoins. ### Who do I need to integrate with? There are two common approaches. In a buy model, a provider manages licensing, custody, wallets, and blockchain connectivity, so you may never interact with stablecoins directly. In a build model, you integrate directly with custodians, wallet providers, and blockchain networks. The right choice depends on your timeline, internal resources, and how much control you need. View Tempo's [infrastructure partners](https://tempo.xyz/ecosystem) for opportunities to integrate. ### What about regulatory and audit concerns? Any treasury implementation must meet regulatory expectations and withstand internal and external audit scrutiny. - **Regulatory status.** In the US, the GENIUS Act provides a federal framework. The EU's MiCA regulations are in force. The UAE and Singapore have established frameworks, and many jurisdictions expect to publish theirs in the coming year. - **Audit trail.** Onchain transactions are permanently recorded with timestamps and cryptographic proof. - **Compliance.** Work with providers offering transaction monitoring, sanctions screening, and AML tools for blockchain. - **External auditor comfort.** Major issuers like Circle (USDC) and Paxos (USDP) publish monthly attestations. Stablecoin-as-a-service providers like Agora, Bridge, and M0 offer similar capabilities for custom issuance. ### What are the risk considerations? The primary risks associated with stablecoin-based treasury flows fall into three categories: - **Counterparty risk.** Stablecoin issuer solvency and infrastructure provider stability. Mitigation: Stablecoins backed 1:1 by HQLA under regulatory frameworks like GENIUS represent lower risk. - **Operational risk.** Variable fee structures and network performance across blockchains. Mitigation: Select providers offering fee consistency and evaluate reliability alongside speed. - **Regulatory risk.** Potential restrictions in certain jurisdictions. Mitigation: Start with dollar-based movements between your own entities before expanding to external use cases. ### How does this integrate with our ERP/TMS? Most TMS platforms (e.g. Kyriba, TreasuryXpress, GTreasury) support native integrations or API connections. A typical flow would look like this: - Payment instruction originates in ERP/TMS - Instruction routes to a stablecoin infrastructure provider - Settlement occurs on-chain - Confirmation and settlement data flows back to TMS - Accounting entries are generated automatically Tempo offers ISO 20022-compatible messaging, simplifying integration for teams already working with SWIFT MT messages. --- ## Coupang and Woori Bank complete Korea's first end-to-end KRW stablecoin payment on Tempo > Source: https://tempo.xyz/blog/coupang-woori-bank-krw-stablecoin-payments/ > Language: en **_Coupang and Woori Bank have completed Korea's first end-to-end proof of concept for KRW stablecoin payments and settlement in a consumer-facing commercial service. Built on Tempo, the test followed a Coupang Eats order from payment through real-time onchain merchant settlement and conversion between stablecoins and fiat currency._** US technology company Coupang and Woori Bank have completed Korea's first end-to-end proof of concept for KRW stablecoin payments and settlement in a commercial consumer service. Built on Tempo, the PoC tested how orders placed through Coupang Eats could be settled to merchants in real time using a KRW-denominated stablecoin. Woori Bank provided the on-ramp and off-ramp functionality, connecting digital wallets with bank accounts to convert between stablecoins and fiat currency. This shows how stablecoins can connect consumer payments, merchant settlement, and existing banking infrastructure in a single commercial workflow. ## From a Coupang Eats order to merchant settlement The PoC covered multiple payment scenarios through Coupang Eats. After an order was placed, the merchant received settlement in a KRW-denominated stablecoin on Tempo, while Woori Bank enabled conversion between the stablecoin and fiat currency through linked bank accounts. Together, these steps created an end-to-end flow from a consumer payment to real-time onchain settlement and bank-led conversion. Coupang has participated in Tempo as an early strategic partner and investor, which is part of [Coupang’s efforts](https://www.aboutcoupang.com/coupang-ai-investments-contoro-robotics/) to redefine the future of global commerce through advanced technologies. Through the PoC, the company tested how a payments-first blockchain could meet the scale, reliability, and operating requirements of a commercial service. ## Improving cash flow for merchants Merchant settlement can take anywhere from several days to several weeks after a customer pays. For small and medium-sized businesses, that delay ties up working capital and can increase financing costs. Stablecoin-based settlement can shorten that cycle. Settling the onchain leg in real time gives merchants faster access to funds and lets them put working capital back into the business sooner. For commerce platforms, faster settlement can improve the merchant experience while reducing the operational friction created by delayed payouts. > "We will continue leveraging innovative technologies, including stablecoins, to enhance customer value while advancing inclusive financial services that create greater opportunities for our merchant partners." > > – Coupang spokesperson ## Stablecoins in commercial services Tempo is a Layer 1 blockchain purpose-built for stablecoin payments at scale. It provides near-instant settlement with no re-orgs and sub-cent fees. This means payment platforms can move value around the clock while keeping settlement fast and costs low. The Coupang and Woori Bank PoC shows how those onchain capabilities can connect to the financial system people and businesses already use. Coupang managed the commercial payment experience on top of Tempo's settlement layer, while Woori Bank connected stablecoin balances to bank accounts and fiat currency. The result is a practical model for bringing stablecoin payments into everyday commerce. > "Seeing Coupang and Woori Bank test a complete merchant payment flow together is a clear signal that stablecoins are moving into everyday commerce. We're excited to see Tempo provide the settlement layer for these payment flows to work seamlessly." > > – Nischay Upadhyayula, GTM, Tempo ## What’s next Coupang and Woori Bank have entered a strategic partnership to deepen their collaboration on blockchain-based payment technology. The companies plan to continue conducting technology validations as Korea's regulatory framework for digital assets develops. > "This PoC represents a meaningful milestone in proactively validating the use of KRW stablecoins for payments and settlement. We will continue expanding financial innovation built on KRW stablecoins as the market and regulatory environment evolves." > > – Woori Bank spokesperson By connecting a major commerce platform and a major bank through a real consumer payment flow, the PoC gives merchants a path to faster access to funds and offers payment platforms and financial institutions a practical model for bringing stablecoins into commercial services. [Read Coupang's announcement](https://news.coupang.com/archives/64957/) If your team is evaluating stablecoin payment and settlement infrastructure, [get in touch with Tempo](/contact). --- ## Creating More Liquidity Mobility in Markets > Source: https://tempo.xyz/blog/creating-more-liquidity-mobility-in-markets/ > Language: en **_Every generation of market infrastructure gets built to fix trapped liquidity, only to move the trap somewhere else. Public chains deliver mobility, but lack privacy. Private chains deliver privacy, but trap liquidity inside vertical silos. Our new whitepaper argues that liquidity mobility is the primary frame for evaluating the next generation of settlement infrastructure._** [_Read the whitepaper_](/report/creating-more-liquidity-mobility-in-markets). [Download full report](/report/creating-more-liquidity-mobility-in-markets) Every era of market infrastructure has a version of the same story. Liquidity gets trapped, the industry builds a fix, and the trap moves somewhere new. DTC immobilized paper certificates after the late-1960s paperwork crisis, CLS closed the FX timing gap after Herstatt, and tri-party repo freed collateral trapped in bilateral silos. Oliver Wyman puts the annual cost of trapped liquidity at $120 billion, and GFMA estimates $25.5 trillion in assets sitting idle as dead capital. Public chains delivered the first proof that liquidity mobility can work. A user can route funds across rollups, swap stablecoins, and deploy into a yield strategy on a different chain inside a single transaction. The cost is fragmentation. Roughly $40 billion in liquidity sits dispersed across more than twenty L2s, and bridges have lost billions to exploits. Private chains went the other way. The largest live institutional DLT processes around $385 billion in daily repo volume with strong privacy and sub-second finality, but the cash leg is captive to a single market. A treasurer moving the same dollar from a repo platform to an FX venue to a corporate payout needs three different cash instruments, three reconciliation paths, and three operating models. Mobility is the price. Modern blockchains can deliver all three together by separating execution from settlement. Private execution environments keep transactions invisible to the public, while a shared mainnet keeps liquidity unified across venues. The trade-off between privacy and mobility was an artifact of older architectures, not a structural one. ## Three properties to balance Three properties matter for institutional cash infrastructure. - **Speed and reliability** mean sub-second finality of transactions, dedicated blockspace to ensure that other activity on a blockchain cannot starve payments, and predictable fees that a treasury team can model. This is the easiest of the three to deliver and is no longer a differentiator. - **Privacy** means payment amounts, counterparty identities, and balances stay invisible to the public. The issuer, the regulator, and the parties to a transaction each get exactly the visibility they need and no more. - **Liquidity mobility** means the same cash can clear a repo trade, fund a cross-border payment, post margin at a derivatives venue, and settle a tokenized securities trade. None of those flows requires re-issuing the cash at each hop. The first two are now available from multiple vendors. The third is what separates next-generation settlement infrastructure from the silos the industry has been building for the last decade. ## Architecting for liquidity mobility For most of the last decade, the trade-off looked binary. Private chains optimized for privacy and threw away mobility. Public chains optimized for mobility and threw away privacy. Builders accepted one as the cost of the other. That trade-off was never structural. The architectural move that resolves it is the separation of execution from settlement. Private execution environments run as parallel chains where participants transact without public visibility. Funds remain in contracts on a common mainnet, assets stay interoperable across environments, and liquidity pools on the mainnet remain accessible. Privacy is handled at the execution layer. Liquidity is handled at the settlement layer. The two stop fighting each other. FMI and bank strategists choosing settlement infrastructure today should be asking different questions than the industry has been asking. Not how fast, and not how private. The question is whether the cash leg can move across venues, asset classes, and use cases without being re-tokenized at every hop. Architectures that answer "yes" treat cash as first-class, and architectures that answer "no" are building a new silo at a new layer. Our whitepaper, "Creating More Liquidity Mobility in Markets", works through the historical pattern of trapped liquidity and the trade-offs in current institutional DLT designs. It also covers the architectural separation that lets cash stay mobile without sacrificing speed or privacy. [Read the whitepaper](/report/creating-more-liquidity-mobility-in-markets). --- ## Daya expands cross-border payments for African businesses with Tempo > Source: https://tempo.xyz/blog/daya-expands-cross-border-payments-for-african-businesses-with-tempo/ > Language: en **_Daya gives African businesses one place to collect locally, access FX, manage balances across currencies, and pay suppliers around the world. With Tempo supporting its stablecoin payment flows, Daya can extend that experience over infrastructure designed for payments while keeping routing, liquidity, and settlement complexity out of sight for customers._** [_Learn more about Daya._](https://daya.co/) ## Connecting African businesses to global markets Daya provides unified payment infrastructure, real-time FX, stablecoin rails, and treasury management for African businesses. Its current products support Nigerian businesses with local NGN collection and payouts, conversion between NGN, ZAR, GHS, KSH, and stablecoins, USD, EUR, CNY, HKD, and GBP virtual accounts and payouts. ![Daya send money interface showing wallet addresses and local currency accounts](/blog/daya-send-money.png) For importers, exporters, startups, and growing businesses, that brings local collection, currency conversion, multi-currency accounts, and global payments into one product. Daya coordinates the routing, liquidity, FX, and reconciliation across providers so its customers do not have to. ## Extending Daya’s payment infrastructure with Tempo Daya is now powered by Tempo, giving Daya a payments-first settlement rail for stablecoin movement inside the products its customers already use, while Daya continues to manage FX, liquidity, routing, and support within one product experience. ## Why Tempo Tempo is a blockchain built for payments at scale. Its deterministic, sub-second finality gives Daya clear settlement certainty, while fixed, predictable fees make network costs easier to forecast as payment volume grows. Fees can be paid in stablecoins, reducing the need to manage a separate asset for network fees. > “We want African businesses to move between local currencies and stablecoins without having to manage the infrastructure underneath. Adding Tempo gives us another payments-first settlement rail while Daya continues to handle routing, liquidity, and FX behind one product experience.” > > — Aleph L, Founder and CEO, Daya > “Daya is building the financial infrastructure African businesses need to operate across borders. We’re glad to support that work as Daya brings more stablecoin payment flows onto a network designed for payments.” > > — Josh Itzkovitz, Tempo ## What comes next Daya and Tempo will continue expanding the integration across more of Daya’s stablecoin payment flows. The teams will share more as additional customer use cases go live and there are verified operational outcomes to report. [Learn more about Daya.](https://daya.co/) If you are a payments platform or fintech evaluating stablecoins for cross-border settlement, [get in touch with Tempo.](https://tempo.xyz/contact) --- ## Deel launches stablecoin wallet for global contractors, exclusively on Tempo > Source: https://tempo.xyz/blog/deel-launches-dlusd-stablecoin-wallet-for-global-contractors/ > Language: en **_Deel powers payroll for 40,000+ businesses across 150 countries. Today, they launched DLUSD, a dollar-backed stablecoin, and the Deel stablecoin wallet for its global contractor base. Workers can hold a dollar-backed balance, earn, and soon will also be able to spend globally via a card, all inside the platform they already use to get paid. Tempo is Deel's exclusive chain partner for wallet and earn products._** [_Read the full Deel case study_](https://tempo.xyz/customer-stories/deel) In markets like Argentina, currency devaluation has made local earnings increasingly unreliable. The Argentine peso lost over 50% of its value against the dollar in a single year. A Deel survey found 84.6% of contractors in Argentina would choose USD over local currency, yet accessing dollars remains difficult. Government restrictions cap purchases, local banks impose extensive documentation requirements and minimum balances, and many simply don't offer USD accounts at all. > Millions of contractors around the world watch their earnings lose value the moment they land. Today we give them the infrastructure to change that: a dollar-backed balance inside the platform they already use, rewards that accrue automatically, and a card to spend anywhere. No new account or learning curve required. > > — Thierry Edde, Head of Crypto, Deel Today, Deel's new stablecoin wallet gives workers outside the US, UK, and Eurozone a dollar-backed balance inside the Deel platform, with three core features: - **Hold.** A USD-backed balance, DLUSD, that tracks USD value 1:1 and is always redeemable. - **Earn.** A single-tap opt-in to accrue rewards. - **Spend.** A waitlist is available for the stablecoin card. Workers never interact with the underlying infrastructure. There is no new account, no separate app, no key management. The whole experience sits inside the Deel account contractors already use to receive pay and manage contracts. > Deel is at the forefront of redefining what global payroll should look like, and has designed an experience that brings the power of stablecoins to global contractors without the complexity of crypto. Tempo is proud to partner with Deel on DLUSD, the contractor wallets, and Earn, to power reliable, private, and economical payroll across 150+ countries. > > — Ani Narayan, GTM, Tempo ## What runs on Tempo Tempo is Deel's exclusive chain partner for the contractor wallet stack with DLUSD issued on Tempo. The embedded wallets that hold contractor balances are provisioned by Privy on Tempo. The Morpho-powered earn product runs on Tempo. Three Tempo capabilities mattered most for the architecture: **Native account abstraction.** Passkey authentication, transaction batching, and fee sponsorship are built into the protocol. That is what lets a contractor sign in with Face ID, never touch a private key, and have Deel sponsor fees on their behalf. **Fixed, predictable fees paid in stablecoins.** Every Tempo transaction costs $0.001, paid in stablecoins with no account rent. Tempo doesn't charge a storage deposit to keep accounts in state. For a wallet operating at consumer scale with small per-user balances, that combination of fee predictability, no rent overhead, and no exposure to a volatile native token were prerequisites. **Privacy at the protocol level.** Deel uses Tempo Zones to keep contractor wallet balances and payout history confidential from public view, while preserving auditable access for Deel. ## What's next The Deel stablecoin wallet launches in Latin America, starting with early access in Argentina. Contractors in remaining LATAM countries will be onboarded over the next few weeks, with APAC, MENA, and Africa to follow. ## Get started If you are a platform building stablecoin balances for your users, get in touch. [Read the full Deel case study](https://tempo.xyz/customer-stories/deel) --- ## DoorDash partners with Tempo to bring stablecoin payments to its global marketplace > Source: https://tempo.xyz/blog/doordash-partners-with-tempo-to-bring-stablecoin-payments-to-its-global-marketplace/ > Language: en **_DoorDash, one of the world's largest local commerce platforms, is building stablecoin-powered payment infrastructure on Tempo for its marketplace of merchants and Dashers across 40+ countries._** [_Read the full case study_](https://tempo.xyz/customer-stories/doordash) Every DoorDash transaction involves at least three parties: a consumer paying for an order, a merchant receiving revenue, and a Dasher earning income for fulfilling the delivery. Multiply that across more than 40 countries, each with different payment rails, compliance requirements, and settlement timelines, and the complexity of running global payments at DoorDash's scale becomes clear. DoorDash was founded in 2013 with a mission to empower local economies. Through its marketplace and acquisitions like Wolt and Deliveroo, DoorDash connects consumers, merchants, and delivery workers across more than 40 countries. Now, DoorDash is partnering with Tempo to bring stablecoin settlement to its global payment operations. ## DoorDash and Tempo DoorDash and Tempo are working together to bring stablecoin-powered payments to the flows where they deliver the most immediate value: faster payouts for merchants and Dashers, lower costs on cross-border transactions, and simpler reconciliation across dozens of markets. DoorDash's marketplace creates payment complexity that most companies never encounter. A consumer modifies an order after checkout. A refund needs to process in minutes. Each of these flows adds cost and friction that compounds across millions of transactions globally. Stablecoins settle in seconds, around the clock, reducing the intermediaries and delays at every step. > There's real promise with stablecoins transforming financial infrastructure, not just in America, but globally. We want to be a proactive participant and not just passive. > > — Andy Fang, co-founder of DoorDash ## Why Tempo Tempo is purpose-built for institutional payments. For a use case like multi-party marketplace payouts across dozens of countries, several capabilities made the difference. Sub-second finality means payouts to merchants and Dashers settle in under a second with deterministic confirmation. Dollar-denominated fees make cost predictable at millions-of-transactions scale. Dedicated payment lanes guarantee that payout throughput is never affected by other network activity. And ISO 20022-compatible memo fields support the structured reconciliation workflows that a global treasury operation requires. > If we can get merchants and Dashers their money faster, and do that in a way that's affordable for them, that's a no-brainer for the entire ecosystem. > > — Andy Fang, co-founder of DoorDash ## What this means For marketplace operators and platforms running multi-party payments across borders, DoorDash's partnership with Tempo signals where global payout infrastructure is heading. [Read the full DoorDash case study](https://tempo.xyz/customer-stories/doordash) --- ## DoorDash, Stripe, Coastal, ARQ and others bring payment operations onto stablecoins on Tempo > Source: https://tempo.xyz/blog/enterprise/ > Language: en **_DoorDash, Stripe, Coastal, ARQ, and more are bringing stablecoin payment flows into production on Tempo. Today, Tempo is also launching Stablecoin Advisory, a hands-on practice that brings the expertise behind these partnerships to every company evaluating bringing payments onto stablecoin rails._** [_Learn more_](https://tempo.xyz/contact/) [Watch customer stories](/videos/homepage/tempo-case-studies.mp4) Enterprises and financial institutions are increasingly turning to stablecoins to move money faster, reduce costs, and simplify global payment operations. But getting from interest to production means navigating payments, compliance, custody, and infrastructure decisions that require a depth of stablecoin expertise most companies don't have in-house. ## Building Tempo for real-world payments use cases Over the past year, Tempo has been working directly with [design partners](https://tempo.xyz/ecosystem) across industries to integrate stablecoins into real payment operations. Companies like DoorDash, Shopify, and Coastal came to Tempo with specific problems: global payouts that took days and cost too much, payment infrastructure fragmented across dozens of markets, and growing demand for instant settlement. Working with these partners shaped how Tempo is built today. With input from fintechs and Fortune 500s, these companies' requirements pushed us to solve for the things enterprise payment teams actually care about: scale, reliability, compliance, privacy, and cost predictability. Those requirements are now built into Tempo, with features like dedicated payment lanes for guaranteed throughput, fixed dollar-denominated fees, virtual addresses for clean reconciliation at scale, programmable account controls for compliance teams, and [Tempo Zones](https://tempo.xyz/blog/introducing-tempo-zones) for private stablecoin payments where only the parties to a transaction see the details. Now, Tempo's design partners are bringing stablecoin payment flows into production. Here's a preview of how enterprises on Tempo are upgrading their payment operations with stablecoins. ### DoorDash DoorDash operates a three-sided marketplace across 40+ countries, enabling payments between consumers, merchants, and Dashers in every transaction. Each market brings different payment rails, FX dynamics, and settlement timelines which adds meaningful complexity. > There's real promise with stablecoins transforming financial infrastructure, not just in America, but globally. We want to be a proactive participant and not just passive. > > — Andy Fang, Co-founder, DoorDash Now, DoorDash is working with Tempo to bring stablecoin-powered payouts to its global marketplace, starting with the flows where faster, more affordable settlement creates the most value for merchants. [Read the full story](https://tempo.xyz/customer-stories/doordash) ### Stripe As stablecoin demand grew across Stripe's customer base, Stripe needed blockchain infrastructure that could match its scale, reliability, and cost requirements for global payments. General-purpose blockchains built for trading and DeFi introduced unpredictable fees, throughput constraints, and operational complexity that didn't fit Stripe's payment workloads. > It should be easy and instant to move money anywhere in the world. That's the promise of programmable financial services. As we bring stablecoin infrastructure into more Stripe products, we're delivering on that promise at scale—so every Stripe user can benefit from faster, cheaper, borderless money movement. > > — Neetika Bansal, Head of Connect and Money Management at Stripe Now, Tempo serves as core blockchain infrastructure powering Stripe's money management capabilities, letting millions of businesses hold, send, and receive stablecoins directly from Stripe. When a business sends a payout to a contractor abroad or a platform distributes earnings to sellers across 100+ countries, Tempo is the settlement layer making those transactions fast and low-cost via stablecoins. [Read the full story](https://tempo.xyz/customer-stories/stripe) ### Coastal Bank Coastal Bank is a regulated sponsor bank that powers financial products for fintech partners ranging from early-stage companies to mature platforms operating at scale. As those partners increasingly needed faster, lower-cost payment capabilities, Coastal needed stablecoin infrastructure that could sit alongside its existing rails without introducing compliance risk or operational complexity. > What was particularly interesting about Tempo was here's a partner focused on a payments-first use case and focused on how we can enable the next generation of money movement. Faster payments, more efficient payments, and safer and more secure payments. > > — Ryan Hall, Chief Product Officer, Coastal Bank Coastal is building stablecoin-native payment infrastructure on Tempo alongside its existing rails, giving its fintech partners access to faster settlement, lower costs, and global reach through a single integration. [Read the full story](https://tempo.xyz/customer-stories/coastal) ### ARQ ARQ is a financial services platform serving over 2 million customers across Mexico, Colombia, Argentina, and Brazil, processing more than $10 billion in annualized transaction volume on stablecoin infrastructure. As it scaled, ARQ needed a settlement layer that could keep pace with growing volume while keeping costs predictable. > From day one, Tempo understood what we were building, moved with urgency, and offered the infrastructure, product vision, and long-term alignment we needed to scale ARQ. > > — Zach Garman, Co-founder and CPO, ARQ Now ARQ runs its stablecoin payment infrastructure on Tempo, gaining direct control over settlement costs and the performance characteristics its products depend on at scale. [Read the full story](https://tempo.xyz/customer-stories/arq) DoorDash, Stripe, Coastal, and ARQ are among the first enterprises and financial institutions bringing payment operations onto Tempo. We'll also be sharing stories from Felix, Klarna, Shopify, Visa, and more over the coming weeks. ## Why Tempo Tempo is a blockchain purpose-built for payments, incubated by Stripe and Paradigm. Unlike general-purpose blockchains designed for trading and DeFi, Tempo was built from the ground up for enterprise payment teams. - **Sub-second finality.** Transactions finalize in under a second with deterministic settlement. Payment operators get the same settlement certainty they expect from existing financial systems. - **Predictable, dollar-denominated fees.** Transaction fees are paid in stablecoins and stay predictable at any volume, with no need to hold a native token and no fee spikes. Payment applications operate entirely in the same currency as their underlying flows. - **Dedicated payment lanes.** Payments have guaranteed blockspace reserved at the protocol level, so a surge in other network activity never affects payment throughput or latency. - **Tempo Zones for private payments.** Zones enable private stablecoin payments where only the parties to a transaction see the details. For enterprises that need payment privacy without sacrificing compliance, Zones provide confidential transactions with selective disclosure to authorized parties. [Learn more](https://tempo.xyz/blog/privacy-on-tempo) - **Payments metadata.** Each transfer can include structured memo fields for invoice numbers, cost centers, and other identifiers, making reconciliation against existing ERP, TMS, and accounting systems straightforward. - **Native account abstraction.** Spend permissions, transaction batching, fee sponsorship, and passkey authentication are built in, so you can batch thousands of payouts in a single operation and sponsor fees so recipients never touch crypto. ### Tempo's infrastructure partners Along with Tempo's native payments features, over 50 infrastructure partners across custody, compliance, on/off ramps, card issuance, and orchestration ensure that enterprises building on Tempo have production-grade infrastructure from day one. [See Tempo's infrastructure partners](https://tempo.xyz/ecosystem) ## Tempo’s stablecoin advisory Tempo's design partner program gave us a playbook for taking enterprises from stablecoin evaluation to production. Now, we’re launching our [Stablecoin Advisory](https://tempo.xyz/contact/) to open that playbook to every enterprise and financial institution ready to upgrade their payments workloads with stablecoins. Tempo’s Stablecoin Advisory is a hands-on practice of payments specialists, banking experts, and forward-deployed engineers helping the next generation of enterprises and financial institutions to bring stablecoins into production, including: - **Use case scoping and strategy.** The advisory team works with partners to identify the highest-impact use case, model the economics, and build the internal case for moving forward. - **Solution architecture.** Tempo's payments and banking specialists design the technical architecture for each use case, covering custody, compliance, on/off ramps, and integration with existing treasury and ERP systems. - **Forward-deployed engineering.** For partners ready to build, Tempo provides engineers who work alongside your team from architecture to working prototype to production on mainnet. - **Infrastructure partner access.** Infrastructure partners span custody, compliance, on/off ramps, card issuance, and orchestration, so partners get connected to the right infrastructure for their use case rather than assembling a stack from scratch. If you're an enterprise or financial institution looking to get first access to our Stablecoin Advisory, [**get in touch**](https://tempo.xyz/contact/). ## Get started If you're evaluating stablecoins for global payouts, cross-border payments, treasury operations, embedded finance, commerce, payroll, agentic payments, tokenized deposits, or any other payments use cases, we want to hear from you. [**Talk to us**](https://tempo.xyz/contact) --- ## Felix brings instant remittance settlement on Tempo > Source: https://tempo.xyz/blog/felix-brings-instant-remittance-settlement-on-tempo/ > Language: en **_Felix built a remittance product that lives entirely inside WhatsApp, processing over $5 billion for more than one million users across Latin America. As volume scales, Felix is adding Tempo to its settlement infrastructure for predictable fees, sub-second finality, and dedicated capacity for payment flows._** [_Learn more in the full case study_](https://tempo.xyz/customer-stories/felix-pago) Cross-border remittances remain one of the most expensive and inconvenient financial services in the world. Senders visit storefronts, pay steep fees, and wait days for money to arrive. More than half of transfers in Latin America still happen at physical locations. For the families who depend on these payments, every dollar lost to fees and delays is a dollar that does not arrive. Felix is changing how remittances work. Through an AI-powered chatbot on WhatsApp, users in the US tell Felix how much to send and where, pick a payment method, and the recipient in Latin America receives local currency in their bank account within seconds. No app download, no storefront, no crypto terminology. Felix currently serves nine corridors across Mexico, Central America, and the Caribbean, charging a flat $2.99 for the majority of transfers. ## Felix and Tempo Behind the scenes, Felix settles through stablecoins. The sender pays in dollars, Felix converts to stablecoins for settlement, and the recipient receives local currency on the other end. Neither side ever touches crypto. This architecture is what makes the $2.99 fee possible at scale. As Felix has grown past one million users and $5 billion in cumulative volume, building redundancy across critical infrastructure has become a priority. Felix is adding Tempo to its settlement layer because Tempo was purpose-built for exactly this kind of high-volume payment flow. > As we scale, we’re intentional about building redundancy across our settlement infrastructure. Tempo adds a settlement layer purpose-built for payments, which is important for a real-time remittance product like ours. > > — Hugo Rodriguez, Associate Director of Strategy, Felix Pago ## Why Tempo Tempo is purpose-built for stablecoin payments at scale. For a product that commits to a flat consumer fee and promises delivery in seconds, several capabilities matter. Predictable transaction fees keep settlement costs low regardless of network load. There are no gas auctions and no fee spikes during high-traffic periods. For a business running on thin margins at high volume, cost predictability is a prerequisite. Dedicated payment lanes reserve blockspace at the protocol level for payment transactions. A surge in trading or other on-chain activity never affects payment throughput or latency. Sub-second finality means transactions finalize in under a second with deterministic settlement. When a user sends money through WhatsApp and expects it to arrive instantly, the settlement layer has to keep that promise every time. ## What this means Felix is starting with its existing remittance corridors across Mexico, Central America, and the Caribbean. Lower, more predictable settlement costs give Felix room to reinvest in growth or pass savings back to senders as lower fees. The US-to-Latin America remittance corridor moves hundreds of billions of dollars a year, and the shift from cash to digital is still early. Tempo is the settlement layer making it work at scale. [_Read the full case study_](https://tempo.xyz/customer-stories/felix-pago) --- ## Flutterwave and Tempo partner to expand stablecoin settlement options to African payments > Source: https://tempo.xyz/blog/flutterwave-and-tempo-partner-to-expand-stablecoin-settlement-options-to-african-payments/ > Language: en **_Flutterwave, one of Africa's largest payments companies, is partnering with Tempo to expand stablecoin settlement options to cross-border payments across the continent._** [Flutterwave](https://flutterwave.com/) connects businesses and individuals to local and cross-border payments across 34 African markets. Its Send App moves money from the diaspora in the US, UK, EU, and Canada to recipients across Africa, and Flutterwave for Business powers enterprise cross-border payments and supplier settlements. ## The cost of moving money across Africa Moving money into and across the continent is still slow and expensive. Remittance fees to sub-Saharan Africa average around 7 percent, above the global average and well above the United Nations target of 3 percent. The cost comes from a chain of correspondent banks and foreign exchange conversions, and that same chain can hold settlement for several business days. For businesses, that ties up working capital. For families, it means less money arriving, and a longer wait for it. ## What Flutterwave is building with Tempo Flutterwave is integrating Tempo as a settlement network across the Send App and Flutterwave for Business, as part of a move toward multi-rail payments infrastructure. Once live, the integration will support wallet-to-wallet stablecoin payments, with the option to settle across corridors in seconds rather than days, at predictable cost. Rather than routing every payment through a single path, Flutterwave will be able to support interoperability across corridors based on specific corridor requirements and customer preferences, complementing its existing blockchain settlement infrastructure. ## Why Tempo Tempo is a blockchain built for payments, incubated by Stripe and Paradigm. For a platform operating at Flutterwave's scale, two things matter most: fast, deterministic finality, so settlement is certain, and fixed, predictable fees, so cost can be forecast across millions of payments. Structured payments metadata lets transfers carry the identifiers finance teams need to reconcile against their existing systems. > Our partnership with Tempo allows us to expand our existing payments ecosystem by adding additional practical stablecoin settlement rails. We are working together to turn these into everyday tools that will make cross-border payments faster, more predictable, and more cost-efficient for businesses and individuals across Africa > > — Olugbenga “GB” Agboola, Founder & CEO, Flutterwave ## What's next Flutterwave and Tempo are working to move the integration into production. We will share more as corridors go live. If you are a payments platform or fintech evaluating stablecoins for cross-border settlement, [get in touch](https://tempo.xyz/contact). --- ## Stablecoins for Global Payouts > Source: https://tempo.xyz/blog/global-payouts/ > Language: en **_Stablecoins settle instantly, 24/7, across borders. For companies that run global payouts, that means faster delivery, lower fees, and fewer steps to pay recipients. This guide explains the benefits for businesses evaluating stablecoins to simplify their payout operations._** [_Contact us_](https://tempo.xyz/contact) if you’re evaluating stablecoins for global payouts. For any business operating globally, whether a marketplace paying thousands of merchants or a software company with a distributed team, payouts are operationally complex. Stablecoins simplify this by enabling dollar-based payouts to over 140 countries, arriving in seconds. Recipients receive funds in a stablecoin-compatible wallet, giving them control, speed, and stability. ## The costs of traditional cross-border payouts Consider an example: when you send $1,000 to a contractor in Brazil using traditional rails, the costs add up quickly. Your payment processor may charge a $10–40 fee per payment, while intermediary banks take anywhere from 0.1% to 4.0% on the FX spread. By the time the payment clears five days later, the recipient has lost $80 to fees. If local currency moved adversely in that window, they would lose again. The friction falls into predictable categories: - **High transaction costs:** A single cross-border payment can pass through three or four intermediary banks, each taking a cut. When multiplied by thousands of payouts, these fees erode margins for the company and reduce the take-home pay for the recipient. - **Slow, unpredictable settlement:** Payouts can take 3-5 business days to arrive, complicated by time zones, bank holidays, and compliance checks. This uncertainty makes cash flow management difficult for recipients who rely on timely payments. - **Payout failures and reconciliation overheads:** A simple data entry error can cause a payment to fail, leading to a lengthy and manual reconciliation process. For finance teams, tracking and resolving thousands of individual payments creates a significant operational burden. - **Currency volatility risk:** Recipients in emerging markets are often exposed to the volatility of their local currency. A payment that was worth $1,000 when sent might be worth significantly less by the time it arrives and can be converted, unfairly penalizing the earner. ## How stablecoins improve global payouts Stablecoins bypass the correspondent banking system entirely, enabling direct payouts to any worker or contractor with a compatible wallet. Stablecoin payments settle in seconds, 24/7, without being constrained by banking hours, public holidays, or time zones. When you send $1,000 to a contractor in Brazil using stablecoin rails, the process is far more straightforward: your stablecoin partner may charge a flat fee of 0.1–0.4% for the onramp and transfer, delivering a ~60–80% cost reduction[1] compared to traditional rails. Recipients receive dollar-denominated stablecoins and can convert to local currency when and how they choose, typically paying a transparent offramp fee in the 0.1–2.0% range. The benefits are concrete: ### Instant settlement Stablecoins are powered by blockchains that operate 24/7/365, and stablecoin payouts settle in seconds, not days. This means workers and merchants get paid on time, every time, improving satisfaction and retention. ![Global payouts](/images/blog/global_payouts_1.png) ### Lower costs By eliminating intermediaries, stablecoins can reduce the cost of a cross-border payment by at least ~60-80%. This allows platforms to save on operational costs or pass the savings on to their users. ![Global payouts](/images/blog/global_payouts_2.png) ### Traceability Every stablecoin transaction is recorded on the blockchain, creating an immutable audit trail that can be tracked in real-time by both payers and payees. This reduces disputes and simplifies reconciliation. ![Global payouts](/images/blog/global_payouts_3.png) ### Dollar-based stability Payouts sent in US dollar-denominated stablecoins protect recipients from local currency devaluation. They receive a stable store of value and can convert to their local currency on their own terms. ![Global payouts](/images/blog/global_payouts_4.png) ### Broader access Stablecoins can be sent to any compatible digital wallet, anywhere in the world. This opens access to global economic opportunities for individuals in countries underserved by traditional banking. ![Global Payouts](/images/blog/global_payouts_5.png) ## Evaluating stablecoins for global payouts Stablecoin adoption starts with a clear business use case. Before evaluating vendors or integration paths, here is a helpful framework for evaluating stablecoins for global payouts: - **Do you pay people internationally?** If you are paying contractors, merchants, or employees across borders, you are already managing multiple currencies, banks, and regulatory regimes. - **Do those payments create friction today?** Delays, failed transfers, opaque fees, FX leakage, and reconciliation errors are signals that your current payout rails are not keeping up. - **Are you forced to pre-fund payouts?** Long settlement times often require holding excess balances across banks and currencies, tying up working capital. - **Would reducing that friction materially impact your business?** Faster payouts, lower costs, and happier recipients can improve retention, reduce operational overhead, and unlock new geographies. - **Can instant payouts become a new revenue stream?** Many platforms offer real-time payouts as a premium feature, turning speed and reliability into a paid upgrade rather than a cost center. If the answer to these questions is yes, you should be evaluating the stablecoin partner ecosystem. The infrastructure is ready, regulation is clearer, and the economics are hard to ignore. ## Getting started with stablecoins Payouts are one of the cleanest entry points for stablecoins: easy to pilot and deliver immediate, measurable impact. Teams can start with a single corridor, validate speed and cost improvements quickly, and scale once the business case is proven. Here’s how to get started: ### Step 1: Clarify the business case Pick your highest-friction payout corridor, such as the U.S. to the Philippines, Nigeria, or Brazil. Identify a segment of contractors that are frustrated with delays and fees in the current system. Offer them instant payouts with 60–80% lower fees. You can start manually or move directly into a pilot to test the impact at scale. ### Step 2: Identify an integration approach Decide whether to partner with a third party or build infrastructure yourself. Partners can simplify implementation by handling blockchain selection, liquidity sourcing, custody, and other operational complexities. Companies that build in-house must assemble their own stack: wallets, custody, liquidity, bank relationships, and potentially MTL or similar local licenses. ### Step 3: Pilot stablecoins for payouts Run a pilot. Integrations can take as little as two weeks, with providers like BVNK, ZeroHash, or Bridge handling the underlying infrastructure. Add a small number of API calls to your existing payout flow and run stablecoin payouts alongside your existing system for 60 days to build confidence before scaling. Pilots quickly reveal benefits as well as operational complexities like customer support needs, integration gaps, or errors. ### Step 4: Operationalize Turn the pilot into a standard payout flow. Lock in processes across finance, ops, support, and compliance, including SLAs, reconciliation, treasury management, and exception handling. Train support teams on how stablecoin payouts work. Then expand to new corridors and segments, increase volumes, and automate what was manual during the pilot. ## Work with Tempo Tempo’s enterprise team helps companies evaluate and implement stablecoins as part of a modern global payouts strategy, from initial analysis through pilot and scale. - Analyze your operations to identify high-value use cases - Model the business case with your transaction data - Review integration requirements for your tech stack - Design a pilot program tailored to your operational needs - Connect you with companies that have implemented stablecoin payouts > If you'd like to explore stablecoin payouts with our financial services consulting and product teams, [get in touch](https://tempo.xyz/contact) with our Enterprise Team. ## Frequently Asked Questions ### Do I have to hold and manage stablecoins? No. Many infrastructure providers, such as BVNK, Bridge, and ZeroHash, abstract the complexity of managing stablecoins, wallets, or licensing. You connect to their API to instruct a stablecoin payout, send funds from your bank account in fiat currency, and they handle on- and off-ramp, custody, and liquidity management. ### Will recipients understand stablecoins? They don’t have to. Historically, stablecoin payouts were used primarily by crypto-native developers and contractors. That is changing as new fintech apps hide the complexity. Modern stablecoin infrastructure, like embedded wallets, can be invisible. The recipient gets a notification that payment arrived and sees a balance in US dollars on a mobile app. ### What happens if a recipient wants local currency? Recipients can convert stablecoins to local currency through supported off-ramps as soon as funds arrive. This is often a one-click experience inside a fintech app or exchange, with transparent fees that are typically far lower than traditional bank FX spreads. Stablecoin orchestration platforms can also automate this process end-to-end. ### Is this only useful for emerging markets? No. While the benefits are most visible in emerging markets with high fees or volatile currencies, stablecoin payouts are increasingly used in developed markets as well, especially for instant payouts, weekend payments, or premium payout features. ### Is this regulated? Yes, increasingly so. Since the passage of the GENIUS Act in the United States, the compliance landscape for stablecoins has become clearer. Any money transmitter, financial institution, or nonbank money mover is subject to travel rule requirements. In practice, regulatory requirements like KYC/KYB and screening of senders over $1,000 are lower risk in payout use cases because the payer is the corporation itself. [1]_ Cost reduction calculation: Traditional cross-border wire fees on a $1,000 payout typically range from $10–40 (1.0–4.0%) excluding FX spreads. Stablecoin onramp fees range from 0.1–0.4%. Comparing the high end of stablecoin costs (0.4%) against the low end of wire costs ($10/1.0%) yields a 60% reduction. The upper range reflects comparisons against higher wire fees and FX spreads._ --- ## Meet Tempo's infrastructure partners > Source: https://tempo.xyz/blog/infra-partners/ > Language: en > Update as of December 9, 2025 **_Since launching Tempo and announcing our initial infrastructure partners in September, we've been overwhelmed by the response from the ecosystem. In just under three months, we've welcomed 40 additional ecosystem partners who share our vision of bringing the world's payments onchain._** Our new partners include: Agant, AllUnity, BitGo, Blockaid, Blockdaemon, Blockradar, BlockScout, Chainlink, Chainstack, Chaos Labs, Conduit Pay, Cybrid, Dfns, Due, Elliptic, Fonbnk, Gelato, Goldsky, Infinite, Lean, Levl.ch, LiFi, Manteca, Nillion, OpenFX, Orda Network, Para, PDAX, Range, Relay, Roma Global, Splits, Thirdweb, Thunes, Toku, Ubyx, Utila, ZeroDev, and Zerion. We're continuing to expand our ecosystem. If you'd like to build with us, please [get in touch](https://tempo.xyz/contact). ![Infrastructure Partners](/images/blog/Screenshot_2026-04-03_at_8.59.29_AM.png) ## Say hello our infrastructure partners We're building Tempo as an open, permissionless payments-focused blockchain capable of bringing the world's payments onchain. Our goal is for Tempo to be the high-throughput, low-cost, global base layer for any kind of payment. To accelerate that vision, we're excited to announce Tempo's initial infrastructure partners. This is a cohort of best-in-class infrastructure providers, selected for their deep experience building stablecoin applications. They each enable critical services to help businesses and users interact with Tempo. The partners offer building blocks such as wallet services, stablecoin orchestration, on/off ramps, developer tooling, stablecoin-linked cards, stablecoin issuance, onchain metrics providers, interoperability solutions, compliance providers, and more. Current Tempo infrastructure partners include: Across, Agora, Alchemy, Allium, Artemis, Brale, Bridge, Chainalysis, Conduit, Crossmint, Farcaster, Fireblocks, Frax, LayerZero, Mesh, MetaMask, Phantom, Privy, QuickNode, Sardine, Tenderly, TRM Labs, Turnkey, and Yellow Card Their efforts will contribute to optimizing Tempo to meet the needs of modern payment processing. We're collaborating with these infrastructure partners, along with our growing group of design partners [announced](https://tempo.xyz/blog/introducing-tempo) earlier this month, to ensure Tempo is the easiest platform for onchain payments. ![Infra partners 2](/images/blog/Screenshot_2026-04-03_at_8.59.41_AM.png) We're just getting started here. If you'd like to build with us, [get in touch](https://tempo.xyz/contact) with our Enterprise Team. --- ## Unlock new revenue streams with Tempo Earn > Source: https://tempo.xyz/blog/introducing-tempo-earn/ > Language: en **_Tempo Earn puts idle stablecoin balances to work: end users earn on balances they already hold and you control how rewards are split. [Talk with our team](/earn/)_** Today, we're introducing [Tempo Earn](https://tempo.xyz/earn/). Platforms can now build embedded Earn products with a wide range of assets and full control over reward economics. Businesses can integrate Earn programs into their products to create revenue, attract users, and improve retention. - **Build a new revenue stream from idle balances:** You choose the underlying assets and decide how earnings are split between your platform and your customers. - **Attract new users:** A clear financial incentive on balances creates new opportunities for innovative stablecoin offerings. - **Improve retention:** Customers get a reason to keep funds on-platform instead of moving them elsewhere. With Tempo, you get access to institutional-grade assets, enterprise-ready features, and strategy & engineering support to get to market fast with your Earn program. ## Access institutional-grade assets Tempo provides access to unique and diverse institutional-grade assets to cover a wide range of risk and return profiles for any use case. This includes tokenized money market funds, onchain lending, and institutional credit. Our team helps you evaluate asset issuers and protocols based on track record, security, liquidity, and operational fit. ## Build a fully custom Earn program into your product Earn works best when it lives inside the existing payment flow, and Tempo's enterprise features make it simple to launch Earn products. - **Privacy:** Unlike other chains, Tempo lets users earn onchain while keeping balances and activity private from other network participants through [Tempo Zones](/blog/introducing-tempo-zones). - **Reward economics:** Control over how rewards are split between you and your customers. - **Spend while earning:** Funds keep earning until they're needed, then become available for withdrawal, in the same flow. - **Account policies:** Set rules for who can access, hold, and transfer using Earn products, with transfer memos to support reconciliation. Your users and customers can opt into earning on their balances without leaving your platform. You can sponsor network fees, so they never manage a separate fee token. ## How Deel enabled global contractor rewards inside their app Deel built a stablecoin wallet on Tempo that lets global contractors hold dollar-backed balances, and earn rewards, all inside the Deel app. Tempo Zones keep contractor balances and payout history private. Fees stay predictable at any volume and are paid in stablecoins, so there are no gas spikes or volatile fee tokens to manage. Under the hood, Deel issues DLUSD with Bridge, Privy provides the embedded wallet, and Morpho powers the rewards product, all running on Tempo. [Read the Deel customer story](/customer-stories/deel/) ## Tempo provides strategy and engineering support to get to market, fast Tempo advises your team at every step so you can launch Earn programs to meet customer needs: - **Design around your requirements:** Working sessions to turn your compliance, liquidity, return, and user experience requirements into a launch-ready product design. - **Choose trusted partners that fit:** We connect you to the right partners and assess operational needs. - **Support launch of your Earn product:** Before launch, we validate key workflows and the user experience with you. ## Build your Earn product with Tempo Tempo combines payment infrastructure with hands-on support to help you build a custom Earn experience for your users. [Talk with our team](/earn/) --- ## Introducing Tempo Zones > Source: https://tempo.xyz/blog/introducing-tempo-zones/ > Language: en **_We're excited to introduce Tempo Zones, which bring [privacy](/blog/privacy-on-tempo) and scalability to Tempo. A zone is an EVM-compatible private chain that runs in parallel to Tempo Mainnet. Anyone can deploy a new zone on Tempo, and users can seamlessly and privately move funds between different zones._** ![How zones work](/blog/zone-overview.svg) ## How do zones work? Users can send funds to a zone address through a zone contract on Mainnet. Inside the zone, all transactions are private and invisible to the public. When first [depositing to the zone](/developers/docs/guide/private-zones/deposit-to-a-zone), the recipient and memo are encrypted, so only the sender and amount are visible on Mainnet. Each zone has an operator who builds blocks and confirms transactions. The operator is a trusted party in the zone and, besides the sender and recipient, is the only actor who can see the recipient of the transaction. The operator can see the balances and transactions between addresses in the zone. All transactions within a zone are private from the public, and the operator can never transfer a user's funds to another party. Users retain ownership of their assets at all times. As an example, a company could run a Tempo zone where it pays out its employees — one of several [enterprise payment](/blog/new-features-for-enterprise-payments) workflows enabled by zones. These transactions happen in a parallel blockspace, which lets Tempo scale its blockspace horizontally with every new zone. Each transaction in the zone is only visible to the company, the employee getting paid, and the relevant zone operator. This maps closely to real world expectations of privacy — when someone gets paid, they know that their employer is aware of it but expect it to be private from everyone else. Users can withdraw funds from a zone and send them to a destination on Mainnet privately. The sender's address is hidden with a cryptographic commitment which is only revealed to the recipient of the transaction. ## How does interoperability between zones work? Zones bring first class interoperability to Tempo while preserving privacy. Users can seamlessly move funds between zones by transferring them through Tempo Mainnet. This happens very quickly and in a privacy preserving manner. Try the testnet demo below to see how easy it is to move funds between zones: > Interactive cross zone transfer demo is available on the HTML page. Zones avoid fragmenting liquidity by letting users seamlessly withdraw tokens to Mainnet, swap them on a stablecoin exchange and deposit the results back into a zone. There is no need for each zone to build its own exchange and liquidity pool, they can just take advantage of pools available on Tempo Mainnet. The transaction remains private to everyone except the zone operator. Zones also avoid token fragmentation. Every [TIP-20](/blog/tip20) token deployed on Mainnet can be enabled in any zone by its operator, along with its [TIP-403](/blog/compliance-controls) policy. Assets can move freely between zones and take advantage of liquidity on Mainnet while preserving privacy. We're excited to announce that the first Tempo Zone is available on testnet today. Learn more about Zones by [reading the docs](/developers/docs/guide/private-zones), reviewing the [protocol specification](/developers/docs/protocol/zones), or by [exploring the source code](https://github.com/tempoxyz/zones). You can also use private balances on Tempo Testnet with your [Tempo Wallet](https://app.moderato.tempo.xyz/) starting today. ## Frequently Asked Questions **What trust assumptions are placed on the operator?** The operator can see all activity within the zone between addresses. The operator can also suspend a user's ability to transfer or withdraw funds based on its own compliance rules. **Who can run zones on Tempo?** Anyone will be able to deploy a zone on Tempo. The protocol software for zones is fully open-source and permissionless to run. For example, Conduit plans to support launching zones on Tempo, and we expect other infrastructure providers will as well. **How is privacy preserved at the node level?** Privacy is enforced down to the RPC level. To check your balances, your client must sign an auth-token with the keypair that controls the account. The RPC verifies the signature and then returns the balance. Attempting to read a balance for an account where you do not have the keypair will fail. **Which tokens can be used in a zone?** Any [TIP-20](/blog/tip20) token can enter any zone and be transferred privately as long as both of the following conditions are met: 1. The zone operator has enabled that token to transact in the zone. 2. The issuer of the TIP-20 has either enabled the zone (if they have a whitelist [TIP-403](/blog/compliance-controls) policy) or not disabled the zone (if they have a blacklist [TIP-403](/blog/compliance-controls) policy). **Can tokens run in multiple zones?** Yes. A [TIP-20](/blog/tip20) token deployed on Tempo Mainnet is immediately eligible to be enabled by the operator of any zone, and its compliance policies are mirrored. The same token can exist in multiple zones at once. **Can you transfer from zone to zone directly?** Today, transfers between zones go through Tempo Mainnet. You withdraw from one zone and deposit into another. This happens quickly and privately (amount, origin zone and target zone are visible publicly). **Can you do swaps within a zone?** No. To swap, you withdraw to Tempo Mainnet, use a stablecoin exchange there and deposit the result back into the zone. No one on Tempo Mainnet can see who initiated the swap or who received the proceeds on the zone. **Can an address inside a zone hold multiple assets?** Yes. A zone address can hold any [TIP-20](/blog/tip20) token that the zone operator enabled for the zone. **What is visible when someone deposits into a zone?** The token, amount and sender are visible on Tempo Mainnet. The recipient inside the zone is encrypted and hidden. Only the sender and the zone operator know who received the funds. **Can you see which zones an address has used?** Deposits into zones are visible on Tempo Mainnet, so you can see which zones an address has sent funds into. Withdrawals are also visible, but the sender from inside the zone is hidden. An observer can tell that funds left a zone but not which address inside the zone sent them. **How do deposits and withdrawals preserve privacy?** When depositing into a zone, the recipient address is encrypted so that no one else on Mainnet knows where the funds are going. Only the zone operator can decrypt the recipient. When withdrawing, the sender's address is hidden with a cryptographic commitment that is only revealed to the recipient. See the [deposit guide](/developers/docs/guide/private-zones/deposit-to-a-zone) and withdrawal guide for details. **What are the trust assumptions in more detail?** The operator can see all activity within the zone and controls transaction sequencing, inclusion, and liveness. The operator cannot transfer a user's funds to another party. Users retain ownership of their assets at all times, with funds held in a zone contract on Mainnet. For a full specification of the trust model, see the [Zones protocol documentation](/developers/docs/protocol/zones). --- ## Introducing Tempo, the payments-first blockchain > Source: https://tempo.xyz/blog/introducing-tempo/ > Language: en **_Tempo is a payments-first blockchain incubated by Stripe and Paradigm._** As stablecoins go mainstream, there's a need for optimized infrastructure. Tempo is purpose-built for stablecoins and real-world payments, born from Stripe's experience in global payments and Paradigm's expertise in crypto. To ensure Tempo serves a broad array of needs, we're excited to be working with a group of initial design partners, including: Anthropic, Coupang, Deutsche Bank, DoorDash, Lead Bank, Mercury, Nubank, OpenAI, Revolut, Shopify, Standard Chartered, Visa, and more. ## Tempo's payments-first design - Predictable low fees - Opt-in privacy - Payments/gas in any stablecoin via enshrined AMM - Payments-first UX (dedicated payments lane, memos, access lists, etc) - Scale (100K+ TPS, sub-second finality) - EVM-compatible, built on Reth ## Tempo brings real-world payments onchain - Global payouts, payins, and payroll - Embedded financial accounts - Fast and cheap remittances - Tokenized deposits for 24/7 settlement - Microtransactions - Agentic payments We're building Tempo with core principles of decentralization and neutrality. Tempo will be a neutral platform with respect to stablecoins, allowing users to make transfers and pay gas fees in any stablecoin. The blockchain will be secured by an independent and diverse validator set, with a roadmap toward permissionless validators. We're partnering with builders across fintech, banking, ecommerce, agentic finance, and more — if you'd like to build with us, [get in touch](https://tempo.xyz/contact). --- ## Karta is building its self-custody money app on Tempo > Source: https://tempo.xyz/blog/karta-is-building-its-self-custody-money-app-on-tempo/ > Language: en **_Karta, a self-custody money app with more than 25,000 monthly cardholders and 1,250+ business teams across 150+ countries, is building on Tempo. Karta's treasury is live on Tempo today, and Karta Personal launches on Tempo soon._** [_Read the full Karta case study_](https://tempo.xyz/customer-stories/karta) Karta is a self-custody money app: a Visa card accepted in 150+ countries, fiat virtual accounts available in the US today with expansion underway globally, and one wallet to earn, spend, and send across currencies. Karta's uses [Privy](https://www.privy.io/) for self-custody wallets, [Bridge](https://bridge.xyz/) for fiat rails and virtual accounts, and Tempo for settlement. Privy's embedded wallets manage keys, signing, and authorization policies in the background, so Karta can deliver a seamless self-custodial experience that still meets the reliability requirements of real-time payments. ## Building self-custody payments at consumer scale Onchain card products have historically had to navigate a set of constraints that traditional payment infrastructure does not face. According to Karta, four are material: - **Gas.** On a general-purpose chain, every transaction requires a native gas token. Users have to acquire that token before they can move the asset they actually care about. - **Per-transaction signing.** In a pure self-custodial model, every transaction requires a live signature from the wallet owner. Asynchronous flows like card authorizations cannot pause while a user opens an app to approve. - **Finality as a fraud surface.** Seconds-long finality creates a window for double-spend attempts and race conditions that millisecond-level card authorization flows cannot tolerate. - **Structured metadata.** Reconciliation, compliance, and dispute resolution depend on per-transaction context. Rebuilding that from event logs is fragile. Each of these has been solved individually on different chains. Paymaster contracts abstract gas. Session keys and account abstraction approximate asynchronous signing. Emerging rollups approach sub-second finality. Specialty payment chains expose structured metadata. > At Karta, self-custody isn't a feature, it's the architecture. Every user holds their own stablecoin balance on their own wallet, and every transaction they make settles on-chain. Doing that at consumer scale was only possible on infrastructure built for payments, not retrofitted for them. Tempo is the first chain where we didn't have to trade self-custody for a product that actually works. > > — Nik Zimarkov, Co-founder and CEO, Karta ## How Tempo addresses these constraints Tempo is a payments-purpose-built chain. Each constraint above maps to a native Tempo capability. - **Sub-second deterministic finality.** Transactions finalize on-chain in approximately 500ms with no re-orgs, inside standard card authorization windows. - **Stablecoin-native gas.** Gas is paid in USD stablecoins at the protocol level. No native gas token, no paymaster contracts, no ERC-4337 retrofits. - **Access Keys.** A protocol-level primitive for authorized debits against a wallet without custody transfer. Card authorizations can settle asynchronously against an on-chain balance without a live wallet signature at authorization time. - **Dedicated payment lanes.** Payment traffic has guaranteed blockspace at the protocol level, insulated from unrelated network activity. - **Structured memo fields.** Native per-transfer metadata, ISO 20022-compatible, supports reconciliation and compliance workflows. Karta's treasury is live on Tempo today. Karta Personal launches on Tempo soon, alongside fiat virtual account expansion to new markets. Karta Business migrates onto the same settlement layer shortly after. ## Get started Tempo is incubated by Stripe and Paradigm and built for payment use cases like Karta's: card issuance, treasury operations, and consumer payments. [Read the Karta case study](https://tempo.xyz/customer-stories/karta) --- ## KAST is bringing its stablecoin earn product onto Tempo and joining as design partner > Source: https://tempo.xyz/blog/kast-stablecoin-earn-product-tempo-design-partner/ > Language: en **_KAST, a financial platform available in 170+ countries and built on stablecoin rails, plans to launch its stablecoin earn product on Tempo. Additionally, KAST is working with Tempo as a design partner to help shape new features and products for consumer stablecoin payments._** [_Read the case study_](/customer-stories/kast) KAST is a financial platform for users to store, earn, move, and spend stablecoins. KAST plans to enable their users to earn on their idle stablecoin balances on Tempo, directly in the KAST app. The product is designed to be always-on and globally accessible, with room to extend across new product designs and asset types over time. > KAST is focused on building real financial products that scale globally. Tempo gives us a foundation to build on what stablecoin rails can unlock across payments and the next generation of money movement. > > — Raagulan Pathy, Founder & CEO, KAST KAST provides USD-denominated accounts, global pay-ins and payouts to more than 170 countries and is accepted at 150 million merchants. KAST users in LATAM, MENA, and Asia benefit from KAST’s frictionless movement of money, given the difficulty of traditional banking and cross-border payments in those regions. Workers paid across borders, families sending money home, and small businesses operating in multiple currencies use KAST to hold, move, and spend stablecoin balances in places legacy rails struggle to reach. KAST and Tempo are also working together as design partners to shape new features and products for the next frontier of stablecoin money movement. KAST’s user base across LATAM, North America, MENA, and Asia provide a real-world testing ground for what consumer stablecoin products need at scale. ## What's next Over the coming months, KAST and Tempo plan to explore direct settlement and real-time authorizations to unlock faster, more reliable money movement. [Talk to us](/contact) · [Browse the ecosystem](/ecosystem) · [Learn about stablecoins](/learn/what-are-stablecoins) --- ## Knova and Tempo help institutions launch tokenized products without rebuilding systems > Source: https://tempo.xyz/blog/knova-tempo-tokenized-products/ > Language: en **_Knova helps financial institutions launch tokenized payment products while keeping their existing systems and providers. Its partnership with Tempo connects payments, stablecoins and tokenized deposits to those systems through one operating platform. [Request a briefing on the Knova integration.](https://tempo.xyz/contact/?utm_source=tempo_blog&utm_medium=referral&utm_campaign=knova_partnership&utm_content=integration_briefing)_** ## One platform for traditional and tokenized assets Knova is a financial operations platform that connects institutions’ existing systems, asset data and transaction workflows. Banks and other financial institutions can use it to coordinate traditional and digital assets while continuing to work with their custody and payment providers. The platform combines three components. Connectors link the systems an institution uses. Digital Twin Assets create standardized records of assets, including ownership and current state. A Transaction Workflow Engine uses those records and connections to automate operations across blockchain networks and existing financial systems. That gives institutions a way to manage processes that span multiple assets and providers. Knova’s platform supports workflows such as netted settlement, moving balances between accounts and converting between traditional money and stablecoins. Knova coordinates these operations without holding customer assets. ## Connecting Knova to Tempo Knova’s partnership with Tempo focuses on bringing that simplified operating model to payments, stablecoins, and tokenized deposits on Tempo. For financial institutions, the aim is to connect a new settlement network to the systems and processes they’re already running. Institutions can connect supported TIP-20 assets on Tempo or create new tokens through Knova. Knova supports TIP-20 transfers and, where the institution has the required issuer permissions, minting and burning. The integration also credits inbound on-chain deposits and debits outbound withdrawals. Supported Tempo assets and events connect to Knova’s Transaction Engine and digital twins, so institutions can configure workflows and automations and apply AI-driven insights and actions. Knova uses Tempo’s webhooks to receive on-chain updates. Institutions sign transactions through a supported wallet provider of their choice, with custody remaining with the institution or its chosen custody provider. ## An illustrative tokenized deposit workflow ### Issuance and bank controls Consider a bank that wants to issue tokenized deposits backed by customer funds. It could configure approval and screening steps in Knova’s Transaction Engine, using its existing compliance systems for KYC, AML and sanctions checks. Knova would orchestrate those checks rather than perform them. The bank could place these steps before issuance or elsewhere in the workflow, based on its risk and compliance requirements. Once the configured checks pass, Knova could instruct the bank’s core system to move the corresponding funds into a settlement account, where the bank’s controls reserve them for redemption. Using an account with the required issuer permissions, the workflow could then mint the equivalent TIP-20 balance on Tempo. A digital twin record would link that on-chain balance to the reserved funds. ### Private transfers between banks Using Tempo Zones, currently available on testnet only, a bank could operate its own private execution environment. Knova could coordinate both banks’ configured checks before routing a transfer between their Zones. This would allow the banks to transact without exposing their broader internal balances and transaction histories to each other or public observers. Each Zone operator would retain visibility into its own Zone to support compliance processes. Some deposit and withdrawal information would remain visible on the public chain. ### Liquidity and redemption As balances accumulate, the bank could configure Knova to reconcile and rebalance funds across its traditional payment systems at specified thresholds or on a schedule. Those movements would follow the bank’s reserve and liquidity controls. On redemption, the workflow could first return the customer’s tokens to an issuer-authorized account for burning. Only after the burn is confirmed via Tempo’s webhook would the bank’s core system release the corresponding reserved funds to the customer. Knova would reconcile the traditional ledger and on-chain balances as each step is confirmed. This example shows how Knova can coordinate institutional systems and operational workflows around settlement on Tempo. The exact configuration depends on the bank’s systems, permissions and controls. ## Why Tempo Knova is chain-agnostic by design. Its platform connects institutions’ existing systems to supported networks for a given asset or workflow. Tempo adds a network built for payments, with fast, low-cost settlement. The integration brings token operations on Tempo into Knova’s configurable workflows and controls. Tempo is a blockchain built for payments, incubated by Stripe and Paradigm. Standard token transfers typically cost less than a tenth of a cent, with fees payable in supported USD stablecoins. Payment memos carry references that help enterprise operations teams match transfers to their internal records. > “Our goal is to make it dramatically easier for financial institutions to launch tokenized payment products without rebuilding their existing infrastructure. Together with Tempo, Knova provides the operational layer to connect systems, automate workflows, and reconcile activity—helping institutions move from idea to production faster, all from one control plane.” > > Natalya Thakur, CEO, Knova > “Knova is helping financial institutions bring stablecoins and tokenized deposits into the systems they already use. We’re glad to support that work as Knova brings more institutional payment flows onto a network designed for payments.” > > Ninad Nirgudkar, GTM, Tempo ## Discuss your integration If your institution is evaluating payments, stablecoins or tokenized deposits on Tempo, [request a briefing on the Knova integration](https://tempo.xyz/contact/?utm_source=tempo_blog&utm_medium=referral&utm_campaign=knova_partnership&utm_content=integration_briefing) so our teams can help you work out the best path forward. --- ## Kraken adds native support for USDT0 deposits and withdrawals on Tempo > Source: https://tempo.xyz/blog/kraken-adds-native-support-on-tempo/ > Language: en **_Kraken now supports deposits and withdrawals of USDT0 on Tempo, making it the first U.S. exchange to natively support the network._** Kraken clients can now move USDT0 on Tempo: sub-second settlement, fees paid in stablecoins, no separate gas token required. USDT0 is designed to move across networks while remaining redeemable 1:1 for the underlying USDT reserve. On Tempo, dollar-denominated value moves between Kraken and Tempo wallets and applications with deterministic finality in roughly 0.6 seconds. For exchanges, stablecoin transfers are a core funding rail. Clients expect money to move quickly and at low cost. Tempo was built for that: a payments-first Layer 1 with stablecoin-native fees, dedicated payment lanes for predictable costs during high activity, and settlement finality without re-orgs. For Kraken clients, stablecoin funding is faster and simpler, without the overhead of managing a separate gas asset. ## What's next Kraken and Tempo will continue to explore additional use cases. More partner spotlights from the Tempo ecosystem coming soon. --- ## Kraken and Tempo partner to bring institutional stablecoin infrastructure to payments > Source: https://tempo.xyz/blog/kraken-and-tempo-partner-to-bring-institutional-stablecoin-infrastructure-to-payments/ > Language: en **_Kraken is the first U.S. centralized exchange to support Tempo, giving fintechs, neobanks, payment companies, and stablecoin issuers building on Tempo access to liquidity, custody, on/off-ramps, execution, and listings support in one unified stack. [Get in touch](https://tempo.xyz/contact/)._** ## Institutional infrastructure for stablecoin payments Companies building stablecoin payment products need more than a chain. They need reliable ways to move between fiat and stablecoins, source liquidity, custody reserves, and support treasury operations. Those functions are often split across multiple vendors: one for OTC liquidity, another for custody, another for on/off-ramps, another for compliance. Each relationship adds diligence, integration work, and coordination overhead. Kraken gives teams building on Tempo a single centralized exchange partner for all of it. ## What the partnership enables USDT0 and USDC.e deposits and withdrawals are live on Kraken via Tempo, with native chain support. For teams building wallets, payment products, remittance flows, or stablecoin issuance products, that's a direct bridge between Tempo-based assets and one of the largest global crypto platforms. The institutional stack covers five areas: - **Liquidity and OTC.** Kraken provides spot and OTC liquidity across stablecoins, fiat pairs, and major digital assets, supporting settlement, treasury balancing, and high-volume conversion. - **On/off-ramps.** Teams can access fiat and stablecoin movement through Kraken's APIs and embedded services from Payward Services. That matters for products built around cross-border payments, payouts, and remittance. - **Qualified custody.** Kraken Financial, a Wyoming SPDI, provides qualified custody for stablecoin reserves, operating treasuries, and protocol assets. - **Listings support.** Tokens and stablecoins launching natively on Tempo get an introduction to Kraken's listings team, creating a clearer path from launch to distribution. - **Compliance operations.** Kraken's institutional stack includes KYB, transaction monitoring, and sanctions screening, reducing the compliance infrastructure each team needs to build from scratch. ## Why this matters for builders Fast settlement and low fees solve part of the payment problem. But shipping a real payment product also means sourcing liquidity, accessing fiat rails, managing custody, and handling compliance. Those requirements get harder to ignore as volume grows. Working with Kraken means Tempo builders can get to market without stitching together separate vendor relationships for each of those needs. If you're building stablecoin payments, issuing a token, or bringing financial products onchain, [get in touch](https://tempo.xyz/contact). --- ## Tempo Mainnet is live > Source: https://tempo.xyz/blog/mainnet/ > Language: en **_We’re excited to share that Tempo Mainnet is live!_** Tempo is infrastructure for real-world payments at internet scale. It’s designed for instant settlement, predictable low fees, high throughput, and global availability. Starting today, you can build on Tempo through our public RPC endpoints. [Start building](/developers/) Alongside mainnet, we’re also introducing the [Machine Payments Protocol](https://mpp.dev/) (MPP), an open standard for machine payments co-authored by [Stripe](https://stripe.com/) and Tempo. More below. When we first [announced](https://tempo.xyz/blog/introducing-tempo) Tempo in September, our premise was simple: if stablecoins become a core layer of internet commerce, the infrastructure that moves money needs to be purpose-built for payments. Stablecoins make it possible to move value across borders with instant settlement and continuous availability. But most existing blockchains were not designed for large-scale payment workloads. Fees fluctuate, throughput is limited, and transaction structures are poorly suited to common payment flows. Unlike other blockchains, Tempo was designed around the requirements of real payment systems: predictable costs, high throughput, and reliable settlement for large volumes of transactions. Over the past several months, a new class of applications has started to make those requirements much more visible: ## The rise of agentic payments Agents can already write code, coordinate services, retrieve data, and execute complex workflows across the internet. But as these systems become more capable, they increasingly need to transact. A research agent may pay for access to a dataset. A development agent may purchase compute or testing infrastructure. A workflow agent might coordinate several services, paying each one as it completes a task. In these environments, payments become continuous and programmatic. Instead of a single transaction between two parties, a single workflow may involve dozens or hundreds of small payments across different services. This pattern quickly exposes the limitations of existing payment rails. Traditional payment systems assume human-initiated transactions and manual approval flows. Many blockchains, meanwhile, were not designed for high-frequency, low-value transactions where predictable costs and reliability matter most. Tempo provides the settlement infrastructure for this scale of interactions, allowing agents to transact programmatically. ## Introducing the Machine Payments Protocol ![Machine Payments Protocol Thumbnail](/images/blog/mpp_thumb.png) To build these foundations, we’re releasing the [Machine Payments Protocol](https://mpp.dev) (MPP), an open standard for machine payments. MPP is designed to be extensible and agnostic to any payment method, already working with stablecoins, cards, and more [supported payment methods](https://stripe.com/blog/supporting-additional-payment-methods-for-agentic-commerce). MPP provides a standard way for agents and services to coordinate payments programmatically. Instead of each service inventing its own billing flow, MPP defines a simple protocol for requesting, authorizing, and settling payments between machines. We decided to launch MPP as an open standard so that machine payments can work consistently across services and payment rails. MPP runs on Tempo today, but the protocol itself is designed to be rail-agnostic and extensible. For example, our design partner Visa has already extended MPP to support [card-based payments](https://mpp.dev/payment-methods/card) on their network. Stripe has extended it to support cards, wallets, and other payment methods through their platform. Lightspark has also extended it for [Bitcoin payments](https://mpp.dev/payment-methods/lightning) over the Lightning network. ### Sessions for streaming payments ![How MPP Sessions Work](/images/blog/how_mpp_sessions_work.png) MPP lets an agent pay for services autonomously: an agent can request a resource from a service, and the service responds with a payment request. The agent then authorizes payment from its wallet, the transaction settles instantly, and the service delivers the requested resource to the agent. This is made possible with a new primitive called [sessions](https://mpp.dev/payment-methods/tempo/session#how-it-works), which allows for continuous payments. Think of it as OAuth for money: authorize once, then allow payments to execute programmatically within defined limits. When an agent opens a session, it sets aside funds upfront. As the agent consumes resources from services (an API call, a model inference, a data query, etc.), payments stream continuously without requiring a separate onchain transaction for each interaction. Thousands of small transactions can be aggregated into a single settlement transaction, making true pay-per-use payments viable at internet scale. ### Payments directory ![MPP Payments Directory](/images/blog/payments_directory.png) Our new [payments directory](https://mpp.dev/services) provides a unified catalog of MPP-compatible services that any agent can transact with automatically. Service providers can integrate to monetize their service and become discoverable to agents as well. MPP enables a variety of use cases, including pay-per-call APIs, monetized MCP servers, gated content and data, multi-service workflows, and much more. At launch, the payments directory already includes integrations with more than 100 services spanning model providers, developer infrastructure, compute platforms, and data services, including [Alchemy](https://www.alchemy.com/), [Dune Analytics](https://dune.com/home), [Merit Systems](https://www.merit.systems/), and [Parallel Web Systems](https://parallel.ai/). ### Infrastructure for payments at scale While agents represent a new class of commerce emerging on Tempo, we’ve architected the infrastructure to support established payment flows such as global payouts, cross-border remittances, embedded finance, and tokenized deposits, which remain surprisingly cumbersome to build and operate today. Since launching the [public testnet](https://tempo.xyz/blog/testnet) in December, we’ve been working with design partners across payments, commerce, and financial services to bring real payment workloads onto stablecoins: - **Global payouts.** Platforms distributing payments to workers, sellers, and creators often process millions of disbursements at once. These systems require predictable costs and reliable throughput. Tempo’s dedicated payment lanes allow large payout runs to settle instantly without congestion or fee spikes. - **Cross-border remittances:** International transfers today often move through several intermediaries and settle over multiple days. Partners are testing remittance corridors on Tempo that settle in seconds with full auditability and predictable costs. - **Embedded finance.** Software companies increasingly embed payment flows directly into their applications. Tempo’s smart accounts and protocol-level memos allow developers to integrate financial workflows directly into products without building separate ledger infrastructure. - **Tokenized deposits:** Financial institutions are exploring tokenized representations of deposits and other assets that can settle continuously rather than within traditional banking hours. Tempo provides reconciliation primitives and compliance registries that mirror traditional financial controls while enabling real-time settlement. We’re working with [partners](https://tempo.xyz/ecosystem) including Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, Standard Chartered, and Visa to bring these use cases onto mainnet. We’ll also be introducing additional features designed specifically to support enterprise payment workloads, and we’ll have more to share in the coming months. ## Start building on Tempo Tempo Mainnet is live today. Developers building agents can start using MPP to let agents pay for services. Fund an agent wallet, define spending limits, and allow your agents to transact autonomously across the internet. Builders working on global payment systems can use Tempo’s infrastructure for high-throughput settlement, cross-border transfers, and embedded financial workflows. You can get started in a few ways: ### Create a wallet Create a wallet on Tempo to run your first transaction. [Create a wallet](https://wallet.tempo.xyz/welcome) ### Explore the Machine Payments Protocol Explore MPP docs and SDKs to let agents pay for services programmatically. [Read the docs](https://mpp.dev/overview) ### Monetize your API List your service in the payments directory so agents can transact with it automatically. [Get listed](https://mpp.dev/services) ### Build directly on Tempo Mainnet Connect to Tempo through the public RPC endpoints and start building. [Start building](/developers/) --- ## Meow and Tempo partner to bring stablecoin-native banking to global businesses > Source: https://tempo.xyz/blog/meow-and-tempo-stablecoin-native-banking/ > Language: en **_Meow is bringing payments-grade stablecoin infrastructure to its business banking platform on Tempo. Together, the companies will support instant settlement, automated financial operations, and global payouts for businesses and AI agents. [Get in touch](/contact) if you're building stablecoin payment or treasury products._** ## Stablecoin infrastructure for modern businesses [Meow](https://www.meow.com/) powers banking for AI agents and global teams. Corporate cards, invoicing, payouts in 50+ currencies, treasury, and stablecoins like USDC and USDT run from one platform, with the approvals and spend controls finance teams need, for domestic and multi-national businesses. Meow lets multi-national businesses and AI agents open and operate a business bank account end to end. Tempo gives Meow customers a new settlement layer: a payments-first blockchain built for predictable, high-volume activity with transactions that settle in under a second for a fraction of a cent. ## What the partnership enables Tempo provides dedicated payment lanes with protocol-reserved blockspace, deterministic finality in under a second, and capacity above 20,000 transactions per second. Unrelated network activity, like NFT mints or memecoin trading, can't consume the blockspace reserved for payments. For Meow customers, that means stablecoin transfers stay fast and predictable when payment timing matters. Tempo also provides protocol-level primitives for automated financial operations: - **Scheduled payments** for recurring invoices, and vendor obligations. - **Batch transactions** for processing large payout runs efficiently. - **Smart accounts and passkey authentication** for programmable access with familiar authorization flows. - **Gas sponsorship** so customers can transact without acquiring a separate network token. These primitives give AI agents safer building blocks for accounts payable, accounts receivable, and treasury operations. Businesses define permissions and controls; agents execute the approved financial workflows. > “There's a clear need for a solution like Tempo. We're excited to have Meow be Tempo's premier business banking fintech partner.” > > Brandon Arvanaghi, CEO, Meow ## Why this matters for enterprises The partnership will extend Meow's business banking experience with stablecoin settlement on Tempo. That gives finance teams one settlement layer for activity that traditionally spans bank accounts, payment processors, and blockchain networks. Once live, customers can invoice, send, and receive funds 24/7, with near-instant finality and network fees below a cent. The same rails handle global vendor, and contractor payments, so businesses can send stablecoins across borders without waiting for correspondent banks or local banking hours. For companies managing distributed teams and international suppliers, that means faster delivery, clearer payment status, and fewer intermediaries. Meow and Tempo will keep working together to make stablecoins a practical foundation for business banking, global payments, and agent-led financial operations. [Get in touch with Tempo](/contact) if you're building stablecoin payment or treasury products. --- ## Morpho is now live on Tempo > Source: https://tempo.xyz/blog/morpho-is-now-live-on-tempo/ > Language: en **_Morpho is now live on Tempo. Enterprises and apps on Tempo can now use Morpho in DeFi use cases, including earn products, lending, and onchain credit. [See Tempo Earn](/earn/)._** [Morpho](https://morpho.org/) is an open credit network for lending and borrowing, enabling builders to create lending markets, vault-based earn products, and other onchain credit applications. Enterprises looking to build DeFi use cases on Tempo, including earn products, lending, and onchain credit, can [get in touch](/contact). --- ## Introducing MPP Credits: fund your agent with a card > Source: https://tempo.xyz/blog/mpp-credits/ > Language: en **_MPP Credits are a new way for developers and agents to pay for MPP services using a credit or debit card. Buy credits from the Agent payments page in Tempo Wallet and let your agent spend on MPP-enabled services, with merchants settling in stablecoins on Tempo._** [_Fund your agent_](https://wallet.tempo.xyz/agent?action=fund&intent=credits) The [Machine Payments Protocol (MPP)](https://mpp.dev/) is an open standard for machine payments, co-authored by Stripe and Tempo. Agents use it to pay for the things they need as they work, whether that's LLM inference, compute, data, or other API services. Until now, funding an agent's wallet meant moving stablecoins onto Tempo first, which adds a step most developers don't want and many can't easily complete. Now, with MPP credits, you can directly fund your agent with a card. ## What MPP Credits are MPP Credits work like the API credits you already buy from developer platforms. You add a card, purchase credits, and your agent spends them at MPP services. The differences are under the hood: credits live in your Tempo Wallet, they work across every Tempo-proxied MPP service rather than a single provider, and merchants receive settlement in USDC.e on Tempo within seconds. A few things to know: - Credits are redeemable only at MPP services. See the full list in [the MPP Services Directory](https://mpp.dev/services). - Credits are prepaid and non-refundable. They can't be withdrawn, swapped for other tokens, or converted back to fiat. Treat them like API credits, not like a wallet balance. - Credits are issued by [Coinflow](https://coinflow.cash/), a licensed payment service provider. Coinflow handles card processing and settles instantly with merchants in stablecoins. ## Why credits Card onramps into crypto have historically lost a large share of users at the first payment step due to low authorization rates. MPP Credits support for credit and debit cards globally plus Apple Pay and Google Pay, and saved cards for instant top-ups. Your agent runs out of funds mid-task, you approve a top-up, and it keeps working. MPP was designed to support any payment method, including stablecoins and cards. Credits are the first card-based path into the protocol. ## How it works 1. Your agent calls an MPP-enabled API and receives a 402 Payment Required response. 1. If the wallet has insufficient funds, run `tempo wallet fund` . For credit-enabled services, you're directed to a standard checkout at [wallet.tempo.xyz](https://wallet.tempo.xyz). 1. Enter your card once and save it, so future top-ups happen instantly. 1. Your agent spends credits at MPP services programmatically. Check your balance and where it's accepted with `tempo wallet whoami --credits`. ## Get started MPP Credits are accepted at Tempo-proxied MPP services, including LLM inference, compute, and data APIs. Browse [the MPP Services Directory](https://mpp.dev/services). Buy your first credits from [wallet.tempo.xyz/agent](https://wallet.tempo.xyz/agent?action=fund&intent=credits), or point your agent at the Tempo CLI and let it walk you through funding when it hits its first 402. Read the MPP spec and browse services at mpp.dev. --- ## MPP Sessions: Web-Scale Payments for AI Agents > Source: https://tempo.xyz/blog/mpp-sessions/ > Language: en **_Agents need to transact at speeds that today's payment rails can't support. MPP Sessions fix this by collapsing unlimited micropayments into two onchain transactions: one to open a session, one to settle. If you're building agents or agentic payment infrastructure, get started at [mpp.dev](https://mpp.dev/payment-methods/tempo/session) or read the [machine payments guide](/developers/docs/guide/machine-payments)._** Agents already write code, handle customer support, and help people organize their schedules. To be truly helpful, agents need to be able to pay. This is why we partnered with Stripe to create the [Machine Payments Protocol](https://mpp.dev/). However, agents must be able to transact far faster than even the fastest payment systems allow. Card schemes, today's most performant payment rails, can process thousands of transactions per second. That's a lot when most payments are still made by humans. It's nothing when payments are made by tireless AI agents. [MPP Sessions](https://mpp.dev/payment-methods/tempo/session), an MPP primitive, was built to fix this. MPP Sessions allow the underlying payment rails to scale to 1 million TPS and beyond, which is the scale needed to support the agentic future. ## An architecture built for speed Enabling agents to pay at machine speed requires solving two problems: how machines pay, and how to scale the rails underneath. MPP addresses the first. MPP Sessions address the second: - **MPP lets machines pay** for services (including services provided by other agents) in real time, over plain [HTTP](https://mpp.dev/protocol/http-402). Today, the protocol enables two payment modes (or "[intents](https://mpp.dev/payment-methods)"): "[charge](https://mpp.dev/payment-methods/tempo/charge)" for one-time payments (e.g. an API call), and "[sessions](https://mpp.dev/payment-methods/tempo/session)" for continuous usage (e.g. compute). - MPP is agnostic to payment rails, and **MPP Sessions is what allows those rails to scale** to machine speed of agents. Instead of settling every payment individually, a session requires only two transactions to handle an unlimited number of payments. You can think of sessions as a card authorization at a gas station. The pump pre-authorizes a hold, then charges the final amount when done. Two transactions, regardless of how much gas flows. MPP Sessions work the same way: **every gallon is metered, but only two transactions hit the rail**. ## How MPP sessions work on Tempo Tempo provides the **reference implementation of [MPP Sessions](https://mpp.dev/payment-methods/tempo/session) on a blockchain**. A session requires only two transactions, but those two transactions need to settle instantly and definitively. [Tempo's](https://mpp.dev/payment-methods/tempo) sub-second finality ensures they do. A payment session goes through a simple lifecycle: open a session, consume the service, settle once at the end. ![MPP session lifecycle: open, consume, settle](/blog/mpp-sessions/1.png) - With MPP, when an agent requests a paid resource, the server responds with a [402](https://mpp.dev/protocol/http-402) and the supported payment options. **The [Tempo payment method](https://mpp.dev/payment-methods/tempo) enables payments using stablecoins**, and supports both the "[charge](https://mpp.dev/payment-methods/tempo/charge)" and the "[session](https://mpp.dev/payment-methods/tempo/session)" intents. ![402 payment challenge flow](/blog/mpp-sessions/2.png) - For continuous usage (e.g. paying for LLM tokens as they stream in), **an agent opens a payment session** by depositing funds into an onchain escrow. The server then streams data back to the client. For predictable recurring charges, the same account model also supports [subscriptions on Tempo](/blog/subscriptions-on-tempo). ![Opening a payment session with escrow deposit](/blog/mpp-sessions/3.png) - For each unit of service consumed, **the agent signs an offchain message, or a voucher,** with an incremented cumulative amount. A new voucher goes out on every stream tick (per token, per video chunk, per byte). ![Off-chain voucher exchange during streaming](/blog/mpp-sessions/4.png) - **Vouchers are exchanged offchain.** The server only needs to verify a cryptographic signature before continuing to stream data, which takes microseconds. Each voucher replaces the previous one, so the server only needs to submit the last one onchain to [settle](https://mpp.dev/protocol/receipts). ![Final settlement with last voucher](/blog/mpp-sessions/5.png) - When the session ends, the agent closes it and **the server submits the latest voucher onchain**. The payment settles, and any unused funds from the original deposit are released back to the agent's wallet. The result: you pay for exactly two onchain transactions (open and close), whether 10 or 10,000 vouchers were exchanged in between. That's what makes sessions highly cost-efficient and enables millions of micropayments with near-zero fees. ## MPP session demo This demo runs an MPP session on Tempo's testnet, Tempo Moderato. Click Sign up to create a wallet and Authorize a $10 PathUSD access key. The access key lets the session run without you having to sign every voucher. Click Send query to run the session: it opens a session, streams tokens with signed vouchers, and closes the session with a final transaction that settles the final amount and returns unused funds. > Interactive mpp sessions demo is available on the HTML page. ## Where MPP sessions matter From AI inference to financial markets to industrial IoT, MPP sessions enable real-time payments at scale. For example: - **AI agent orchestration.** A coordinator agent delegates tasks to specialized sub-agents: a web search agent, a summarization agent, a fact-checking agent, each charging per operation. The coordinator opens one session per sub-agent and settles once at the end. For recurring agent workloads, sessions pair naturally with [subscriptions](/blog/subscriptions-on-tempo) to cap periodic spend. - **LLM inference marketplace.** An agent queries multiple LLM providers simultaneously and pays per token as responses [stream in](https://mpp.dev/guides/streamed-payments). MPP sessions allow the agent to pay for consumed tokens in real time, with settlement costs amortized across the entire session. - **Dynamic compute allocation.** An AI agent runs inference across a marketplace of GPU providers, switching between them based on real-time pricing. The agent opens [sessions](https://mpp.dev/payment-methods/tempo/session) with multiple providers and pays per millisecond of compute time, redirecting work instantly as prices shift. - **Real-time data feeds.** A trading agent consumes market data from multiple providers, paying per tick at thousands of updates per second. MPP sessions enable the agent to pay for each update with an offchain voucher verified in microseconds. - **IoT microtransactions.** Industrial sensors sell real-time data to systems that need it. A weather station provides temperature and humidity readings to an agricultural AI, billing per data point. A supply chain sensor streams location data to logistics systems, billing per update. In each case, the speed and cost structure of MPP sessions turn micropayments from a theoretical concept into practical infrastructure. Sessions are part of a broader set of [enterprise payment features](/blog/new-features-for-enterprise-payments) on Tempo. To learn more about machine payments on Tempo, see the [machine payments overview](/developers/docs/guide/machine-payments/). ## Start building with MPP Whether you're building AI agents or infrastructure for machine-to-machine payments, we can help you get started: ### Learn about the Machine Payments Protocol Understand the fundamentals of MPP, how payment sessions work, and the problems they solve. The protocol specification defines how machines negotiate payments over HTTP. [Read the spec](https://mpp.dev) ### Learn about Tempo's implementation of MPP Explore how Tempo implements MPP with native blockchain primitives, including one-time charges and pay-as-you-go sessions. Start with our documentation to understand the architecture. [Read the docs](https://mpp.dev/payment-methods/tempo) ### Use SDKs If you're ready to build, download SDKs for your language of choice in TypeScript, Python, or Rust. Our libraries handle session management, voucher signing, and settlement. [Get started](https://mpp.dev/sdk) ## Frequently Asked Questions ### What is a session? MPP sessions are a payment primitive in the Machine Payments Protocol that let AI agents and machines transact at scale. A session requires only two onchain transactions, one to open and one to settle, regardless of how many payments occur in between. ### Why not send an onchain transaction per request? Because it's too slow and expensive. Sessions move payments offchain so high-frequency, low-value payments can happen without onchain overhead. ### How do payments work during a session? The client sends signed vouchers representing cumulative payment. A voucher is a signed offchain message from the client that represents how much the server can claim from the session. The server verifies each voucher locally. No onchain interaction is needed per request. ### How is the final payment settled? The final payment is settled in an onchain transaction where the server submits the latest voucher to claim its payment from escrow, and any remaining funds are released back to the client. ### What guarantees payment and prevents overspending? Funds are locked onchain in an escrow contract at session start, and vouchers are signed by the client. The server can only claim what the client signed, and the client cannot exceed the locked amount. ### When should I use sessions? For continuous, usage-based payments like LLM tokens or streaming. ### What are the costs of using MPP sessions? An MPP session requires exactly two onchain transactions regardless of session length: one to open (deposit into escrow) and one to close (settle the final amount). All intermediate payments are offchain vouchers with zero transaction fees. ### How fast is this? Voucher verification is just a signature check, so it runs inside the request loop without waiting onchain. --- ## New features on Tempo for enterprise payments > Source: https://tempo.xyz/blog/new-features-for-enterprise-payments/ > Language: en **_Tempo is purpose-built for global payments at scale. Today we're shipping new capabilities that make more enterprise payment workflows work natively on stablecoins: subscription billing and auto pay through enhanced [access keys](/developers/docs/guide/tempo-transaction#access-keys), and per-customer deposit attribution, invoice-level reconciliation, and multi-tenant wallet structures through [virtual addresses](/developers/docs/guide/payments/virtual-addresses). All live on mainnet. If you're evaluating any of these workflows, our Stablecoin Advisory team can help you scope the use case and get to production at [tempo.xyz/contact](https://tempo.xyz/contact/)._** Tempo is a payments-first blockchain, built to give enterprises the rails they need to move money globally on stablecoins. Last week we launched Stablecoin Advisory and introduced the first wave of enterprises going live on Tempo. Today we're adding new capabilities to the network that bring more of the payment workflows enterprises run every day onto stablecoins. Stablecoin infrastructure has made one-time global payments practical, but the recurring flows, attribution challenges, and multi-tenant wallet patterns that make up the rest of enterprise payment operations have been harder. New features on Tempo close those gaps. ## Recurring payments with enhanced access keys Recurring billing on stablecoins has forced a tradeoff that neither option handles well. Businesses have had to either re-prompt users at every charge, which breaks the subscription model, or ask users to pre-authorize significantly more funds than they actually need, which degrades the user experience and increases risk for the consumer. Enhanced [access keys](/developers/docs/guide/tempo-transaction#access-keys) remove that tradeoff. A user authorizes a per-period cap once, for example $50 per week for 52 weeks, and the service charges on schedule within that limit. The cap resets automatically when the period ends, and the user can revoke the authorization at any time. Access keys can also be scoped to a specific contract, so a key authorized for one service cannot be used to interact with anything else. ![Subscriptions on Tempo](/blog/subscriptions-on-tempo-diagram.png) This makes several common enterprise billing patterns practical on stablecoins for the first time. ### Subscription billing SaaS companies, streaming services, and any business with a fixed recurring charge now have a native stablecoin path. A subscriber authorizes an access key once, and the service charges on the same schedule across every country the business operates in, with instant settlement and no regional payment integrations to maintain. ### Auto pay The same primitive enables auto pay for recurring obligations. Utility bills, rent, loan servicing, and any recurring business obligation can be paid on a schedule by authorizing a per-period cap to the payee. The pattern is functionally similar to ACH debits in traditional banking, with the difference that settlement is instant, the authorization is programmatically scoped to a specific payee, and the user can revoke at any time without contacting the payee. ### Metered and usage-based billing For services that charge variable amounts per period, access keys also support usage-based billing. A customer authorizes "up to $500 this month," and the service charges based on actual usage, whether that's API calls, compute time, data access, or throughput. The ceiling protects the customer, the recurring authorization simplifies operations for the service, and neither side has to manage prepaid credits or handle overage surprises. [Read more about access keys](/blog/subscriptions-on-tempo) ## Customer deposits and platform wallet structures with virtual addresses Every business that holds customer funds runs into the same problem. Giving each customer a dedicated deposit address makes reconciliation tractable and matches how fintech platforms have always structured customer money. Managing those addresses at scale is expensive, because on most chains every deposit address is a real onchain account that has to be initialized, monitored, and swept into a treasury wallet with additional transactions. At scale, that becomes operationally prohibitive. [Virtual addresses](/developers/docs/guide/payments/virtual-addresses) solve this at the protocol layer. A business registers a master wallet once, then derives unique customer-specific virtual addresses offline. Deposits sent to any of them credit directly to the master wallet with no sweep step in between and no per-address initialization cost. The sender still has a unique address to send to, and the operator receives funds in one consolidated wallet. ![Virtual addresses on Tempo](/blog/virtual-addresses-on-tempo.png) ### Per-customer deposit attribution For exchanges, neobanks, ramps, and custodians, virtual addresses deliver per-customer deposit attribution without the infrastructure tax. Every customer gets a dedicated deposit address that represents them specifically, inbound payments are attributed automatically, and operators keep the reconciliation benefits without the operational overhead of managing thousands of onchain wallets. ### Invoice-level reconciliation The same primitive enables invoice-level reconciliation for marketplaces and billing platforms. Instead of one address per customer, operators can issue one address per invoice. Inbound payments match to invoices automatically on arrival, and finance teams get clean structured reconciliation data rather than manually matching senders to line items. ### Multi-tenant wallet structures Virtual addresses also support multi-tenant wallet structures for fintech platforms and embedded finance companies. Sponsor banks today offer virtual accounts to fintechs: one master account holds customer funds, with structured sub-accounts and managed balances per end user. Virtual addresses are the onchain analogue of that pattern. A platform can maintain one master wallet while giving every end user a dedicated virtual address, preserving the customer-level structure that platforms need to run their business, without the infrastructure cost of separate wallets per user. The master wallet address is not directly exposed to senders, and each customer interacts only with their own virtual address. Virtual addresses work with [TIP-20](/blog/tip20) stablecoins, and non-TIP-20 tokens sent to a virtual address may be lost. [Read more about virtual addresses](/blog/virtual-addresses) ## Getting started Every capability described here is live on Tempo mainnet today. If you're evaluating stablecoins for subscription billing, auto pay, metered pricing, customer deposit attribution, invoice-level reconciliation, or multi-tenant wallet structures, Tempo's Stablecoin Advisory team can help you scope the use case, design the architecture, and support a pilot. Read the [documentation](/developers) or work with us at [tempo.xyz/contact](https://tempo.xyz/contact/). --- ## The Settlement Gap Banks Can Own By Adopting Stablecoins > Source: https://tempo.xyz/blog/off-hours-cash-stablecoin-settlement-gap/ > Language: en **_Banks have stayed out of stablecoins for two reasons: regulatory clarity was missing, and customers moving deposits into stablecoins cannibalize the loan book. The GENIUS Act provided the clarity. Our new whitepaper shows how banks can use wholesale deposits, which never funded the loan book, to back an off-hours stablecoin sleeve and own the weekend settlement market before non-bank issuers become the default._** [_Read the whitepaper_](/report/off-hours-cash). [Download full report](/report/off-hours-cash) Fedwire closes on Friday and does not reopen until late Sunday. CLS and TARGET2 are closed on weekends. For decades, those closed windows were tolerable because nothing much happened on weekends. That has changed. Over a single weekend in April 2026, trade.xyz, a perpetual derivatives venue, processed $1.5 billion in institutional notional across crude oil, the Nasdaq 100, and the S&P 500. All of it settled in stablecoins. Hedge funds, commodity traders, asset managers, and corporate treasurers with weekend exposure are already routing around closed bank rails. Each weekend, more institutional workflows default to non-bank infrastructure. Banks have a way to claim this flow without harming the deposit franchise. A bank-issued stablecoin sleeve, backed by wholesale deposits rather than core retail balances, turns idle weekend liquidity into a 48-hour transactional inventory. It reverts to deposit form on Monday morning, leaving the franchise intact while opening a revenue line during hours the franchise cannot reach. ## What the sleeve looks like Under the GENIUS Act, reserves backing a payment stablecoin must be segregated into high-quality liquid assets. Every dollar a client converts from a deposit becomes a dollar the bank can no longer lend. That logic applies to core retail deposits. It does not apply to wholesale deposits, which never funded the loan book and already attract a 40% LCR outflow rate or higher. The opportunity cost of using wholesale balances to back a stablecoin is far smaller than the headline number suggests, because the HQLA was already there. A bank-issued stablecoin "sleeve" allows banks to offer their corporate and institutional customers settlement during off-hours. The sleeve is a tightly sized, prefunded, KYC'd pool of stablecoin liquidity that is reversible to deposit form on Monday morning. - At 4:30 PM New York on Friday, an institutional client converts $100 million in wholesale balances into a regulated stablecoin under the bank's rulebook. - That stablecoin moves through whitelisted venues and custodians to post margin, substitute collateral, or settle weekend exposure. - On Monday morning, any unused balance reverts to the original deposit account through automatic sweep. The $100 million was a deposit on Friday and a deposit on Monday. For the 48 hours in between, it was a regulated stablecoin inside a defined rulebook. For a $500 billion wholesale bank running a $5 billion peak sleeve only on weekends, total annual cost runs around $38 million against $260 billion in annualized flow. Break-even sits at 1.4 to 1.6 bps. At the same time: - Tri-party collateral movement charges 1 to 3 bps today. - Weekend FX conversion runs 5 to 20 bps. - Prime brokerage off-hours financing clears 5 to 15 bps over base. At the right size, the math clears a standalone P&L with meaningful revenue above the cost. The sleeve is not a replacement for the deposit franchise. It is a revenue line that runs alongside it, during hours the franchise cannot reach. ## The sleeve is a decade-long product Fedwire is extending to 22 hours a day, six days a week, but no earlier than 2028. Saturdays remain out of scope. CLS and TARGET2 weekend closure stays. A permanent gap from Friday evening to Sunday evening is a feature of the dollar settlement day for the foreseeable future. The deeper fix, central bank money with cross-network tokenized deposit interoperability, is plausibly ten to fifteen years out. The solution has to reconcile multiple central bank legal frameworks at once, which is what 24/7 cross-perimeter public money settlement requires. The binding constraint is governance, not technology. That gives banks a window measured in years, not months. The catch is that every weekend, flow routed through a non-bank stablecoin normalizes non-bank money for institutional use. Five years from now, the default reference for cross-perimeter weekend flows will be whatever banks did or did not deploy in the next eighteen months. Issuing a sleeve does not threaten the deposit franchise. Letting clients build weekend workflows on a non-bank stablecoin does. Our whitepaper, "Off-Hours Cash: The Settlement Gap Banks Can Own By Adopting Stablecoins", works through the design parameters of the stablecoin sleeve, the regulatory treatment, and the unit economics. [Read it here](/report/off-hours-cash). --- ## OKX launches as Tempo's first international exchange partner > Source: https://tempo.xyz/blog/okx-launches-as-tempos-first-international-exchange-partner/ > Language: en **_OKX is the first international exchange to support Tempo at launch, with deposits and withdrawals on Tempo mainnet and native support in OKX Wallet from day one._** Stablecoin infrastructure only works if users can move assets on and offchain without friction. That means exchange support from day one, not as a follow-up. Today we're announcing that OKX is the first international exchange to support Tempo at launch. OKX users will be able to deposit and withdraw USDT0 directly on Tempo, and hold and manage assets on the network through OKX Wallet with full self-custody. This connects one of the world's largest trading platforms to Tempo's payment infrastructure with no wrapping, no bridging, and no waiting for third-party integrations to catch up. USDT0 is a unified stablecoin that operates as a single standard across chains, drawing from a shared global USDT supply. Users get consistent behavior wherever they move it, without the liquidity fragmentation or bridge risk that typically comes with cross-chain stablecoin transfers. --- ## Ondo’s USDY is now live on Tempo > Source: https://tempo.xyz/blog/ondo-usdy-is-now-live-on-tempo/ > Language: en **_Ondo’s U.S. Dollar Yield Token (USDY) is now live on Tempo. The integration gives platforms a Treasury-backed asset they can use in [Earn](https://tempo.xyz/earn/) products, treasury balances, and payment flows where funds may otherwise sit idle._** ## Tokenized Treasuries for payment flows Stablecoin balances often sit between financial actions. A company collects revenue before settlement. Payroll funds wait to be disbursed. A platform prefunds a payout corridor to pay recipients on time. These balances are part of the payments system, but they are not always productive for the businesses and users who hold them. Ondo’s [USDY](https://ondo.finance/usdy) gives eligible non-U.S. businesses and persons access to tokenized U.S. Treasury-backed yield through a freely transferable onchain asset. Bringing USDY to Tempo makes that asset available on a payments-first blockchain built for predictable, high-volume dollar movement. For platforms building on Tempo, yield can now sit closer to the payment experience itself. Funds can earn while they wait to be spent, settled, paid out, or moved across borders. ## What USDY enables on Tempo Tempo is designed for payment applications that need speed, predictable fees, and reliable capacity. Transactions settle in under a second. Fees are denominated in stablecoins, so businesses do not need to manage a separate volatile gas token. Dedicated payment lanes reserve blockspace for payment activity, helping large payout runs and settlement flows stay predictable when timing matters. USDY adds a Treasury-backed asset to that foundation. A wallet, neobank, payroll platform, merchant treasury tool, or financial application can use USDY as part of the balance experience customers already know: holding funds, earning on them, and moving them when needed. This is where [Tempo Earn](https://tempo.xyz/earn/) fits. Earn helps platforms offer productive balances inside their own products, with assets tailored to their users, risk profiles, liquidity needs, and compliance requirements. Businesses can decide how rewards are shared while keeping funds connected to payments, payouts, card spending, and withdrawals. With USDY on Tempo, platforms can integrate a transferable, Treasury-backed asset as a balance layer, collateral asset, or Earn option without sending users into a separate financial product. Tempo’s privacy, account policies, transfer controls, reward economics, and payment infrastructure help make that possible in real customer workflows. ## Building with Ondo and Tempo Ondo and Tempo are working together to make Treasury-backed yield easier to integrate into payment applications. USDY gives platforms another way to make balances useful while they are waiting for the next transaction. > “Bringing USDY to Tempo puts institutional-grade yield directly into the payments layer. Every business and individual transacting on Tempo can now hold dollars that earn between transactions, backed by short-term U.S. Treasuries. This is another key step toward establishing USDY as a core primitive of onchain finance.” > > — Ian De Bode, Ondo Finance “Global payment platforms already hold balances that sit idle between transactions. Launching Ondo’s USDY on Tempo enables them to put those balances to work,” said Eric Kang, GTM at Tempo. “Tempo Earn gives platforms control over how idle balances are used, and makes it simple to build rewards into existing products.” This launch is part of a broader effort to make stablecoin balances more useful for businesses, platforms, and end users. More Earn assets, ecosystem integrations, and developer resources are coming soon. [Get in touch with Tempo](https://tempo.xyz/earn/) if you’re building Earn, treasury, or payment products on stablecoin rails. --- ## Open USD is coming to Tempo > Source: https://tempo.xyz/blog/open-usd-ousd/ > Language: en **_Today Open Standard introduced Open USD (OUSD), a new stablecoin designed as open infrastructure for global money movement. OUSD will be issued natively on Tempo from day one, giving enterprises and developers another stablecoin they can use in payment, settlement, treasury, and distribution flows._** > "Open Standard describes OUSD around three principles: built for scale, shared reserve economics for participants, and collaborative management through an independent entity." > > — From the [Open Standard announcement](https://joinopenstandard.com/blog/introducing-open-usd) Combined with Tempo's purpose-built infrastructure for payments, including near-instant settlement, sub-cent fees, and built-in privacy and compliance features, OUSD can help grow stablecoin adoption in real-world payments use cases. For businesses that choose OUSD, Tempo will support it natively with the liquidity, ecosystem access, and infrastructure needed for any payments use case. ## Why Tempo Tempo is built for payments at scale, designed for enterprises and developers building across payment, settlement, treasury, and distribution flows. As stablecoin-first payments infrastructure, Tempo comes with features including: - **A stablecoin-native token standard:** Tempo's token standard, TIP-20, is designed for stablecoin payments, with structured memo fields for reconciliation, policies for compliance, and the ability to abstract gas fees in any stablecoin. - **Deterministic, low-cost settlement:** Tempo has near-instant settlement, sub-cent transaction fees, and high throughput to sustain even the most demanding payments workloads. - **Fees paid in stablecoins:** Pay transaction fees in any USD-denominated stablecoin, rather than a separate gas token. The Fee AMM converts automatically to each validator's preferred stablecoin with no extra integration. - **A built-in stablecoin DEX:** Tempo features an enshrined decentralized exchange designed for trading between stablecoins of the same underlying asset, providing optimal pricing for cross-stablecoin payments. - **Modern wallet signing:** Fee sponsorship for gasless experiences, batched and scheduled payments, passkey authentication, and scoped access keys for payroll, subscriptions, and agents. - **Opt-in privacy:** Tempo Zones for private balances and transfers, with the auditability enterprises need to fulfill compliance requirements. ## More stablecoin choice for businesses OUSD adds another option for businesses building with stablecoins. Some companies will use open-loop stablecoins like OUSD. Others will issue or distribute their own stablecoins for specific customer networks, geographies, or commercial models. OUSD will sit alongside other stablecoins in the Tempo ecosystem, and we plan to support it with deep liquidity, ecosystem support across ramps, exchanges, and DeFi, and payments infrastructure designed for production use. > "We're excited for Tempo to support OUSD natively on day one, bringing more stablecoin options for businesses. > > Combined with Tempo's stablecoin-native token standard, near-instant settlement, sub-cent fees paid in any stablecoin, built-in stablecoin DEX, and privacy and compliance features, we're committed to providing the infrastructure for enterprises to use OUSD across real-world payments use cases." > > — Dan Romero, Business Lead, Tempo ## Get started Read the [Open Standard announcement](https://joinopenstandard.com/blog/introducing-open-usd) to learn more about OUSD. If you're evaluating stablecoins for global payouts, cross-border payments, treasury operations, embedded finance, commerce, payroll, agentic payments, tokenized deposits, or any other payments use cases, [get in touch](https://tempo.xyz/contact) to see how Tempo can support you. --- ## OUSD is live on Tempo > Source: https://tempo.xyz/blog/ousd-is-live-on-tempo/ > Language: en **_Open USD (OUSD) is live on Tempo, with deep liquidity for enterprise payments. Issued natively on Tempo, OUSD has $400M+ in liquidity available at launch, deployed with partners across decentralized exchanges, stablecoin swaps, and bridges. Mint and burn infrastructure is available on Tempo at no cost to businesses through Coinbase, Stripe, Visa (VSP), and soon Mastercard. [Get started with OUSD on Tempo](https://tempo.xyz/ousd)._** OUSD is a new stablecoin from [Open Standard](https://joinopenstandard.com/) designed for global money movement at scale. Issued natively on Tempo, enterprises can now use OUSD to fund accounts, hold operating balances, make payments and payouts, swap into other supported stablecoins, and bring more money movement flows onto stablecoins. Businesses can [access OUSD on Tempo](https://tempo.xyz/ousd) through Coinbase, Stripe, Visa (VSP), and soon Mastercard. These providers offer minting and burning at no cost. "For a new stablecoin, liquidity on day one determines what businesses can actually do with it," said Dan Romero, Chief Business Officer at Tempo. "Tempo supports all kinds of stablecoins that help businesses move money more efficiently, and native OUSD offers customers a seamless way to build stablecoin payment products at scale." ## Partners supporting OUSD on Tempo ![Partners supporting OUSD on Tempo](/blog/ousd-is-live-on-tempo/ousd-partners.png) Tempo’s ecosystem includes infrastructure partners that help businesses integrate OUSD into their payment flows, with support across ramps, wallets, custody, security, liquidity, and financial products. - **Payments and ramps:** Stripe, Bridge, Coinbase, Mastercard, Visa (VSP), Blindpay, Fonbnk, Infinia, Relay - **Wallets and custody:** Privy, Anchorage Digital, Blockradar, Crossmint, Fireblocks, Utila - **Security and compliance:** Blockaid, Chainalysis, Elliptic, Hypernative - **Liquidity, swaps, and oracles:** Chainlink, Uniswap - **DeFi and earn (coming soon):** Morpho, Aave, Sentora, Gauntlet, Figure ## Put OUSD to work across payments, settlement, and treasury Tempo gives businesses more control over how they move and manage OUSD, with near-instant onchain settlement, sub-cent network fees, and features purpose-built for enterprise stablecoin payments: - **Privacy:** Keep customer balances and sensitive payment activity out of public view with opt-in privacy through Tempo Zones. Authorized parties retain defined access, while deposits and withdrawals remain visible on Tempo Mainnet. - **FX:** Swap OUSD into supported stablecoins on Tempo. We are working to connect more currencies, liquidity providers, and ramps so businesses can collect in one currency and pay out in another with fewer integrations. - **Earn:** Create new revenue streams by allowing end users to earn on balances they already hold, while your business controls how rewards are split. OUSD support for Tempo Earn is rolling out soon. OUSD’s [supply and activity on Tempo](https://ousd.fyi/) are publicly visible. ## Get started with OUSD on Tempo Enterprises can now access OUSD on Tempo through Coinbase, Stripe, and Visa (VSP), with Mastercard coming soon. To integrate OUSD into your payment, treasury, and money movement flows, [get in touch](https://tempo.xyz/contact/) or explore how to [integrate OUSD on Tempo](https://tempo.xyz/ousd). --- ## Privacy is live on Tempo > Source: https://tempo.xyz/blog/privacy-is-live-on-tempo/ > Language: en **_[Tempo Zones](https://tempo.xyz/zones/) let enterprises keep customer stablecoin balances and payments private, with built-in compliance controls and full access to Tempo's global liquidity. Starting today, Zones are generally available for enterprises. Deel is the first to use a Zone in production, paying contractors around the world without revealing who gets paid or how much. [If you're interested in a Zone for your business, reach out](https://tempo.xyz/contact/)._** Here’s why Zones work for enterprises: 1. **Streamlined integration.** Enterprises can integrate with Tempo _once_ and then choose which flows are public or private. Privy and Bridge support Tempo Zones natively, and [Privy’s wallet infrastructure](https://docs.privy.io/financial-flows/private-transactions) lets businesses add Zones seamlessly through familiar APIs. 2. **Compliance.** Zone operators decide who can participate, which assets are allowed, and how incoming funds are screened. [Issuer policies](https://tempo.xyz/blog/compliance-controls/) carry into every Zone automatically. Teams keep the records they need for reconciliation, customer support, and reporting. 3. **Liquidity.** Private accounts reach global liquidity on Tempo, including stablecoin swaps, FX, ramps, card programs, and yield. Since Zones are a native feature of Tempo, every smart contract and protocol that works on Tempo also works with private balances on a Zone. [Watch video](/videos/privacy/privacy-on-tempo-20261015.mp4) ## What's private, what's public Zones give enterprises the privacy they expect from a bank. Nothing inside a Zone is visible to the public. The Zone operator, however, can see activity inside a Zone and can pause transfers to meet compliance requirements. Here’s an overview of what is public and private: |Action|Public|Private| |-|-|-| |Deposit into a Zone|Token, amount, sender|Recipient| |Transfers in a Zone|Nothing|Sender, recipient, amount| |Balances in a Zone|Nothing|Balance (visible only to the account holder and operator)| |Withdrawal from a Zone|Amount, recipient|Sender| |Interact with Earn / DeFi|Deposit, withdrawal, amount|Who owns the position| ## Deel: private contractor pay and earn with stablecoins [Deel](https://tempo.xyz/customer-stories/deel/) runs payroll for 40,000+ businesses across 150 countries. In June, they launched a stablecoin wallet on Tempo, giving contractors in markets with volatile local currencies, like Argentina, a dollar-backed balance they can hold and earn on. Tempo and Privy worked together to bring Deel’s Zone into production, integrating Zones natively with Privy’s APIs to keep contractor wallets private. Deel's treasury deposit into its Zone is visible on Tempo, but which contractors are paid, how much each receives, and what they hold are not. Contractors see their own balances in Deel, and Deel keeps the access it needs for reconciliation and audit. “Workers' financial data should be private by default. Sensitive information such as salaries, balances, and payout history doesn't belong on a public ledger,” said Thierry Edde, Head of Crypto at Deel. “Tempo Zones give us that privacy without sacrificing what contractors actually care about: keeping their earnings stable, growing their balance, and getting paid fast. That's the infrastructure global payroll should be built on.” "Privacy is built into Tempo as a native capability, so businesses can keep sensitive financial information confidential while continuing to transact using stablecoins," said Dan Romero, Chief Business Officer at Tempo. "Deel is the first enterprise to put Zones into production, bringing privacy to contractor payouts without giving up access to the rest of the network." ## Availability Zones are now available for enterprises running payroll, contractor payouts, B2B payments, and treasury on stablecoins. [Talk to our team](https://tempo.xyz/contact/) to bring privacy to your stablecoin use case today. --- ## Privacy on Tempo > Source: https://tempo.xyz/blog/privacy-on-tempo/ > Language: en **_Enterprises want the benefits of stablecoin rails without public visibility into payments. Tempo Zones enable private stablecoin transactions, fully interoperable with Tempo Mainnet and other Zones. Several enterprises and financial institutions are exploring using Zones._** [_Reach out_](https://tempo.xyz/contact) if you are interested in exploring how Zones could serve your use-case. Stablecoin rails reduce settlement time, simplify cross-border movement, and lower reconciliation overhead. These are the properties that consistently draw enterprises and financial institutions to stablecoins. But today's stablecoin networks still broadcast everything publicly by default. A company running payroll would publish every salary. A payment processor settling with merchants would leak confidential volume data on every onchain transaction. Banks and financial institutions face a version of the same problem. Tokenized deposits, trade settlement, and capital markets use cases require counterparty information and transaction data to be private, while the tokens themselves still need to follow compliance rules and remain interoperable across institutions. In every case, the requirement is the same: the parties to a transaction should see the details, the broad public should not, all while retaining the usability and interoperability of stablecoin rails. ## Introducing Tempo Zones We're solving this with what we call [Tempo Zones](/blog/introducing-tempo-zones). A Zone is a private execution environment, i.e., a parallel blockchain connected to Tempo Mainnet. Within a Zone, participants can transact privately without revealing any information to the public. Assets on Tempo Mainnet are interoperable across zones. Users on a zone can seamlessly interact with other zones and Tempo Mainnet, including accessing onramps and offramps through Mainnet as well as liquidity in decentralized exchanges on Mainnet. For implementation details, read [Introducing Tempo Zones](/blog/introducing-tempo-zones). A Zone can be operated by an enterprise itself or by an infrastructure provider and customized to the needs of their use case(s). The operator manages transaction processing and system availability. The operator does not control the underlying assets. Funds are locked in a zone contract on Tempo Mainnet and can only be withdrawn by the user owning the asset. ### Who sees what The zone operator has visibility into all transactions within the zone. This is by design: a regulated institution running a zone may have additional compliance or reporting requirements. Enterprises can exercise tighter control by operating their own zone. Users of the zone can only see their own transactions and balances. Everyone else only sees cryptographic proofs of the zone's validity. Enterprises managing payroll on Tempo are early users of Zones: ![Tempo Zones in action: Payroll](/blog/tempo-zones-payroll.png) _A company onramps to Tempo Mainnet and funds a payroll account within a Tempo Zone. It pays employees and contractors inside that Zone. Recipients can withdraw to Tempo Mainnet for swaps or offramps. The payroll ledger remains private and is not visible to the public._ ### Compliance rules travel with the token Every token on Tempo natively allows issuer-defined [compliance controls](https://tempo.xyz/blog/compliance-controls), including allowlists, blocklists, and freeze capabilities. Those controls are enforced across zones, ensuring transfers adhere to issuer policies and blockchain rules. Every time an issuer updates a blocklist or allowlist, or freezes a token on Mainnet, all zones enforce the change automatically. ### The operator never has custody of funds Funds are locked on Tempo Mainnet in a Zone contract, only withdrawable by the user. The operator can only include, sequence and process valid transactions on the zone. The validity of transactions processed and compliance rule enforcement are verified cryptographically by Tempo Mainnet, independent of the operator. Read more about the technical details of [Tempo Zones](/blog/introducing-tempo-zones), or see the [protocol specification](/developers/docs/protocol/zones) and [developer guide](/developers/docs/guide/private-zones). ## How Zones compare to other solutions Any privacy solution inevitably involves tradeoffs across three axes: privacy, usability, and interoperability. Enterprises are forced to choose between the level and scope of privacy, usability for their teams and users, and interoperability with public blockchain infrastructure such as DeFi protocols and onramps. Most existing approaches to privacy force an enterprise into suboptimal tradeoffs: - The default model on most blockchains, pseudonymity, does not ensure privacy. Transaction patterns and external data make it possible to link wallets to real-world identities. - Some approaches only provide partial privacy, e.g., hiding only amounts or only participants. - Some projects rely on advanced cryptography to hide transaction data entirely or completely anonymize users. While powerful, these approaches introduce unnecessary operational complexity and usability tradeoffs, often require users to have specialized wallets, be responsible for storing their own data, or aren't compliant with enterprise requirements. - Finally, there are private ledgers. These enterprise blockchain projects address privacy by creating separate, permissioned networks but in turn isolate assets, fragment liquidity, and require custom integrations. Zones remove these tradeoffs, allowing enterprises and their users complete privacy from the public while remaining usable (high throughput, standard wallets) and fully benefiting from liquidity and infrastructure on Tempo Mainnet and interoperability with other zones. Privacy is not a one-size-fits-all, and we are excited to work with enterprises to help shape Zones for their use-case, or guide them to one of these other solutions on Tempo if that best fits their needs. Learn more about [how privacy works on Tempo](/developers/docs/guide/private-zones/). ## Build on Zones Tempo Zones are available with design partners today, with production deployments planned in phases. If your team is evaluating private stablecoin workflows for payroll, treasury, settlement, or tokenized deposits, we can walk your finance, compliance, and platform teams through the operating model. [Get in touch](https://tempo.xyz/contact) with our Enterprise team. --- ## Introducing Receive Policies > Source: https://tempo.xyz/blog/receive-policies/ > Language: en **_On most blockchains, any token can land in any account, and there is no native way to refuse it or get it back. Receive policies on Tempo let exchanges, custodians, and payment platforms decide which tokens and senders their accounts accept, and recover anything they don't._** Businesses that receive stablecoins at scale, including exchanges, custodians, on and off ramps, payment processors, and treasury systems manage a constant stream of inbound transfers. On a general-purpose blockchain, an account accepts whatever is sent to it. There is no clear way to validate beforehand which tokens will be sent or who is sending them, resulting in a number of problems: - A token lands in a deposit address on a blockchain the platform doesn’t support - A regulated account has no native control over which counterparties can fund it - Scam tokens can be sent by any malicious user to try drain an address’ funds Each of these cases becomes a reconciliation exception, a support ticket, or in the worst case, a deposit no one can recover. ## How receive policies work An account configures three things: the **tokens** it accepts, the **senders** it accepts, and the **recovery authority** that can reclaim a transfer the account does not accept. Controls are opt-in and set per account. A sender does not need to know the policy exists: they start a normal transfer, and the policy decides what happens on receipt. The important part is what happens to a transfer the account does not accept. It is not bounced and it is not lost. It succeeds at the protocol level, the funds route to a protocol guard with a receipt, and they stay recoverable by the authority the account named in advance. For operations teams, a blocked transfer becomes a recovery workflow instead of a lost-funds incident. > Interactive receive policy demo flow is available on the HTML page. ## What this enables - Deposit addresses that accept only supported assets, with fewer reconciliation exceptions. - A protocol-native control over inbound transfers for compliance and operations teams, rather than screening that runs only after funds arrive. - Account controls that embedded-wallet and wallet-as-a-service providers can expose to their own customers. - Held transfers that support teams can surface for recovery instead of opening a ticket for every mismatch. ## Get started with receive policies If you receive stablecoins at scale and want native control over what your accounts accept, [get in touch](https://tempo.xyz/contact). Our team works with exchanges, custodians, and payment platforms to put account controls into production. --- ## RedotPay integrates MPP to bring agentic payments to its 7.5 million users > Source: https://tempo.xyz/blog/redotpay-integrates-mpp-to-bring-agentic-payments-to-its-users/ > Language: en **_RedotPay is integrating the Machine Payments Protocol (MPP) so AI agents can transact on behalf of its 7M+ users, with settlement on Tempo._** [_Read the full case study_](https://tempo.xyz/customer-stories/redotpay) RedotPay, a global stablecoin-based payment fintech serving over 7 million users across 130 million merchants worldwide, is integrating the Machine Payments Protocol to enable AI agents to transact on behalf of users. Most payments still need a human in the loop for a recommendation, a search, a click, or a purchase. AI agents are increasingly capable of handling each of those steps, but the infrastructure for autonomous payments is only now catching up. MPP gives agents a standard way to send and receive payments programmatically, from microtransactions to merchant-direct purchases. ## RedotPay and Tempo RedotPay serves over 7 million users across 100+ countries through global card networks, and processes more than $10 billion in annualized payment volume. With MPP integrated, an AI agent can process a purchase request inside the app from end to end. The agent handles discovery and checkout, RedotPay settles with the merchant on Tempo in stablecoins, and the user settles with RedotPay from their existing wallet balance, without bridging funds or holding ecosystem-specific tokens. "Agentic payments represent a fundamental shift in user experience, transforming how we discover, purchase, and pay," said **Jonathan Chan, Co-Founder and Head of Partnerships of RedotPay**. "At RedotPay, innovation has always been our focus. By partnering with Tempo to integrate AI with stablecoin payments, we are shaping the future of payment solutions and making digital asset spending more seamless, intuitive, and accessible for everyday life." ## What's next RedotPay's MPP integration is live on Tempo today. RedotPay is set to launch the second phase of its agentic payments capability, with the payment skill becoming available for download in June this year. Users will be able to access agentic payments with AI agents handling discovery and purchase. [Read the full case study](https://tempo.xyz/customer-stories/redotpay) · [Explore MPP](https://mpp.dev) --- ## How stablecoin remittances work and what are the key benefits > Source: https://tempo.xyz/blog/remittances/ > Language: en **_The average cost of sending a $200 remittance is 6.5%. With stablecoins, total cost drops below 1% and funds arrive in seconds. Fintechs and smaller banks can now launch competitive remittance services, and institutions already offering remittances can serve corridors and customer segments that previously weren't economical. This article explains how stablecoin remittances work, how to evaluate if they fit your business, and how to launch a pilot. If you're ready to get started, [get in touch](https://tempo.xyz/contact)._** For millions of people, remittances are a lifeline: regular payments sent home to support families, fund education, or cover essential expenses. According to World Bank estimates, the global remittance market moves over $900 billion annually, with 200 million people sending money home each year[1]. Stablecoins have opened remittances to fintechs and smaller banks, without requiring correspondent banks. Moreover, in many corridors, dollar demand outstrips local supply, giving them a structural FX advantage over incumbents through liquidity premiums. Companies like DolarApp, Félix Pago, and Chipper Cash are already using stablecoins to power remittances across Latin America and Africa. They are offering consumers lower fees, better exchange rates, and money that arrives in seconds, capturing market share from legacy players. ## Why traditional rails are prohibitively expensive For fintechs and smaller banks looking to offer remittances, traditional correspondent banking creates barriers and adds cost at every step: - **Correspondent relationships are difficult to obtain.** To send a remittance to Mexico, an institution needs a banking relationship with a correspondent that has access to Mexico's local payment rails. Large banks are de-risking, refusing to onboard smaller institutions to avoid compliance overhead. Those without correspondent access must use intermediaries who might charge 10x more. - **Unit economics are broken.** According to World Bank data, the global average cost of sending a $200 remittance is 6.5%[2]. Domestic fast payment systems typically cost less than 1%. That gap is the correspondent banking tax: each intermediary adds processing overhead, compliance costs, and margin. - **FX rates are dictated by correspondents.** Smaller institutions have no leverage to negotiate competitive foreign exchange rates. This hidden cost gets passed to customers or absorbed as margin compression, and there is no practical way to shop for better rates without building additional banking relationships. - **Liquidity sits frozen in nostro accounts.** Correspondent banking takes days to settle, but customers want their money fast. The only solution is pre-funding local currency accounts in every destination. McKinsey estimates this trapped capital represents 34% of international payment costs[3]. For institutions already offering remittances, expansion is expensive. Each new corridor means new correspondent relationships, more pre-funded accounts, and additional compliance overhead. Many corridors simply are not worth the investment. ## Benefits of stablecoins for remittances Stablecoins change how cross-border payments work. Instead of relying on correspondent banks, the flow is simpler: local currency is converted to stablecoins, transferred on a blockchain, then converted back to local currency at the destination. This approach is often called the "**stablecoin sandwich**". The sender pays a local onramp provider, which converts the funds into stablecoins and sends them onchain to a provider at the destination. That provider converts the stablecoins into local currency and pays the recipient through a bank account, wallet, or cash-pickup service. The blockchain settles the stablecoin transfer; the providers handle currency conversion, compliance checks, and the local payout, so end-to-end timing depends on those steps. ![Stablecoins for remittances](/images/blog/remmitances_1.png) ### Access without banking partnerships Institutions do not need permission from large banks to access their payment networks. They need an orchestration partner that provides on-ramps to convert local currency to stablecoins and off-ramps to convert stablecoins back to local currency at the destination. These are competitive service providers, not gatekeepers. ![costs-light](/images/blog/costs-light.png) ### Costs that enable competitive pricing Stablecoin remittances have three fee components: on-ramp conversion (0.1-0.5%), blockchain fees (under $0.01), and off-ramp conversion (0.1-0.5%). A total cost under 1% means remittance providers can undercut legacy pricing while still maintaining a healthy margin. ![Stablecoins for remittances](/images/blog/remittances_2.png) ### Cheaper FX through the USD demand premium In many markets, demand for US dollars outstrips local supply, creating a 20–200 bps FX premium for USD stablecoins above market rates, depending on the corridor. Instead of being locked into one correspondent bank, remitters can work with multiple off-ramp providers who compete on rates, passing that margin directly to customers. ![long-tail-light](/images/blog/long-tail-light.png) ### Access to long tail markets Correspondent banking only works for high-volume corridors. Stablecoins open up smaller markets because the infrastructure cost is the same whether you are sending to Mexico or Mongolia. If an off-ramp exists, the corridor is open. ![Stablecoins for remittances](/images/blog/remittances_3.png) ### Settlement in seconds, without pre-funding Stablecoins settle near-instantly, eliminating the need for pre-funded accounts in every destination country. No trapped capital, no multi-day uncertainty. Customers see their transfer complete in real time. ## Evaluating stablecoins for remittances Stablecoin adoption starts with a clear business case. Before evaluating orchestration partners or integration paths, use this framework to assess whether stablecoins make sense for your remittance offering: - **Are your customers already using remittances?** If you are seeing outflows to Wise, Remitly, Western Union, or similar services, your customers are sending money abroad, just not through you. - **Are you blocked from offering remittances today?** Correspondent banking relationships, SWIFT infrastructure costs, or compliance overhead can make it impossible to build a remittance product that competes on price and speed. - **Already offering remittances, but cannot compete on experience?** Traditional rails mean customers send money and wait days without knowing if or when it will arrive. This generates support tickets, complaints, and manual follow-ups that drain operational resources. - **Would faster, cheaper remittances strengthen customer retention?** Remittances are a frequent, high-value touchpoint. Offering instant settlement at lower fees can deepen relationships, increase wallet share, and differentiate you from competitors. If the answer to these questions is yes, you should be evaluating stablecoins. The infrastructure is ready, regulation is clearer, and the economics are compelling. ## Getting started with stablecoins You can start with a single corridor, validate unit economics, track adoption, and scale once the business case is proven. Here's how to approach it: #### Step 1: Pick your corridor Start with one remittance corridor that matters to your customers. Look at your payment outflows to identify where customers are using third-party remittance services. Survey a sample of these customers to understand which corridors they're using most. Focus on corridors with high volume or poor customer experience (long settlement times, high fees, frequent complaints). #### Step 2: Choose your integration approach Decide whether to partner with an orchestration provider or build your own infrastructure. Partners handle on-ramps, off-ramps, liquidity sourcing, compliance, and custody, letting you integrate via API in weeks. Building in-house gives you more control, but the biggest hurdle is often licensing: obtaining money transmitter licenses, virtual asset service provider registrations, or equivalent authorizations in every jurisdiction you operate in. #### Step 3: Start with wholesale on-ramp and off-ramp You do not need to process each remittance individually from day one. Batching transactions (converting to and from stablecoins in bulk) offers better rates, but slower settlement. It is a practical way to validate a corridor and build operational confidence. Just be ready to move to per-transaction processing shortly, as competition and customer expectations will require instant settlement. #### Step 4: Pilot alongside existing rails If you already have SWIFT connectivity or correspondent banking relationships, keep them. Run stablecoins in parallel. Offer a subset of customers the option to receive funds via stablecoins instead of traditional rails. Let them experience faster settlement and lower fees. Run the pilot for 60-90 days to validate cost savings, identify operational gaps, and gather customer feedback before committing to scale. #### Step 5: Ensure compliance Work with your orchestration partner or legal team to ensure compliance with the Travel Rule and local regulations. The Travel Rule requires transmitting customer information with transactions above certain thresholds. Your partner should handle this as part of their service, or you'll need to implement it yourself. Also verify that your chosen corridors and on/off-ramp providers meet local licensing requirements. ## Risks and limitations Stablecoins solve fundamental problems with traditional remittance rails, but they introduce their own constraints. Here is what to consider: - **Regulatory coverage is uneven.** Some corridors have clear stablecoin regulations. Others are in regulatory gray zones or explicitly prohibit stablecoin use for payments. Before piloting a corridor, verify that both the sending and receiving jurisdictions permit stablecoin-based money transmission. - **Off-ramp availability varies by geography.** An orchestration partner may not have local off-ramp coverage in every required country. Tier-1 corridors like the U.S. to Mexico or the U.S. to the Philippines have mature liquidity. Less common corridors may have limited off-ramp options, higher conversion costs, or longer settlement times that erode the stablecoin advantage. - **New infrastructure means new failure modes.** Stablecoin rails introduce dependencies that do not exist in traditional payments: blockchain uptime, smart contract risk, wallet custody, and API reliability from on/off-ramp partners. Each is a potential point of failure requiring monitoring, fallback procedures, and updated support processes. - **Economics break down at low volumes.** On-ramp and off-ramp providers typically charge percentage-based fees. At scale, these fees are competitive with traditional rails. At low corridor volumes, they can be prohibitive. If an institution processes a few transactions per month in a corridor, the unit economics may not justify the integration effort. - **Regulators may require additional reporting.** Many regulators are still building familiarity with stablecoin infrastructure. Even in jurisdictions where stablecoins are legal, institutions may face extra reporting requirements, audits, or documentation requests that would not apply to traditional remittance rails. Institutions should budget time for compliance conversations and expect iteration as regulatory expectations evolve. ## Work with Tempo Tempo's enterprise team helps banks and fintechs evaluate and implement stablecoins as part of a modern remittance strategy, from initial analysis through pilot and scale. - Analyze your payment outflows to identify high-impact corridors - Model the business case with your transaction data - Review integration requirements for your tech stack - Design a pilot program tailored to your operational needs - Connect you with institutions that have launched stablecoin remittances If you'd like to explore stablecoin remittances with our financial services consulting and product teams, [contact](https://tempo.xyz/contact) our Enterprise Team. [1] Source: [2025 Digital Remittances Adoption Report](https://corporate.visa.com/en/products/visa-direct/resources/money-travels-report.html) [2] Source: [World Bank Remittance Prices Worldwide](https://remittanceprices.worldbank.org/) [3] Source: [Global Payments 2016: Strong Fundamentals Despite Uncertain Times](https://www.mckinsey.com/~/media/McKinsey/Industries/Financial%20Services/Our%20Insights/A%20mixed%202015%20for%20the%20global%20payments%20industry/Global-Payments-2016.pdf) ## FAQs ### Do institutions have to hold and manage stablecoins? No. Stablecoin orchestration providers like Bridge and BVNK abstract the complexity of managing stablecoins, wallets, and licensing. Institutions connect to the provider's API to instruct a remittance, send funds from a bank account in fiat currency, and they handle on-ramp, off-ramp, custody, and liquidity management. ### Will recipients understand stablecoins? They do not have to. Modern stablecoin infrastructure can be invisible to end users. Recipients get a notification that payment arrived and see a balance in their local currency or USD in a mobile app. The underlying blockchain technology is abstracted away. ### What currency does the recipient receive? The recipient receives local currency directly in their bank account or mobile wallet. The orchestration partner handles the stablecoin conversion automatically behind the scenes. From the recipient's perspective, it works exactly like a traditional remittance: they get a notification and see local currency available for withdrawal or use. ### How does the Travel Rule work for stablecoin remittances? The Travel Rule requires transmitting customer information with transactions above certain thresholds (typically $1,000 in the U.S.). The orchestration partner should handle Travel Rule compliance as part of their service. If building in-house, institutions need to implement Travel Rule protocols directly and ensure compliance in each jurisdiction. ### Is this regulated? Yes. Stablecoin remittances are subject to money transmission regulations in most jurisdictions. Any institution offering remittance services must comply with KYC/AML requirements, Travel Rule obligations, and obtain appropriate licenses. Regulatory clarity has improved significantly, particularly in the U.S., following recent legislation. --- ## Stablecoin Fees on Tempo > Source: https://tempo.xyz/blog/stablecoin-fees/ > Language: en **_Tempo enables users to pay transaction fees in any stablecoin, including custom-issued tokens and tokenized deposits, no volatile gas token required. Stablecoin fees are native to the protocol and deliver transparent, predictable costs and simpler accounting. Work with our infrastructure partners rolling out stablecoin fee support, including [Bridge](https://www.bridge.xyz/), [Frax](https://frax.com/), and [MetaMask](https://metamask.io/), or start building with [our docs](/developers/docs/protocol/fees)._** Institutional adoption of stablecoins has been held back by a surprisingly small detail: the "gas token." On most blockchains, sending stablecoins means holding a separate, often volatile token just to pay transaction fees. Companies end up managing a second balance, funding it at the right times, and explaining it to their accountants and auditors. Tempo takes a different approach. Designed for payment use cases, it allows fees to be paid in stablecoins at the blockchain level: fees are treated as part of the payment flow, and the blockchain handles the mechanics needed to make stablecoin fees work reliably at scale. ## The case for fees in stablecoins On Tempo, transaction fees can be paid in any supported stablecoin, including custom-issued tokens and tokenized deposits. Users pay fees in the same asset they already hold, and the protocol handles the rest. This matters because most blockchains require a separate, often volatile token just to pay fees. "Gas tokens" introduce operational overhead: additional accounting, potential tax consequences when the token is sold to pay fees, and processes that many treasury teams are not set up to run day to day. They also carry steep capital charges, since banks must hold far more regulatory capital against volatile crypto assets. Stablecoins, by contrast, align with the fiat currencies these institutions already manage. There is also a regulatory dimension. Stablecoins increasingly operate under clear frameworks like the GENIUS Act, with defined rules for reserves, audits, and compliance. Volatile gas tokens often exist in regulatory gray areas, creating compliance uncertainty, and in some cases, preventing enterprises from holding such tokens on their balance sheet altogether. By paying fees in regulated stablecoins, companies avoid this ambiguity. Alternatively, companies can pay for a gas abstraction service, but this adds extra costs and requires additional integration work; further, critically, it still leaves them exposed to unpredictable costs driven by volatile token prices. By enabling fees to be paid in stablecoins, Tempo delivers the accounting simplicity, operational efficiency, and regulatory clarity enterprises require. Fees become a clean, auditable line-item expense, denominated in the same units as the payments themselves. > Bridge is leveraging Tempo to provide low, predictable fees for our developers. Payments should not go slower or cost more because of unrelated blockchain activity and Tempo solves this pain point for our developers. > > — Aadil Mamujee, Head of Crypto, Bridge ## The building blocks behind stablecoin fees Enabling any stablecoin to be natively used for network fees requires deep protocol integration. Tempo achieves this through two core components: ### TIP-20 token standard Tempo's native [token standard](/developers/docs/protocol/tip20/overview) extends ERC-20 with features essential for payment use cases: memos for reconciliation, built-in compliance controls, and the ability to serve as fee tokens. Only TIP-20 tokens can be used to pay transaction fees on Tempo. ![Stablecoin fees on Tempo](/images/blog/stablecoin_fees_1.png) ### Fee AMM This protocol-native [automated market maker](/developers/docs/protocol/fees/fee-amm) handles fee conversion between stablecoins. If a payer prefers USD-X but the validator wants to receive fees in USD-Y, the Fee AMM performs this conversion automatically at a fixed rate, as part of the user's transaction. ![fee-amm-swap-color-dark](/images/blog/fee-amm-swap-color-dark.png) Tempo's [payment-first design](https://tempo.xyz/blog/tempo-transactions), native token [standard for stablecoins](https://tempo.xyz/blog/tip20), and the ability to pay fees in any stablecoin create the conditions for a thriving stablecoin ecosystem. To support this, we built the Tempo [Stablecoin DEX](/developers/docs/protocol/exchange), a protocol-native exchange designed specifically for stablecoin trading. > Tempo and Frax share the same mission: to innovate around stablecoins to make them more usable in the real world. TIP-20 is a clear example of that progress, with stablecoin-native fees, built-in reward distribution, and a token standard designed for payments from day one. We're excited to be among the first teams adopting TIP-20 with frxUSD, both for rewards streaming and as gas, to push stablecoin UX forward. > > — Sam Kazemian, Founder and CEO, Frax ## How stablecoin fees work on Tempo Paying fees in stablecoins on Tempo is straightforward. The protocol handles the complexity. ### Fee token selection When submitting a transaction, choose which [TIP-20 stablecoin](/developers/docs/protocol/tip20/overview) to use for fees. Tokenized deposits are also supported. You can also set fee preferences at the account level. If no preference is specified, fees are paid in the same token as the payment. No extra decisions, no extra balance to manage. ![Stablecoin fees on Tempo](/images/blog/stablecoin_fees_2.png) ### Supported stablecoins Today, any USD-denominated TIP-20 stablecoin can be used to pay fees. Support for non-USD stablecoins will be added as those markets develop. This will eliminate FX complexity for companies operating in non-USD currencies, keeping both payments and fees in the same currency. ![Stablecoin fees on Tempo](/images/blog/stablecoin_fees_3.png) ### Automatic fee conversion Validators specify which stablecoin they want to receive fees in. When there is a mismatch, the [Fee AMM](/developers/docs/protocol/fees/fee-amm) performs an automatic conversion. These swaps execute at a fixed rate, with liquidity providers earning 0.3% per swap. ![Stablecoin fees on Tempo](/images/blog/stablecoin_fees_4.png) ### Liquidity and routing For a stablecoin to be accepted as a fee token, it needs sufficient [Fee AMM liquidity](/developers/docs/protocol/fees/fee-amm). The Fee AMM performs direct conversion between any two stablecoins, ensuring concentrated liquidity and efficient pricing. ![Stablecoin fees on Tempo](/images/blog/stablecoin_fees_5.png) ### Putting the pieces together Here is how it works in practice. A company submits a payment transaction and selects USDX as their fee token. A validator building the next block includes this transaction but prefers to receive fees in USDY. The Fee AMM automatically handles the conversion from USDX to USDY within the same transaction. The company pays in their preferred stablecoin, the validator receives theirs, and liquidity providers earn fees on the swaps. Learn more about stablecoin fees in [our docs](/developers/docs/protocol/fees). ## Who benefits from stablecoin fees Stablecoin fees create value across the entire payment ecosystem, from the companies making payments to the validators securing the network: - **Payers:** A company running global payroll can fund their Tempo account with any stablecoin and execute thousands of payouts without ever needing to acquire or manage a volatile gas token. Their fee expenses are predictable, easy to forecast, and integrate cleanly into existing accounting systems. - **Validators:** Validators receive their fee revenue in stable, liquid assets they can immediately use. The result: more predictable economics and simpler operations. - **Neobanks and fintechs:** Applications can sponsor transaction fees for users using stablecoins from their own treasury. This creates a "gasless" experience that feels like a traditional fintech app without crypto friction or complexity. - **Payment processors:** As protocols like "x402" emerge, native onchain payment processors will be able to collect and pay fees in stablecoins, simplifying their own operations and business models. - **Market makers:** Liquidity providers earn fees on every swap that occurs through the Fee AMM and Stablecoin DEX. We expect Tempo to host thriving stablecoin markets with deep liquidity. ## Start building with Tempo Whether you're exploring stablecoins or already use them in your payment stack, we can help you get started: ### Learn the fundamentals Visit the Learn section of the Tempo documentation to understand stablecoins, how they work, and the payment use cases they enable. [Learn](/learn) ### Start building If you're familiar with blockchain development, head to our docs to connect to Tempo, access test funds, download SDKs, and start building with Tempo Transactions. [Read the docs](/developers/docs/protocol/tip20/overview) ### Move faster with partners You can also work with our infrastructure partners including Crossmint, Fireblocks, Privy, and Turnkey, who are rolling out Tempo Transactions and can help accelerate your development timeline. Visit the Ecosystem section to explore Tempo's growing network of partners. [Explore ecosystem](/ecosystem) For guidance on choosing the right approach for your use case, contact our [Enterprise Team](https://tempo.xyz/contact). --- ## Issuing Stablecoins on Tempo > Source: https://tempo.xyz/blog/stablecoin-issuance/ > Language: en **_Issuing your stablecoin on Tempo gives you distribution into enterprise payment flows, structural demand through network economics, and native compliance infrastructure. This guide covers what Tempo offers stablecoin issuers and how to get started._** [_Get in touch_](https://tempo.xyz/contact) with our Enterprise Team. Companies like Klarna, Nubank, Shopify, Deel, DoorDash and many others are working with Tempo to bring stablecoins to their customers. For stablecoin issuers, these are real payment flows moving onchain: enterprise payroll, global payouts, and remittances. Issuing on Tempo means your stablecoin shows up where payments are already happening, with 60+ ecosystem partners integrated and compliance built-in. ## Why issue a stablecoin on Tempo Launching a stablecoin is straightforward. Getting the adoption is the hard part. It comes down to three things: distribution, compliance that unlocks regulated holders, and economics that give distribution partners a reason to choose yours. Here is what Tempo offers: ![distribution-color-light](/images/blog/distribution-color-light.png) ### Distribution into active payment flows Tempo is purpose-built for payments: high throughput, low cost, and native account abstraction designed for real-world use cases. [Enterprises are building](https://tempo.xyz/ecosystem) cross-border payouts, remittances, payroll, and embedded finance on Tempo. Issuing on Tempo means your stablecoin is available in these flows from day one. ![automatic-fee-conversion-color-dark](/images/blog/automatic-fee-conversion-color-dark.png) ### Network economics that create stablecoin demand On Tempo, [users can pay fees in any stablecoin](https://tempo.xyz/blog/stablecoin-fees), which means validators are paid in stablecoins too. The Fee AMM converts between the stablecoin the user pays and the one the validator prefers. This creates structural demand for stablecoins as network activity grows. ![account-owner-color-dark](/images/blog/account-owner-color-dark.png) ### Protocol-level compliance Regulated institutions require compliance controls before adopting a stablecoin. Tempo's [TIP-20](https://tempo.xyz/blog/compliance-controls) token standard supports native mint, burn, and transfer restrictions. TIP-403 Policies let you define compliance rules once and enforce them across every token you issue. Transfer Memos attach references to transfers for offchain reconciliation and compliance systems. ![stablecoin-dex-color-dark](/images/blog/stablecoin-dex-color-dark.png) ### Role-based access control Minting, freezing, and burning blocked balances are [separate roles](/developers/docs/protocol/tip20/overview/#role-based-access-control-rbac), each delegatable to different teams or addresses. Every action is logged onchain, giving regulated issuers a complete audit trail. ![yield-distribution-color-dark](/images/blog/yield-distribution-color-dark.png) ### Native yield distribution TIP-20 has [reward distribution](/developers/docs/protocol/tip20-rewards/overview) built into the token standard. Issuers call a native function and every opted-in holder receives their share proportionally. No separate staking contracts or manual reconciliation. ![role-based-color-dark](/images/blog/role-based-color-dark.png) ### Onchain liquidity A native [stablecoin DEX](/developers/docs/protocol/exchange) lets partners move into and out of your stablecoin directly onchain, without external onramps. Onchain FX is on the roadmap, starting with non-USD stablecoins as fee tokens, with the goal of supporting stablecoins in any currency. Together, these capabilities cover the core needs of stablecoin issuers: distribution through real payment flows, built-in compliance, and yield distribution tooling that scales. ## How to get started Issuing a stablecoin on Tempo starts with a clear use case and well-defined requirements. Here's how to approach it: ### Step 1: Define your requirements Work with Tempo to scope your issuance. What currency is your stablecoin pegged to? Who are your target users? What regulatory and compliance requirements apply to your jurisdiction? The answers determine your token configuration and integration path. ### Step 2: Review TIP-20 and Tempo Policies TIP-20 is Tempo's token standard for payments. Tempo Policies let you define permissioning rules at the protocol level. The Role-Based Access Control system separates operational roles (e.g., who can mint) from administrative roles (e.g., who can pause). ### Step 3: Deploy on testnet Tempo's public testnet is live. Deploy your stablecoin, test mint and burn flows, and validate your compliance configuration before going to mainnet. Most integrations are straightforward for teams already familiar with EVM tooling. ### Step 4: Connect with ecosystem partners Learn about the Fee AMM and the stablecoin DEX. Tempo works with 60+ ecosystem partners and our enterprise team can connect you with the right partners to ensure your stablecoin has liquidity and on-ramp and off-ramp options. ### Step 5: Prepare for mainnet Before going live, work with Tempo's team to connect with the design partners building active payment flows on Tempo. Getting your stablecoin into payroll, payout, and remittance products before launch means you are not starting from zero on day one. [_Reach out_](https://tempo.xyz/contact) to our Enterprise Team to start issuing your stablecoin on Tempo. --- ## Stablecoin Opportunity for Sponsor Banks > Source: https://tempo.xyz/blog/stablecoin-opportunity-for-sponsor-banks/ > Language: en **_Sponsor banks already power fintechs with bank accounts, virtual accounts, and payments. The same fintechs now need stablecoin wallets, transfers, and cards. Sponsor banks that build for this can defend their customer base and grow revenue per relationship._** [_Get in touch_](https://tempo.xyz/contact) if you are a sponsor bank evaluating stablecoin services for your fintech customers. The last decade of fintech ran on sponsor banks. Banks like Cross River, Coastal, and Lead and others gave fintechs access to the regulatory and operational rails that they couldn't access on their own: bank accounts, payments, and cards, packaged behind modern APIs. Fintechs owned the customer relationship while their bank partners provided the charter, the balance sheet and access to payment rails. Banks that successfully adopted this partnership model have realized above-market return on equity over the past decade. Fintech companies are now coming onchain. Their customers now also want stablecoin accounts, instant cross-border payments, and onchain savings products. Stablecoin supply has crossed $300 billion[^1]. McKinsey & Company tracked more than $390 billion[^2] in real payment volume over the past year. Visa hosts more than 160 stablecoin card programs globally and settles $7 billion in annualized stablecoin card payment volume, which is up nearly 200% year-over-year[^3]. Supporting stablecoin-backed business models is now a golden opportunity for sponsor banks. The passage of the GENIUS act in the US and MiCA in Europe have cleared the regulatory path. Regulators across the globe have given banks the greenlight to build on stablecoin infrastructure. Sponsor banks already have the relationship, the compliance program, and the integration in place for fintech programs. Extending into stablecoins deepens existing relationships and opens new revenue streams. ## What fintechs are asking for Remittance companies already use stablecoins to save on fees or serve long-tail corridors. PSPs sell global payouts with stablecoins to marketplaces. Neobanks let users hold savings in dollars with stablecoins, especially in markets with high inflation. The growing number of use-cases presents an opportunity for sponsor banks to handle the whole stack: - **Custodial stablecoin accounts** for fintechs and their end-users. The bank retains control over onchain accounts with stablecoin balances landing on its books, the same way DDA and FBO programs work for fiat. - **Onramp and offramp between fiat and stablecoins**. Funds flow via ACH or card the same way they do for DDA accounts, but get credited to custodial wallets in stablecoins. The conversion step is a new piece. - **Stablecoin payment origination** for domestic or cross-border payments. Payments are sent and received on behalf of fintech customers, including flows routed through the so-called stablecoin sandwich. Same role banks already play in ACH and wire payments. - **Stablecoin card programs**. Authorization runs in real time against the cardholder's onchain balance in the custodial account, not a fiat DDA. BIN sponsorship and program management carry over directly from fiat debit and prepaid cards. - **Savings products**. Customers earn interest on their stablecoin balance, with returns sourced from tokenized money market funds or DeFi protocols. Same product as a fiat high-yield savings account, except the yield passes through directly from the fund or protocol rather than the bank's NIM on deposits. A fintech that wants this stack has two options. Find new vendors and build a parallel onchain program on top of their sponsor bank's fiat offering. Or ask their sponsor bank to expand the relationship to cover both. The second option is the cleanest for the fintech and the most defensible for the bank. A single compliance program, a single contract, a single API integration, fiat and stablecoins on the same statement. ## Why banks choose to build on Tempo Tempo is built for payments, with high throughput, predictable low fees, and fees payable in stablecoins instead of a native gas token. However, several features were designed specifically for financial institutions, and they map directly to how sponsor banks already work. - [**Virtual addresses**](https://tempo.xyz/blog/virtual-addresses) are the onchain analog of virtual account numbers. A sponsor bank registers a master wallet for each fintech, creating an equivalent of an FBO account, and then derives a unique receive address for every fintech end-user. Inbound transfers route to the master wallet automatically, with no sweep step. Reconciliation works the same way it does for virtual accounts. ![Virtual addresses for sponsor bank stablecoin programs](/blog/stablecoin-opportunity-for-sponsor-banks/virtual-addresses.png) - [**Tempo Zones**](https://tempo.xyz/blog/privacy-on-tempo) give regulated institutions privacy at the protocol level. Account balances and transactions stay confidential while remaining auditable for the bank and its regulators. A sponsor bank can run its own zone or use a partner-operated one. ![Tempo Zones for private stablecoin transactions](/blog/stablecoin-opportunity-for-sponsor-banks/tempo-zones.png) - [**Compliance controls**](https://tempo.xyz/blog/compliance-controls) are native to the protocol. Token-level allowlists and blocklists let issuers gate stablecoins to KYC'd users. Account-level policies, rolling out soon, let custodial wallet operators (sponsor banks among them) restrict which addresses a wallet can transact with and which tokens it can hold. ![Compliance controls on Tempo](/blog/stablecoin-opportunity-for-sponsor-banks/compliance-controls.png) - [**Transfer memos**](https://tempo.xyz/blog/tip20) are additional information attached to any native token transfer on Tempo. Transfer memos can be used for reconciliation across onchain and offchain rails, for example, to reconcile stablecoin transfers with IVMS101 and SWIFT messages. ![Transfer memos on Tempo](/blog/stablecoin-opportunity-for-sponsor-banks/transfer-memos.png) More than [**60 partners have already integrated Tempo**](https://tempo.xyz/ecosystem) features across custody, wallets, onramps and offramps, compliance, cards, and savings. Sponsor banks can compose a stack from the ecosystem rather than build one to accelerate development. ## How to build it Sponsor banks don't need to ship the full stack on day one. Pick a fintech client or segment with clear stablecoin demand and build for them first. The rest of the book follows. - **Start with a minimum viable offering.** Onramp and offramp paired with custody is enough to launch. The ability to hold, send, and receive stablecoins covers many use cases, from global trade to cross-border payouts. Cards and savings can come later. - **Partner for wallets.** Wallet infrastructure is fundamentally a security problem with multi-chain complexity. Key storage, transaction signing, and account recovery are easy to get wrong, and getting them right requires a crypto-engineering team most banks don’t have. Privy, Turnkey, and Crossmint run embedded and custodial wallet platforms covering authentication, key management, signing, recovery, and multi-chain support. - **Line up issuers for onramp.** The sponsor bank is already the fiat leg of the onramp through ACH and wires. The missing piece is a direct mint and redemption relationship with stablecoin issuers. Consider holding pre-minted inventory for real-time user onramps. Orchestration platforms like Bridge and BVNK enter the picture later, when fintechs need to serve markets outside the US or in non-USD currencies. - **Extend the compliance program.** Your fiat AML and sanctions tooling carries over. What's new onchain is screening for sanctioned addresses, monitoring counterparty wallets, and applying the Travel Rule to stablecoin transfers. Vendors like Chainalysis, TRM, and Sardine plug into the case management your team already runs. - **Scope the rollout.** Launch with a small number of fintech partners who already serve the use cases that fit. Run them on real volume for 60 to 90 days. Use what you learn to harden the product before opening it to the rest of your book. Once the core products are live, collect feedback from fintech partners and their end-users on what's actually being used, where flows break, and what they ask for next. Use that feedback to prioritize the next layer of products. Some emerging product and revenue opportunities include: - **Add stablecoin cards.** Stablecoin cards are the fastest-growing stablecoin product. They let consumers and businesses spend stablecoins anywhere a card is accepted. Consider settlement with the card networks in stablecoins as well. - **Source the savings yield**. Onchain yield comes from tokenized money market funds or DeFi lending protocols like Aave and Morpho. Most sponsor banks won’t offer these products themselves, so set up partnership early. This is usually the next ask after launch. - **Enable merchant payouts**. PSPs and marketplaces can pay merchants in seconds, not days. Merchants get working capital sooner, and the platform can offer instant payouts as a premium feature. Build capabilities to enable mass stablecoin payouts. - **Add non-USD, FX, and custom stablecoins.** USD stablecoins are the starting point. The next layer is non-USD stablecoins and onchain FX between them. Tailor the offering for local markets and use cases. Several areas need answers before launch. Who custodies the stablecoins and on whose books they sit. How reconciliation handles a payment that can arrive onchain or via wire. How suspicious activity reporting works for onchain flows. Which stablecoins the program supports, and on which networks. Discovering the answer after launch is expensive. ## Work with Tempo Tempo supports sponsor bank stablecoin programs through advisory, native protocol features, and a partner ecosystem. That includes designing the use case, bringing the right partners, and developing missing blockchain features when needed. - **Stablecoin Advisory**. Tempo's advisory team helps sponsor banks scope the offering, select partners, design the compliance program, and run the first pilot. [_Learn about Tempo’s Stablecoin Advisory_](https://tempo.xyz/contact/). - **Native protocol features**. Tempo builds capabilities critical to real-world use cases, like privacy and compliance, directly into the protocol. That removes the need for application-layer workarounds. [_Read the docs and try demos_](/developers/)_._ - **Partner ecosystem**. Whether finding wallet partners, lining up issuers, sourcing savings yield, or extending the compliance program, Tempo's partner ecosystem covers it. Tempo continues to bring in new partners as use cases emerge. [_Explore the ecosystem._](https://tempo.xyz/ecosystem) If you're a sponsor bank evaluating stablecoin services for your fintech customers, see what [companies are building](https://tempo.xyz/customer-stories) on Tempo and [get in touch](https://tempo.xyz/contact) with our Enterprise Team. [^1]: [Artemis](https://classic.artemis.ai/stablecoins) [^2]: [McKinsey & Company](https://www.mckinsey.com/industries/financial-services/our-insights/stablecoins-in-payments-what-the-raw-transaction-numbers-miss) [^3]: [Visa Investor Relations](https://investor.visa.com/) --- ## Stablecoins for Neobanks > Source: https://tempo.xyz/blog/stablecoins-for-neobanks/ > Language: en **_Stablecoins help neobanks launch new products, reach new customer segments, and expand into new markets. Many build on Tempo for predictable costs, built-in compliance, and a growing ecosystem of 60+ partners. If you want to explore this for your company,_** [_get in touch_](https://tempo.xyz/contact) with our Enterprise team. Neobanks won customers and market share with better mobile apps, faster onboarding, and lower fees, but the infrastructure they’re built on did not change. Cross-border payments still rely on correspondent banking, offering yield still depends on partner banks, and expansion still means more licenses, new integrations, and months of work. Stablecoins and onchain infrastructure remove these constraints. Neobanks move money globally with stablecoins, offer yield through tokenized funds, and enter new markets through self-custodial wallets without having to secure a banking partner in each market. For neobanks ready to capture this opportunity, Tempo offers three ways to get started. Each builds on the last and brings you closer to the products your customers expect. ![Offer cross-border payments](/images/blog/-__22_.png) ## Offer cross-border payments Every time a customer leaves your app to send money abroad, you lose them. They move funds out, pay someone else’s fees, and often don’t come back. Stablecoins enable near-instant [cross-border payments](https://tempo.xyz/blog/remittances) at costs competitive with specialized remittance services. Cross-border payments with stablecoins involve three steps: funds are converted to stablecoins, sent onchain, and paid out locally through partners into bank accounts or wallets. Expanding to new corridors primarily involves finding new offramps, which is generally simpler than securing new banking relationships. A neobank running this model has very different unit economics from one relying on correspondent banks, and customers no longer need to leave your app to send money abroad. ![Embed stablecoin wallets](/images/blog/-__23_.png) ## Embed stablecoin wallets An existing neobank can add custodial stablecoin accounts alongside its core product. Users onramp and offramp, send and receive stablecoins, while you retain full control over compliance and regulatory requirements. Instead of losing customers to standalone crypto wallets, you offer the same functionality natively. Users hold dollar-denominated stablecoins, convert when they choose, and transact globally from the same place they manage their fiat accounts. This is especially relevant for companies [paying international contractors](https://tempo.xyz/blog/global-payouts) and employees working for global companies. Stablecoin wallets sit alongside existing accounts, with partners handling key management, security, and transaction infrastructure. ![Expand to new markets](/images/blog/-__24_.png) ## Expand to new markets Self-custodial wallets let neobanks enter new markets without setting up local banking relationships or navigating full licensing in every jurisdiction. Your app can support payments, on and offramps, cards, savings, and lending without custodying funds. This changes the regulatory setup. Non-custodial products can face lighter requirements than deposit-taking models, leading to faster expansion, though in some jurisdictions these still require licensing. The same wallet infrastructure supports multiple products, from cards for spending stablecoins at the point of sale to tokenized funds and lending. This path requires more investment, but the economics are stronger, with recurring revenue across multiple products rather than one-off fees. ## What to evaluate before building Before building, evaluate where the opportunity is real and what it will take to support it. - **Is there real demand?** If customers are sending money to remittance services, this signals cross-border payment demand. If they are using exchanges or onramps, this signals demand for embedded wallets. Survey your customers to validate this. - **What are the regulatory constraints?** Requirements differ by country. Some require licensing even for self-custodial wallets, while others restrict or ban stablecoins. This determines which products you can offer and where. - **Do you have the right partners?** Understand your target markets and corridors. This will shape your choice of partners, as their capabilities vary by geography, coverage, and product scope. - **Build or partner?** Start with partners to move faster, especially for components that require licenses, such as onramps, custody, and payouts. Consider building in-house where licensing is not required and where it creates differentiation or improves unit economics. The choice of partners and regulatory constraints will shape what you can launch and how quickly you can scale. ## Why neobanks build on Tempo Tempo provides many of the core capabilities you need out of the box, with a growing partner ecosystem to cover the remaining gaps. This is why many neobanks are already building on Tempo. Tempo offers: - **Predictable fees.** Tempo provides low, [predictable fees paid in stablecoins](https://tempo.xyz/blog/stablecoin-fees). Transactions cost fractions of a cent, with no separate gas token or price spikes during congestion. There is no account rent, and account creation is effectively free at scale. - **Privacy.** Tempo supports privacy where it matters. Balances and transaction flows can remain private while still being auditable for compliance and regulatory requirements. - **Compliance.** [Compliance runs at the protocol level](https://tempo.xyz/blog/compliance-controls). Policy controls such as whitelist and blacklist enforcement and transfer restrictions are built directly into account and token operations, with additional monitoring and screening supported through partners. - **User Experience.** [Smart accounts](https://tempo.xyz/blog/account-abstraction) enable passkey authentication, gas sponsorship, batch transactions, and scheduled payments. Users sign in with biometrics instead of managing seed phrases or transaction fees. - **Partners.** The [ecosystem](https://tempo.xyz/ecosystem) fills in the rest. Wallet infrastructure, stablecoin issuance, payments orchestration, cards, and tokenized funds are available through partners, reducing the need to build each component internally. ## Work with Tempo Tempo works with neobanks to evaluate the opportunity and implement stablecoin products, from initial analysis through pilot and scale. - Identify which path fits your business, from cross-border payments to wallets and new market expansion - Analyze your transaction flows to identify high-impact corridors and use cases - Model the business case using your volumes, pricing, and unit economics - Review integration requirements for your existing stack - Design a pilot tailored to your highest-impact use case - Connect with partners for wallets, payments, cards, and compliance If you want to explore how this could work for your company, [get in touch](https://tempo.xyz/contact) with our Enterprise team. ## Frequently Asked Questions ### What problem do stablecoins solve for neobanks? They remove three constraints. Dependence on correspondent banks for cross-border payments, reliance on external apps for stablecoin access, and the need for local banking partners when entering new markets. ### Do I need a banking partner in every country? No. Stablecoin rails and local payout partners remove the need for direct banking relationships in each market. You may still choose to partner with a bank or fintech to support onramping and offramping. ### Can I keep compliance under control? Yes. Policy controls such as whitelists, blacklists, and transfer rules can be enforced at the protocol level, with additional monitoring via partners. ### Should I choose custodial or self-custodial wallets? Custodial gives you control over UX and compliance. Self-custodial reduces regulatory burden and speeds up market entry, but shifts control to the user. ### Is regulatory approval required? Depends on jurisdiction and product. Some require licenses even for non-custodial setups, others restrict stablecoins entirely. ### Should I build or partner? Start with partners for licensed components like custody, onramps, and payouts. Build in-house where it improves unit economics or differentiation. ### How do I get started? Define target markets and use cases, assess regulatory constraints, then run a pilot with selected partners before scaling. [Get in touch](https://tempo.xyz/contact) with our Enterprise team to get started. --- ## Stablecoins for Payroll > Source: https://tempo.xyz/blog/stablecoins-for-payroll/ > Language: en **_Stablecoins enable faster payroll funding, cheaper cross-border payouts, and new revenue streams for payroll providers. This guide covers how to move from faster funding cycles to a full financial services platform, and what to evaluate before building._** [_Contact us_](https://tempo.xyz/contact) if you're ready to explore what stablecoin payroll looks like for your client base. Payroll providers are starting to take stablecoins seriously. The reasons are familiar to anyone running global payroll: ACH funding takes 2-3 days and carries return risk, cross-border settlement routes through multiple intermediaries that each extract fees, and employees in emerging markets lose money to forced currency conversion. Stablecoins fix all of that, but the opportunity goes beyond faster and cheaper payments. There are three use cases here, and they build on each other: faster payroll account funding, cheaper cross-border payouts to employee wallets, and embedded wallets that turn payroll into a financial services platform. Providers like Deel and Gusto have already started moving in this direction. Here is what each looks like in practice. ![Payroll account funding diagram](/images/blog/-__16_.png) ## 1. Faster payroll account funding Funding payroll accounts with stablecoins is the lowest-lift opportunity and the one most providers overlook. Today, employers fund payroll accounts via ACH, which takes 2-3 days to settle and can be returned after employees have already been paid. The provider carries that exposure. Stablecoin funding settles in seconds. Same-day payroll cycles become possible without the provider absorbing settlement risk. Nothing changes for employees here. They still receive payroll the same way. The improvement is entirely on the funding side: faster cycles, no float risk, simpler cash management. Banking platforms like Ramp, Brex, and Meow are already adding stablecoin support, which makes it easier for employers to fund payroll accounts in stablecoins. For providers processing significant volume, eliminating 2-3 days of settlement risk and the operational overhead of managing ACH returns is meaningful on its own. ![Instant payroll payments](/images/blog/-__17_.png) ## 2. Faster, cheaper cross-border payouts Cross-border payroll routes through payment processors, correspondent banking networks, and local receiving banks. Each intermediary takes a cut. Employees absorb FX spreads of 1-4% when their payment is converted to local currency: a cost they can't negotiate and often can't see. Stablecoins cut through the intermediary chain. Payouts settle in seconds to wallets employees already have, regardless of time zone or bank holiday. Transaction costs drop to cents. The total [cost reduction for cross-border payouts runs 60-80%](https://tempo.xyz/blog/global-payouts). Providers don't need to build wallet infrastructure either; employees can bring their own. For employees, the experience also changes for the better. They receive dollar-denominated stablecoins and choose when (or whether) to convert to local currency. In markets with currency volatility, like Argentina, Nigeria, or Turkey, the ability to hold dollars and convert on their own terms preserves purchasing power. Workers stop losing money to exchange rates set by banks they didn't choose. This is where payroll providers start to differentiate. If your competitors are still routing through correspondent banking and your clients' contractors are getting paid in seconds at a fraction of the cost, that's a tangible advantage in competitive deals. ![Self-custodial wallet](/images/blog/-__18_.png) ## 3. Embedded wallets and financial services The first two use cases make payroll faster and cheaper. The third one changes the business model. Today, payroll providers handle the payout. Banks capture everything that happens after. Employee deposits get monetized through cards, savings accounts, loans, and investment products. The payroll provider did the work of acquiring and paying the employee, but the bank captures the ongoing financial relationship. Embedded wallets flip this. When a payroll provider issues a wallet to each employee, the provider controls the user interface and maintains the relationship after funds land. That opens three revenue streams that don't exist in traditional payroll: - **Branded stablecoins and reserve yield.** Instead of paying employees in USDC, a provider can issue its own stablecoin backed 1:1 by reserves (US Treasuries and deposits). The provider earns the yield on those reserves for as long as employees hold balances. Partners like Bridge handle issuance and compliance. - **Card interchange.** Stablecoin-backed cards with automatic conversion at point of sale generate 1-2% interchange on spend. For a client with 1,000 employees spending $2,000/month on cards, that's $240K-$480K in annual interchange revenue. - **Tokenized investment products.** Wallets can offer tokenized money market funds yielding 3-3.5%, or structured credit products at 6-8%. This gives employees access to yields they wouldn't typically get through a traditional payroll deposit, and creates distribution revenue for the provider. The wallet approach also simplifies global rollout. Non-custodial wallets don't hold customer funds, so they don't require banking or payment institution licenses in every jurisdiction. A provider can launch wallets across dozens of countries with the same infrastructure. That's fundamentally different from custodial financial services, which need per-market licensing. This is the most ambitious path, and it requires investment in infrastructure, compliance, and product. However, it's also the path that turns payroll from a low-margin transaction business into a platform with recurring revenue. The unit economics shift from "fee per payout" to "lifetime value of a financial relationship." ## What to evaluate before building Not every payroll provider needs to go to level three on day one. The right starting point depends on your client base and where the pain is sharpest. - **Where are your clients' employees?** If you're primarily in the US or Europe, the pain points are real but less acute. If you serve companies with contractors across Latin America, Africa, or Southeast Asia, the case for stablecoins is immediate and measurable. - **What corridors are most expensive or unreliable?** Focus stablecoin payouts where correspondent banking is slowest and most expensive. - **Do you want to capture value beyond the transaction fee?** If yes, the wallet path is worth serious evaluation. You can start with payroll account funding and cross-border payouts while building toward wallets. This is a multi-year build, and partner selection matters more than most providers expect. Choose partners who are thinking long term. ## How Tempo fits The stablecoin you pay employees with is only as reliable as the infrastructure it runs on. At scale, the differences between chains become operationally significant. - **Privacy for sensitive payroll data.** Salary information on a public blockchain is a non-starter. Tempo's opt-in privacy solution keeps salary amounts, employee identities, and payment patterns shielded from the public while maintaining full auditability for compliance and internal controls. Employees and employers get privacy by default. Auditors and regulators can access data when required. - **Predictable delivery during congestion.** Dedicated payment lanes ensure payroll transactions process on schedule even when the network is busy. Missing a payroll cycle because of network congestion is not acceptable. - **Compliance and reconciliation built into the chain.** Native memo fields attach travel rule identifiers, invoice references, and reconciliation metadata directly to transactions, so payroll records map cleanly to onchain activity. Allow/blocklists for transaction control. These aren't add-ons; they're native to the chain. - **No account rent.** When you're provisioning wallets for hundreds of thousands of employees, account rent fees on other chains become a real cost line. Tempo doesn't charge account rent. - **Low, predictable fees paid in stablecoins.** No token management overhead. No gas price volatility. Fees are measured in cents and can be sponsored so employees never see them. ## Other factors to consider Stablecoins solve real problems, but they create new considerations. - **Regulation and compliance don't disappear.** Stablecoins change the payment mechanism, not the regulatory framework. Tax withholding, labor law, and reporting requirements still apply in every jurisdiction. Some countries restrict or prohibit stablecoin payments entirely, so you need to verify the landscape in every market where you operate. - **Not all employees will want stablecoins.** Maintaining parallel payroll rails adds complexity, but forcing adoption creates friction. Offer stablecoins as an option, not a mandate. - **Employee education takes work.** Workers unfamiliar with digital wallets need clear onboarding. Support teams need training. This is operational investment that's easy to underestimate. > [Reach out](https://tempo.xyz/contact) to our Enterprise Team, if you want to explore what stablecoin payroll looks like for your client base. --- ## Stripe and Tempo: stablecoin settlement for global money movement > Source: https://tempo.xyz/blog/stripe-and-tempo-stablecoin-settlement-for-global-money-movement/ > Language: en **_Stripe's money management capabilities now support stablecoin transfers on Tempo. Businesses in 100+ countries can hold, send, and receive stablecoins directly from Stripe, settling in under a second._** [_Learn more in the full case study_](https://tempo.xyz/customer-stories/stripe) Global payouts remain one of the most expensive and unpredictable parts of running an international business. A company paying contractors in 30 countries manages a patchwork of regional payment rails, each with its own settlement timelines, fee structures, and intermediaries that add cost at every hop. For platforms distributing earnings to sellers and creators across dozens of markets, those limitations compound with every payout. As stablecoin demand grew across Stripe's customer base, Stripe needed blockchain infrastructure that could match its scale, reliability, and cost requirements for global payments. General-purpose blockchains built for trading and DeFi introduced unpredictable fees, throughput constraints, and operational complexity that didn't fit Stripe's payment workloads. ## Stripe and Tempo Tempo now serves as core blockchain infrastructure powering Stripe's [money management capabilities](https://stripe.com/financial-accounts). Millions of businesses can hold, send, and receive stablecoins directly from Stripe. When a business sends a payout to a contractor abroad or a platform distributes earnings to sellers across 100+ countries, the transaction settles in under a second at a fixed cost of $0.001. But money management is just the starting point. Tempo is being integrated more broadly across Stripe products. Connect payouts, card issuance, and onramp infrastructure all benefit from the same settlement properties. Through Stripe's partnership with Visa, recipients can spend directly from stablecoin balances at merchant locations worldwide. The full loop works on a single stack: collect revenue through Stripe, hold stablecoins, pay out globally on Tempo, and let recipients spend via card. "It should be easy and instant to move money anywhere in the world. That's the promise of programmable financial services. As we bring stablecoin infrastructure into more Stripe products, we're delivering on that promise at scale, so every Stripe user can benefit from faster, cheaper, borderless money movement." — Neetika Bansal, Head of Connect and Money Management at Stripe ## What Stripe needs from a settlement layer Moving money at Stripe's scale puts specific demands on the infrastructure underneath. Millions of businesses sending payouts across 100+ countries need a settlement layer that is fast, predictable, and operationally invisible. Dedicated payment lanes guarantee blockspace for payment transactions at the protocol level, so throughput is never affected by other network activity. For infrastructure supporting millions of businesses, that reliability is a prerequisite. Gas abstraction means the entire money management experience operates in dollars. Fees are denominated in stablecoins rather than a volatile native token, keeping operational budgets predictable and accounting simple. Native memo fields compatible with ISO 20022 let each transfer carry structured metadata: invoice numbers, cost centers, payout identifiers. For businesses reconciling thousands of payouts against ERP and treasury management systems, this makes reconciliation straightforward. Fixed fees per transaction eliminate the cost uncertainty of traditional correspondent banking, regardless of volume. ## What this means Stripe's approach positions Tempo as invisible infrastructure underneath the products millions of businesses already use. A business on Stripe does not need to know their payout settled on Tempo. They see a faster, cheaper transfer in their dashboard. For the broader market, the largest payment processor in the world running production infrastructure on Tempo signals where stablecoin settlement is heading. The question for enterprise payment teams is no longer whether stablecoins will play a role in global money movement, but which settlement layer to build on. [_Read the full case study_](https://tempo.xyz/customer-stories/stripe) --- ## Stripe, Visa, and Zodia Custody by Standard Chartered join as validators on Tempo > Source: https://tempo.xyz/blog/stripe-visa-zodia-join-as-validators/ > Language: en **_Starting today, Stripe, Visa, and Zodia Custody by Standard Chartered are validators on Tempo._** These organizations collectively process trillions of dollars in payments every year across nearly every country in the world. As some of the largest institutions in global payments, they maintain infrastructure at massive scale and have deep experience with the reliability and uptime standards that payments demand, bringing that same technical excellence to validate the Tempo network. > Tempo is building payments infrastructure the way we think about it at Visa, purpose-built for moving value at scale. Visa has spent decades running one of the world's most resilient payment networks, with globally distributed data centers, built‑in redundancy, and network‑level defenses that block tens of millions of attacks and billions in fraud every year. Bringing that operational rigor to Tempo's validator set is a natural next step as stablecoin payments scale. > > — Cuy Sheffield, Head of Crypto, Visa All of these companies have been part of Tempo from day one, helping shape the protocol as design partners and testing real workloads onchain. Each of these partners is also involved in building real payment flows on Tempo across a range of use cases, which we'll share more about soon. We'll continue expanding the validator set with additional partners on our path to permissionless validation. Tempo is live and open for building. Explore the [docs](/developers), [create a wallet](https://wallet.tempo.xyz/welcome), or [get in touch](https://tempo.xyz/contact). --- ## Subscriptions on Tempo: Onchain Billing Made Easy > Source: https://tempo.xyz/blog/subscriptions-on-tempo/ > Language: en **_Tempo's [access keys](/developers/docs/guide/tempo-transaction#access-keys) now support periodic spending limits, making subscription billing possible onchain without re-prompting users or holding their keys. The same mechanism works for human subscribers and AI agents. If you want to build recurring or scoped billing flows using stablecoins, reach out at [partners@tempo.xyz](mailto:partners@tempo.xyz)._** Many business models center around recurring billing: a customer pays a set amount every week, month or year for a product or service. This model works fine when the customer wants to pay using a credit card. It works less well for customers without a card or AI agents, who increasingly rely on stablecoins. For usage-based flows, [MPP Sessions](/blog/mpp-sessions) handles high-frequency payments without charging onchain for every request. While stablecoins handle one-time global payments cleanly, recurring billing has been harder. One option is to require fresh user approval at each charge. The other is to get approval from the user for significantly more funds than immediately needed, e.g., an approval for a year's worth of payments. This results in very poor UX and heightens the risk for consumers. Tempo [access keys](/developers/docs/guide/tempo-transaction#access-keys) let users delegate signing authority to a service with defined constraints: spend up to a fixed total, on specific tokens, until a given expiry. Access keys now also support periodic spending limits, which enables subscriptions. ## How Tempo solves the problem Access keys are a native primitive on Tempo that enables a wide range of payments use cases. This is how access keys work on Tempo: - A user authorizes an access key, specifying a maximum amount and an expiry. - They can hand this access key to a service without handing over control to their entire account. - A service can use the access key to "pull" funds from the user's account within that limit and until it expires. - Access keys can also be scoped to specific contracts and function selectors, so a key for one service can't be used elsewhere. The user can always revoke the authorization at any time. ![Subscriptions on Tempo](/blog/subscriptions-on-tempo-diagram.png) With periodic spending limits, that authorization now includes a per-period cap that resets automatically: - A service can be granted a right to spend, e.g., "$50 per week for the next 50 weeks" rather than a lump-sum total.[^1] - The protocol validates each charge against the current week's remaining allowance. If it fits, it succeeds. If it doesn't, it fails. - When the week ends, the window resets. The user sets terms once, and the service charges on schedule without re-prompting. ## What this enables Access keys make recurring payments with stablecoins practical in a way they weren't before, without repeated approvals or overly permissive authorizations. A SaaS company billing subscribers across 30 countries no longer needs regional payment integrations for each market. Every subscriber pays in stablecoins with the same flow: one access key authorization, periodic charges, instant settlement. Similarly, an AI agent that consumes a paid inference API can be granted a key scoped to that API's contract with a $100 monthly limit — complementing the real-time billing enabled by [MPP Sessions](/blog/mpp-sessions). The agent calls the service throughout the period using the access key to authorize payment. Each charge is validated against the remaining allowance, and the limit resets automatically. The agent cannot spend the funds elsewhere with that key. Finally, access keys also enable simple subscription services that charge a fixed periodic amount. For example, a user subscribes to a newsletter or a streaming service by authorizing an access key with a matching limit. ## Getting started If you're building recurring billing, agentic payments or stablecoin cards on Tempo, start with the [access keys documentation](/developers/docs/protocol/transactions/AccountKeychain) to understand key scoping and periodic limits, or explore [MPP Sessions](/blog/mpp-sessions) for usage-based billing patterns. Recurring billing is one of several new enterprise features live on Tempo today. For the full picture, see [new features on Tempo for enterprise payments](/blog/new-features-for-enterprise-payments). To discuss your use case with the product team, get in touch at [tempo.xyz/contact](https://tempo.xyz/contact/). [^1]: Recurring limits currently only support fixed time periods (e.g., 1 day, 1 week). Calendar support (e.g., 1 month) will be available after a future upgrade. --- ## Tempo and Privy launch limited-time Earn boost program > Source: https://tempo.xyz/blog/tempo-and-privy-launch-limited-time-earn-boost-program/ > Language: en **_Tempo and Privy are offering a limited-time Earn boost for eligible Privy customers building stablecoin rewards products. Apply by September 30, 2026 to find out if you are eligible to receive a 7% boosted rewards rate on the first $10 million in deposits for three months. [Learn more about Tempo Earn](/earn/)._** Stablecoin balances are increasingly part of products that people already use to manage money and make payments. For platforms, those balances can improve retention, create new revenue streams, and give customers a clear reason to keep funds on-platform. [Privy](https://www.privy.io/yield-integrations) makes it easier for platforms to embed rewards on Tempo. Through Privy's dashboard and Earn API, platforms can launch Earn directly within their applications. Tempo provides the payments-first stablecoin rail, so funds can move easily between earning, sending, and spending. For users, that means idle balances can earn rewards without leaving the product. For platforms, it means native reporting, simpler reconciliation, and more flexibility over vault ownership, reward economics, and strategy. ## A limited-time boost for eligible platforms For a limited time, eligible platforms can access a boosted Earn program through Tempo and Privy. Platforms that apply by September 30, 2026 can receive: - A 7% APY rewards rate for three months, covering up to $10 million in TVL per company - No gas fees for the first three months - Dedicated onboarding support from Tempo and Privy Existing Privy customers may also be eligible for bundled discounts on Privy monthly spend at renewal when they enable Earn on Tempo through Privy. ## Built to power embedded financial products Earn products should feel like normal financial products. Users should be able to put balances to work inside an application they already use, without leaving the product or managing unfamiliar workflows. With Privy, platforms can configure and launch Earn, then offer rewards to users directly within a familiar in-app experience. Privy and Tempo handle the wallet, vault, and payment infrastructure behind the scenes. Platforms can also configure how rewards are shared between the business and users. This creates a new revenue stream while giving customers a clearer reason to maintain balances. For supported vaults, the program uses Morpho vault infrastructure, with Sentora supporting vault curation, risk parameters, and monitoring. This gives teams one integration path for balances, rewards, movement, reporting, and controls. ## White-glove support from Tempo and Privy Tempo and Privy's solutions teams work directly with teams through implementation, from product design and vault selection to launch readiness. Teams get support configuring reward economics, risk and compliance requirements, reporting, and ongoing operations. --- ## Tempo × Commonware > Source: https://tempo.xyz/blog/tempo-commonware/ > Language: en **_Tempo will adopt the [Commonware Library](https://docs.rs/commonware-p2p/latest/commonware_p2p/) and become a core contributor to its ongoing development. We're also leading a $25 million strategic investment round in Commonware to advance our shared vision of high-performance, reliable infrastructure for every builder._** This is a great advancement for Tempo, for a few reasons: - We can focus on shipping key payments features and optimizing Tempo, instead of reinventing the consensus wheel. This will enable us to ship more, faster. - Commonware will enable us to get to <250ms finality on a globally distributed permissionless payments system. This will come via multiple innovations in consensus, cryptography, and networking. - Tempo will accelerate the maturation of the Commonware Library, stress testing its performance and reliability for real-world usage. We were first impressed by the Commonware team's approach to building consensus algorithms as a library, and we continue to be impressed by their continuous progress on the frontier of distributed systems. Read more [here](https://commonware.xyz/blogs/welcome-tempo), but this is the start of a long-term collaboration between our two teams, focused on speed, simplicity, and open infrastructure. If you're building at the frontier, reach out to [join@tempo.xyz](mailto:join@tempo.xyz) or [commonware.xyz](mailto:hello@commonware.xyz). --- ## Tempo Earn now supports Hastra’s PRIME and wYLDS > Source: https://tempo.xyz/blog/tempo-earn-hastra-prime-wylds/ > Language: en **_[Tempo Earn](https://tempo.xyz/solutions/earn/) now supports Hastra-minted PRIME and wYLDS, giving platforms more ways to embed real-world yield into treasury, card, and payment products. The assets give platforms additional options for credit-based returns and DeFi-native yield products, alongside the yield assets already available on Tempo._** The right yield asset depends on how customers use their funds, how quickly they may need access, where they are located, and what kind of risk they are prepared to take. A card program may prioritize balances that remain available for spending. A treasury or savings product may want to offer a different return profile tied to real-world lending. Platforms need the ability to support both experiences without building separate products and infrastructure for each one. Through Tempo Earn, platforms can now access Hastra-minted DeFi assets connected to Figure’s Democratized Prime marketplace. [Figure](https://www.figure.com/) is a blockchain-native capital marketplace focused on bringing lending, funding, and real-world asset markets onchain. Figure’s Democratized Prime marketplace connects lenders with pools of real-world loans. [Hastra](https://hastra.io/prime), a protocol developed in partnership with Figure, brings these assets into DeFi. Users can mint wYLDS through the protocol and stake wYLDS to receive PRIME. PRIME’s return is connected to Figure’s home equity lending operations. For platforms, this creates more room to design Earn products around specific customer needs. Rather than applying one asset and return profile to every balance, platforms can choose based on liquidity, eligibility, risk, and intended use. ## PRIME PRIME is a Hastra-enabled DeFi asset created by staking wYLDS, with both wYLDS and PRIME bridged to Tempo through [Chainlink’s Cross-Chain Interoperability Protocol](https://chain.link/cross-chain). It currently offers an indicative APY of approximately 7%.\* Returns are linked to Figure’s HELOC lending operations and vary with borrower demand and pool utilization. PRIME is available to eligible customers globally, subject to local restrictions. Customers can unstake without a fixed lockup and redeem PRIME for wYLDS. Redemption and final conversion into other assets depend on the network, access route, and available liquidity. Eligible users can explore the [PRIME pool on Uniswap](https://app.uniswap.org/explore/pools/tempo/0x0b9a0ce880fd51829b650bf2bbacff62f10ffe274b2250b2c3cf1c5614aab427), which currently has approximately $25M in liquidity. PRIME provides access to a potentially higher, credit-based return while retaining onchain utility. It gives platforms another option for customers who can accept a different risk and liquidity profile in exchange for exposure to real-world lending. ## What Tempo Earn provides Tempo Earn helps platforms turn these assets into embedded customer products. Platforms choose which assets to offer, decide how rewards are divided between the platform and its customers, and control how funds move between earning, spending, payouts, and withdrawals. Tempo provides the infrastructure needed to operate these products at scale. Tempo Zones help keep balances and activity private. Account policies and transfer controls let platforms define how funds can move. Stablecoin-denominated fees remove the need for users to manage a separate fee token, while Tempo’s payment infrastructure supports high-volume dollar movement. The partnership combines three parts of the product stack. Figure provides onchain capital markets and real-world lending infrastructure. Hastra enables users to mint and access wYLDS and PRIME for use in DeFi. Tempo provides the payments-first network that connects these assets to customer-facing products. If you are building Earn, treasury, card, or payment products on stablecoin rails, [get in touch with Tempo](/contact). Eligible users can learn more about [accessing PRIME through Hastra](https://hastra.io/?utm_source=partner&utm_medium=blog&utm_campaign=tempo). \*The PRIME Effective APY displayed is an estimate based on the trailing 24-hour change of each displayed Hastra token’s Net Asset Value. It reflects the actual yield distributed to holders, including both the Democratized Prime pool rate and wYLDS interest on unutilized pool liquidity, net of the 50 bps Hastra fee. The rate is updated in the Hastra UI every 5 minutes. Prior rates do not guarantee future rates. --- ## Tempo expands onchain yield offering with BlackRock’s BUIDL fund > Source: https://tempo.xyz/blog/tempo-expands-onchain-yield-offering-with-blackrocks-buidl-fund/ > Language: en **_The [BlackRock](https://www.blackrock.com/) USD Institutional Digital Liquidity Fund (BUIDL) is now available on Tempo. Companies building wallets, treasury products, and global money movement applications on Tempo can let eligible customers move idle stablecoin balances into tokenized fund shares without leaving their onchain workflows. [Get in touch](https://tempo.xyz/contact/)._** The integration extends the companies' work on institutional stablecoin and tokenized asset infrastructure. The deployment brings the Moody’s AAA-mf rated tokenized fund to Tempo, giving eligible users a way to hold stablecoin balances and access yield through tokenized fund shares. BUIDL is BlackRock's flagship tokenized short-term treasury fund. It gives qualified investors exposure to U.S. dollar yield through a fund share backed by cash, U.S. Treasury bills, and repurchase agreements. Bringing BUIDL to Tempo expands access to institutional-grade yield on infrastructure built for high-volume, low-cost, compliant financial activity. BUIDL’s availability on Tempo is supported by [Securitize](https://securitize.io/)’s tokenization and transfer agent infrastructure, with daily onchain valuation and interest accrual supported by [RedStone](https://www.redstone.finance/) oracle feeds. "Institutions want the benefits of stablecoins without giving up access to familiar products like treasury funds," said Ninad Nirgudkar, GTM at Tempo. "BUIDL on Tempo brings those closer together. With the participation of companies like BlackRock on Tempo, we are building the infrastructure for yield-bearing balances, treasury management, and settlement onchain." “As stablecoins become part of more cash, payment, and settlement activity, cash management products should be available where digital dollar balances are held and used,” said Maxwell Stein, Director, Digital Assets at BlackRock. “Making BUIDL available on Tempo reflects our continued effort to expand access for eligible investors to tokenized U.S. dollar yield as onchain finance develops.” “BUIDL has established itself as a leading example of how tokenization can bring trusted financial products onto blockchain infrastructure at institutional scale,” said Carlos Domingo, Co-Founder and CEO of Securitize. “We’re excited to integrate Securitize with Tempo for the first time, bringing BUIDL to its growing ecosystem of companies building the next generation of payments, treasury management and onchain financial services.” The integration reflects broader collaboration across tokenized finance. Companies are exploring more ways to connect regulated financial products with stablecoin-native payment and settlement infrastructure. Tempo is building payment-first blockchain infrastructure for stablecoins, tokenized deposits, and real-world financial activity. With BlackRock now participating in the ecosystem, Tempo will continue developing onchain yield capabilities for institutions that need speed, programmability, compliance, and access to products their customers already understand. --- ## Introducing Tempo Transactions > Source: https://tempo.xyz/blog/tempo-transactions/ > Language: en **_Tempo Transactions are a new, native transaction type introduced in Tempo. They enable features like paying network fees in any stablecoin, batch and concurrent transactions, fee sponsorship, scheduled payments, and modern authentication using passkeys (FaceID, biometrics). This unlocks use cases like payroll, payouts, and subscriptions while allowing applications to offer seamless user experiences with low operational overhead and complexity. Learn more in [our docs](/developers/docs/protocol/transactions)._** Stablecoins have enabled 24/7 settlement and lower-cost transactions. Tempo’s goal is to unlock the potential of stablecoins, with primitives for at-scale payments such as batching, scheduling, and complex payment workflows. Tempo is built for moving money at scale and at low cost, with the operational efficiency banks, fintechs, and enterprises depend on. Tempo Transactions bring the modern payment mechanics that these businesses need onchain. > Building wallet infrastructure, we've gotten to work across a huge number of chains in the past. Partnering with Tempo to help them integrate the features we wish existed onchain has been very exciting. Integrated fee sponsorship, batching, and transaction memos stand to transform the developer experience building payments on blockchain. We're excited to support Tempo developers building with Privy to power these new use cases. > > — Henri Stern, CEO, Privy ## A native transaction type for modern payments Enterprise payment systems rely on capabilities that traditional blockchains rarely provide out of the box: structured data, concurrency, and the ability to orchestrate many transactions within a single atomic workflow. Tempo Transactions provide these capabilities natively. The functionality that real-world enterprise payment workflows require is built directly into the protocol: - **[Configurable fee token](/developers/docs/protocol/transactions#configurable-fee-tokens).** Pay transaction fees with any USD-denominated stablecoin. - **[Concurrent transactions](/developers/docs/protocol/transactions#concurrent-transactions).** Execute multiple transactions from the same account in parallel. - **[Batch calls](/developers/docs/protocol/transactions#batch-calls).** Batch multiple transactions together for higher throughput and atomic execution. - **[Scheduled transactions](/developers/docs/protocol/transactions#scheduled-transactions).** Schedule transactions to execute within a specific future time window. - **[Fee sponsorship](/developers/docs/protocol/transactions#fee-sponsorship).** Applications or third parties can cover users' gas fees for a more seamless UX. - **[Passkeys](/developers/docs/protocol/transactions/AccountKeychain).** Users can authenticate and authorize transactions with biometrics (fingerprint, Face ID, Touch ID). With Tempo, these features are available and optimized at the protocol level, so that developers can focus on building payment applications instead of building around infrastructure gaps. We've partnered with infrastructure providers including [Crossmint](https://www.crossmint.com/), [Fireblocks](https://www.fireblocks.com/), [Privy](https://www.privy.io/), and [Turnkey](https://www.turnkey.com/), who are rolling out Tempo Transactions to help accelerate your development. > We're excited to partner with Tempo because Turnkey makes it possible for developers to build on Tempo using both legacy Ethereum transactions and Tempo's new EIP-2718 transactions with payload signing, including support for Tempo's native gas sponsorship. > > — Bryce Ferguson, CEO, Turnkey ## Bringing real-world payments onchain We worked with design partners across finance, commerce, and technology to understand the requirements of real-world payment systems. Tempo Transactions reflect these learnings. The capabilities of Tempo Transactions reflect these learnings, providing the features necessary to bring a wide range of payment use cases onchain: ![Introducing Tempo Transactions Global Payouts](/images/blog/tempo_transactions_3.png) ### Payroll and merchant payouts Batch transactions allow large payout runs to be processed efficiently and securely. Payments execute in a single atomic batch: the entire batch succeeds as a single transaction, eliminating partial failures and manual reruns. ![Introducing Tempo Transactions Neobanks](/images/blog/tempo_transactions_2.png) ### Wallets and neobanks Fee sponsorship removes gas from the user experience entirely. Combined with passkey authentication, users interact with a familiar fintech-grade interface with all of the blockchain complexity abstracted away. ![fee-amm-swap-color-dark](/images/blog/fee-amm-swap-color-dark.png) ### Commerce As stablecoin adoption grows, platforms need flexibility in how fees are paid. Configurable fee tokens allow transaction fees to be paid in any USD stablecoin, while fee sponsorship enables merchants to offer seamless checkout experiences for users. ![Introducing Tempo Transactions Post Subscriptions](/images/blog/tempo_transactions_1.png) ### Subscriptions Scheduled transactions automate recurring payments and enable true subscription services onchain. Tempo Transactions simplify what previously required significant developer effort. Batching and atomic execution are native—no custom smart contracts needed. Fee sponsorship is built in, so users don't need to hold volatile tokens for gas. Passkeys replace seed phrases. And scheduled transactions make recurring payments straightforward to implement. > Tempo Transactions give us the payment primitives our enterprise clients need while keeping integration simple. That means faster time-to-market for use cases like cross-border payments, global payroll, and neobank applications. > > — Alfonso Gómez-Jordana, Co-Founder, Crossmint ## Start building with Tempo Transactions Whether you’re just starting to explore stablecoins or already use them in your payment stack, we can help you get started: ### Learn the fundamentals Visit the Learn section of the Tempo documentation to understand stablecoins, how they work, and the payment use cases they enable. [Learn](/learn) ### Start building If you're familiar with blockchain development, head to our docs to connect to Tempo, access test funds, download SDKs, and start building with Tempo Transactions. [Read the docs](/developers/docs/protocol/tip20/overview) ### Move faster with partners You can also work with our infrastructure partners including Crossmint, Fireblocks, Privy, and Turnkey, who are rolling out Tempo Transactions and can help accelerate your development timeline. Visit the Ecosystem section to explore Tempo's growing network of partners. [Explore ecosystem](/ecosystem) For guidance on choosing the right approach for your use case, [reach out](https://tempo.xyz/contact) to our Enterprise Team. --- ## Tempo x Ithaca > Source: https://tempo.xyz/blog/tempo-x-ithaca/ > Language: en **_The Tempo team is excited to join forces with the Ithaca team. Together, we will [develop](https://www.paradigm.xyz/2025/10/ithaca-x-tempo) the infrastructure Tempo needs to scale and meet real-world demand._** The Ithaca team has created several major crypto projects, from [Foundry](https://www.paradigm.xyz/2021/12/introducing-the-foundry-ethereum-development-toolbox) to [Reth](https://www.paradigm.xyz/2024/06/reth-prod) to [Alloy](https://www.paradigm.xyz/2025/05/introducing-alloy-v1-0) to [Solar](https://www.paradigm.xyz/2024/11/solar) and then [Porto](https://ithaca.xyz/updates/porto-production-ready); these projects will continue to be actively developed and improved as neutral open source building blocks. We are actively hiring world class talent across multiple roles – see our open listings [here](https://jobs.ashbyhq.com/tempo-xyz). --- ## Tempo × Merkle > Source: https://tempo.xyz/blog/tempo-x-merkle/ > Language: en **_The Tempo team is excited to welcome the Merkle team, the creators of Farcaster. Their expertise in protocol design and shipping crypto products will be key as we scale._** Dan and Varun, co-founders of Merkle, have both spent over a decade in crypto: helping build and scale Coinbase early on, then spending the last five years building onchain applications with Farcaster. The rest of the Merkle team will join as well, bringing deep product and engineering experience to the Tempo team. Together, we will build the infrastructure to power the next generation of global payments. We are actively hiring world-class talent across multiple roles – see our open listings [here](https://jobs.ashbyhq.com/tempo-xyz). --- ## Tempo's testnet is live > Source: https://tempo.xyz/blog/testnet/ > Language: en > **Update, August 27, 2026:** [Tempo Mainnet has been live since March 18, 2026](/blog/mainnet). This article documents Tempo's public testnet launch in December 2025. See the [current network connection details](/developers/docs/quickstart/connection-details) to build on mainnet. **_Today, with the launch of our public testnet, anyone can [start building](/developers/) on Tempo._** Tempo is built to deliver instant, deterministic settlement, predictably low fees, and a stablecoin-native experience, which are qualities that most general-purpose blockchains still struggle to provide for financial applications. The testnet brings together the core features that make payments viable onchain. Since [announcing Tempo](https://tempo.xyz/blog/introducing-tempo) in September, we've moved quickly from concept to implementation. What began as a vision for a payments-first blockchain is now a functioning network being tested by many of the world's leading companies. We've been proud to work with a broad initial set of [design partners](https://tempo.xyz/ecosystem) – including Anthropic, Coupang, Deutsche Bank, DoorDash, Lead Bank, Mercury, Nubank, OpenAI, Revolut, Shopify, Standard Chartered, and Visa — and to have their help validating real payment workloads. Since our announcement, we've welcomed Brex, Coastal, Cross River, Deel, Faire, Figure, Gusto, Kalshi, Klarna, Mastercard, Payoneer, Persona, Ramp, UBS as design partners as well. ## What's live on the testnet ### Dedicated payment lanes Payments have guaranteed blockspace reserved at the protocol level. They don't compete with other traffic like NFT mints, liquidations, or high-frequency contract calls. Fees stay low and stable even when other network activity spikes, with a target of one-tenth of a cent per payment transaction. For payment processors, that means no "downtime" from congestion, and predictable economics for high-volume flows. ![Testnet is live - Payment lanes](/images/blog/testnet_is_live_1.png) ### Stablecoin-native gas Transaction fees can be paid directly in USD-denominated stablecoins. This removes the need for volatile gas tokens and lets payment applications operate entirely in the same currency as their underlying flows, ensuring predictable costs and simpler accounting. For wallets and custodians, this removes the need to hold a balance of new cryptoassets just to facilitate stablecoin payments. ![Testnet is live - Stablecoin fees](/images/blog/testnet_is_live_2.png) ### Built-in stable asset DEX Tempo includes a native decentralized exchange optimized for stablecoins and tokenized deposits. This means users can pay fees in any USD stablecoin, and validators can receive fees in any USD stablecoin, with the protocol automatically converting between them using onchain liquidity. It also consolidates onchain liquidity into a single system that simplifies routing and makes it easy for users to trade between stablecoins, or send cross-stablecoin payments. ![fee-amm-swap-color-dark](/images/blog/fee-amm-swap-color-dark.png) ### Payments and transfers metadata Each transfer can include structured memo fields for invoice numbers, cost centers, or other identifiers. This makes it simple to reconcile payments against existing ERP, TMS, and accounting systems without having to write and maintain code to do so. Larger payloads can reference off-chain data via hashed commitments, preserving privacy while keeping onchain records auditable. ![Testnet is live - Metadata](/images/blog/testnet_is_live_3.png) ### Fast, deterministic finality Tempo uses Byzantine fault-tolerant consensus. To start, we operate four validators and will soon have many more, as discussed below. Blocks are finalized every ~0.5 seconds, and transactions in finalized blocks are guaranteed to be included in the chain. This gives payment operators the same settlement certainty they expect from existing financial systems, with speed that matches best-in-class blockchains. Looking ahead, we are exploring even faster confirmation paths to support API-speed payment flows. ![Testnet is live - Deterministic finality](/images/blog/testnet_is_live_4.png) ### Modern wallet signing methods Tempo has built-in support for gas sponsorship, batch transactions, scheduled payments, and modern authentication through passkeys. Developers can deploy payment logic without managing additional middleware or custom contracts. ![Testnet is live - Modern signing methods](/images/blog/testnet_is_live_5.png) ## What can you build with Tempo? Tempo is being used to validate payments workloads across several categories that reflect the core of the global payments economy, including: ### Remittances Tempo's deterministic finality removes settlement uncertainty, and stablecoin gas makes cross-border transfers simple to price and execute 24/7. Partners are testing corridor payments that settle in seconds with full auditability. ![Stablecoins for Corporate Treasury](/images/blog/corporate_treasury_3.png) ### Global payouts Design partners such as payroll platforms and global commerce networks will be using Tempo's dedicated payment lanes to guarantee reliability even during market volatility. The result is a stable, low-cost rail for high-volume disbursements. ![TIP-20 Token Standard](/images/blog/TIP-20_4.png) ### Embedded finance Developers are integrating Tempo's smart accounts and protocol-level memos to embed payment flows inside consumer and enterprise applications, without building new ledger infrastructure. ![Testnet is live - Embedded Finance](/images/blog/testnet_is_live_6.png) ### Microtransactions Tempo's fixed fee model, which targets one-tenth of a cent, makes use cases like usage-based APIs, content streaming, and IoT services commercially viable. ![Testnet is live - Microtransaction](/images/blog/testnet_is_live_7.png) ### Agentic commerce Developers working on agent frameworks are using Tempo's programmable accounts and deterministic settlement to allow agents to transact with immediate finality and predictable fees, without dependency on volatile token markets. ![Testnet is live - Agentic commerce](/images/blog/testnet_is_live_8.png) ### Tokenized deposits Financial institutions are testing Tempo as a base layer for tokenized deposits, leveraging our reconciliation primitives and compliance registry to mirror traditional banking controls while gaining real-time settlement capabilities. ![Testnet is live - Tokenized deposits](/images/blog/testnet_is_live_9.png) A payments-first blockchain is just the foundation to power use cases like these. We're grateful that best-in-class infrastructure providers, with deep experience building stablecoin applications, have chosen to partner with us. Since our announcement, we've [expanded the Tempo ecosystem](https://tempo.xyz/blog/infra-partners) with an additional 40 infrastructure partners who span developer tools, on- and off-ramps, DeFi applications, and more. They each enable critical services to help businesses and users interact with Tempo. ## What's next for Tempo? Today's testnet launch kicks off the next phase of Tempo's development, with a focus on scale, reliability, and integration experience. Over the coming months, we'll continue onboarding new [infrastructure partners](https://tempo.xyz/ecosystem), adding new features and developer tooling, and stress-testing throughput under real payment loads. ## A permissionless future Tempo will be a permissionless, decentralized chain, and we've already shipped the foundation for that in this testnet. The Tempo client is open source under the Apache license, and anyone can run a node or sync the chain. The chain is permissionless and neutral, allowing anyone to deploy contracts, issue tokens, and send transactions. Today's testnet uses a rotating set of four validators operated by our team. As we move toward mainnet, we'll onboard validators from design partners, infrastructure partners, and other independent operators. Over time, we plan to expand to a fully permissionless validator set. Our goal remains the same: to make payments onchain fast, reliable, and composable. Basically, to behave like payments should on the internet. ## Dive deep into Tempo - [Discover use cases for building with Tempo](/learn) - [Start building on Tempo Mainnet](/developers/docs/quickstart/integrate-tempo) - [Contribute to Tempo as an ecosystem partner](mailto:partners@tempo.xyz?subject=Partnership%20with%20Tempo) - [Reach out if you have more questions](https://tempo.xyz/contact) - [Apply now to join Tempo's team](https://jobs.ashbyhq.com/tempo-xyz) --- ## TIP-20: Tempo's Token Standard for Payments > Source: https://tempo.xyz/blog/tip20/ > Language: en **_TIP-20 is Tempo's native token standard, designed for stablecoins and payment use cases. It extends ERC-20 with transfer memos, compliance controls, and reward distribution. Work with our infrastructure partners who are rolling out TIP-20 support, including [AllUnity](https://allunity.com/), [Bridge](https://www.bridge.xyz/), and [LayerZero](https://layerzero.network/), or start building with TIP-20 using [our docs](/developers/docs/protocol/tip20/overview)._** Stablecoins are increasingly being used for real-world payments, settlement, and treasury operations. TIP-20 is Tempo's native standard for fungible tokens, designed from the ground up with these use cases in mind. It builds on ERC-20, the existing standard across Ethereum and EVM-compatible chains, and is fully backward compatible. In a world of many stablecoins, each designed for different use cases, regulatory frameworks, and jurisdictions, the TIP-20 standard ensures tokens behave in a consistent and interoperable way. > TIP‑20 on Tempo turns tokens into true payment instruments. EURAU is ready for TIP‑20 so European corporates can pay and get paid in a fully regulated euro on a real payment chain that delivers European‑quality compliance and privacy with global‑grade speed and FX reach. > > — Peter Grosskopf, CTO, AllUnity ## Building a payments-focused framework for tokens A token standard is a shared set of rules that defines how digital tokens behave. It provides a common framework so tokens can be created, integrated, and used consistently across the ecosystem. ERC-20 is the most widely adopted example. It specifies core functionality like sending, receiving, and checking balances in a predictable format. This enables ERC-20 tokens to be traded on decentralized exchanges and integrated into DeFi protocols without custom integrations. The standard handles coordination upfront. TIP-20 applies this same principle to stablecoins and payment tokens, extending the standard with features specific to real-world payments: transfer memos, compliance controls, and reward distribution. ## TIP-20: a token standard built for payments The TIP-20 standard is a foundational primitive in Tempo. Like [Tempo Transactions](https://tempo.xyz/blog/tempo-transactions), it brings real-world payments use cases onchain: - The TIP-20 standard enables the [issuance of custom stablecoins](/developers/docs/guide/issuance) tailored to specific payment use cases while meeting operational and compliance requirements. - To ensure high throughput and predictable fees, Tempo has [dedicated payment lanes](/developers/docs/protocol/blockspace/payment-lane-specification) : reserved blockspace for payment transactions. Payment transactions using TIP-20 tokens automatically access these lanes for reliable, high-volume payments. - Any USD-denominated TIP-20 stablecoin can be used to [pay transaction fees on Tempo](/developers/docs/protocol/fees/spec-fee-amm). In the future, we plan to support paying fees in non-USD stablecoins. - TIP-20 tokens can be traded on [Tempo's native decentralized exchange](/developers/docs/protocol/exchange), which natively enables stablecoin-to-stablecoin swaps, and, in the future, onchain FX. > TIP-20 allows us to move custom engineering work towards standardized on chain primitives. This allows us to issue custom regulated stablecoins with off-the-shelf templates, enable role based access, use transfer policies, enable onchain reward distribution, specify currencies, and pay gas in custom stablecoins. > > — Aadil Mamujee, Head of Crypto, Bridge ## TIP-20 was designed with stablecoin issuers in mind TIP-20 is designed to meet the operational, compliance, and distribution needs of stablecoin issuers. Beyond basic transfers, it provides built-in features for payment reconciliation, regulatory requirements, and issuer controls at scale. TIP-20 tokens: - **[Native currency identifier](/developers/docs/protocol/tip20/overview#currency-declaration).** Support an optional currency identifier that specifies the real-world asset backing the token, when applicable. - **[Transfer memos](/developers/docs/protocol/tip20/spec#memos).** Enable transfers with payment references and invoice IDs attached to each transaction for easier reconciliation. - **[Reward distribution](/developers/docs/protocol/tip20-rewards/overview).** Offer an opt-in reward distribution system that allows issuers to distribute rewards to token holders or distributors. - **[Custom policy registries](/developers/docs/protocol/tip403/overview).** Enforce compliance and regulatory requirements through custom policy registries, such as blocklists and whitelists. - **[Operational controls](/developers/docs/protocol/tip20/overview#operational-controls).** Provide operational controls, such as pause and unpause functions for emergency halts. - **[Role-based access management](/developers/docs/protocol/tip20/overview#role-based-access-control-rbac).** Implement role-based access management for operational and administrative roles, such as minting and burning privileges. Although designed for stablecoins in mind, TIP-20 is a general-purpose fungible token standard. Assets like bridged BTC or ETH can use the same operational controls and native DEX integration. We've partnered with infrastructure providers including [AllUnity](https://allunity.com/), [Bridge](https://www.bridge.xyz/), and [LayerZero](https://layerzero.network/), who are rolling out TIP-20 to help accelerate your development. > As a day-one infrastructure partner for Tempo, LayerZero is excited to see the network's focus on payments with TIP-20. > > This integration means that any asset issuer can extend their tokens to support TIP-20, ensuring they are ready for Tempo’s payment ecosystem from the start. > > — Simon Baksys, VP, Business Development, LayerZero ## The case for custom stablecoins Stablecoins are moving beyond peer-to-peer payments into treasury management, settlement, and foreign exchange. Custom stablecoins built on TIP-20 can be designed for these specific use cases: ### Corporate treasury management Custom stablecoins can streamline global treasury operations, allowing funds to move instantly between subsidiaries. TIP-20's reward distribution enables reserve income to be shared across business units without complex off-chain accounting. ![TIP20 Token Standard](/images/blog/TIP-20_2.png) ### Cross-border payments Stablecoins allow smaller banks and payment providers to participate in cross-border flows without correspondent banking networks. TIP-20's native transfer memos enable reconciliation between stablecoin transactions and existing payment engines that support SWIFT messaging. ![TIP-20 Token Standard](/images/blog/TIP-20_4.png) ### Wholesale settlement and deposit tokens Policy registries enable permissioned stablecoins and deposit tokens for bank-to-bank settlement. Issuers can enforce transfer rules directly at the token level, supporting regulated and wholesale payment systems. ![TIP-20 Token Standard](/images/blog/TIP-20_3.png) ### Interest-bearing stablecoins TIP-20 simplifies interest-bearing stablecoin issuance with native yield distribution. Issuers can programmatically share yield with users and intermediaries in real time, eliminating manual calculations and off-chain reconciliation. ![TIP-20 Token Standard](/images/blog/TIP-20_6.png) ### Non-USD stablecoins and onchain FX A global stablecoin ecosystem requires currencies beyond USD. TIP-20 tokens include an optional currency identifier specifying the fiat currency they represent. Tempo's native DEX will enable onchain foreign exchange between stablecoins. ![TIP-20 Token Standard](/images/blog/TIP-20_1.png) All of these capabilities are built into TIP-20, so issuers can use a proven implementation rather than building core stablecoin logic themselves. ## Start building with TIP-20 Whether you're exploring stablecoins or already use them in your payment stack, we can help you get started: ### Learn the fundamentals Visit the Learn section of the Tempo documentation to understand stablecoins, how they work, and the payment use cases they enable. [Learn](/learn) ### Start building If you're familiar with blockchain development, head to our docs to connect to Tempo, access test funds, download SDKs, and start building with Tempo Transactions. [Read the docs](/developers/docs/protocol/tip20/overview) ### Move faster with partners You can also work with our infrastructure partners including Crossmint, Fireblocks, Privy, and Turnkey, who are rolling out Tempo Transactions and can help accelerate your development timeline. Visit the Ecosystem section to explore Tempo's growing network of partners. [Explore ecosystem](/ecosystem) For guidance on choosing the right approach for your use case, [reach out](https://tempo.xyz/contact) to our Enterprise Team. --- ## What Are Tokenized Deposits? A Guide for Banks and Institutions > Source: https://tempo.xyz/blog/tokenized-money-for-banks/ > Language: en **_Banks have been issuing tokenized money for the better part of a decade, but those products were primarily tokenized deposits on private networks. Regulation has since cleared a path for tokenized money on public networks, giving financial institutions more options to serve the growing institutional demand. Our new whitepaper works through three product families of tokenized money with the primary use case, the deposit trade-off, and the liquidity ratio impact._** [_Read the whitepaper_](/report/tokenized-money-for-banks). [Download full report](/report/tokenized-money-for-banks) In most cases, tokenized money at banks means private-ledger products that never left the bank's network. JPMorgan, Citibank, HSBC, and others tokenized deposit liabilities on infrastructure they controlled. Each served wholesale payments between vetted institutional clients and stayed inside the perimeter. The customer relationship was preserved, and the regulatory uncertainty was small. Outside the bank perimeter, stablecoins emerged as an alternative form of tokenized money. They moved more than $300 billion in payment volume over the past year. Visa settles over $7 billion in stablecoin card volume annually, across multiple blockchains and stablecoins. Trade.XYZ, an institutional perpetual venue, has cleared $100 billion on the S&P 500 perpetual since March 2026, all settled in stablecoins. The GENIUS Act and Basel SCO60 now give banks a clear rulebook for issuing tokenized money, including stablecoins, on public networks. Banks can serve this emerging demand with tokenized deposits, first-party stablecoins, or third-party stablecoins. Each carries a different trade-off across the deposit franchise, interoperability, and liquidity ratios. Most banks will end up needing more than one. ## Three families of tokenized money A bank has three structural options for serving tokenized money flows. Each carries a different balance-sheet cost and reaches a different range of venues. - **Tokenized deposits.** A tokenized deposit is a regular bank deposit wrapped in a token. The customer holds the token in a wallet, but the money stays on the bank's books, so the deposit franchise stays intact. The trade-off is reach, since the token only moves between counterparties the bank has approved. JPMD on Base is the live example. It pays interest because it is still a deposit underneath the wrapper. - **First-party stablecoins.** A first-party stablecoin is one the bank issues itself, backed dollar-for-dollar by a segregated pool of reserves. The customer's claim is no longer a deposit at the bank but a redemption contract against that pool. That shifts the liability from the cheapest Basel category to the most expensive. In return, the bank gets a 24/7 settlement currency it controls. The structure can sit on the bank's own balance sheet, inside a separately licensed subsidiary, or inside a consortium with peer banks. - **Third-party stablecoins.** A third-party stablecoin is one the bank does not issue. The bank helps the customer to onramp to a stablecoin from another issuer, and the customer's money leaves the bank's balance sheet to fund the purchase. The upside is reach. The customer can settle on the widest range of venues, including the public crypto derivatives markets where most institutional weekend flow now clears. ## Why banks will need all three None of the three families is a strictly better answer than the others. A retail-deposit-heavy bank has a different answer from a transaction bank serving hedge funds and corporate treasuries. The bank with clients on its own permissioned networks faces a different question than the bank with clients trading on Hyperliquid. Tokenized deposits defend the existing deposit franchise, but reach a narrow venue set. First-party stablecoins build an internal rail, but change the bank's liability profile under Basel requirements. Third-party stablecoins access the widest liquidity pool, but externalize the customer claim. Each choice carries a specific cost and capacity release across LCR, NSFR, and risk-weighted assets. Even within a single bank, institutional clients use different forms of settlement for different purposes. A hedge fund may post initial margin on the bank's tokenized-deposit network, hedge weekend exposure with a third-party stablecoin, and rebalance through a consortium-issued first-party stablecoin. A bank that issues only one of these cannot fully serve that client. The three families will coexist. Banks need to incorporate all three into their strategy, not pick one and ignore the rest. Our whitepaper, "Tokenized Money for Banks", covers each product with its LCR and NSFR impact, deposit franchise trade-off, and the conditions under which it fits. [Read the whitepaper](/report/tokenized-money-for-banks). --- ## Virtual addresses for stablecoin deposits > Source: https://tempo.xyz/blog/virtual-addresses/ > Language: en **_[Virtual addresses](/developers/docs/guide/payments/virtual-addresses) on Tempo give exchanges, ramps, neobanks and financial institutions unique deposit addresses for every customer without the overhead of sweep transactions. Funds sent to a virtual address are credited directly to a registered master wallet at the protocol layer. Contact us if you are evaluating how to streamline stablecoin deposit flows._** Every payments company runs into the same deposit problem: offering customers unique recipient addresses makes reconciliation easier, but managing these addresses at scale is expensive. If you issue a unique address to each customer, merchant, or invoice, you also inherit the work of sweeping funds, monitoring balances across thousands of endpoints, and managing a much larger wallet surface area. For enterprise teams, that overhead shows up in more complex ledger logic, more treasury operations, more transactions to pay for, and more chances for funds to get stuck between "received" and "available." ## Why deposit addresses get expensive Consider a neobank that provides each user with a unique address to fund their account. On most chains, a deposit address is a real account. At scale, that creates several problems. First, funds land in the deposit address itself. On some chains, you need to pay a certain amount ("state rent") to initialize an account to receive funds, which can be cost-prohibitive at scale. If your treasury wallet needs consolidated funds, you have to sweep those balances out with separate transactions. That adds latency, gas costs, and failure modes. This also adds infrastructure overhead for the network and for the applications that need to monitor and reconcile those accounts. Support, finance, operations, security and compliance teams all need to understand where funds landed, when they moved, and whether that movement was expected. ## Introducing virtual addresses [Virtual addresses](/developers/docs/guide/payments/virtual-addresses) are now live on Tempo. A virtual address looks like a normal address to the sender, but it is not a standalone wallet that needs to hold or sweep funds. A business registers a master wallet once. After that, it can derive trillions of customer-specific virtual addresses offline. When a sender transfers a [TIP-20](/blog/tip20) stablecoin to one of those addresses, Tempo detects the [virtual address format](/developers/docs/protocol/tip20/virtual-addresses), resolves it to the registered master wallet, and credits the master directly. ![Virtual addresses on Tempo](/blog/virtual-addresses-on-tempo.png) As a result, the sender still has a unique address to send to, while the operator receives funds in one real wallet without a sweep step in between. Virtual addresses are especially useful for businesses that receive stablecoin payments at scale: - Exchanges and brokers issuing dedicated deposit addresses - Onramps and offramps attributing inbound customer funds - Marketplaces that need one address per merchant or invoice - Treasury platforms that want segmented inbound payments In each case, the business need is the same: accurately attribute the payment to the intended recipient, while holding the funds at rest in a single address. ## Why virtual addresses matter for enterprise teams Virtual addresses are not an application-layer forwarding workaround. They are built into how Tempo handles [TIP-20](/blog/tip20) transfers, and offer a native solution to the reconciliation challenge without the complexity that typically comes with creating separate onchain accounts for each customer: - **Straightforward customer attribution.** Each virtual address can still represent a specific customer, merchant, corridor, or payment flow. You keep the reconciliation benefits of unique deposit endpoints without turning every endpoint into another wallet your team has to manage. - **No sweep operations.** Funds arrive where your business actually wants to manage them. There is no second transaction to move assets out of a deposit address and into a treasury wallet. That reduces latency, lowers transaction overhead, and removes an entire operational workflow. - **Lower infrastructure overhead.** Virtual addresses do not create separate onchain accounts for each recipient. That means no new-account cost for every deposit endpoint you issue. Sponsor banks let fintechs issue virtual accounts to their users. Virtual addresses serve as the onchain analogue of those accounts. Combined with [subscriptions](/blog/subscriptions-on-tempo) and [MPP Sessions](/blog/mpp-sessions), they give platforms a complete deposit-and-billing stack on stablecoins. ## Work with Tempo If you're building deposit flows, merchant settlement, exchange funding, or payout infrastructure, virtual addresses can remove a meaningful amount of operational overhead from your stack. Tempo's enterprise team can help evaluate whether virtual addresses fit your payment flows, map them into your ledger and reconciliation systems, and support a pilot with the right partners. Virtual addresses are part of a broader set of new enterprise features live on Tempo today. For the full picture, see [new features on Tempo for enterprise payments](/blog/new-features-for-enterprise-payments). Read the [documentation](/developers/docs/guide/payments/virtual-addresses) or [contact our enterprise team](https://tempo.xyz/contact/) to explore virtual addresses on Tempo. --- ## Wirex is now live on Tempo for enterprise stablecoin card programs > Source: https://tempo.xyz/blog/wirex-is-now-live-on-tempo/ > Language: en **_Wirex enables its partners to use Tempo as a key settlement layer for enterprise stablecoin card programs._** Wirex, the global stablecoin infrastructure provider and a principal member of Visa and Mastercard, has added Tempo to its platform. The live integration enables Wirex partners to select Tempo as a preferred settlement layer for enterprise stablecoin card programs. ## Stablecoin card infrastructure built for scale Wirex gives fintechs and digital platforms a single integration for regulated card issuance, wallets, compliance, and stablecoin settlement. Wirex issues cards under its own licences as a principal member of Visa and Mastercard. Its infrastructure reached $1 billion in annualized onchain volume just 131 days after launch, and [doubled that volume 110 days later,](https://www.wirexapp.com/post/wirex-baas-doubles-annualised-volume-to-2b-in-110-days-as-stablecoin-based-financial-services-accel) making it one of the fastest-scaling stablecoin card platforms in the industry. > “It’s great to offer Tempo as a key settlement layer for enterprise stablecoin card programs integrating with Wirex’s infrastructure. As a purpose-built blockchain for stablecoin payments at scale, Tempo gives our partners fast, predictable and private settlement, while Tempo’s advisory and engineering teams help them move from integration to production faster.” > > — Daniel Rowlands, General Manager, Wirex ## Why Wirex chose Tempo Wirex selected Tempo because it offers more than a settlement network, bringing extensive payments expertise thanks to their incubation by Stripe. Together, Wirex and Tempo can give enterprises a supported path from product design to a live stablecoin card program using Tempo’s [Stablecoin Advisory](/contact/). Wirex provides the regulated card stack. Tempo’s Stablecoin Advisory and forward-deployed engineers work directly with customers to: - Design the card and settlement flow - Select and integrate the right infrastructure partners - Move from architecture to prototype and production This approach is informed by Tempo’s work with enterprises including DoorDash, Deel, Klarna, Felix, and ARQ. > “Wirex gives companies building on Tempo a straightforward way to launch stablecoin-backed card programs. Customers can combine Wirex’s regulated card infrastructure with Tempo’s settlement network and hands-on support to seamlessly bring new products to market.” > > — Ani Narayan, GTM, Tempo Customers also benefit from a network built specifically for stablecoin payments. Tempo provides Wirex partners with the following features: - **Fast, predictable settlement.** Transactions finalize in under a second, with dedicated payment capacity and predictable sub-cent fees. - **Private payments.** Tempo Zones keep balances and transactions private while supporting selective disclosure for audit and compliance. - **Stablecoin-native operations.** Network fees are paid in stablecoins, eliminating the need to hold a separate gas token. - **Simpler reconciliation.** Structured transaction data keeps funds and settlement information on the same rail. Together, Wirex’s regulated infrastructure and Tempo’s network and implementation support help enterprises bring stablecoin-backed card programs to market faster. ## What’s next Wirex and Tempo are working together to bring more fintech and enterprise card programs onto the network. If you are evaluating stablecoin-backed cards, [get in touch](/contact/). --- ## zerohash joins Tempo as a validator and infrastructure partner > Source: https://tempo.xyz/blog/zerohash-joins-tempo-as-a-validator-and-infrastructure-partner/ > Language: en **_zerohash is joining Tempo’s validator set and partnering to give enterprises a practical path to build stablecoin payment flows on Tempo through infrastructure designed for compliance, custody, liquidity, and settlement. [Contact Tempo](/contact) to discuss enterprise payment use cases._** Stablecoin payments are moving from pilots to production. That shift changes what institutions need from the underlying infrastructure. Speed and low fees matter, but so do predictable settlement, custody, liquidity, policy controls, fiat connectivity, and integrations that fit existing financial workflows. zerohash is joining Tempo as a validator and infrastructure partner to bring those pieces closer together for companies launching stablecoin programs inside their own products. zerohash brings an infrastructure layer already used by banks, fintechs, brokerages, payment companies, and platforms that are bringing stablecoin products to market. > "Tempo's validator set is designed to reflect the businesses that move money, and zerohash operates the infrastructure behind hundreds of banks, fintechs, and payment platforms," said Dan Romero, Chief Business Officer at Tempo. "Having zerohash on board as a validator to help secure the network, in addition to connecting with it, strengthens Tempo for every business using it to move money with stablecoins." ## What zerohash does [zerohash](https://zerohash.com/) provides the infrastructure companies use to launch crypto, stablecoin, and tokenized asset capabilities inside their own products. Its APIs and embeddable tools help partners add money movement, trading, tokenization, and fiat access without building the underlying stack themselves. Behind those experiences, zerohash helps partners manage the operational pieces institutions need: access to supported assets and blockchain networks, custody, liquidity, compliance and transaction monitoring workflows, settlement, and fiat conversion. That lets companies build stablecoin products without managing every part of the stablecoin stack themselves. By integrating Tempo, zerohash can give its partners access to a payment-focused network built for stablecoin settlement. ## Validators should reflect payment infrastructure Tempo’s institutional validator set includes companies such as Stripe, Visa, and Zodia Custody by Standard Chartered. It is designed to bring production payment experience closer to the network layer. Validators help secure Tempo, and they also reflect the institutions and infrastructure providers stablecoin payments need in order to scale responsibly. > “Tempo represents exactly the kind of ecosystem our partners need to move stablecoins at scale. It’s fast, predictable, and built for onchain velocity,” said **Mark Daly**, Chief Business Officer at zerohash. “Integrating Tempo, and further, having a role as a validator, puts zerohash even closer to the core of how this network operates, letting us bring that reliability directly to world-class institutions and platforms we serve.” As a validator and integration partner, zerohash will sit closer to the network layer while giving its partners a practical way to access Tempo through existing infrastructure. ## Why this partnership matters for customers Together, Tempo and zerohash can reduce the distance between wanting to use stablecoins and being able to ship stablecoin products to customers. Banks, fintechs, brokerages, payroll platforms, payment companies, and marketplaces can access Tempo through infrastructure designed to fit regulated financial workflows. For customers, that means faster access to Tempo, less need to build and maintain direct integrations across every network and asset, and a clearer path to launch stablecoin use cases such as cross-border payouts, payroll, merchant settlement, account funding, and trading. ## What comes next Tempo and zerohash will work together to make Tempo available to zerohash partners building stablecoin-powered products across payments, commerce, payroll, remittances, trading, tokenization, and on- and off-ramps. The partnership reflects a simple view of where stablecoin payments are going: institutions need purpose-built settlement infrastructure, and they need partners that can make that infrastructure usable in production. Learn more about [Tempo](/) and [zerohash](https://zerohash.com/), or [contact Tempo](/contact) to discuss stablecoin payment use cases. --- ## Contact Tempo > Source: https://tempo.xyz/contact/ > Language: en # Get in touch Tell us a bit about yourself and what you're building. We'll help you explore how Tempo can accelerate your payments infrastructure. For technical questions or support, please reach out to [support@tempo.xyz](mailto:support@tempo.xyz). For press inquiries, please reach out to [press@tempo.xyz](mailto:press@tempo.xyz). > Interactive contact form is available on the HTML page. --- ## Customer Stories > Source: https://tempo.xyz/customer-stories/ > Language: en ## [Altitude brings its financial operating system onto Tempo](/customer-stories/altitude/) Altitude customers can now send and receive USDC on Tempo directly through Altitude's stablecoin-native financial operating system. ## [ARQ is scaling cross-border payments on Tempo across Latin America](/customer-stories/arq/) ARQ, a financial services platform serving over 2 million customers across Latin America, is building its cross-border payment infrastructure on Tempo for faster settlement, lower costs, and a foundation for its expanding product suite. ## [Coastal is turning cross-border settlement from days into minutes](/customer-stories/coastal/) Coastal is building stablecoin-settled payment infrastructure on Tempo for its fintech clients, pairing existing institutional messaging with onchain settlement to move money faster, at lower cost, with fewer intermediaries. ## [How Deel built its private stablecoin wallet for global contractors on Tempo](/customer-stories/deel/) Deel’s private stablecoin wallet lets contractors in 80+ countries hold dollar-backed balances, earn rewards, and spend globally. Built on Tempo and embedded in the platform 40,000+ businesses use to pay global workers, it keeps balances and payout history private. ## [DoorDash is bringing stablecoin-powered payments to 40+ countries](/customer-stories/doordash/) DoorDash is building stablecoin-powered payment infrastructure on Tempo for its three-sided global marketplace, bringing faster and more cost-effective payouts to merchants and Dashers across 40+ countries. ## [Felix: instant remittances for one million families, settled on Tempo](/customer-stories/felix-pago/) Felix Pago built a remittance product that lives entirely inside WhatsApp, processing over $5 billion for more than one million users across nine Latin American corridors. Felix is adding Tempo to its settlement infrastructure for predictable costs, dedicated payment capacity, and sub-second finality at scale. ## [Howard Hughes Holdings pilots onchain financial verification with Tempo](/customer-stories/howard-hughes/) Howard Hughes Holdings is piloting Tempo for reconciliation, audit, and cash management across its portfolio, with a path toward stablecoin settlement. ## [Karta is building its self-custody money app on Tempo](/customer-stories/karta/) Karta, a self-custody money app with more than 25,000 monthly cardholders and 1,250+ business teams across 150+ countries, is building on Tempo. Karta's treasury is live on Tempo today, and Karta Personal launches on Tempo soon. ## [KAST is bringing its stablecoin earn product onto Tempo and joining as design partner](/customer-stories/kast/) KAST is a global financial platform built on stablecoin rails. Users can hold, move, and spend stablecoin balances through a card accepted at 150 million merchants in 170+ countries. ## [MoneyGram is joining Tempo as its first remittance validator and settlement partner](/customer-stories/moneygram/) MoneyGram, one of the world's largest global payments networks, is joining Tempo as its first remittance validator and advancing stablecoin-based settlement across its network spanning 200+ countries and territories. ## [OnePay and Tempo partner to help shape next generation of stablecoin-powered payments](/customer-stories/onepay/) OnePay, the consumer fintech trusted by millions of Americans, is partnering with Tempo on stablecoin payouts and instant account funding for its banking product. ## [RedotPay integrates MPP to bring agentic payments to its 7.5 million users](/customer-stories/redotpay/) RedotPay is integrating the Machine Payments Protocol (MPP) to enable AI agents to transact on behalf of its 7.5 million users across 130 million merchants worldwide, with settlement on Tempo. ## [Stripe Treasury: stablecoin capabilities on Tempo](/customer-stories/stripe/) Tempo powers the stablecoin capabilities in Stripe Treasury today, letting businesses access dollar-backed stablecoins, move money across borders, and manage funds from the Stripe Dashboard in 100+ countries. As Stripe expands Treasury's stablecoin footprint, Tempo is the settlement layer making those transfers fast, final, and predictable. --- ## Altitude brings its financial operating system onto Tempo > Source: https://tempo.xyz/customer-stories/altitude/ > Language: en # Altitude brings its financial operating system onto Tempo Altitude customers can now send and receive USDC on Tempo directly through Altitude's stablecoin-native financial operating system. ## At a glance - **150+** — Countries - **USDC** — Send and receive on Tempo - **Live** — Inside Altitude ## Altitude is now live on Tempo [Altitude](https://altitude.xyz) is now live on Tempo. Businesses running on Altitude, the financial operating system built around stablecoins, can now send and receive stablecoin payments on Tempo alongside the rest of their accounts, cards, payments, and finance operations. Altitude is the financial operating system for businesses running on stablecoins. The platform consolidates multi-currency accounts, business cards, payments, FX, and finance operations on a stablecoin-native architecture, available to companies across 150+ countries. Where most business accounts are software layered on top of banks, Altitude is built around programmable accounts that businesses control directly, with stablecoins at the core of the stack. With this release, Tempo is supported directly inside Altitude as a network for sending and receiving USDC. ## What's now live Altitude customers can send and receive stablecoin payments on Tempo directly through the Altitude platform, with the approval flows, role-based controls, and reporting their finance teams already rely on. Bringing Tempo into the workflow means no separate wallet to set up, no new integration to maintain, and no extra reconciliation work for the operations team. ## Why Tempo Tempo is a blockchain built for payments, incubated by Stripe and Paradigm. Two capabilities matter most for the kinds of stablecoin flows Altitude's customers run: - Bounded fees paid in stablecoins — T7 lets Tempo's base fee move with network usage inside a defined cap and floor. Businesses keep network costs dollar-denominated without managing a separate gas token. - Sub-second finality — Tempo finalizes in under a second with deterministic settlement. For operations teams reconciling against existing finance systems, that matches the certainty they get from traditional rails. ## What's next We're excited for Altitude to bring stablecoin payments on Tempo to its financial operating system, with more to come in the coming months. ## Learn more - [Explore embedded finance](/solutions/embedded-finance) - [Learn about stablecoins](/learn/what-are-stablecoins) - [Browse the ecosystem](/ecosystem) --- ## ARQ is scaling cross-border payments on Tempo across Latin America > Source: https://tempo.xyz/customer-stories/arq/ > Language: en # ARQ is scaling cross-border payments on Tempo across Latin America ARQ, a financial services platform serving over 2 million customers across Latin America, is building its cross-border payment infrastructure on Tempo for faster settlement, lower costs, and a foundation for its expanding product suite. ## At a glance - **2M+** — Customers - **$10B** — Annualized volume - **4** — Countries ## Scaling cross-border payments across four countries ARQ is a financial services platform serving over 2 million customers across Mexico, Colombia, Argentina, and Brazil. From a single app, users hold and move digital dollars and euros, invest in international markets, and spend worldwide. The platform processes more than $10 billion in annualized transaction volume, all built on stablecoin infrastructure that users never have to think about. Stablecoins have powered ARQ's cross-border payment engine from the start, letting users move money between countries in seconds rather than days. But as the platform expands beyond payments into investing, credit, and everyday spending, the demands on the settlement layer grow. Each new product vertical adds complexity. Transaction volume compounds. And the cost, speed, and reliability of the infrastructure underneath directly affects what ARQ can offer its customers and at what margin. At $10 billion in annualized volume and growing, the settlement layer is not a background concern. It is a strategic decision that shapes product speed, unit economics, and the ability to expand into new markets and use cases. ## What ARQ is building on Tempo ARQ is moving its cross-border payment infrastructure onto Tempo, bringing the settlement layer for its core products onto a chain purpose-built for high-volume stablecoin payments. For ARQ, this means a bounded dynamic base fee paid in stablecoins rather than a separate gas token. Under T7, the fee cap is below Tempo's previous fixed fee and can fall further as network usage drops. It also means sub-second deterministic finality and built-in tooling for compliance, reconciliation, and payment operations that would otherwise require custom engineering at ARQ's scale. The shift is invisible to ARQ's customers. They still hold digital dollars, move euros, and spend worldwide from the same app. What changes is the infrastructure underneath: faster, cheaper, and designed for the kind of high-throughput stablecoin settlement that ARQ's growth demands. ## Why ARQ chose Tempo When ARQ evaluated infrastructure partners, the decision came down to a specific set of requirements: low, predictable transaction costs without managing gas token balances; instant settlement finality; built-in compliance and reconciliation tooling; a payments-focused ecosystem; and a clear product roadmap toward capabilities ARQ needs as it scales, including on-chain FX and privacy. Tempo's architecture matched that profile. Gas abstraction lets ARQ pay fees in any USD-denominated stablecoin, so the entire operation stays denominated in dollars with no volatile token to manage. Protocol-level compliance controls, including allowlists, blocklists, and freeze-and-pause capabilities, are built directly into the chain. Native memo fields compatible with ISO 20022 make reconciliation against existing systems straightforward. And dedicated payment lanes guarantee that ARQ's transaction throughput is never affected by other network activity. Beyond the infrastructure, alignment mattered. > From day one, Tempo understood what we were building, moved with urgency, and offered the infrastructure, product vision, and long-term alignment we needed to scale ARQ. > > — **Zach Garman**, Co-founder and CPO, ARQ What started as a dollar-access product for Latin American consumers is becoming a full financial services platform for cross-border commerce and personal finance across the Americas. The infrastructure underneath needs to match that ambition. ## What's ahead Tempo gives ARQ a foundation that scales with the product roadmap. In the near term, it means faster settlement, lower costs, and a more seamless experience for the 2 million customers who already use ARQ daily. Over time, building on Tempo opens a path to capabilities that matter as the platform grows: native on-chain FX between stablecoins, direct merchant settlement, programmable payment flows, and privacy features for enterprise use cases. For ARQ's customers across the Americas, the result is a financial platform where the infrastructure underneath keeps pace with the product on top. If you're a fintech or financial services company exploring stablecoin settlement infrastructure, get in touch. ## Learn more - [Explore cross border payments](/solutions/cross-border-payments) - [Learn about stablecoins](/learn/what-are-stablecoins/) - [Browse the ecosystem](https://tempo.xyz/ecosystem) --- ## Coastal is turning cross-border settlement from days into minutes > Source: https://tempo.xyz/customer-stories/coastal/ > Language: en # Coastal is turning cross-border settlement from days into minutes Coastal is building stablecoin-settled payment infrastructure on Tempo for its fintech clients, pairing existing institutional messaging with onchain settlement to move money faster, at lower cost, with fewer intermediaries. ## At a glance - **$4.7B** — Total assets - **Minutes** — Settlement time vs. days - **24/7** — Always-on settlement ## The problem with cross-border payments Cross-border payments still move through chains of correspondent banks, each adding cost, latency, and operational overhead. A transfer between two banks in different countries can take days to settle, requires pre-funded correspondent accounts, and operates only during banking hours. Banks and their clients absorb the difference. For Coastal Financial Corporation, a regulated sponsor bank that powers financial products for fintech companies nationwide through its [CCBX](https://ccbx.com/) division, those limitations directly affect the partners it serves. Coastal's fintech clients need faster, cheaper ways to move money across borders. Traditional correspondent banking infrastructure was not built to deliver that. ## What Coastal is building Coastal and Tempo are building a cross-border payment corridor that keeps existing compliance infrastructure in place while replacing the settlement layer underneath with stablecoins on Tempo. Here's how it works: a customer at a partner bank abroad initiates a payment. The sending bank runs its standard KYC/AML screening and sends a payment instruction to Coastal with the transaction details. The sending bank then funds a wallet on Tempo via a stablecoin issuer, converting local currency to USD stablecoins. Those stablecoins transfer to Coastal's wallet on Tempo. Coastal redeems the stablecoins, confirms the payment back to the sending bank, and credits the recipient's account in USD. The entire settlement happens in minutes. The compliance infrastructure, including messaging, KYC/AML screening, and bank-to-bank confirmations, stays exactly where it is. What changes is the settlement layer. Instead of routing through multiple correspondent banks over several days, the value moves on Tempo, near-instantly, at a fraction of the cost. This is a controlled implementation by design. Both sides of the transaction are known, regulated financial institutions with an existing relationship. Wallets are whitelisted. The flow is permissioned end-to-end. It's the kind of use case that lets a bank move into stablecoin settlement without rebuilding its compliance stack. ## Why Coastal chose Tempo Ryan Hall, Chief Product Officer at Coastal, joined the bank after building and scaling the SoFi Money product. He came to Coastal specifically to help transform it into a next-generation sponsor bank. When Coastal evaluated stablecoin infrastructure partners, what stood out about Tempo was focus. > What was particularly interesting about Tempo was that they were focused on a payments-first use case and on enabling the next generation of money movement. Faster, more efficient, and more secure payments. > > — **Ryan Hall**, Chief Product Officer, Coastal Bank That focus translated into features that matter for institutional cross-border settlement. Tempo Zones give banks the equivalent of a private cloud on a shared network: only the zone operator and transaction counterparties see the details, with selective disclosure to regulators, while institutions retain full access to shared liquidity across the broader network and the ability to meet their compliance obligations. Gas abstraction lets institutions pay fees in any USD-denominated stablecoin, avoiding uncertain capital treatment on volatile crypto holdings. Protocol-level compliance controls, including allowlists, blocklists, and freeze-and-pause capabilities, are built directly into the chain. And native memo fields support structured payment data compatible with ISO 20022, the messaging standard used across global institutional payments. For Coastal, the alignment went beyond features. Hall described the Tempo team as builders with the same urgency to get real use cases into production. > The immediate focus was, which use cases can we bring to market right away? How do we think about where the need is, where the opportunity is, where the greatest friction is, and how can we solve those problems right now, today, in a real-world use case? > > — **Ryan Hall**, Chief Product Officer, Coastal Bank ## Bridging legacy and next-generation rails Coastal's approach is not to replace legacy banking infrastructure overnight. The bank is building a system that runs stablecoin and traditional rails in parallel, giving fintech partners access to both through a single integration. > We are building the next generation of infrastructure on digital currency and stablecoin while also supporting legacy rails. The goal is to abstract those two systems into a unified experience, while giving our partners access to the next generation of innovation. > > — **Ryan Hall**, Chief Product Officer, Coastal Bank Full distribution in the United States still requires legacy rails. Every endpoint, every bank account, every existing payment flow still runs on traditional infrastructure. But for specific corridors where speed, cost, and settlement time are the priority, stablecoin rails on Tempo offer a step change. For Coastal's fintech partners, that means access to stablecoin-powered cross-border settlement without abandoning the infrastructure they still depend on. ## What's ahead > Our partners are continually raising the bar for what modern financial services should look like: faster, more flexible, and always available. By integrating stablecoin capabilities and Tempo's blockchain-based infrastructure into our platform, we're enabling our partners to build more seamless, efficient experiences for their customers while staying grounded in the trust and reliability of the banking system. > > — **Brian Hamilton**, President of CCBX, Coastal Bank Cross-border payments are the starting point. The infrastructure Coastal is building on Tempo, combining institutional messaging, compliance-native controls, and stablecoin settlement, is a foundation for any payment corridor that needs to move faster and cost less. ## Learn more - [Explore institutional money movement](/solutions/institutional-money-movement) - [Learn about stablecoins](/learn/what-are-stablecoins/) - [Browse the ecosystem](https://tempo.xyz/ecosystem) --- ## How Deel built its private stablecoin wallet for global contractors on Tempo > Source: https://tempo.xyz/customer-stories/deel/ > Language: en # How Deel built its private stablecoin wallet for global contractors on Tempo Deel’s private stablecoin wallet lets contractors in 80+ countries hold dollar-backed balances, earn rewards, and spend globally. Built on Tempo and embedded in the platform 40,000+ businesses use to pay global workers, it keeps balances and payout history private. ## At a glance - **40,000+** — Businesses - **150+** — Countries - **84.6%** — Argentine contractors choosing USD ## Deel Earn results - **74%** — payout recipients deposited into Earn - **85%** — 30-day Earn retention - **60%** — Eligible users actively earning - **+72%** — Earn balance growth after 30 days _Compares each cohort’s combined Earn balance after 30 days with its starting balance. Includes rewards earned, but growth is largely driven by net deposits._ ## The challenge Deel powers payroll for more than 40,000 businesses across 150 countries. For contractors in markets with volatile local currencies, getting paid in dollars has not always meant being able to hold them. In 2025, 84.6% of Argentine contractors on Deel chose USD over pesos. Deel wanted contractors to hold dollar balances, earn rewards, and spend globally without leaving the platform. The wallet needed to be self-custodial and embedded in Deel, with their financial records kept private. Deel [launched its stablecoin wallet on Tempo in June 2026](https://stripe.com/newsroom/news/deel-and-stripe), starting in Argentina. By August, it had [expanded to eligible contractors in 80+ countries](https://www.deel.com/blog/introducing-stablecoin-wallet/). Zones add privacy to that existing wallet and payment infrastructure. ## Private contractor payouts with Tempo Zones Deel uses Tempo Zones in production to keep contractor balances and payout history private. Tempo and Privy worked together to bring Deel’s Zone into production, integrating Zones natively with Privy’s APIs. Deel’s treasury deposit into its Zone is visible on Tempo, but which contractors are paid, how much each receives, and what they hold are not. Contractors see their own balances in Deel, while Deel retains access for reconciliation and audit. [Watch video](/videos/privacy/privacy-on-tempo-20261015.mp4) ## Why Tempo **Privacy zones:** contractor wallet balances and payout history stay private. **Private earn:** balances keep earning yield inside the zone without giving up user privacy. **Same tech stack:** existing customer wallets and Deel treasury rails remained unchanged. ## What Deel built Bridge issues Deel’s dollar-backed stablecoin on Tempo, while Privy provides the embedded wallets. Wallets are created for contractors who have completed identity verification on Deel. Workers can sign in with device biometrics, with no seed phrase or separate app. Deel sponsors payment fees, so workers never need a separate gas asset. Contractors can put idle balances into the Morpho-powered earn product with a single tap, without a lock-up or minimum holding period. Access is limited to verified Deel contractors. They can withdraw all or part of their balance, including accrued rewards, at any time. Workers can move funds back to their Deel balance to use existing withdrawal options, or transfer them to an external wallet. The Deel Card connects the wallet to everyday spending. > Millions of contractors around the world watch their earnings lose value the moment they land. Today we give them the infrastructure to change that: a dollar-backed balance inside the platform they already use, rewards that accrue automatically, and a card to spend anywhere. No new account or learning curve required. > > — **Thierry Edde**, Head of Crypto, Deel ## Now live in 80+ countries The wallet is now live for eligible contractors in 80+ countries across LATAM, Africa, the Middle East, and APAC. --- ## DoorDash is bringing stablecoin-powered payments to 40+ countries > Source: https://tempo.xyz/customer-stories/doordash/ > Language: en # DoorDash is bringing stablecoin-powered payments to 40+ countries DoorDash is building stablecoin-powered payment infrastructure on Tempo for its three-sided global marketplace, bringing faster and more cost-effective payouts to merchants and Dashers across 40+ countries. ## At a glance - **40+** — Countries - **3-sided** — Marketplace payments - **USD** — Network fee denomination > There's real promise with stablecoins transforming financial infrastructure, not just in America, but globally. We want to be a proactive participant and not just passive. > > — **Andy Fang**, Co-founder, DoorDash ## The problem with global marketplace payments Most companies process payments between two parties. DoorDash enables transactions across three: a consumer pays for an order, a merchant receives revenue, and a Dasher earns income for fulfilling the delivery. Each party has different payout timing, currency, and compliance requirements, and each needs to be served well for the marketplace to work. Now multiply that across more than 40 countries. Each market has different payment rails, FX dynamics, settlement timelines, and regulatory requirements. A payout flow that works in Atlanta does not apply in Helsinki. The logistics of getting a Dasher paid in one country look nothing like the logistics in another. For Dashers, whose delivery income is a flexible earnings stream, waiting days for a payout is a real friction point. For merchants, a significant share of revenue flows through DoorDash, and getting that money faster and more affordably is something they ask for explicitly. And marketplace transactions are not simple one-way payments: consumers modify orders after checkout, and refunds need to process quickly. > Global payments is complex in terms of what the requirements are for any different country. Figuring out a way to provide solutions to the end customer that feel frictionless, while integrating with rails that are dynamic enough to handle the different requirements of different countries, is at the heart of the complexity. > > — **Andy Fang**, Co-founder, DoorDash ## What DoorDash is building DoorDash and Tempo are building stablecoin-powered payment infrastructure for DoorDash's global marketplace, starting with the flows where faster, more affordable settlement creates the most value for merchants and Dashers. The focus is on three areas where stablecoins deliver immediate improvements over traditional rails. > If we can get merchants and Dashers their money faster, and do that in a way that's affordable for them, that's a no-brainer for the entire ecosystem. > > — **Andy Fang**, Co-founder, DoorDash - Payout speed — Merchants and Dashers consistently ask for faster access to their earnings. Traditional payout cycles involve intermediaries and settlement windows that vary by country. Stablecoins on Tempo settle in under a second, globally, around the clock. - Cross-border cost — Moving money across 40+ countries means FX spreads, intermediary bank fees, and processing charges that compound across millions of transactions. Stablecoin rails reduce the number of intermediaries and the cost of moving money across borders. - Transaction flexibility — Marketplace transactions require handling order modifications, refunds, multi-party splits, and dispute resolution. Programmable stablecoin payments on Tempo provide the flexibility to handle these flows with less friction and fewer manual steps than traditional rails. ## Why DoorDash chose Tempo DoorDash was founded in 2013 with a mission to empower local economies. That mission now operates across more than 40 countries through its marketplace and acquisitions like Wolt and Deliveroo. When DoorDash evaluated stablecoin infrastructure partners, what stood out about Tempo was its combination of payments focus and enterprise readiness. > Tempo has a world-class team in the crypto space. They have experience not only with crypto from a technology standpoint, but also from an enterprise readiness standpoint, thinking about what would make this technology work realistically for an enterprise like DoorDash. > > — **Andy Fang**, Co-founder, DoorDash That focus translated into features that matter for global marketplace payouts at scale. Sub-second finality means payouts to merchants and Dashers settle in under a second with deterministic confirmation, giving both parties the speed they have been asking for. Low transaction fees make cost predictable for a platform processing millions of payouts. Dedicated payment lanes guarantee that payout throughput is never affected by other network activity, critical for a marketplace with peak-hour volume spikes. And ISO 20022-compatible memo fields support the structured reconciliation workflows that a global treasury operation requires across dozens of markets and currencies. For DoorDash, the alignment went beyond features. The partnership is structured as a two-way collaboration where both sides bring domain expertise the other needs. > We can teach them about the dynamics of payments in a marketplace setting, and we can learn from them about the emergence of stablecoin technologies and how that can be applied in an enterprise-ready setting. > > — **Andy Fang**, Co-founder, DoorDash ## Building for the entire ecosystem DoorDash's approach to stablecoins reflects how the company has always operated: solve for the local, and the global follows. Rather than waiting for stablecoin infrastructure to mature and then adopting it, DoorDash is investing early to help shape how stablecoin payments work for large-scale marketplaces. > If we can participate in the ecosystem and help design for these use cases up front, maybe problems that are painful today can be painless tomorrow. > > — **Andy Fang**, Co-founder, DoorDash The problems DoorDash faces on traditional rails, including costly FX, high payout processing costs, delayed payouts, and fragmented infrastructure across markets, are exactly the problems stablecoin payments are designed to solve. By working with Tempo as a design partner, DoorDash is helping ensure that the solutions work for the specific complexity of three-sided marketplace payments at global scale. ## What's ahead > There's real promise with stablecoins transforming financial infrastructure, not just in America, but globally. We want to be a proactive participant and not just passive. > > — **Andy Fang**, Co-founder, DoorDash DoorDash is working with Tempo to bring stablecoin-powered payments to its marketplace, starting with the use cases where faster, more affordable settlement creates the most value for merchants and Dashers, across its global footprint. If you're a marketplace, platform, or enterprise exploring how stablecoins can modernize your payment operations, get in touch at partners@tempo.xyz. ## Learn more - [Explore cross border payments](/solutions/cross-border-payments) - [Learn about stablecoins](/learn/what-are-stablecoins/) - [Browse the ecosystem](https://tempo.xyz/ecosystem) --- ## Felix: instant remittances for one million families, settled on Tempo > Source: https://tempo.xyz/customer-stories/felix-pago/ > Language: en # Felix: instant remittances for one million families, settled on Tempo Felix Pago built a remittance product that lives entirely inside WhatsApp, processing over $5 billion for more than one million users across nine Latin American corridors. Felix is adding Tempo to its settlement infrastructure for predictable costs, dedicated payment capacity, and sub-second finality at scale. ## At a glance - **1M+** — Users served - **$5B+** — Total volume - **9** — Corridors > As we scale, we're intentional about building redundancy across our settlement infrastructure. Tempo adds a settlement layer purpose-built for payments, which is important for a real-time remittance product like ours. > > — **Hugo Rodriguez**, Associate Director of Strategy, Felix Pago ## How Felix Pago works A worker in Houston opens WhatsApp, types a few words to an AI chatbot, and money arrives in her mother's bank account in Guadalajara within seconds. She never sees a blockchain, never holds a token, never downloads an app. Felix Pago makes cross-border remittances feel like a WhatsApp conversation. A user in the US texts Felix's AI chatbot, says how much to send and where, picks a payment method, and the recipient in Latin America receives local currency deposited within seconds. No app download, no storefront visit, no crypto terminology. Felix currently serves nine corridors across Mexico, Central America, and the Caribbean and has processed over $5 billion in total volume for more than one million users. The majority of transfers cost a flat $2.99. ## The challenge with settlement at scale Felix settles remittances through stablecoins behind the scenes. The sender pays in dollars, Felix converts to stablecoins for settlement, and the recipient receives local currency on the other end. Neither side ever touches crypto. This architecture is what lets Felix charge $2.99 per transfer while offering competitive exchange rates, undercutting legacy remittance providers significantly. At over $5 billion in cumulative volume and growing, the economics of the settlement layer compound. Every fraction of a cent in transaction fees matters when you process hundreds of millions of dollars per month on a flat consumer fee. And for a product that promises delivery in seconds, settlement reliability is not optional. Downtime or degraded performance means a sender in Houston watching a WhatsApp thread and waiting for confirmation that never comes. As volume has scaled, Felix's focus has shifted toward building redundancy across all critical infrastructure. Settlement is the layer where cost predictability and throughput most directly determine whether the unit economics hold. Felix needed infrastructure that was both reliable under load and purpose-built for payment flows. ## Why Felix chose Tempo Felix is integrating Tempo into its settlement infrastructure to add redundancy and improve performance as volume scales. What drew Felix to Tempo was its focus on payments as a first-class use case. - Predictable transaction fees — Tempo charges a flat fee per transaction regardless of network conditions. For a business that commits to a $2.99 consumer fee, knowing the settlement cost in advance is the difference between sustainable margins and guesswork. There are no gas auctions and no fee spikes during periods of high network activity. - Dedicated payment lanes — Tempo reserves blockspace at the protocol level for payment transactions. A surge in trading volume or other on-chain activity never affects payment throughput or latency. For Felix, this means settlement performance stays consistent whether the network is quiet or under heavy load. - Sub-second finality — Transactions on Tempo finalize in under a second with deterministic settlement. When a user sends money through WhatsApp and expects it to arrive in seconds, the settlement layer has to keep that promise every time. Deterministic finality removes the ambiguity of probabilistic confirmation that exists on general-purpose chains. > Our priority is delivering a consistent experience for users sending money in real time. Tempo helps us strengthen that by providing fast and predictable settlement as part of a broader, redundant infrastructure strategy. > > — **Hugo Rodriguez**, Associate Director of Strategy, Felix Pago ## What's ahead Felix is starting with its existing remittance corridors across Mexico, Central America, and the Caribbean. Lower, more predictable settlement costs give Felix room to either reinvest in growth or pass savings back to senders as lower fees. The US-to-Latin America remittance corridor moves hundreds of billions of dollars a year. More than half of transfers in the region still happen at physical storefronts. For the families who depend on Felix to get money home, better infrastructure behind the scenes means more money arriving on the other end. ## Learn more - [Explore cross-border payments](https://tempo.xyz/solutions/cross-border-payments) - [Learn about stablecoins](/learn/what-are-stablecoins/) - [Browse the ecosystem](https://tempo.xyz/ecosystem) --- ## Howard Hughes Holdings pilots onchain financial verification with Tempo > Source: https://tempo.xyz/customer-stories/howard-hughes/ > Language: en # Howard Hughes Holdings pilots onchain financial verification with Tempo Howard Hughes Holdings is piloting Tempo for reconciliation, audit, and cash management across its portfolio, with a path toward stablecoin settlement. ## At a glance - **NYSE: HHH** — Publicly traded - **Real-time** — Reconciliation across rails - **TDV™ + OneRail™** — Products built on Tempo > Knowing how much cash you have or by how much it changed is not hard, you can tell from your general ledger and your bank statements. However, understanding how each dollar was spent and generated requires analysis that involves ledgers, subledgers, humans, and time. I've spent most of my career trying to solve this problem in real-time, with auditable evidence and confirmation from all third parties involved. We're working to solve this with Tempo as a single, trustworthy ledger across every entity and every payment rail, while protecting the security of our sensitive information. > > — **Carlos A. Olea**, CFO, Howard Hughes ## About Howard Hughes Holdings Howard Hughes Holdings (NYSE: HHH) is a publicly traded holding company focused on growing long-term shareholder value. Through its real estate platform, Howard Hughes Communities, the company owns, manages, and develops commercial, residential, and mixed-use real estate throughout the U.S. The company manages billions of dollars in annual cash movement and builds shared operational infrastructure across its portfolio to drive efficiency at scale. ## What Howard Hughes is building Howard Hughes is developing two products on Tempo. - TDV™ (Trustless Data Verification) — Records every general ledger transaction from the ERP onchain in verified form, classified by cash and non-cash movement. This enables real-time reconciliation, automated financial statement classification, and evidence that traces each cash transaction to bank settlement in one place. The goal is to shift the timing from month-end to always, allowing the company to identify trends, issues, and opportunities much faster, and largely shifting internal controls from full-population review to estimates only. - OneRail™ — Sits on top of the company's payment rails (ACH, wire, card, and eventually stablecoins) and represents all cash movement in a single canonical object called ORTO™ (OneRail Transaction Object). ORTO captures every cash-related event, who, what, when, how much, and why, in a standardized format, regardless of source system or payment rail. The practical result: reconciliation that currently requires teams to manually match transactions across ERPs and bank statements happens automatically at the point of payment. Finance teams spend less time tracing discrepancies and more time on estimates and analysis. Year-end audits will start from a verified, immutable ledger instead of full GL populations. If a team starts with knowing that 80% of revenue is already reconciled to cash and validated by the bank and customers onchain, the risk is now only the remaining 20%. Because TDV classifies every line item by cash and non-cash movement, Howard Hughes will generate direct-method cash flow statements automatically, something most companies avoid because the manual effort is too high. Howard Hughes has already validated the system against real transactions from its operating data with positive results. ## Why Tempo The company evaluated multiple approaches before building on Tempo: - Tempo Zones — Howard Hughes is a public company. Construction budgets, lease terms, and development economics are sensitive financial data that cannot sit on a public ledger. Tempo Zones let Howard Hughes control exactly who sees what. Auditors get full access. Authorized counterparties see only the transactions relevant to them. Everything else stays private. Compliance workflows like counterparty verification, audit trail generation, and transaction-level access governance are enforced at the zone level rather than through manual oversight. - Memo fields — Every transaction on Tempo can carry metadata like invoice references, PO numbers, and reconciliation tags. For Howard Hughes, this means every payment on the ledger links directly back to the source document in the ERP, enabling end-to-end traceability. - Immutability — Once a transaction is recorded on Tempo, it cannot be changed. This reduces the time and cost of year-end audits, since auditors can verify the ledger directly rather than rebuilding it from source systems. - Cost and throughput — Low, stablecoin-paid fees with sub-second finality. Low enough to run daily financial operations through the network at scale. - Payments-first design — Tempo is a Layer 1 blockchain purpose-built for payments. Its architecture, including deterministic transaction ordering, predictable fees, and stablecoin-native execution, aligns with how OneRail™ works: Tempo serves as the execution and settlement layer while OneRail handles integration, orchestration, and reconciliation on top. ## What's next Expanding the pilot to additional entities, leveraging AI agents, and expanding the use of Tempo to include onchain settlement. ## Learn more - [Explore institutional money movement](/solutions/institutional-money-movement) - [Contact us](/contact) --- ## Karta is building its self-custody money app on Tempo > Source: https://tempo.xyz/customer-stories/karta/ > Language: en # Karta is building its self-custody money app on Tempo Karta, a self-custody money app with more than 25,000 monthly cardholders and 1,250+ business teams across 150+ countries, is building on Tempo. Karta's treasury is live on Tempo today, and Karta Personal launches on Tempo soon. ## At a glance - **25,000+** — Monthly cardholders - **1,250+** — Business teams - **150+** — Countries > At Karta, self-custody isn't a feature, it's the architecture. Every user holds their own stablecoin balance on their own wallet, and every transaction they make settles on-chain. Doing that at consumer scale was only possible on infrastructure built for payments, not retrofitted for them. Tempo is the first chain where we didn't have to trade self-custody for a product that actually works. > > — **Nik Zimarkov**, Co-founder and CEO, Karta ## About Karta Karta is a self-custody money app. Its product includes a Visa card accepted in 150+ countries, fiat virtual accounts in the US today with expansion underway globally, and a wallet for cross-currency earning, spending, and sending. Karta is live on Telegram, with iOS and Android rolling out, and reports 25,000+ monthly cardholders and 1,250+ business teams. Karta's partner stack is Privy for self-custody wallets, Bridge for fiat rails and virtual accounts, and Tempo for settlement. ## The problem Karta set out to solve Karta describes its challenge as four payment-infrastructure constraints that converge when building self-custody payments at consumer scale. - Gas. Every transaction on a general-purpose chain requires a native gas token, which users of a consumer money app would have to acquire before moving the asset they actually care about. - Signing. In a pure self-custodial model, every transaction requires a live signature from the wallet owner, which makes real-time asynchronous flows like card authorizations structurally difficult. - Finality as a fraud surface. Seconds-long finality creates windows for double-spend attempts that millisecond-level card authorization cannot tolerate. - Metadata and reconciliation. Partner rails depend on per-transaction context such as invoice references and compliance flags. Rebuilding that from event logs adds cost and fragility. ## What Karta is building on Tempo Karta's treasury is live on Tempo today. Karta Personal, Karta's consumer product, launches on Tempo soon, alongside fiat virtual account expansion to new markets. Karta Business migrates onto the same settlement layer shortly after. Per Karta, its consumer architecture is structured as follows: a self-custodial smart account is provisioned on Tempo via Privy, USD balances are held as USDC on that account, and card authorizations settle against the on-chain balance inside standard card authorization windows. ## Why Karta chose Tempo Each of the constraints above has been solved individually on different chains. Paymaster contracts handle gas abstraction. Account abstraction and session keys approximate asynchronous signing. Emerging rollups approach sub-second finality. Specialty payment chains expose structured metadata. Tempo's architecture consolidates each of them into native protocol capabilities. - Sub-second deterministic finality. Transactions finalize on-chain in approximately 500ms with no re-orgs, inside standard card authorization windows. - Stablecoin-native gas. Gas is paid in USD stablecoins at the protocol level. No native gas token, no paymaster contracts, no ERC-4337 retrofits. - Access Keys. A protocol-level primitive for authorized debits against a wallet without custody transfer. Card authorizations can settle asynchronously against an on-chain balance without a live wallet signature at authorization time. - Dedicated payment lanes. Payment traffic has guaranteed blockspace at the protocol level, insulated from unrelated network activity. - Structured memo fields. Native per-transfer metadata, ISO 20022-compatible, supports reconciliation and compliance workflows. > Each of these problems has a workaround somewhere: paymasters for gas, session keys for signing, rollups for finality. But they live on different chains and in different retrofits, and shipping a consumer product at mainstream scale means solving all of them on the same stack. Tempo is the first chain where each one is a first-class protocol feature rather than a workaround bolted onto a general-purpose VM. That's the difference between the full payment path living on-chain and an off-chain ledger reconciled after the fact. > > — **Matt Aliev**, Co-founder and CTO, Karta ## What's ahead Karta Personal launches on Tempo soon, with fiat virtual account expansion to new markets following close behind. Karta Business migrates onto the same settlement layer shortly after. If you're building a payments product, get in touch at partners@tempo.xyz. ## Learn more - [Explore embedded finance](/solutions/embedded-finance) - [Learn about stablecoins](/learn/what-are-stablecoins/) - [Browse the ecosystem](https://tempo.xyz/ecosystem) --- ## KAST is bringing its stablecoin earn product onto Tempo and joining as design partner > Source: https://tempo.xyz/customer-stories/kast/ > Language: en # KAST is bringing its stablecoin earn product onto Tempo and joining as design partner KAST is a global financial platform built on stablecoin rails. Users can hold, move, and spend stablecoin balances through a card accepted at 150 million merchants in 170+ countries. ## At a glance - **1M+** — Users - **$5B** — Annualized transaction volume - **170+** — Countries ## About KAST [KAST](https://www.kast.xyz/) is a global financial platform built on stablecoin rails. Users can hold, move, and spend stablecoin balances through a card accepted at 150 million merchants in 170+ countries. Since launch, KAST has grown to more than one million users and processes close to $5B in annualized transaction volume.1 KAST's growth has been driven by markets where traditional banking and cross-border payments leave the most friction on the table: global citizens, workers paid across borders, families sending money home, and small businesses operating in multiple currencies. Stablecoins do work that legacy rails cannot. ## The challenge For stablecoins to power mainstream financial products, the infrastructure underneath has to be built for real-world throughput, reliability, and operations. General-purpose blockchains were not built with those requirements in mind. As KAST scales, the settlement layer becomes a strategic decision. Three things mattered most: Performance at consumer scale. Card authorizations, merchant settlements, and user-facing transfers cannot compete with NFT mints or DeFi liquidations for blockspace. Predictable economics. Fee volatility breaks unit economics for high-volume, low-margin consumer flows. Operational maturity. Reconciliation, compliance, and treasury workflows are non-negotiable for a regulated consumer financial product. ## The approach KAST is working with Tempo on two specific commitments: A stablecoin earn product on Tempo. KAST plans to launch its earn product that will let users put idle stablecoin balances to work without leaving the KAST app, powered by a vault on Tempo. The design is global by default and extensible across product types and asset classes over time. Design partner on what comes next. KAST is working with Tempo as a design partner to shape new features and products. KAST's scale across 170+ countries and its user base spanning LATAM, North America, MENA, and Asia provide a real-world testing ground for what consumer stablecoin products need at scale. ## Why Tempo Tempo is incubated by Stripe and Paradigm and built specifically for payments at scale. The capabilities that mattered most to KAST: - Sub-second finality with deterministic settlement - Bounded dynamic fees paid in stablecoins, with no separate gas token - Dedicated payment lanes with guaranteed blockspace at the protocol level - Native account abstraction for batch payouts, fee sponsorship, and passkey authentication - Payments metadata for clean reconciliation against existing systems > KAST is focused on building real financial products that scale globally. Tempo gives us a foundation to build on what stablecoin rails can unlock across payments and the next generation of money movement. > > — **Raagulan Pathy**, Founder & CEO, KAST ## What's next KAST and Tempo are rolling out across these workstreams over the coming months. If you are building consumer financial products on stablecoins, [talk to us](/contact). ## Learn more - [Talk to us](/contact) - [Browse the ecosystem](/ecosystem) - [Learn about stablecoins](/learn/what-are-stablecoins) --- ## MoneyGram is joining Tempo as its first remittance validator and settlement partner > Source: https://tempo.xyz/customer-stories/moneygram/ > Language: en # MoneyGram is joining Tempo as its first remittance validator and settlement partner MoneyGram, one of the world's largest global payments networks, is joining Tempo as its first remittance validator and advancing stablecoin-based settlement across its network spanning 200+ countries and territories. ## At a glance - **200+** — Countries and territories - **50M+** — Customers served - **1st** — Remittance validator ## Bringing global remittance expertise onchain MoneyGram moves money for over 50 million customers across more than 200 countries and territories. With decades of experience operating at that scale, MoneyGram has built deep expertise in navigating dozens of regulatory regimes, managing settlement flows across hundreds of currencies, and delivering the operational reliability required by people who depend on those transfers every day. That's exactly why MoneyGram is building with Tempo: to bring that expertise into the next generation of global payments and help power faster, more efficient settlement flows at global scale. ## What MoneyGram is building with Tempo The partnership has two dimensions. MoneyGram is joining Tempo's network as its first remittance validator, among a select group of institutions designated to validate transactions on the network. After 5+ years of building on blockchain rails, MoneyGram is now helping to secure the infrastructure it builds on. On settlement, MoneyGram, Tempo, and Stripe plan to bring stablecoin settlement into live flows, with Stripe to settle to MoneyGram through Tempo using onchain infrastructure. This will enable more efficient treasury operations across MoneyGram's global footprint. > As stablecoins and blockchain technology become more deeply integrated into mainstream financial services, MoneyGram is actively building the next era of payments infrastructure. Tempo, as a purpose-built blockchain for payments that shares our focus on solving real consumer problems, is a natural partner. > > — **Anthony Soohoo**, CEO and Chairman, MoneyGram ## Why Tempo Tempo was built for the use cases MoneyGram runs every day: high-volume cross-border transfers, stablecoin-denominated settlement, and the operational reliability required to serve tens of millions of customers. As the partnership deepens, MoneyGram and Tempo will explore additional corridors, settlement flows, and integrations across the crypto ecosystem. If you're a financial institution or payments network exploring how stablecoin infrastructure can modernize your settlement operations, reach out at [partners@tempo.xyz](mailto:partners@tempo.xyz). ## Learn more - [Explore cross-border payments](/solutions/cross-border-payments) - [Browse the ecosystem](/ecosystem) - [Contact partnerships](mailto:partners@tempo.xyz) --- ## OnePay and Tempo partner to help shape next generation of stablecoin-powered payments > Source: https://tempo.xyz/customer-stories/onepay/ > Language: en # OnePay and Tempo partner to help shape next generation of stablecoin-powered payments OnePay, the consumer fintech trusted by millions of Americans, is partnering with Tempo on stablecoin payouts and instant account funding for its banking product. ## At a glance - **Millions** — Americans served - **Instant** — Payouts and funding - **Planned** — Tempo validator > We're proud to serve an incredible customer base that values their money working harder and moving faster. Tempo's payments-focused architecture and built-in privacy and compliance tooling make it the right infrastructure partner as we expand into stablecoin-powered experiences for our customers. > > — **Pierce Harger**, Head of Crypto at OnePay ## OnePay and Tempo OnePay, the consumer fintech trusted by millions of Americans, is partnering with Tempo. The partnership's early efforts will center on areas like stablecoin payouts and instant account funding for OnePay's banking product, with OnePay and Tempo working to expand into additional use cases over time. OnePay also plans to launch a validator on Tempo. OnePay already powers instant payouts and direct deposit access for millions of workers and consumers. Stablecoin infrastructure represents the next evolution of that capability, enabling always-on settlement, lower infrastructure costs, and new ways to move money into and out of the OnePay platform. ## OnePay plans to launch validator on Tempo As part of the partnership, OnePay plans to launch a validator on Tempo. The commitment signals OnePay's interest not only in building customer-facing products on stablecoin rails, but in actively supporting the infrastructure that powers them. > The next wave of onchain adoption will come from products that solve real problems for everyday users. OnePay serves millions of workers and consumers who stand to benefit from faster, cheaper money movement. Partnering with them is a clear step in shaping the next generation of consumer finance. > > — **Ani Narayan**, GTM, Tempo ## What's next OnePay and Tempo will continue to explore additional use cases over time, with additional partner spotlights from the Tempo ecosystem to come. ## Learn more - [Explore embedded finance](/solutions/embedded-finance) - [Browse the ecosystem](/ecosystem) - [Contact partnerships](mailto:partners@tempo.xyz) --- ## RedotPay integrates MPP to bring agentic payments to its 7.5 million users > Source: https://tempo.xyz/customer-stories/redotpay/ > Language: en # RedotPay integrates MPP to bring agentic payments to its 7.5 million users RedotPay is integrating the Machine Payments Protocol (MPP) to enable AI agents to transact on behalf of its 7.5 million users across 130 million merchants worldwide, with settlement on Tempo. ## At a glance - **7.5M** — Users - **130M** — Merchants - **100+** — Countries ## About RedotPay RedotPay is a global stablecoin-based payment fintech that bridges blockchain solutions with traditional banking and finance infrastructures. Serving over 7 million registered users across more than 100 countries, RedotPay enables the spending and sending of digital assets at 130 million merchants worldwide. The company processes over $10 billion in annualized payment volume and raised $107 million in a Series B in 2025. RedotPay’s mission is to make digital finance accessible, secure, and efficient for everyone, from crypto-native users to underbanked populations with limited access to legacy financial systems. ## The problem Agentic commerce is moving from concept to product faster than most payment infrastructure can handle. AI agents can browse, compare, and recommend products, but most still hand off to a human at checkout. This handoff introduces significant friction and is a primary driver of conversion drops. The **[Machine Payments Protocol (MPP)](https://mpp.dev/)**, co-authored by Stripe and Tempo, provides a specification for AI agents to send and receive payments programmatically. It covers microtransactions, recurring payments, and direct merchant flows. RedotPay is integrating MPP into its app with Tempo as the settlement chain. The flow: an AI agent processes a user request. MPP handles discovery, comparison, and checkout inside a single experience. RedotPay settles with the merchant using stablecoins on Tempo, and with the user from their existing wallet balance. For RedotPay’s users, they do not need to bridge or hold any assets on Tempo. Merchants receive stablecoin payments from AI agents and can off-ramp as needed. For consumers, this collapses product search, price comparison, and purchase into a single touchpoint inside the RedotPay app, reducing steps, latency, and drop-off. For merchants, it opens a direct channel for accepting AI-initiated stablecoin payments, with settlement handled on the back-end. ## Why Tempo For RedotPay, building agentic payment flows on Tempo means using MPP where it has the most mature implementation. Stripe and Tempo co-authored the protocol, and the chain’s design was shaped around the flows MPP enables. - Access keys for agents — Tempo’s native account abstraction lets AI agents sign payment transactions on behalf of users using delegated keys, without exposing root private keys. The user authorizes the agent once; the agent handles the rest. This is the foundation that makes autonomous, trustworthy agentic commerce possible inside the RedotPay app. - Sub-second finality — Transactions on Tempo finalize in under a second with deterministic settlement. When an agent completes a purchase, the user sees a confirmed transaction, not a pending state. For a product built around seamless, single-touchpoint commerce, the settlement layer has to keep up. - Predictable, stablecoin-denominated fees — Tempo charges a flat fee per transaction, payable in stablecoins, with no fee spikes from network activity. For a platform serving 7 million users across 100 countries, simplicity matters. Users participate without holding anything extra. > Agentic payments represent a fundamental shift in user experience, transforming how we discover, purchase, and pay. At RedotPay, innovation has always been our focus. By partnering with Tempo to integrate AI with stablecoin payments, we are shaping the future of payment solutions and making digital asset spending more seamless, intuitive, and accessible for everyday life. > > — **Jonathan Chan**, Co-Founder and Head of Partnerships, RedotPay ## What’s next RedotPay’s MPP integration is live on Tempo today. RedotPay is set to launch the second phase of its agentic payments capability, with the payment skill becoming available for download in June this year. Users will be able to access agentic payments with AI agents handling discovery and purchase. The partnership is designed to grow with both companies. As RedotPay expands its product suite and Tempo deepens MPP’s reach across merchants and payment methods, both users and merchants get a new channel for AI-initiated payments. ## Learn more - [Explore agentic payments on Tempo](/solutions/agentic-payments) - [Get in touch](https://tempo.xyz/contact) - [Explore MPP](https://mpp.dev) - [Browse the ecosystem](https://tempo.xyz/ecosystem) --- ## Stripe Treasury: stablecoin capabilities on Tempo > Source: https://tempo.xyz/customer-stories/stripe/ > Language: en # Stripe Treasury: stablecoin capabilities on Tempo Tempo powers the stablecoin capabilities in Stripe Treasury today, letting businesses access dollar-backed stablecoins, move money across borders, and manage funds from the Stripe Dashboard in 100+ countries. As Stripe expands Treasury's stablecoin footprint, Tempo is the settlement layer making those transfers fast, final, and predictable. ## At a glance - **100+** — Countries supported - **<1s** — Settlement time - **USD** — Network fee denomination ## The problem with global payouts Global money movement for businesses still runs on infrastructure built for a different era. A company paying contractors in 30 countries manages a patchwork of regional payment rails, each with its own settlement timelines, fee structures, and operational requirements. Wire transfers route through intermediary banks that add cost and latency at every hop. Payments initiated on Friday afternoon sit idle until Monday morning. For platforms and marketplaces, the problem compounds. A marketplace distributing earnings to sellers across dozens of countries needs each payout to be fast, cheap, and predictable. But the underlying rails offer none of those properties consistently. Settlement times vary by corridor. Fees depend on which intermediaries handle the transfer. And reconciling thousands of cross-border payouts against internal systems is a manual, error-prone process. ## What Stripe Treasury is enabling [Stripe Treasury](https://stripe.com/treasury) now gives businesses one place to send money, manage spend, and access stablecoins from the Stripe Dashboard. Businesses can store dollar-backed stablecoins, move funds across borders, and operate more like a local business in 100+ countries without taking on blockchain complexity themselves. Tempo powers those stablecoin capabilities in Stripe Treasury today. When a business uses Treasury to hold a stablecoin balance, send funds internationally, or move money faster outside traditional banking windows, Tempo is the settlement layer making those transfers fast, final, and predictable. Stripe's Sessions 2026 launch made that Treasury positioning more explicit. Stripe framed Treasury around stablecoin-backed balances, local operating accounts, and cross-border money movement, with stablecoin support expanding into additional markets and noncustodial wallet-backed Treasury accounts on the roadmap. Tempo sits underneath that product surface as the blockchain infrastructure for Treasury's stablecoin experience. ## What Stripe Treasury needs from a settlement layer Powering stablecoin balances and cross-border transfers inside Stripe Treasury puts specific demands on the infrastructure underneath. Businesses using Treasury in 100+ countries need a settlement layer that is fast, predictable, and operationally invisible. > It should be easy and instant to move money anywhere in the world. That's the promise of programmable financial services. As we bring stablecoin infrastructure into more Stripe products, we're delivering on that promise at scale, so every Stripe user can benefit from faster, cheaper, borderless money movement. > > — **Neetika Bansal**, Head of Connect and Money Management, Stripe Tempo's architecture addresses each of those requirements directly. Dedicated payment lanes guarantee blockspace for payment transactions at the protocol level, so throughput is never affected by other network activity. For infrastructure supporting millions of businesses, that reliability is a prerequisite. Gas abstraction means the entire Treasury stablecoin experience operates in dollars. Fees are denominated in stablecoins rather than a volatile native token, which means no separate token to hold, no FX risk on the settlement layer, and simpler accounting for the businesses using the product. Native memo fields compatible with ISO 20022 let each transfer carry structured metadata: invoice numbers, cost centers, payout identifiers. For businesses reconciling thousands of payouts against ERP and treasury management systems, this makes reconciliation straightforward rather than manual. T7's bounded dynamic base fee keeps network costs within a defined range and lets fees fall as network usage drops. Fees remain denominated in stablecoins, so businesses avoid a separate gas token and keep settlement accounting in dollars. ## Powering stablecoins inside Stripe Treasury [Stripe Treasury](https://stripe.com/treasury) positions Tempo not as a standalone blockchain integration, but as invisible infrastructure underneath a financial account businesses already use. A Treasury user does not need to know that their stablecoin balance or transfer settled on Tempo. They see a faster, cheaper way to store funds, send money, and access stablecoins from the Stripe Dashboard. The blockchain is the rail, not the product. That is what makes the Stripe relationship notable. Tempo is powering a live stablecoin capability inside Stripe Treasury today, not a lab experiment or a standalone crypto surface. As Stripe expands Treasury stablecoin support into more countries and workflows, every new Treasury flow that touches stablecoin movement is a potential surface for Tempo settlement. ## What's ahead Stripe is expanding [Treasury's](https://stripe.com/treasury) stablecoin capabilities, including support for additional markets and wallet-backed accounts, as it brings more businesses into a Treasury model that combines local money movement with dollar-backed stablecoins. As that footprint grows, the settlement layer underneath becomes critical infrastructure. For enterprise payment teams evaluating where stablecoins fit into their stack, the signal is clear: Tempo is already powering stablecoin capabilities inside Stripe Treasury today. If you're evaluating stablecoins for treasury operations, cross-border transfers, or embedded finance, get in touch at partners@tempo.xyz. ## Learn more - [Learn about Stripe Treasury](https://stripe.com/treasury) - [Explore embedded finance](/solutions/embedded-finance) - [Learn about stablecoins](/learn/what-are-stablecoins/) - [Browse the ecosystem](https://tempo.xyz/ecosystem) --- ## Sprechen Sie mit Tempo > Source: https://tempo.xyz/de/contact/ > Language: de # Kontakt aufnehmen Erzählen Sie uns ein wenig über sich und Ihr Projekt. Wir helfen Ihnen gerne herauszufinden, wie Tempo Ihre Zahlungsinfrastruktur beschleunigen kann. Bei technischen Fragen oder wenn Sie Unterstützung benötigen, wenden Sie sich bitte an [support@tempo.xyz](mailto:support@tempo.xyz). Bei Presseanfragen erreichen Sie uns unter [press@tempo.xyz](mailto:press@tempo.xyz) > Interactive contact form is available on the HTML page. --- ## Tempo Earn — Put stablecoin balances to work on Tempo > Source: https://tempo.xyz/earn/ > Language: en # Put stablecoin balances to work on Tempo Tempo Earn Tempo Earn lets your business access yield on stablecoins using enterprise-grade strategies. [Talk with our team](/contact/) [Explore API](/developers/docs/api/earn) ## Grow revenue and win new customers with Earn ### Earn on stablecoin balances Offer up to 7% APY on stablecoins next to the products your customers already love. ### Launch in 100+ countries Attract new customers globally with a reason to keep funds on your platform. ### Enterprise-grade strategies Access U.S. Treasuries, private credit, and collateralized lending with Tempo Earn. ## Build your Earn product on Tempo with confidence ### Earn and Spend in one account Launch a unified stablecoin account that earns until you spend, with cards backed by Tempo Earn balances. ### Configurable rewards and pricing Monetize a share of the returns generated on balances and access competitive pricing. ### Privacy and access controls Define policy controls on who can access your Tempo Earn program and keep activity private with Tempo Zones. [Tempo Zones](/zones/) ## Identify Earn strategies that fit your business Asset options ### U.S. Treasuries Tokenized U.S. Treasury bonds and sovereign debt products. - BlackRock - Ondo Finance - Figure Finance ### Institutional credit Tokenized private credit, HELOC warehouse lending and AAA CLOs. - Figure Finance - Maple Finance - Huma Finance ### Collateralized lending Onchain lending pools. Rates move with borrow demand. - Morpho - Veda - SKY ## Design your Tempo Earn program. How it works Build a custom Earn program around your target return, liquidity needs, and customer eligibility requirements. [Talk with our team](/contact/) ## Deel contractors earn on stablecoin balances with Tempo Earn Deel’s global stablecoin wallet lets contractors in 80+ countries get paid in their dollar-backed stablecoins and earn up to 4% interest. [Customer story](/customer-stories/deel/) ## FAQ ### Why should platforms offer earn? Earn can help platforms attract and retain users. Businesses may offer rewards programs to users and charge a fee. If a strategy produces a 5% return, businesses may let users earn 4% and take the remaining 1% as their fee. For balances of $10M this can generate $100,000 in revenue. ### What returns can customers earn? Returns depend on the underlying assets and market conditions, currently between 3.5% and 7%. Rates can change and are not guaranteed. ### Can customers withdraw at any time? Withdrawal timing depends on the underlying asset’s liquidity and redemption terms. Tempo Earn offers both synchronous and asynchronous withdrawal products. ### Where can I offer Earn? Availability depends on the asset provider, your product structure, and customer eligibility. Contact Tempo Advisory to evaluate your strategy. ### What about compliance and privacy? Tempo provides native privacy, access controls, and transfer policies which help financial platforms and regulated businesses build and scale Earn programs. ## Launch your Earn program Work with Tempo to design and launch custom Earn vaults or tap into existing strategies on Tempo. [Talk with our team](/contact/) --- ## Ecosystem – Tempo > Source: https://tempo.xyz/ecosystem/ > Language: en ## Ecosystem Partners We have curated a class of leading infrastructure providers that make it easy to build, launch, and scale payment & stablecoin use cases. [Become a partner](/contact) [Integrate with Tempo](/developers/) ### [0x](https://0x.org/) Institutional DEX aggregation and smart order routing API powered by 0x. Access 100+ liquidity sources across chains with production-grade execution infrastructure. Infrastructure, Developer Tools ### [Across](https://across.to) Across Protocol unifies web3 with fast, cheap, and secure crosschain interoperability. Across provides users and developers with seamless experiences powered by intents. Interoperability ### [Agant](https://agant.io) Agant is enhancing money by making it safer, faster, more accessible and more productive for institutions and the markets they serve. Issuance, Orchestration & Ramps, Infrastructure ### [Alchemy](https://alchemy.com) With Alchemy, build the fastest, most reliable apps for millions of people worldwide—stablecoins, tokenization, real-world assets, and more. Developer Tools, Infrastructure ### [Allium](https://allium.so) Allium provides blockchain data for every use case - Analytics, Applications, Accounting and more. Data ### [AllUnity EUR Stable](https://allunity.com) AllUnity is a BaFin-regulated e-money institute providing institutional-grade infrastructure for seamless, secure, real-time digital Euro transactions, with full reserve backing and regulatory transparency. Issuance ### [AllUnity SEK Stable](https://allunity.com) AllUnity is a BaFin-regulated e-money institute providing institutional-grade infrastructure for seamless, secure, real-time digital Swedish krona transactions, with full reserve backing and regulatory transparency. Issuance ### [AllUnity CHF Stable](https://allunity.com) AllUnity is a BaFin-regulated e-money institute providing institutional-grade infrastructure for seamless, secure, real-time digital Swiss franc transactions, with full reserve backing and regulatory transparency. Issuance ### [Artemis](https://artemisanalytics.com) Artemis is the premier analytics platform for blockchain data. Industry leaders like Visa, Grayscale, Pantera trust Artemis. Data ### [BitGo](https://bitgo.com) BitGo is a digital asset infrastructure company, delivering custody, wallets, staking, trading, financing, and settlement services from regulated cold storage. Wallets, Infrastructure, Developer Tools, Issuance ### [Blockaid](https://blockaid.io) Blockaid detects, understands, and protects against fraud, scams, and exploits in real time. Compliance & Fraud ### [Blockdaemon](https://blockdaemon.com) Blockdaemon offers institutional-grade blockchain infrastructure spanning nodes, APIs, staking, MPC wallets and vaults. Wallets, Infrastructure ### [Blockradar](https://blockradar.co) Blockradar is a stablecoin wallet infrastructure provider purpose built for fintechs. With one API, teams can issue non-custodial wallets, move funds onchain, and manage settlements securely at scale. Wallets, Orchestration & Ramps ### [Brale](https://brale.xyz) Brale has built the first stablecoin issuance platform modeled after the tried and tested card issuance model. Issuance ### [Bridge](https://bridge.xyz) Streamline global money movement with stablecoin infrastructure. Orchestration & Ramps ### [Bungee](https://www.bungee.exchange/) Bungee is a protocol that powers seamless swaps within and between blockchains. Interoperability ### [Cap](https://www.cap.app/) Cap is a covered credit application consisting of a digital dollar, a credit platform, and a financial guarantee market to underwrite individual loans. Infrastructure, Issuance ### [Chainalysis](https://chainalysis.com) Chainalysis is the leading blockchain intelligence company enabling governments and businesses to assess and investigate crypto activity. Compliance & Fraud ### [Chainlink](https://docs.chain.link/data-feeds/price-feeds/addresses?network=tempo) Chainlink Data Feeds provide live, decentralized market data on Tempo for lending, FX, tokenized assets, stablecoins, and other onchain applications. Interoperability, Data ### [Chainstack](https://chainstack.com) Chainstack delivers SOC 2 Type 2 certified, scalable blockchain infrastructure with low-latency RPC nodes, high-performance execution, and rapid archive data access. Developer Tools ### [Chronicle](https://chroniclelabs.org/) Chronicle provides onchain data verification infrastructure that enables institutions to confidently participate in tokenized financial markets. Infrastructure ### [Conduit](https://conduit.xyz) Conduit provides enterprise-grade blockchain infrastructure & advanced dev tooling for teams building the next generation of finance. Developer Tools ### [Coinbase](https://www.coinbase.com/) Coinbase supports Tempo for custody, trading, and transfers, including in its iOS and Android apps. Retail and exchange customers can trade supported stablecoins and select Tempo when sending or receiving. Eligible Coinbase Prime clients can access custody support, with availability varying by asset and contracting entity. Wallets, Payments ### [Coingecko](https://www.coingecko.com/) The CoinGecko API is a unified and comprehensive crypto data API that provides reliable market data, metadata, historical data, on-chain data, and more. Data ### [Coins.ph](https://www.coins.ph/en-ph/business) Coins.ph provides regulated payment, payout, trading, and on-ramp and off-ramp APIs connecting PHP and stablecoins in the Philippines. Orchestration & Ramps, Payments ### [Crossmint](https://crossmint.com) Enterprise-grade APIs for wallets, stablecoins, and agentic commerce. Wallets ### [Cubist](https://cubist.dev/) Cubist is high-performance infrastructure for safely and privately automating digital asset operations at scale. Developer Tools, Infrastructure, Wallets ### [Cybrid](https://cybrid.xyz) Cybrid offers an orchestration platform that brings together banking, wallet infrastructure, and stablecoin rails to support compliant stablecoin and fiat payments through one API. Orchestration & Ramps ### [DFNS](https://dfns.co) Dfns is the leading Wallets-as-a-Service (WaaS) platform to build onchain faster, enabling developers, fintechs, and institutions to streamline digital asset operations and launch apps at scale—safely. Wallets, Developer Tools, Orchestration & Ramps ### [Dynamic](https://dynamic.xyz) Dynamic combines authentication, smart wallets, and secure key management into one flexible SDK. Wallets ### [dRPC](https://drpc.org/) Decentralized RPC endpoints for Tempo with smart routing, analytics, and advanced key management controls. Developer Tools, Infrastructure ### [Due](http://opendue.com/) Due offers a payment infrastructure API linking fintechs to stablecoin networks and local rails across 80+ countries, with on/off ramps, virtual accounts, cross-border payments, mid-market FX, and Pay QR support. Orchestration & Ramps ### [Dune](https://dune.com/home) Query with SQL, stream data via APIs & DataShare, and publish interactive dashboards on Tempo. Data ### [Elliptic](https://elliptic.co) Elliptic provides blockchain data and intelligence for digital asset compliance, risk management, and infrastructure use cases. Compliance & Fraud ### [Farcaster](https://farcaster.xyz) Farcaster is a decentralized social network where you control your account and identity. Wallets ### [Figment](https://www.figment.io/) Figment provides proven validator operations and supporting services globally, with a focus on compliant, secure, and reliable infrastructure at scale. Infrastructure ### [Fireblocks](https://fireblocks.com) Fireblocks is the platform of choice for 2,400+ businesses building and scaling their digital asset strategies. Wallets ### [Fonbnk](https://fonbnk.com) Fonbnk is the stablecoin settlement layer for the Global South — converting mobile money and real-time bank transfers into digital dollars and distributing liquidity across our network of leading wallet partners. Orchestration & Ramps ### [Frax](https://frax.finance) At Frax, we build scalable stablecoin infrastructure around frxUSD, our fully backed digital dollar. Issuance ### [Gem Wallet](https://gemwallet.com) Gem Wallet is an open-source, self-custodial mobile wallet for iOS and Android with native Tempo support for sending, receiving, and swapping assets. Wallets ### [Goldsky](https://goldsky.com) Build powerful apps faster with high-performance blockchain indexing, instant subgraphs, and custom data streaming pipelines. Developer Tools, Data, Infrastructure ### [Hercle](https://www.hercle.com/) Hercle provides competitive FX across EUR, GBP, and 30+ local currencies, with pay-in, payout, and stablecoin ramp infrastructure for EUR and GBP. Orchestration & Ramps ### [Infinite](https://infinite.dev) Infinite enables global businesses to support stablecoin payments and compliance through turnkey orchestration. Orchestration & Ramps, Compliance & Fraud ### [LayerZero](https://layerzero.network) LayerZero is the leading interoperability protocol connecting every type of blockchain. Interoperability ### [Levl](https://levl.ch) Levl is a Galaxy Digital–backed payments platform using stablecoins to power faster, cheaper global payouts and payment processing. Orchestration & Ramps ### [LI.FI](https://li.fi) LI.FI offers a unified API that aggregates bridges, DEXs, and solvers, enabling applications to route value across the blockchain ecosystem into swaps, perps, yield, and other on-chain positions. Infrastructure ### [Luganodes](https://www.luganodes.com/) Luganodes provides institutional blockchain infrastructure, offering non-custodial node operations across 40+ networks. Infrastructure ### [Manteca](https://manteca.dev) Manteca is the all-in-one API infrastructure powering payments, crypto, FX and brokerage across Latin America—built for scale, compliance and real business. Orchestration & Ramps, Interoperability ### [MeshPay](https://www.meshpay.com) MeshPay lets businesses accept crypto payments from hundreds of wallets and settle in stablecoins or local currency through one integration. Orchestration & Ramps, Payments ### [MoonPay](https://www.moonpay.com/business/ramps) MoonPay provides global on-ramp and off-ramp infrastructure through its widget, SDK, and API. Orchestration & Ramps ### [Morpho](https://morpho.org) Morpho is an open credit network for noncustodial lending, borrowing, and vault-based yield opportunities. DeFi, Interoperability ### [Open Standard (OUSD)](https://joinopenstandard.com/) Open Standard governs and operates Open USD (OUSD), a stablecoin designed for payments, transfers, and other financial activity. Issuance ### [OpenFX](https://openfx.com) OpenFX provides real-time, 24/7 FX liquidity for cross-border payments, helping institutions eliminate pre-funding and reduce FX costs by up to 90%. Its single API and treasury platform streamline multi-currency management worldwide. Orchestration & Ramps, Interoperability ### [Orda Network](https://orda.network) Orda is an intent network for moving money across chains, stablecoins, and banking systems in an open market. Orchestration & Ramps, Interoperability ### [OKX Wallet](https://web3.okx.com/) OKX Wallet is a global leading digital asset wallet that adheres to the principles of decentralization. Wallets ### [Para](https://getpara.com) Para provides a wallet and authentication suite designed for fintech and crypto applications. Wallets ### [Phantom](https://phantom.app) Phantom is the world's leading crypto wallet, facilitating over a billion onchain transactions. Wallets ### [Privy](https://privy.io) Privy makes it easy to onboard all your users to web3, regardless of whether they already have wallets. Wallets ### [QuickNode](https://quicknode.com) QuickNode provides blockchain infrastructure powering dApps and companies across the ecosystem. Developer Tools, Infrastructure ### [Range](https://range.org) Range provides security and intelligence for stablecoin infrastructure, powering compliant cross-chain flows and real-time monitoring across all chains. Orchestration & Ramps, Developer Tools, Compliance & Fraud ### [RedStone](https://www.redstone.finance/) RedStone provides modular oracle infrastructure delivering secure, real-time price feeds for DeFi protocols and institutions. ### [Relay](https://relay.link) Relay lets you spend your money anywhere onchain by providing the infrastructure required for paying with any asset on any chain. Interoperability ### [Rhino.fi](https://rhino.fi/) Rhino.fi provides cross-chain liquidity infrastructure for stablecoin onboarding and settlement, enabling seamless deposits and withdrawals across 20+ chains with sub-10-second settlement. Interoperability ### [Rio](https://www.rio.trade/stablecoin-fx) Rio provides real-time stablecoin FX infrastructure for converting between fiat currencies and stablecoins and settling transactions onchain. Orchestration & Ramps, Interoperability ### [Roma Global](https://roma.global) Roma is a fintech that provides stablecoin-native infrastructure for global enterprises - enabling fast, compliant payments, treasury solutions and other digital asset solutions worldwide. Orchestration & Ramps ### [Splits](https://splits.org) Splits builds apps, contracts, and developer tools that make it easy for teams to manage onchain treasuries, revenues, and expenses. Wallets, Developer Tools, Infrastructure ### [SonarX](https://sonarx.com/) SonarX delivers standardized, auditable, and reorg-aware datasets with SOC-grade uptime, featuring standardized schemas — bringing financial system reliability and clarity to on-chain data. Data, Infrastructure ### [Sponge](https://paysponge.com/) Sponge is the easiest way for agents to hold and spend money, and for businesses to sell directly to them. Wallets, Infrastructure ### [SQD](https://www.sqd.ai/) SQD brings high-performance indexing, querying, and data tooling for teams building onchain. Data, Developer Tools ### [Squid](https://www.squidrouter.com/) Squid powers cross-chain swaps and transfers across 100+ chains via API, SDK, and consumer products. Interoperability ### [Symbiosis](https://symbiosis.finance/) Symbiosis is a cross-chain bridge that pools together liquidity from different networks: L1s and L2s, EVM and non-EVM. Interoperability ### [Tenderly](https://tenderly.co) Tenderly is the full-stack Web3 infrastructure and development platform to build, test, monitor, and scale dapps across all major EVM chains. Developer Tools ### [Thunes](https://thunes.com) Thunes is the Smart Superhighway to move money around the world. Thunes' proprietary Direct Global Network allows Members to make payments in real-time in over 130 countries and more than 80 currencies. Orchestration & Ramps, Interoperability ### [TRES](https://www.tres.finance) TRES is the accounting and reconciliation layer for digital asset payments, reconciling onchain settlement against internal and custodial records and delivering outputs in bank-grade formats. Compliance & Fraud ### [TRM](https://trmlabs.com) TRM Labs provides blockchain intelligence to detect, investigate, and disrupt crypto-related fraud and financial crime. Compliance & Fraud ### [Turnkey](https://turnkey.com) Turnkey provides secure private key infrastructure for building wallet and signing experiences. Wallets ### [Ubyx](https://ubyx.xyz) Ubyx enables par-value redemption of stablecoins and tokenized deposits and connects issuers to a global acceptance network. Infrastructure ### [Uniswap](https://app.uniswap.org/) Leading decentralized exchange with over $4T in all-time volume, trusted by millions around the world. Infrastructure, Developer Tools, Wallets ### [UR](https://ur.app/partners/tempo) UR provides infrastructure that connects stablecoins with fiat rails so platforms can build global financial services across account, payment, and card use cases. Orchestration & Ramps ### [Utila](https://utila.io) Utila provides secure digital asset infrastructure for fintechs and enterprises, processing over $15B in monthly volume and securing $100B+ in transactions for 250+ customers. Wallets, Orchestration & Ramps ### [Wirex](https://www.wirexapp.com/) Wirex provides card issuance, wallets, and stablecoin settlement infrastructure. Its integration lets partners use Tempo for enterprise stablecoin card programs. Orchestration & Ramps, Wallets ### [XFX](https://xfx.io) XFX provides institutional FX execution and settlement infrastructure, unifying fiat and stablecoin liquidity into one execution venue (API, web, or OTC) — delivering best price, instant settlement, and zero pre-funding for capital-efficient FX. Orchestration & Ramps ### [ZeroDev](https://zerodev.app) ZeroDev offers smart accounts for ERC-4337 and EIP-7702 along with social logins, gas sponsorship, automation, chain abstraction, and modular wallet components. Developer Tools ### [Zerion](https://zerion.io) Zerion offers wallet infrastructure and real-time token, NFT, and DeFi data APIs, supporting developers and users across Ethereum, Solana, and 50+ EVM networks. Infrastructure, Data ### [Yellowcard](https://yellowcard.io) Yellow Card is the largest licensed stablecoin-based infrastructure provider operating in 20 African countries and the emerging markets. Orchestration & Ramps > Interactive ecosystem tools are available on the HTML page. --- ## Habla con Tempo > Source: https://tempo.xyz/es/contact/ > Language: es # Hablemos Cuéntanos un poco sobre ti y lo que estás desarrollando. Te ayudaremos a descubrir cómo Tempo puede acelerar tu infraestructura de pagos. Para consultas técnicas o soporte, escríbenos a [support@tempo.xyz](mailto:support@tempo.xyz). Para consultas de prensa, escríbenos a [press@tempo.xyz](mailto:press@tempo.xyz) > Interactive contact form is available on the HTML page. --- ## Tempo FAQ | Stablecoin payments, MPP, and technology > Source: https://tempo.xyz/faq/ > Language: en # Frequently asked questions Clear answers about Tempo Mainnet, pathUSD, stablecoin payments, MPP, validators, and the technology behind the network. Tempo fundamentals ## What businesses and developers need to know **What is Tempo?** Tempo is a payments-first Layer 1 blockchain incubated by Stripe and Paradigm, purpose-built for stablecoin payments at scale. It gives businesses and developers a stablecoin-native settlement layer for global payments, including cross-border payments, global payouts, embedded finance, and machine-to-machine payments. Tempo provides high throughput, near-instant onchain settlement, and sub-cent fees for standard stablecoin transfers. Source: [About Tempo](/about/) **Is Tempo Mainnet live?** Yes. Tempo Mainnet has been live since March 18, 2026. Its chain ID is 4217, and its public RPC endpoint is https://rpc.tempo.xyz. Moderato, chain ID 42431, is Tempo's separate public testnet. Sources: [Tempo Mainnet launch](/blog/mainnet/), [Network connection details](/developers/docs/quickstart/connection-details) **Is pathUSD available on Tempo Mainnet?** Yes. pathUSD is a live USD-denominated TIP-20 stablecoin issued by Bridge on Tempo Mainnet. Its mainnet address is 0x20c0000000000000000000000000000000000000. Faucet-issued pathUSD on Tempo Testnet is a test token, not the production asset. Sources: [pathUSD documentation](/developers/docs/protocol/exchange/quote-tokens), [Tempo Mainnet launch](/blog/mainnet/) **How is Tempo related to Stripe?** Tempo was incubated by Stripe and Paradigm. Stripe's experience in global payments helped shape Tempo's design for stablecoin payments, while Paradigm contributed crypto and blockchain engineering expertise. Source: [Introducing Tempo](/blog/introducing-tempo/) **How is Tempo related to Paradigm?** Tempo was incubated by Stripe and Paradigm. Paradigm contributed crypto and blockchain engineering expertise that helped shape Tempo's stablecoin-focused architecture. Source: [Introducing Tempo](/blog/introducing-tempo/) **What is the Machine Payments Protocol (MPP)?** The Machine Payments Protocol (MPP) is an open standard for machine-to-machine payments co-authored by Stripe and Tempo. It lets agents, apps, and people pay for services inline with an HTTP request, without requiring advance setup of API keys or billing accounts. MPP is payment-method agnostic and supports stablecoins, cards, and other payment methods. Source: [About MPP](https://mpp.dev/overview) **How does MPP relate to Tempo?** MPP is payment-method agnostic and is not limited to Tempo. Tempo provides one settlement option for MPP stablecoin payments. Tempo's high throughput, dedicated payment lanes, near-instant onchain settlement, and sub-cent fees make it well suited for machine payments. Source: [Tempo payment method](https://mpp.dev/payment-methods/tempo) **Is Tempo decentralized?** Tempo is continuously expanding its active validator set on a path towards permissionless validation. Current validators include MoneyGram, Stripe, Visa, and Zodia Custody by Standard Chartered. The Tempo node software is open source under the Apache 2.0 license. Sources: [MoneyGram validator](/customer-stories/moneygram/), [Tempo validators](/blog/stripe-visa-zodia-join-as-validators/), [Run a validator](/developers/docs/guide/node/validator) **What does Tempo run on technically?** Tempo is a fully EVM-compatible Layer 1 built with the Reth SDK. Developers can deploy Solidity contracts with familiar tools including Foundry and Hardhat. Tempo Mainnet is live. It provides near-instant onchain settlement with no re-orgs, and network fees are paid in supported USD-denominated stablecoins rather than a volatile native gas token. Standard stablecoin transfers have sub-cent fees. Sources: [EVM compatibility](/developers/docs/quickstart/evm-compatibility), [Tempo fees](/developers/docs/protocol/fees) **Who is involved in building Tempo?** Tempo was designed with input from fintechs, banks, and commerce platforms, including Visa, Deutsche Bank, Mastercard, Shopify, Nubank, and Revolut. Stripe, Visa, and Zodia Custody by Standard Chartered are validators on the network. Separately, MPP was co-authored by Stripe and Tempo. Source: [Tempo Mainnet](/blog/mainnet/) **Who leads Tempo?** Tempo is led by founder and CEO Matt Huang, who is also co-founder and managing partner at Paradigm. Source: [Matt Huang at Paradigm](https://www.paradigm.xyz/team/matt-huang) ## Take your stablecoin strategy into production Start using Tempo ### Design your stablecoin product Enterprises Build on Tempo with payments specialists, forward-deployed engineers, and global banking experts. [Talk to our team](/contact/) ### Start building Developers Build on the blockchain engineered for payments, with the tools and docs to bring your product to life. [Tempo API Platform](https://api.tempo.xyz) --- ## Tempo에 문의하기 > Source: https://tempo.xyz/ko/contact/ > Language: ko # 문의하기 현재 어떤 일을 하고 계신지, 무엇을 만들고 계신지 알려주세요. 결제 인프라를 더 빠르게 구축하실 수 있도록 템포가 지원하겠습니다. 기술 관련 문의나 지원이 필요한 경우 [support@tempo.xyz](mailto:support@tempo.xyz) 로 연락해 주세요. 언론 및 취재 관련 문의는 [press@tempo.xyz](mailto:press@tempo.xyz) 로 연락해 주세요. > Interactive contact form is available on the HTML page. --- ## Learn About Stablecoins & Payments | Tempo > Source: https://tempo.xyz/learn/ > Language: en # Guides on stablecoins, blockchain payments, and global money movement ## [Onchain credit: how it works for payments and receivables](/learn/onchain-credit/) Learn how onchain credit works, how it differs from crypto-backed lending, and how stablecoins support payment prefunding and receivables financing. 2026-10-16 ## [What are tokenized stocks? A guide for fintech teams](/learn/tokenized-stocks/) Learn how tokenized stocks work, how ownership rights differ, and what fintech teams need to evaluate across funding, custody, trading, and settlement. 2026-10-16 ## [Bank-issued stablecoins: Creating a cross-network digital asset](/learn/bank-issued-stablecoins/) Explore how bank-issued stablecoins drive efficiency or cause fragmentation. Learn what infrastructure treasurers need for true interoperability. 2026-10-15 ## [Stablecoin liquidity for exchanges: What it takes](/learn/stablecoin-liquidity-for-exchanges/) Find out what goes into reliable stablecoin liquidity for exchanges, from minting and redemption to rebalancing funds across wallets and networks. 2026-10-15 ## [How settlement works with a stablecoin debit card](/learn/stablecoin-debit-card/) Learn how stablecoin debit card settlement works end to end, including what stays on traditional rails, compliance controls, and reconciliation. 2026-10-13 ## [Settling tokenized deposits and RWAs with stablecoin rails](/learn/tokenized-deposits/) Blockchains move tokens; stablecoins move value. Find out how stablecoin settlement serves as the cash leg for tokenized deposits and RWAs. 2026-10-13 ## [Payment reconciliation: Bridging onchain with ERP](/learn/payment-reconciliation/) Stablecoins are changing the payment reconciliation flow. Learn how it's already possible to bring blockchain into today’s ERP and treasury systems. 2026-10-09 ## [Session keys: Speeding up onchain agentic settlement](/learn/session-keys/) Smart accounts smooth out the pain points in blockchain payments. Learn how session keys and gas abstraction support onchain agentic transactions. 2026-10-09 ## [SWIFT message types (MT) and ISO 20022 MX for developers](/learn/swift-message-types/) Learn how SWIFT message types (MT) differ from ISO 20022 MX messages. Find out what developers need to know about formatting, validation, and integrations. 2026-10-09 ## [AI payment processing: How agents pay for APIs with MPP](/learn/ai-payment-processing/) As agents access paid APIs, AI payment processing is a necessity. Learn how MPP can help support smooth agentic micropayments for premium APIs. 2026-10-07 ## [What is Open USD (OUSD)?](/learn/open-usd-ousd/) Learn how Open USD (OUSD) works, including its reserves, shared economics, governance, and uses for payments, settlement, and treasury. 2026-10-07 ## [Global payouts for neobanks: Faster, more predictable settlement with stablecoins](/learn/global-payouts-for-neobanks/) See how stablecoin rails can make global payout costs more predictable for neobanks by reducing settlement intermediaries, simplifying reconciliation, and keeping network-layer fees low. 2026-09-18 ## [Bringing global batch payments onto stablecoin rails](/learn/batch-payments/) Learn how Tempo helps teams run batch and scheduled cross-border payouts with programmable execution, predictable stablecoin-denominated costs, and reconciliation-ready payment records. 2026-09-10 ## [Rethinking GPU marketplaces for real-time agentic payments](/learn/gpu-marketplace/) GPU marketplaces are moving toward fine-grained, usage-based compute. Learn how MPP and Tempo help agents discover services, authorize budgets, and settle stablecoin payments. 2026-09-10 ## [Stablecoin settlement: An enterprise evaluation guide](/learn/stablecoin-settlement/) Stablecoin settlement infrastructure should be evaluated on finality, fees, reconciliation, policy controls, and fit with existing payment workflows. Learn how Tempo approaches each layer. 2026-09-10 ## [The true cost of correspondent banking services for payouts](/learn/correspondent-banking-services-for-payouts/) Learn how correspondent banking works, where the costs compound, and how stablecoin rails can reduce the operational burden of global payouts. 2026-09-04 ## [What stablecoin payment infrastructure needs to work at enterprise scale](/learn/stablecoin-payment-infrastructure-enterprise-scale/) A guide to evaluating stablecoin infrastructure for enterprise-scale payments, from settlement finality to compliance and reconciliation. 2026-09-04 ## [How stablecoin rails help Banking-as-a-Service scale globally](/learn/stablecoin-rails-banking-as-a-service/) Learn how stablecoin rails help Banking-as-a-Service platforms scale global settlement, reconciliation, and programmable payment workflows. 2026-09-04 ## [How much are wire transfer fees?](/learn/wire-transfer-fees/) International wire transfer fees include sending and receiving fees, correspondent-bank charges, FX spreads, settlement delays, and more 2026-09-03 ## [Confidential B2B settlement on stablecoin rails](/learn/b2b-payment-processing/) Are digital ledgers the next level for enterprise payments? Find out what the future of B2B payment processing is with privacy-preserving blockchains. 2026-08-24 ## [Cross-border payments in Latin America: where stablecoin rails fit](/learn/cross-border-payments-latin-america/) How stablecoin rails help businesses improve cross-border payroll, marketplace settlements, treasury operations, and supplier payments across Latin America. 2026-08-24 ## [Embedded finance for gig economy payments: a payout-routing blueprint](/learn/embedded-finance-gig-economy-payments/) Learn why gig economy payments need embedded payout routing, automated money movement, and reconciliation-ready infrastructure for global contractors. 2026-08-24 ## [Can stablecoins and tokenized deposits coexist?](/learn/stablecoins-and-tokenized-deposits/) Are tokenized deposits competing with B2B stablecoin payments? Compare the differences between these digital assets, and see how they coexist in the market. 2026-08-24 ## [Managing payout complexity for global payroll processing companies](/learn/managing-payout-complexity-global-payroll/) Explore how global payroll processing companies use stablecoin rails to cut cross-border settlement costs, speed up payments, and simplify reconciliation. 2026-08-20 ## [402 Payment Required: the emerging agentic payment pathway](/learn/402-payment-required/) The long-neglected 402 Payment Required is finally having its day thanks to machine-to-machine commerce. Learn what 402 means and how it fits into AI payments. 2026-08-19 ## [How to accept stablecoin payments: integration for B2B companies](/learn/how-to-accept-stablecoin-payments/) Learn how to accept stablecoin payments by integrating with Tempo. Unlock faster settlement, programmable payment logic, and easy reconciliation. 2026-08-19 ## [A guide to stablecoin payroll for global teams](/learn/stablecoin-payroll-for-global-teams/) Learn how stablecoin payroll works, why companies are exploring it for global teams, and the infrastructure required to support compliant payroll operations. 2026-08-19 ## [Beyond sponsor banks: a new era for embedded finance platforms](/learn/beyond-sponsor-banks/) Explore challenges facing sponsor-bank embedded finance platforms and how direct stablecoin infrastructure offers a predictable alternative. 2026-08-07 ## [Blockchain payments: how they work and why enterprises are adopting them](/learn/blockchain-payments/) How blockchain payment infrastructure works, why enterprises are adopting it for global money movement, and how it compares to traditional rails. 2026-05-04 ## [Tokenized deposits and stablecoins for corporate treasury](/learn/corporate-treasury-tokenized-deposits/) How tokenized deposits and stablecoins help treasury teams move liquidity onchain, improve cash visibility, and reduce working capital trapped in transit. 2026-05-04 ## [Cross-border payments with stablecoins](/learn/cross-border-payments/) How stablecoins enable faster, cheaper cross-border payments without correspondent banks, SWIFT delays, or pre-funded accounts. 2026-05-04 ## [Global payouts with stablecoins: a guide for platforms and enterprises](/learn/global-payouts/) How to deliver instant, low-cost global payouts to contractors, merchants, and partners worldwide with stablecoins. 2026-05-04 ## [Microtransactions with stablecoins: sub-cent payments at scale](/learn/microtransactions/) Enable true pay-per-use pricing with sub-cent stablecoin payments for APIs, content, IoT, and machine-to-machine commerce. 2026-05-04 ## [Payment rails compared: ACH vs wire vs SWIFT vs stablecoins](/learn/payment-rails/) Compare ACH, wire transfers, SWIFT, and stablecoin payment rails side by side for cost, speed, finality, and global reach. 2026-05-04 ## [Stablecoin payments: how they work, benefits, and risks](/learn/stablecoin-payments/) Learn how stablecoin payments work, where businesses use them, and what to evaluate across settlement, costs, compliance, and operations. 2026-05-04 ## [Stablecoin payroll for funding and global payouts](/learn/stablecoin-payroll/) Learn how payroll providers can use stablecoins for account funding, cross-border payouts, and employee wallets, plus what to evaluate before integrating. 2026-05-04 ## [Stablecoins for business: a practical guide for finance teams](/learn/stablecoins-for-business/) A practical guide for treasury, finance, and operations teams evaluating stablecoins for payments, treasury management, and global operations. 2026-05-04 ## [What are stablecoins? A guide for finance teams](/learn/what-are-stablecoins/) Learn what stablecoins are, how they maintain value through reserves, and the payment use cases they enable for businesses globally. 2026-05-04 --- ## 402 Payment Required: the emerging agentic payment pathway > Source: https://tempo.xyz/learn/402-payment-required/ > Language: en _HTTP 402 gives servers a standard way to tell clients that payment is required. AI agents are giving the long-dormant status code a practical role as protocols such as the [Machine Payments Protocol](https://mpp.dev/) make payments part of the application flow._ Some HTTP status codes show up daily: 200 OK, 403 Forbidden, and the dreaded 404. Then there is 402 Payment Required. It has been reserved since the early days of the web, yet it almost never appears in practice. Human-friendly payment tools such as checkout pages took over, and 402 sat unused. AI agents are changing that. Agentic commerce is giving this dormant status code a second life. With protocols such as the Machine Payments Protocol (MPP), 402 has a real path to becoming a standard signal for AI-powered transactions. ## What is HTTP 402 Payment Required? 402 means a server wants payment before it hands over a resource. It sounds like it should be one of the most common codes on the web. History had other plans. ### What was 402's original purpose? HTTP's designers reserved 402 to make online payments simpler: one common status code that websites and APIs could use as part of a payment mechanism rather than building every flow from scratch. ### Why was 402 never used? Online payments grew up around people: subscriptions, checkout pages, and third-party gateways. Browsers never added native support for 402 or a standardized payment workflow, so the code sat idle for three decades. ### Why the renewed attention on 402? AI agents need to buy digital services without waiting for a person to click through a checkout page. A machine-readable signal such as 402 removes those manual, people-focused steps from the transaction flow. ## Why AI agents create a new payment problem Today's payment infrastructure assumes a person is in the loop. That model worked for decades. It breaks down for agentic commerce in three ways. ### API access assumes a long-term relationship Signing up for an API usually means creating an account, entering billing details, choosing a pricing plan, and generating keys. That works for a long-term commitment. It is overkill for an agent that needs a temporary data feed. With a 402 workflow, an agent can pay for what it needs without a subscription or a stored API key. ### Agents buy resources dynamically Many agent purchases are one-offs: premium financial data, a burst of GPU compute, or a single tool call. These transactions may cost only a few cents. Subscription billing was not designed for that pattern. ### The internet lacks a native payment layer The internet has standardized protocols for sending messages, transferring files, and exchanging data between applications. Payments never received an equivalent application-layer standard. When a website or API wants to charge for access, it sends users to an external payment provider or a custom billing system. That is mildly inconvenient for a person and a major obstacle for an AI agent. ## How 402 Payment Required works in modern payment architectures Several payment protocols integrate with HTTP 402. The basic flow looks like this: |Step|What happens| |-|-| |Client request|An AI agent requests access to a digital resource or API.| |Server returns 402 Payment Required|Instead of supplying the resource, the server says the client must pay a fee.| |Payment requirements provided|The response includes the price, accepted payment methods, and other details needed to pay.| |Payment execution|The client completes the payment using a compatible system or protocol.| |Resource delivered|After confirming payment, the client retries the request and receives the resource or dataset.| ### Payment becomes part of the application flow With 402, payment becomes a step inside the service's workflow. The client can pay based on usage, and pricing can change with demand or complexity. This enables revenue models such as pay-per-request APIs that subscription billing cannot support efficiently. ## How programmable protocols work with 402 workflows 402 only signals that payment is required. To communicate the requirements and confirm the transaction, servers need a programmable payment protocol such as MPP. ### Why MPP works for machine-to-machine payments Tempo and Stripe created the [Machine Payments Protocol](https://mpp.dev/) to give machine-to-machine commerce a standard payment language. Agents can understand what to pay, how to pay it, and whether the transaction is confirmed without a person approving each step. Developers set parameters such as spending limits, approved merchants, and transaction types. Agents make purchasing decisions within those bounds in real time. The protocol has a simple, extensible core that remains neutral to the underlying payment method: - **An open standard built for the internet.** MPP is an open specification proposed to the IETF, not a proprietary API. Its [payment protocol specifications](https://paymentauth.org/) are public. - **Designed for payments.** Idempotency, security, and receipts are first-class primitives. - **Compatible with stablecoins, cards, and bank transfers.** One protocol can support payment methods and assets including USD, EUR, BRL, USDC.e, and BTC. - **Composable by design.** The core can accommodate advanced flows such as disputes and additional primitives such as identity over time. Stablecoin payments settle on a blockchain built for payments, so confirmation is independently verifiable. That control matters as agents move from single API calls to ongoing commercial relationships. MPP supports both one-off transactions and recurring sessions. ## Why 402 matters beyond any single protocol 402 provides a common HTTP signal that payment is required. Programmable protocols can then define the payment flow without sending a client away from the application. The result is a reusable pattern for machine-readable payments, even when developers choose different methods and rails. ## Why stablecoin payment rails are part of the conversation 402 defines how a server asks for payment. The rails underneath determine how quickly and cheaply that payment settles. As developers compare transaction fees and settlement speeds, stablecoins are a natural fit. ### Internet-native payment infrastructure Stablecoin payments move on public blockchains. They can operate across borders without bank operating hours and manual reconciliation between each intermediary. That gives machine-to-machine payments a settlement layer that is available around the clock. ### Programmable money for programmable systems Agents can make real-time decisions, such as switching APIs or datasets in the middle of a task. Their payment system has to keep up. Stablecoins let developers enforce payment rules in software, without requiring manual approval for every transaction. ### Rails built for agentic commerce Agentic commerce involves frequent, low-value transactions between systems. Traditional rails carry fixed costs and settlement delays that make this pattern difficult. Stablecoins provide global infrastructure with a settlement layer that lives in software. Learn more about how [blockchain payments work](/learn/blockchain-payments). ## 402's future: from placeholder to payment standard Demand for standardized agentic payments, together with protocols such as MPP, can make 402 Payment Required a familiar part of a developer's workflow. Tempo co-authored MPP with Stripe and built the settlement layer underneath it. Together, MPP and Tempo's layer-one blockchain give AI agents a path to stablecoin settlement for API access, datasets, compute, and other digital services. [Contact Tempo](/contact) to discuss building for the agentic economy. --- ## Frequently asked questions **Why was 402 Payment Required never widely adopted?** The web evolved around people-focused payment tools such as checkout pages and subscriptions. Browsers never added native support for 402 or a standardized payment workflow, so the status code had no common mechanism to activate. **Why do AI agents need payment infrastructure?** Agents need to understand and pay for resources such as premium APIs or compute in seconds, without waiting for a person to complete a checkout flow. **What is machine-to-machine commerce?** Machine-to-machine commerce is software finding and purchasing digital services from other software automatically, based on programmed rules and real-time needs. --- **Continue learning:** [Microtransactions](/learn/microtransactions) · [Blockchain payments](/learn/blockchain-payments) · [Stablecoin payments](/learn/stablecoin-payments) --- ## AI payment processing: How agents pay for APIs with MPP > Source: https://tempo.xyz/learn/ai-payment-processing/ > Language: en AI agents are already active online. In PwC’s 2025 survey, [79% of surveyed executives](https://www.pwc.com/us/en/tech-effect/ai-analytics/ai-agent-survey.html) said their companies were adopting AI agents. [A study of 177,436 MCP tools](https://arxiv.org/abs/2603.23802) also found that the share of action tools rose from 27% to 65% of total usage over a 16-month period. Most supported tasks like editing files, but some enabled higher-stakes activities such as financial transactions. As agents take on more work, they need a way to pay for the services they use. One of the major pain points in AI payment processing is the human-centric nature of these workflows. When an AI agent needs one-time API access, it has to deal with cumbersome onboarding flows, API key generation, and subscriptions tied to a human account. The [Machine Payments Protocol (MPP)](https://mpp.dev/), co-authored by Stripe and Tempo, gives agents a machine-readable way to pay for API access. Developers can use its shared payment flow to charge for a single request, ongoing usage, or recurring access. ## What MPP is MPP is an open protocol for machine-to-machine payments. When an AI agent requests a paid service, the server returns machine-readable payment instructions that the client can fulfill using a supported payment method. At the heart of the HTTP flow is the [HTTP 402 Payment Required](https://tempo.xyz/learn/402-payment-required/) status code. MPP uses this response to tell an agent that a resource requires payment and provide the terms needed to complete it. ## How MPP works MPP supports different [payment rails](https://tempo.xyz/learn/payment-rails/) and billing models, including [sessions](https://tempo.xyz/blog/mpp-sessions/) for ongoing usage. The basic HTTP workflow follows five steps. ### Step one: Request The MPP process begins when an AI agent submits an HTTP request for a digital service like an API response or a dataset. ### Step two: Challenge Next, the server responds with a 402 Payment Required status code. This lets the agent know that the data is available if it pays the applicable fee. Along with this response comes a machine-readable payment challenge complete with details on how much access costs and ways to pay. ### Step three: Fulfillment The client checks the payment terms against its configured budget and permissions, then fulfills the challenge using a supported payment method. If the terms exceed those limits or sufficient funds are unavailable, it stops or requests approval. ### Step four: Credential The client creates a payment credential containing the method-specific payment proof or authorization, then retries the original request with that credential in the Authorization header. ### Step five: Delivery The server verifies the credential and payment. If verification succeeds, it returns the requested resource and a payment receipt. ## Why MPP matters Here are a few MPP features that make the entire agent payment process smoother: - **Simplified workflows.** MPP brings payment negotiation into the API request-response flow, allowing AI payments to happen within the application. - **Flexible billing.** Providers can [monetize their APIs with microtransactions](https://tempo.xyz/learn/microtransactions/), metered sessions, or subscriptions, depending on the payment method. Clients can pay for a single request or authorize ongoing access. - **Familiar integration points.** Developers can add payment verification to existing API routes using MPP middleware. The application still controls access, request validation, and how the service is delivered. ## The payment rails underneath MPP MPP is [payment-method agnostic](https://mpp.dev/payment-methods/): the same challenge-and-credential flow can work with different payment rails. It is also [transport agnostic](https://mpp.dev/protocol/transports/), with bindings for HTTP, MCP, and WebSockets. The payment method determines how money moves; the transport determines how the client and server exchange messages. Supported payment methods include card payments through Stripe and [digital assets like stablecoins](https://tempo.xyz/learn/what-are-stablecoins/) on Tempo. Developers can choose the method that fits their customers and billing model. ### Fiat and card rails [Stripe’s MPP integration](https://docs.stripe.com/payments/machine/mpp) supports card payments using Shared Payment Tokens. These tokens let an agent initiate a payment without exposing the underlying card details. [Shared Payment Tokens](https://docs.stripe.com/agentic-commerce/concepts/shared-payment-tokens?agent-seller=agent) grant scoped access to a payment method, with usage and expiration limits. The server uses the token to process the payment through Stripe, where it appears alongside the business’s other payments. ### Blockchain rails For frequent API calls, [blockchain payment rails](https://tempo.xyz/learn/blockchain-payments/) can support small payments with near-instant onchain settlement. Tempo is a layer-1 blockchain built for payments, with sub-cent fees for standard stablecoin transfers and network fees paid in supported stablecoins. For high-frequency usage, [MPP sessions on Tempo](https://mpp.dev/payment-methods/tempo/session) let clients authorize multiple payments through a funded channel. Signed offchain vouchers track cumulative spending, and the provider can settle the aggregate onchain. This reduces the need for a separate onchain transaction for every API call. ## Building agent-ready APIs with MPP Developers can add MPP payment verification to existing APIs through middleware or a gateway. The payment flow works alongside the application’s authentication, authorization, and billing logic. Depending on your application, there are three ways of implementing MPP: - **API gateway pattern.** The most straightforward integration is to put MPP in front of your existing API using an API gateway. With this strategy, your gateway manages the payment workflow while your application focuses on serving requests. - **Per-endpoint pattern.** For more fine-grained control over how to monetize your API, you could choose which routes require payment while keeping others free. For instance, if you have premium models or compute-intensive operations, you could trigger an MPP payment flow for these specific use cases. - **MCP tool monetization.** Since many agents already interact with services via the Model Context Protocol (MCP), using an MCP server linked to MPP transforms APIs into on-demand products. When agents invoke a paid tool, the MCP server responds with an MPP payment challenge, creating a new pay-per-use monetization strategy at the protocol level. ## Choosing between one-time payments, sessions, and subscriptions A [one-time payment](https://mpp.dev/intents/charge) fits a single API response, report, or compute job. The server quotes a price, the client fulfills the payment challenge, and the server delivers the resource after verification. [Sessions](https://tempo.xyz/blog/mpp-sessions/) suit repeated requests and metered usage, such as streamed model output. On Tempo, the client funds a payment channel and signs cumulative offchain vouchers as usage grows. The provider can settle those vouchers onchain, making sessions useful for high-frequency micropayments. [Subscriptions on Tempo](https://mpp.dev/payment-methods/tempo/subscription) provide recurring access at a fixed price. The client authorizes recurring payment terms once, and the server can collect at most one charge per billing period. This supports API plans, memberships, and access bundles without a separate payment for every request. ## MPP for AI agents: Making every API call count Human interactions are holding back the agentic economy. While it’s simple enough to create an account or manage API keys, AI agents can’t operate at scale if payment solutions aren’t machine-readable and programmable. MPP is paving the way for developers to bring automation into AI payments through a standard HTTP workflow. The payment protocol works alongside the infrastructure that moves funds. Tempo supports stablecoin payments with near-instant onchain settlement, sub-cent fees for standard transfers, and dedicated payment lanes. With MPP sessions, providers can also meter frequent API calls and settle aggregate usage onchain. See how Tempo can take your [agentic payment strategy](https://tempo.xyz/solutions/agentic-payments/) from concept to reality. ## FAQ **What’s AI payment processing?** In this context, AI payment processing means an agent initiates and completes payments for services within permissions and spending limits set by a person or business. **Do agents need cryptocurrency to use MPP?** No. MPP supports payment methods such as card payments through Stripe, as well as blockchain payments. The available options depend on the methods implemented by the client and server. **What blockchains support MPP for AI agent transactions?** MPP supports stablecoin payments on [Tempo](https://mpp.dev/payment-methods/tempo) and has documented payment methods for other networks, including [Solana](https://mpp.dev/payment-methods/solana) and the [Bitcoin Lightning Network](https://mpp.dev/payment-methods/lightning). Supported assets and billing models vary by payment method. **How do AI agents authenticate and pay for API calls autonomously?** The client fulfills the server’s payment challenge and sends a method-specific credential with its request. The server verifies the payment before delivering the resource. Application authentication and spending permissions remain part of the surrounding integration. **Is MPP a replacement for traditional payment systems?** MPP complements the current payment infrastructure by providing a machine-native way for AI agents to pay for services, but it isn’t a replacement for traditional payment systems. --- ## Confidential B2B settlement on stablecoin rails > Source: https://tempo.xyz/learn/b2b-payment-processing/ > Language: en _B2B payments often depend on banking, ERP, and procurement systems that do not reconcile in real time. Stablecoin rails can reduce settlement time, but public ledgers create privacy problems for enterprise payment flows. [Tempo Zones](/blog/introducing-tempo-zones/) give enterprises a way to transact privately while keeping assets interoperable with existing financial workflows._ Business-to-business payments move through many systems before they settle: procurement tools, invoice approvals, banking portals, ERP records, compliance checks, and reconciliation workflows. Traditional payment rails protect most transaction details from the public, but they often rely on cutoff times, batch windows, and fragmented records. That can slow settlement and leave finance teams matching payment data across disconnected systems. Public blockchains solve one part of that problem by giving participants a shared record. They create a different problem for enterprises: transaction data is public by default. Even when wallet addresses are pseudonymous, payment timing, amounts, counterparties, and transaction patterns can reveal sensitive commercial information. Confidential B2B settlement addresses that gap. It preserves the speed, programmability, and shared verification of stablecoin rails while limiting who can see sensitive payment details. ## What confidential B2B settlement means Confidential settlement does not mean removing accountability. It means the right parties can verify a transaction without exposing commercial terms to the public. For B2B payments, sensitive data may include supplier identities, purchase order references, invoice details, memo fields, pricing, payment volume, and settlement timing. Buyers, suppliers, operators, compliance teams, and auditors may need access to different parts of that information. The public does not. That distinction matters for stablecoin adoption. Enterprises need payments that settle quickly, reconcile cleanly, and remain auditable. They also need to protect customer, vendor, employee, and counterparty information. ## Where traditional and public rails fall short ### Disconnected systems slow reconciliation A single B2B payment can create records across procurement software, bank portals, payment processors, and ERP systems. Finance teams often spend time matching invoices, payment references, bank confirmations, and internal ledger entries after the fact. Delays in reconciliation can slow supplier payments and make cash positions harder to manage. ### Public ledgers expose commercial terms Public blockchains make payment activity visible by default. That shared visibility can simplify verification, but it is often too much transparency for enterprise payment flows. A company settling supplier invoices, payroll, or marketplace payouts may reveal information about payment volume, counterparties, pricing, or business relationships. ### Legacy rails are not built for continuous settlement Banking infrastructure remains essential for regulated money movement. It provides trust, compliance frameworks, local market access, and financial relationships that enterprises rely on. At the same time, cutoff times, batch processing windows, intermediary banks, and regional business hours can slow global settlement. The goal is not to replace banking partners. The goal is to add a settlement layer that moves faster, works globally, and preserves confidentiality where public ledgers do not. ## How confidential settlement works There are several ways to keep sensitive payment data private while preserving verifiability. ### Offchain records Raw invoice data, supplier identities, and internal approval records can remain in private systems. The ledger stores only a reference, commitment, or identifier that proves a transaction occurred without revealing the underlying business data. This approach works well when the payment record needs to link back to existing ERP, procurement, or compliance systems. ### Private execution environments [Tempo Zones](/blog/introducing-tempo-zones/) are private execution environments: EVM-compatible private chains connected to Tempo Mainnet. Within a Zone, participants can transact without exposing transaction details to the public. The visibility model is explicit. The Zone operator can see activity inside the Zone and manages transaction processing and availability. Users can see their own balances and transactions. The public does not see what happens inside the Zone. On Tempo Mainnet, deposits into a Zone expose limited information such as the token, amount, and sender, while the recipient and memo are encrypted. Funds are locked in a Zone contract on Tempo Mainnet and can only be withdrawn by the asset owner. This gives enterprises privacy from the public while preserving interoperability with Tempo Mainnet. ## How programmability improves settlement Stablecoin rails can also reduce operational work after a payment is sent. Payments can include structured references that connect settlement activity to invoices, purchase orders, customer IDs, or internal records. That helps systems on both sides recognize and match payment data faster. Programmable payment flows can also trigger settlement after defined events, such as invoice approval, delivery confirmation, or compliance review. For finance teams, that means fewer manual checks, faster reconciliation, and less time spent resolving mismatched records. ## Confidential does not mean unaccountable Enterprise payments still need compliance controls. Privacy protects sensitive business data from unnecessary exposure. Compliance controls define who is allowed to transact and under what conditions. [Tempo's Policy Registry](https://docs.tempo.xyz/protocol/tip403/overview) is part of that control layer. Policy Registry lets Tempo’s native token standard reference transfer policies, such as allowlists and blocklists, that determine who can send and receive tokens. Policies can be shared across multiple tokens, so issuers can manage access controls consistently rather than updating each token separately. That is different from confidentiality. Zones protect transaction details from public visibility. Policy Registry helps enforce transfer policies for compliance and access control. Together, they support private, auditable payment flows without making public transparency the default. ## What enterprises should look for When evaluating confidential settlement infrastructure, enterprises should look beyond settlement speed. - **Confidentiality with clear visibility rules.** The system should define who can see payment details, what appears publicly, and what remains available for audit or compliance review. - **Interoperability.** Private payment environments should not isolate assets or require every counterparty to use a custom network. Enterprises need access to onramps, offramps, liquidity, and existing financial workflows. - **Compliance controls.** Transfer policies, sanctions controls, allowlists, blocklists, and auditability need to work with the payment flow rather than sit outside it. - **Payment-grade performance.** Global payment systems need predictable fees, high availability, and fast finality across time zones. - **Reconciliation support.** Payment data should map cleanly to invoices, purchase orders, ERP records, and internal reporting systems. [Tempo](/) is a layer-1 blockchain built for stablecoin payments. It combines private transaction environments through Tempo Zones with compliance controls through Tempo’s native token standard and Policy Registry. [DoorDash is working with Tempo](/customer-stories/doordash/) on stablecoin-powered payment infrastructure for merchants and Dashers across more than 40 countries, starting with flows where faster and more affordable settlement creates clear value. ## Where privacy meets performance Compliance and confidentiality concerns are one reason enterprises hesitate to use blockchain-based B2B payments. Public ledgers expose more information than many enterprise workflows can tolerate. Traditional rails protect privacy, but they can be slow, fragmented, and difficult to reconcile across markets. Confidential stablecoin settlement gives enterprises another option. Sensitive details can remain private from the public, payment activity can settle quickly, and compliance controls can be enforced as part of the transaction flow. If your team is evaluating stablecoins for institutional settlement or global B2B payment flows, learn more about [Tempo's institutional money movement](/solutions/institutional-money-movement/) or [get in touch with Tempo](/contact). --- ## Frequently asked questions **How can enterprises settle B2B invoices confidentially onchain?** Enterprises can separate business data from settlement verification. Raw invoice details, supplier information, and internal memos can stay in private systems, while the ledger stores a reference, commitment, or proof that supports verification. Tempo Zones add a private onchain environment for transaction execution. They are not offchain storage. They are private execution environments connected to Tempo Mainnet, designed so payment activity inside the Zone is not visible to the public. **Who can see activity in a Tempo Zone?** The Zone operator can see activity inside the Zone and manages processing and availability. Users can see their own balances and transactions. The public does not see transaction activity inside the Zone. On deposits to a Zone, Tempo Mainnet shows limited information such as token, amount, and sender, while recipient and memo details are encrypted. **How does Policy Registry fit into confidential B2B payments?** Policy Registry provides transfer policies for Tempo’s native token standard. It helps issuers define who can send and receive tokens through allowlists, blocklists, and shared policies across tokens. It supports compliance and access control, but it is not itself the privacy layer. **What compliance requirements apply to blockchain-based B2B settlement?** The core requirements are similar to traditional payments. Enterprises still need appropriate controls for Know Your Customer (KYC), Know Your Business (KYB), anti-money laundering (AML), sanctions screening, auditability, and data privacy. Stablecoin rails can change how settlement happens, but they do not remove those obligations. --- **Continue learning:** [Introducing Tempo Zones](/blog/introducing-tempo-zones/) · [Institutional money movement](/solutions/institutional-money-movement/) · [DoorDash customer story](/customer-stories/doordash/) --- ## Bank-issued stablecoins: Creating a cross-network digital asset > Source: https://tempo.xyz/learn/bank-issued-stablecoins/ > Language: en Banks evaluating [U.S. dollar-denominated stablecoins](https://tempo.xyz/learn/what-are-stablecoins/) face a practical question: how can they integrate onchain assets without disrupting existing compliance, custody, and ledger workflows? While bank-issued stablecoins are now a possibility, they’re just one part of a much broader array of digital services, including issuing tokenized deposits, partnering with third-party stablecoin issuers, or providing reserve and custody services. Each of these services comes with unique features and limitations. How institutions and clients use them depends heavily on their underlying architecture and capabilities. Before getting serious about experimenting with these digital assets, learn more about the basics of what they offer and where they fit into the broader ecosystem. ## Bank-issued stablecoins vs. tokenized deposits A fiat-backed stablecoin is designed to maintain a stable value relative to a fiat currency, commonly one token per unit of currency. Its reserve model, redemption rights, and market price depend on the issuer and product terms; a stable value is not guaranteed. The defining feature of bank-issued stablecoins is that financial institutions are the ones who issue these tokens, and the redemption rules depend on the financial institution’s legal structure and the reserve system they use to back their offering. Banks are also involved with digital ledger models, though [tokenized deposits](https://tempo.xyz/learn/tokenized-deposits/) represent a direct liability at a commercial bank just like a traditional deposit. While the digital format expands a tokenized deposit’s potential use cases, the underlying claim is still in the client’s hands. [Central bank money](https://www.bis.org/speeches/20210806-cbdc-solution-search-problem) is a separate category: it is a liability of the central bank, including currency and reserve balances. Commercial banks do not issue central bank money. ## Why do banks issue stablecoins? Corporate treasurers face mounting internal demand for onchain settlement to handle [cross-border payments](https://tempo.xyz/learn/cross-border-payments/), programmatic payouts, and 24/7 liquidity management. Financial institutions issue stablecoins for these operational advantages: - Direct onchain access: Instead of treating onchain transactions as a separate system or leaving the activity to third-party issuers, banks can directly help clients who want to move their money onchain. - Extended network reach: The more networks and counterparties a stablecoin connects with, the more opportunities a bank may have to use it across different geographic markets and currency corridors. - Programmable payment logic: Since stablecoins interact with smart contract commands, they support automated [payment workflows](https://tempo.xyz/learn/stablecoin-payments/) for predefined conditions without requiring constant manual oversight. ## What does interoperability mean for bank-issued stablecoins? At its core, stablecoin interoperability measures how easily value and payment data move across disparate networks, public ledgers, and legacy systems. In the context of bank-issued stablecoins, this can include moving value between different blockchains or exchanging between other [stablecoins or tokenized deposits](https://tempo.xyz/learn/stablecoins-and-tokenized-deposits/). Greater interoperability could also mean expanding outside of a bank’s internal network to a wider range of third-party clients and counterparties. ### Interoperability can expand counterparty reach and operating options For an institution to successfully deploy stablecoins, counterparties must accept them under existing [compliance policies](https://tempo.xyz/blog/compliance-controls/), and the underlying infrastructure must prevent fragmented liquidity. Interoperability can connect stablecoin settlement with traditional payment infrastructure through banks and payment providers. ACH and wire systems handle fiat transfers, while SWIFT carries financial messages. Preserving compliance context and payment references requires integrations between these systems. ## How can bank-issued stablecoins lead to fragmentation? Despite the promise of seamless connectivity, there’s a risk that poor implementation could create a fractured financial experience. Instead of money moving through a shared set of rails, clients using bank-issued stablecoins must navigate unique liquidity arrangements and counterparty accessibility in different issuer-specific systems. When two stablecoins lack integration, moving value requires separate conversion and settlement arrangements, adding unnecessary friction and prefunding costs. There are also operational complexities banks must consider as transactions move between systems. Financial institutions need to preserve key information, such as sender/receiver context and transaction purpose, to satisfy compliance checks and [confidentiality requirements](https://tempo.xyz/learn/b2b-payment-processing/). If this context doesn’t move reliably with the value, banks face time-consuming verification and reconciliation processes. ## When are bank-issued stablecoins not the right fit? Stablecoins don’t automatically boost a bank’s operational efficiency in every context. Before committing engineering and compliance resources, treasury teams should recognize where onchain mechanics offer little to no strategic advantage over existing infrastructure: - Domestic payments are already handled efficiently: If an existing payment rail like ACH or wire already meets speed, cost, and operational requirements, adding a stablecoin layer is probably redundant at best. - Transfers within the same bank or closed network: Adding an extra settlement asset may offer little benefit when both sending and receiving accounts already operate within an internal ledger system. - Limited acceptance among key counterparties: A stablecoin becomes operationally cumbersome when businesses or institutions in a bank’s network refuse to support the asset, wallet environment, or redemption process. - Unclear custody or regulatory requirements: Institutions can’t adopt stablecoins at scale if basic obligations like asset safeguarding, accounting treatment, and cross-jurisdictional compliance remain ambiguous. ## What bank-issued stablecoins need to interoperate across networks The key to making bank-issued stablecoins useful beyond one network is to focus on ways to seamlessly connect these digital assets with the systems clients and counterparties already use to move money. ### Shared standards connect issuers and networks Shared standards provide a common language for payments context across different networks, helping banks avoid custom rules for every integration. Banks and payment providers can then connect stablecoin settlement with traditional bank accounts or tokenized deposits through the relevant funding, redemption, and payout arrangements. [Coastal Financial Corporation is building a cross-border payment corridor on Tempo](https://tempo.xyz/customer-stories/coastal/). In the described design, a sending bank performs KYC/AML screening, sends Coastal the payment instructions, and funds a wallet through a stablecoin issuer. Stablecoins move to Coastal’s wallet on Tempo; Coastal then redeems them, confirms the payment, and credits the recipient’s account in USD. The story describes infrastructure being built, rather than measured live results. It illustrates how banks can change the settlement layer while retaining existing messaging, compliance, and confirmation processes. ### Compliance, custody, and confidentiality determine institutional fit Stablecoin interoperability encompasses a wide range of controls and operational requirements that institutions already rely on, including: - Transaction monitoring: Providing sufficient transaction data and context to support ongoing monitoring for unusual activity and potential financial crimes - Sanctions screening: Ensuring transfers fit screening standards against applicable sanctions and flagging transactions for holds, rejections, or escalations when appropriate - Institutional custody support: Verifying that the selected custody provider supports existing access controls, recovery processes, and multiparty authorization workflows - Auditability: Making it easier to reconcile transactions across networks and maintain clean internal records that support a bank’s regulatory reporting and audit processes ## How Tempo supports stablecoin settlement alongside bank systems Tempo provides a stablecoin settlement layer that banks can integrate with their existing infrastructure. [Transfer memos](https://tempo.xyz/developers/docs/guide/payments/transfer-memos) can carry short payment references that applications map to their internal records, supporting ISO 20022-compatible reconciliation workflows. The memo is a fixed 32-byte field, rather than a complete ISO 20022 message. Memos are public transaction data, so sensitive customer and compliance details should stay in controlled systems. Banks and their providers remain responsible for custody, screening, reconciliation, and fiat funding or delivery. Learn more about how [Tempo’s payments-first settlement layer](https://tempo.xyz/) can help you integrate with stablecoins without compromising your compliance or reconciliation systems. ## FAQ ### Are bank-issued stablecoins regulated or insured like bank deposits? Not necessarily. The regulation surrounding bank-issued stablecoins depends on three factors: their legal structure, the issuing entity, and the jurisdiction they’re issued and used. Just because a bank issues a stablecoin doesn’t mean it automatically carries federal deposit insurance or the same legal standing as a traditional commercial bank deposit. ### Who can redeem a bank-issued stablecoin? Redemption rights differ between bank-issued stablecoins based on the issuer’s model and the terms of the digital asset. Some models may restrict direct redemption to eligible institutional or wholesale counterparties, while others may provide broader access. --- ## Bringing global batch payments onto stablecoin rails > Source: https://tempo.xyz/learn/batch-payments/ > Language: en Global cross-border traditional and crypto payment flows approached $1 quadrillion in 2024, according to the [IMF](https://www.imf.org/en/publications/wp/issues/2025/06/13/global-cross-border-payments-a-1-quadrillion-evolving-market-567604). At that scale, sending payments one at a time is no longer practical. Batch and scheduled payments are already the standard way to move high volumes more efficiently, yet they remain challenging on the backend. Platforms paying global contractors or creators have even more to contend with, constantly balancing foreign exchange (FX) conversions, compliance requirements, and reconciliation across regions. Stablecoin rails can help by adding a programmable settlement layer alongside existing banking partners. Tempo is built for that role: stablecoin-denominated fees, near-instant settlement, payment lanes, batch calls, scheduled transactions, fee sponsorship, passkey authentication, and structured payment data that can make reconciliation easier. To overcome this, more companies are adopting stablecoin rails as a programmable shared settlement layer. Rather than replacing traditional banking infrastructure in cross-border payouts, adding a [stablecoin protocol](/learn/what-are-stablecoins/) offers the scalability and speed needed to make high-volume batch payouts easier in the digital economy. ## What are batch and scheduled cross-border payouts? Batch and scheduled payouts are ways of consolidating a company’s payments. The first method can group hundreds or thousands of transactions into one workflow, while the latter automates when those payouts get sent. As businesses expand internationally, it’s more likely they’ll use both of these payout structures to predictably handle higher volumes of transactions for their contractors, content creators, and suppliers. Marketplace and financial platforms show why this matters. DoorDash operates marketplace payout flows across more than 40 countries and is [working with Tempo](/customer-stories/doordash/) on stablecoin-powered payment infrastructure. [Stripe Treasury stablecoin capabilities](/customer-stories/stripe/) are powered by Tempo, giving businesses access to stablecoin movement from the Stripe Dashboard. These examples show why large platforms need payment infrastructure that can support automated, high-volume flows without making settlement and reconciliation harder. ## What changes cross-border? Cross-border payout programs add complexity that domestic batch runs often do not have: - **Multiple currencies and FX.** Currency conversions, spread, and intermediary fees can create a gap between the amount a platform sends and the amount a recipient receives. - **Corridor-specific routing.** Each market can involve different local rails, bank partners, cutoff times, recipient data requirements, and return processes. - **Screening and transfer controls.** Many payout programs include KYC/KYB, AML, sanctions-screening, and address eligibility workflows that teams need to evaluate with legal and compliance partners. - **Settlement timing.** A payout initiated on the same day for every recipient may still arrive at different times because of weekends, holidays, banking hours, and local cutoffs. - **Reconciliation.** Finance teams need to match each payment to the right invoice, contractor, creator, supplier, or marketplace record. Blockchain can reduce payment complexity by adding a fast settlement layer alongside these existing banking systems. By acting as a high-speed digital settlement layer, blockchain handles the global routing, verification, and instant delivery in the background while working alongside traditional financial institutions. Built as a payments-first Layer 1 blockchain, Tempo lets platforms pay transaction fees directly in supported USD-denominated stablecoins, without requiring a separate volatile gas token. It also reserves dedicated blockspace for payment transactions to prevent traffic congestion and fee spikes, has sub-second finality, and can embed structured invoice data and metadata natively for automated ERP reconciliation. ## How to implement batch and scheduled stablecoin payouts Grouping hundreds or thousands of transfers into one run sounds simple. In practice, the quality of the batch depends on the workflow around it: how data is collected, validated, funded, approved, executed, and reconciled. ### Define the payout model Start by deciding which payment flows should be one-time batch runs and which should become recurring or scheduled workflows. There could be infrequent instances when you need to issue one-time batch payouts, such as a bonus or an off-cycle paycheck. In general, companies favor setting up recurring payouts to improve predictability and reduce manual effort. These payouts can leverage protocol-level features like [Tempo’s scheduled transactions](/blog/tempo-transactions/) for automated time windows, executing biweekly, monthly, or in response to trigger-based events across various corridors and currencies. ### Collect and validate payee and payment data In addition to setting payout timing, platforms need to confirm where payments are going and which requirements apply in each payment corridor. At a minimum, they need basic payee information, such as name, desired currency, and payout method. Depending on the destination, country-specific details such as an International Bank Account Number (IBAN) or UK sort code may also be required, along with standard compliance checks such as KYB and sanctions screening. To support these workflows, a platform’s compliance team can use Tempo tools to help enforce transfer policies after eligibility decisions are made. [TIP-403](https://docs.tempo.xyz/protocol/tip403/spec) allows token issuers to express policy controls such as allowlist or blocklist behavior, while [TIP-20](https://docs.tempo.xyz/protocol/tip20/overview) supports stablecoin transfers with payment-focused features such as memos and fee behavior designed for payment use cases. ### Build and format the batch Next, companies can either upload a payment file or build batches programmatically through APIs. File-based workflows are generally suitable for low-frequency payout runs, while high-volume systems require automated validation and execution. Whichever method a company uses, each payout should include the required recipient and payment information. Before execution, the system should run validation checks, including verifying required fields, matching currencies to corridors, and detecting duplicates. For high-volume systems, [Tempo Transactions](https://docs.tempo.xyz/guide/tempo-transaction) support atomic batch calls, allowing multiple payout operations to execute in a single transaction. That means a platform can group related operations together and reduce partial-execution risk at the transaction level. ### Fund and release the payout run Before release, teams need to decide how payout runs are funded: prefunding an account, funding each run before execution, or using partner infrastructure to coordinate balances. For recipients using supported stablecoins, Tempo can settle transfers directly onchain. Tempo also supports fee sponsorship, allowing a platform or sponsor to pay network fees for recipients. That matters for payout products because recipients can receive the intended payout value without needing to separately manage gas. Passkey support can also make user authentication more familiar while enterprise teams layer in their own custody, approval, and operational controls. For supported stablecoins with available liquidity, Tempo's [native DEX](https://docs.tempo.xyz/protocol/exchange/spec) can simplify stablecoin-to-stablecoin conversion and reduce reliance on intermediary routing. Today, teams should describe this as supported stablecoin conversion rather than a blanket replacement for all FX workflows. ### Track statuses and reconcile A payout run is not complete when the transaction is submitted. Finance and operations teams still need payment statuses, exception handling, retries, and records that can match against internal systems. Tempo's payment-focused design helps here. [TIP-20 payment memos](https://docs.tempo.xyz/protocol/tip20/overview) and payment metadata can carry or reference identifiers such as invoice IDs, contractor IDs, or payout run IDs. Indexers, payment processors, and internal systems can use those records to match settled transfers against ERP, accounting, or payroll systems. ## Cost, security, and operating considerations Global batch payout programs should be designed around both payment execution and operating controls: - **Cost predictability.** Tempo offers sub-cent fees for standard payment transactions, with fees paid in supported USD-denominated stablecoins. See the [fee specification](https://docs.tempo.xyz/protocol/fees/spec-fee) and [native stablecoins documentation](https://docs.tempo.xyz/protocol/tip20/overview). - **Approval workflows.** High-value payout runs often need role-based permissions, approvals, and custody policies before release. - **Screening and transfer policies.** Many programs include AML, KYC/KYB, sanctions-screening, and address eligibility workflows. Tempo policy controls can help enforce decisions, but they do not replace legal or compliance review. - **Jurisdiction-specific requirements.** Each market can involve different reporting, data, account, currency, and local payout requirements. - **Exception handling.** Clear statuses and error codes help teams investigate returned, rejected, or failed payouts and retry them when appropriate. ## How does Tempo support batch and scheduled payments? Tempo primarily supports batch and scheduled payments through [Tempo Transactions](https://docs.tempo.xyz/guide/tempo-transaction). Batch calls let platforms group multiple payout operations into one transaction, while scheduled execution windows help applications release payments at the right time. Fee sponsorship and stablecoin-denominated fees can also reduce gas-management friction for recipients. Tempo was also built for settlement reliability at scale. Dedicated payment lanes help preserve throughput for payment activity, and near-instant settlement with no re-orgs reduces settlement uncertainty. For high-volume payout programs, that means more predictable timing than workflows that depend entirely on bank cutoffs and intermediary settlement windows. Large payout runs also depend on operational readiness. [TIP-20](https://docs.tempo.xyz/protocol/tip20/overview) memos and payment metadata can help match transfers to invoices, contractors, or payout runs, while [TIP-403](https://docs.tempo.xyz/protocol/tip403/spec) policy controls can enforce issuer-defined allowlist or blocklist rules. For sensitive workflows, [Tempo Zones](/blog/introducing-tempo-zones/) can keep payment activity private to the relevant parties and zone operator. Companies are already building on these capabilities. [Coastal](/customer-stories/coastal/) is integrating with Tempo to support stablecoin settlement while preserving KYC/AML policies through address whitelisting. [ARQ](/customer-stories/arq/) is building a cross-border settlement layer with stablecoins for high-volume Latin America flows. ## Settle bulk payments on Tempo's payments-first blockchain Batch and scheduled payouts matter most when companies are handling higher transaction volumes across more markets. Grouping payments together is only one part of the workflow. Teams also need predictable costs, reliable timing, clear payment records, and infrastructure that can work alongside existing banking and payout partners. Tempo adds a programmable settlement layer to that stack. It gives payment companies stablecoin-native execution, batching, scheduling, fee sponsorship, payment lanes, and reconciliation-ready transaction data without requiring users to hold a volatile gas token. Explore [Tempo Transactions](https://docs.tempo.xyz/guide/tempo-transaction) for batching and scheduling, [TIP-20](https://docs.tempo.xyz/protocol/tip20/overview) for stablecoin payment features, or the [payments guide](https://docs.tempo.xyz/guide/payments) to start building. ## FAQ ### Should you implement batch payouts with a file upload or an API? The right approach depends on your company’s current size and how often you send payouts. File uploads can work for low-frequency runs. APIs are usually better for recurring, high-volume payouts because they reduce manual work and make validation, approvals, execution, and retries easier to automate. ### How are failed payouts in a batch handled? Most payout systems validate records before release and return status or error information for failed payments. Teams can then correct recipient data, resolve funding issues, or retry eligible payments. On Tempo, batch calls can also execute atomically at the transaction level, reducing the risk that related onchain operations partially execute. ### How can bulk payments be automated? Companies can automate bulk payments with APIs, payout schedules, and event triggers from internal systems such as ERP, payroll, accounting, or marketplace ledgers. Tempo scheduled transactions add a native execution-window primitive that applications can use as part of those workflows. ### How do businesses integrate bulk payments with their systems? Businesses typically connect payout APIs to systems such as ERP, accounting, payroll, and marketplace databases. Payment memos, transaction metadata, indexers, and processor reporting can help each settled payment match the correct internal record. --- ## Beyond sponsor banks: a new era for embedded finance platforms > Source: https://tempo.xyz/learn/beyond-sponsor-banks/ > Language: en _Embedded finance platforms let fintechs and merchants offer financial services without the regulatory and operational burden of becoming banks themselves. Stablecoin infrastructure gives these platforms a more flexible way to scale while preserving the banking relationships they rely on._ For years, sponsor-bank relationships served as the bedrock of embedded finance. But the market has reached an inflection point, and traditional sponsor-bank models are hitting structural limits. Embedded finance solutions were designed for individual use cases such as deposits, payments, and lending. Today's fintechs, however, are building complex, multiproduct programs. As these platforms scale, they quickly run up against strict regulations, limited capacity, and complex technical coordination. The answer is not to abandon traditional banking relationships. Fintechs need a more flexible way to build. This guide explains how stablecoins complement traditional banking infrastructure to address regulatory and operational challenges that sponsor-bank models were not designed to handle. ## The structural limits of sponsor-bank models Traditional sponsor-bank infrastructure often creates operational challenges when integrated into a modern fintech architecture. ### Regulatory and operational asymmetry Sponsor banks are accountable for the embedded financial services their fintech partners launch. Even when a bank lacks direct control over a fintech's internal policies, regulators hold the bank responsible for compliance requirements such as Know Your Customer (KYC), Anti-Money Laundering (AML), and fraud mitigation. Banks must also support consumer protection outcomes, including transparent fee disclosures and safeguards against algorithmic bias in automated lending. At the same time, traditional ledger systems can limit a sponsor bank's visibility into a partner's real-time transactional risk. Banks may be unable to monitor automated transactions or use early-warning fraud detection systems before funds settle. This data latency makes it harder to implement the proactive risk management that modern regulators expect. In response to intensifying regulatory pressure, many sponsor banks are adjusting partner criteria, managing portfolio capacity more conservatively, or reevaluating their presence in the market. For fintechs, navigating changing bank risk appetites while relying on a single partner introduces concentration risk. [Sponsor banks can also use stablecoin infrastructure to expand their capabilities](/blog/stablecoin-opportunity-for-sponsor-banks). ### The multiproduct infrastructure gap Most sponsor banks excel at managing a single financial service and build their infrastructure around that specialty. Expanding into a multiproduct platform introduces significant integration complexity. Each financial service demands distinct operational workflows and regulatory frameworks: - **Payments.** Integrate with payment processors and configure the right rails for each transaction type. - **Lending.** Define credit decisioning logic, set up loan servicing workflows, and manage funding and capital arrangements. - **Deposits.** Structure deposit accounts, maintain FDIC compliance, and develop reliable reconciliation at scale. - **Cards.** Coordinate with card networks and issuer partners. When a bank partner specializes in one product line, fintechs must choose between narrowing the initial product roadmap or managing multiple specialized partner banks behind the scenes. ### Speed and capacity constraints Integrating with specialized sponsor-bank platforms introduces several scaling constraints: - **Variable approval timelines.** Platforms invest time in compliance technology and prototypes before knowing whether a bank will approve the program. - **Evolving compliance scope.** Product requirements change as the sponsor bank assesses long-term risk and compliance needs. - **Unanticipated adjustments.** Ongoing reviews alter product roadmaps and launch schedules. - **Rigid capacity limits.** Banks may cap or pace user onboarding when programs reach internal risk thresholds. Fintechs do not need to abandon traditional banking relationships. They need a more adaptable framework, either by partnering with an agile sponsor bank that evaluates programs quickly or by adopting infrastructure that complements existing bank relationships. ## Why embedded finance platforms are moving toward direct infrastructure Adding direct stablecoin infrastructure to an existing technology stack can address transactional challenges that traditional banking was not designed to handle. This hybrid approach lets fintechs bypass legacy bottlenecks for fast money movement while partner banks focus on regulated financial functions. ### Core drivers for stablecoin adoption Fintech platforms generally choose stablecoin rails for three reasons: - **Cross-border speed.** Traditional banking can require multiple business days to settle global transactions. Stablecoin infrastructure can route international payments in under a second. - **Movement programmability.** Engineering teams can write automated, multiparty routing rules directly into their payment logic. - **Cost predictability.** [Tempo Mainnet](/blog/mainnet) charges dollar-denominated transaction fees based on gas consumption, making network costs predictable. ### Flexible implementation frameworks Stablecoin infrastructure supports several implementation models: - **Direct onchain settlement.** Move transaction clearing onto a blockchain to access stablecoin performance without routing every transaction through a sponsor-bank interface. - **Hybrid architecture.** Keep banking rails for regulated operations such as lending and ACH transfers while routing global payouts through stablecoin rails. - **API-first settlement.** Replace manual approval cycles with automated messages that accelerate multiproduct roadmaps. - **Unified multiproduct infrastructure.** Route transactions through cohesive infrastructure instead of patching together separate bank ledgers for individual products. Tempo supports each of these approaches with native compliance controls, flexible APIs, and automated settlement modules. DoorDash chose Tempo for stablecoin-powered payouts across more than 40 countries, each with distinct regulatory requirements and foreign exchange dynamics. [Read the DoorDash customer story](/customer-stories/doordash/). ## How fintechs move beyond sponsor-bank structures Fintechs use several strategies to work around the limits of the sponsor-bank model. These alternatives give teams more control over settlement speed, costs, and product development. ### Alternatives to sponsor-bank structures - **Direct stablecoin networks** provide a direct path to fast transaction finality, predictable network costs, and programmable settlement logic. - **Direct processor integrations** remove the banking-as-a-service middleware layer. Connecting core systems directly to payment processors such as Stripe gives fintechs more control over their technology stack. - **Hybrid rail ecosystems** combine traditional banking lines with stablecoin infrastructure. The user experience can remain familiar while stablecoins handle settlement in the background. - **Institutional custody partners** such as BitGo and Cactus secure wallet access, protect stablecoins, and may offer insurance against certain losses. Regulated custodians also support requirements such as KYC and SOC 1 and SOC 2 controls. ### Why fintechs choose direct infrastructure Several market dynamics make it difficult for scaling platforms to rely exclusively on sponsor-bank models: - **Regulatory pressure.** Tighter partner criteria and portfolio limits create operational uncertainty and new compliance hurdles. - **Global demand.** Traditional settlement paths slow international expansion with multiday delays and fragmented banking systems. - **Margin pressure.** Predictable costs matter as the embedded finance market grows more competitive. - **Reconciliation gaps.** Separate bank partners create fragmented ledgers that limit multiproduct scalability. ## Can sponsor banks and stablecoin infrastructure work together? Yes. Fintechs that use stablecoin settlement are adding a layer to their existing payment ecosystem, not replacing traditional banking rails. Each system is optimized for different functions. ### Where sponsor banks excel The traditional sponsor-bank model remains a strong foundation for: - Regulated deposit taking - Credit extension - Traditional regulatory compliance ### Where stablecoins excel Stablecoins work well for: - Global programmable settlement - Sub-second finality - Predictable costs at scale Learn more about [how stablecoin payments work](/learn/stablecoin-payments). ## Build infrastructure that works with Tempo Scaling fintechs need infrastructure that can support the speed, scale, and global reach their products demand. That requires more than finding a separate partner bank for every financial product. Tempo provides near-instant settlement, predictable USD-denominated fees, and cross-border payments that settle for fractions of a cent. Platforms can use these capabilities without abandoning valuable long-term banking relationships. [Learn how enterprises are building on Tempo](/blog/enterprise). [Settle faster, cheaper, and farther with Tempo](/contact). --- ## Frequently asked questions **Can I use both sponsor banks and stablecoin infrastructure at the same time?** Yes. Stablecoin settlement complements traditional banking rails rather than replacing them. Sponsor banks remain well suited to regulated deposit taking, credit extension, and traditional compliance. Stablecoins support fast, programmable global settlement with predictable costs. **How do I know if direct infrastructure is right for my business?** Direct infrastructure can help if your business is running into sponsor-bank constraints such as capacity limits or slow, expensive global payments. Moving to stablecoin rails does not mean losing access to regulated services such as consumer deposits or ACH. Stablecoin rails can sit alongside traditional banking rails, improving settlement speed while preserving your banking partnerships. **What alternatives exist when sponsor-bank BaaS models hit compliance limits?** When BaaS frameworks reach compliance limits, engineering teams generally consider direct stablecoin settlement infrastructure, hybrid models that combine onchain and traditional rails, or direct integrations between fintechs and processing partners. They may also work with institutional custody and compliance providers. **What are the regulatory risks of sponsor-bank embedded finance models?** The core risk is compliance asymmetry. Sponsor banks carry responsibility for KYC, AML, and fraud prevention, so regulatory pressure can lead them to tighten onboarding, reduce capacity, or close embedded finance programs. If a bank retreats, a fintech that relies on one partner for most of its financial services faces an immediate single point of failure. --- **Continue learning:** [Stablecoin Payments](/learn/stablecoin-payments) · [Stablecoins for Business](/learn/stablecoins-for-business) · [Global Payouts](/learn/global-payouts) --- ## Blockchain payments: how they work and why enterprises are adopting them > Source: https://tempo.xyz/learn/blockchain-payments/ > Language: en _Blockchain payments are rapidly moving from experimental technology to core enterprise infrastructure. For global businesses, blockchain-based payment rails offer what traditional systems cannot: instant settlement, 24/7 availability, programmable compliance, and dramatic cost reduction on cross-border transfers._ ## What are blockchain payments? Blockchain payments are value transfers executed on distributed ledger networks. Instead of routing money through chains of intermediary banks, a blockchain payment moves value directly from sender to recipient on a shared, cryptographically secured ledger. In practice, this means: - **No intermediaries.** Payments move point-to-point rather than through correspondent banks, payment processors, and clearinghouses. - **24/7 operation.** Blockchains run continuously: no banking hours, no cutoff times, no weekend delays. - **Programmable logic.** Payment rules, compliance checks, and settlement conditions can be encoded directly into the transaction. - **Transparent record.** Every transaction is recorded on a shared ledger, creating an immutable audit trail. For enterprise payment teams, blockchain infrastructure represents a fundamental upgrade to how money moves, particularly across borders. ## How blockchain payments differ from traditional payments Traditional payment systems were built in an era of batch processing, overnight settlement, and national borders. A cross-border wire passes through your bank, one or more correspondent banks, a clearing system, and the recipient's bank, each adding time, cost, and failure risk. ||Traditional rails|Blockchain payments| |-|-|-| |**Settlement**|1–5 business days|Seconds| |**Availability**|Banking hours|24/7/365| |**Intermediaries**|2–5 per transaction|0–1| |**Cost (cross-border)**|$10–40+ per transaction|Sub-cent to $0.01| |**Audit trail**|Fragmented across institutions|Single immutable ledger| |**Programmability**|Limited|Native| The difference is most dramatic for cross-border payments, where correspondent banking adds the most cost and delay. For a detailed comparison of specific rails, see our guide on [payment rails compared](/learn/payment-rails). ## Why blockchain payments increasingly means stablecoin payments Early blockchain payments used volatile cryptocurrencies (Bitcoin, Ether), which introduced exchange rate risk that made them impractical for business use. A payment could lose 5% of its value between initiation and receipt. Stablecoins solved this. By pegging to fiat currencies like the US dollar, stablecoins deliver the settlement advantages of blockchain without the volatility. Today, when enterprises talk about "blockchain payments," they almost universally mean [stablecoin payments](/learn/stablecoin-payments). Stablecoin transaction volumes now exceed those of major card networks for certain categories of cross-border transfers. The technology has moved from proof of concept to production infrastructure. ## Key enterprise use cases ### B2B settlement Inter-company payments (between subsidiaries, vendors, or trading partners) settle instantly onchain instead of waiting for correspondent banking cycles. This is particularly valuable for companies managing cash across multiple jurisdictions. See our [corporate treasury guide](/blog/corporate-treasury). ### Supply chain payments Manufacturers and distributors can execute payments at each stage of the supply chain with programmable settlement conditions, real-time tracking, and instant confirmation. ### Cross-border transfers The highest-impact use case. Stablecoin payments bypass the correspondent banking system entirely, reducing costs by [60–80%](/blog/ach-vs-wire-vs-stablecoins-a-guide-for-finance-teams) and settling in seconds instead of days. Read our [cross-border payments guide](/learn/cross-border-payments). ### Treasury operations Treasury teams use blockchain rails to move funds between entities in real time, improving cash positioning and eliminating the working capital trapped in multi-day settlement cycles. Learn more in our [corporate treasury guide](/blog/corporate-treasury). ## The infrastructure stack Enterprise blockchain payments require several infrastructure layers working together: - **Wallets and custody.** Secure storage for stablecoin balances, ranging from embedded wallets in applications to institutional-grade custody solutions. - **On/off-ramps.** Services that convert between fiat currency and stablecoins, connecting traditional banking to blockchain rails. - **Compliance tooling.** Sanctions screening, transaction monitoring, and Travel Rule compliance integrated into the payment flow. - **Blockchain networks.** The underlying settlement layer that processes and finalizes transactions. Not all blockchains are equal: the choice of network determines speed, cost, privacy, and compliance capabilities. ## Evaluating blockchain payment infrastructure Not all blockchain networks are built for payments. When evaluating infrastructure, enterprise teams should assess: ### Throughput The network must handle your transaction volumes without congestion or degraded performance. General-purpose blockchains built for DeFi and trading may face throughput limitations during peak periods. ### Fees Fees should be predictable and denominated in stable assets. Networks that require volatile gas tokens introduce cost uncertainty and balance sheet complexity. On Tempo, fees are paid in [stablecoins](/blog/stablecoin-fees), with no volatile tokens required. ### Finality Sub-second finality is critical for payments. Blockchains with probabilistic finality (where transactions could theoretically be reversed) introduce settlement risk. ### Compliance features The network should support the compliance controls your business requires. Native support for sanctions screening, transfer restrictions, and Travel Rule compliance at the protocol level is essential for regulated payment flows. ### Privacy Enterprise payments require confidentiality. Transaction data should not be visible to competitors and the public. Evaluate whether the network supports private transactions for sensitive payment flows. ## Why Tempo is purpose-built for payments Tempo was designed from the ground up for payment use cases, with input from leading financial institutions and enterprise payment teams: - **Sub-second finality.** Transactions settle in under a second with deterministic finality. No waiting, no uncertainty. - **Stablecoin fees.** Pay transaction fees in the same stablecoin you're transferring. No volatile gas tokens, no separate token management, no crypto on your balance sheet. [Learn how](/blog/stablecoin-fees) - **Native compliance controls.** [TIP-20](/blog/compliance-controls) provides built-in functions for pause, freeze, allowlists, blocklists, and Travel Rule compliance as protocol-level capabilities, not bolted-on smart contracts. - **Privacy with Tempo Zones.** [Tempo Zones](/blog/introducing-tempo-zones) enable payment confidentiality where only the parties to a transaction see the details. - **Enterprise-grade throughput.** Dedicated payment lanes ensure guaranteed throughput for enterprise payment volumes without competing with other network activity. - **Ecosystem.** Tempo's [ecosystem](/ecosystem) includes stablecoin issuers, banks, exchanges, compliance providers, and orchestration platforms: the complete stack for enterprise payments. For enterprise payment teams, this means a single blockchain can handle settlement, compliance, and privacy without stitching together multiple providers. ## Why this matters for finance teams Blockchain payment infrastructure is no longer experimental. Companies like [DoorDash](/blog/doordash-partners-with-tempo-to-bring-stablecoin-payments-to-its-global-marketplace), [Stripe](/blog/stripe-and-tempo-stablecoin-settlement-for-global-money-movement), and [Coastal Bank](/blog/coastal-bank-partners-with-tempo-to-build-stablecoin-settled-cross-border-payments) are running production payment flows on blockchain rails. The infrastructure decision you make today (which blockchain, which partners, which integration approach) will shape your payment operations for years. The right choice is infrastructure purpose-built for payments, not repurposed from trading or DeFi. If your team is evaluating blockchain payment infrastructure, [contact Tempo](/contact) to discuss your requirements. --- ## Frequently asked questions **Are blockchain payments the same as crypto payments?** Not exactly. "Blockchain payments" refers to value transfer on distributed ledger networks, but enterprise blockchain payments almost exclusively use stablecoins, digital dollars pegged 1:1 to fiat currencies, not volatile cryptocurrencies like Bitcoin or Ether. The technology is blockchain, but the payment experience is dollar-denominated and stable. **Do I need cryptocurrency to make blockchain payments?** No. On Tempo, transaction fees are paid in [stablecoins](/blog/stablecoin-fees), not volatile tokens. With orchestration providers like Bridge, BVNK, or ZeroHash, your business sends fiat from your bank account and the recipient receives fiat. Stablecoins handle the transfer in the middle. You never need to buy, hold, or manage cryptocurrency. **Is blockchain payment data public?** On most public blockchains, yes: all transaction data is visible to anyone. This is a dealbreaker for enterprises that require payment confidentiality. Tempo addresses this with [Tempo Zones](/blog/introducing-tempo-zones), which enable private payments where only the counterparties see transaction details. This brings blockchain payments in line with the confidentiality expectations of traditional financial infrastructure. **What about speed and scalability?** Modern payment-optimized blockchains like Tempo settle transactions in under a second with throughput designed for enterprise volumes. This is a step change from earlier blockchains. Bitcoin takes ~10 minutes per block, Ethereum ~12 seconds. Tempo's dedicated payment lanes provide guaranteed throughput without congestion from other network activity. **How do blockchain payments compare to real-time payment systems like FedNow?** Real-time payment systems like FedNow or SEPA Instant operate within a single country and currency. Blockchain payments are natively global, multi-currency, and operate 24/7/365 without reliance on banking infrastructure. They also support programmable compliance and settlement logic. The two are complementary: use domestic real-time rails for local payments and blockchain rails for cross-border transfers where traditional systems add the most cost and friction. **Is blockchain payment infrastructure regulated?** Yes, and increasingly so. The GENIUS Act in the US and MiCA in the EU establish regulatory frameworks for stablecoins, the primary payment instrument on blockchain rails. Blockchain infrastructure providers like Tempo build native compliance controls (sanctions screening, transfer restrictions, Travel Rule support) directly into the protocol. --- **Continue learning:** [Stablecoin Payments](/learn/stablecoin-payments) · [Payment Rails Compared](/learn/payment-rails) · [Stablecoins for Business](/learn/stablecoins-for-business) --- ## Tokenized deposits and stablecoins for corporate treasury > Source: https://tempo.xyz/learn/corporate-treasury-tokenized-deposits/ > Language: en _Global treasury teams lose working capital to settlement delays, trapped liquidity, and fragmented visibility across banks and time zones. Tokenized deposits and stablecoins solve this with 24/7 onchain liquidity movement, simplified reconciliation, and real-time cash positioning. [Contact us](/contact) to discuss how these tools fit your treasury operations._ ## The challenge with traditional treasury Corporate treasury operations at multinational companies share a common set of constraints. Cash moves slowly across borders. A payment to a subsidiary might take days to clear. Cash collected in one region sits idle over the weekend while banks are closed. Exchange rates shift, fees accumulate, and finance teams operate on stale data. These constraints create three material problems: - **Higher borrowing costs** from trapped cash that cannot be deployed efficiently. McKinsey estimates trapped capital in pre-funded nostro accounts represents 34% of international payment costs. - **Suboptimal hedging** based on incomplete or delayed data. End-of-day reports from disconnected systems replace the real-time visibility treasury teams need. - **Excess bank fees** for maintaining accounts holding idle liquidity across dozens of banking relationships, currencies, and time zones. Despite access to real-time data elsewhere in the organization, treasury teams often rely on end-of-day reports from disconnected systems. ## How tokenized deposits and stablecoins solve this Both tokenized deposits and stablecoins bring treasury assets onto blockchain rails, enabling capabilities that traditional banking infrastructure cannot deliver. ### 24/7 liquidity movement Blockchain networks never close. Treasury teams can move liquidity between subsidiaries on weekends, holidays, and outside banking hours. A Friday evening onchain transfer from New York to a subsidiary in Singapore can settle near-instantly. Conversion and bank payout timing depend on the providers involved. ### Simplified reconciliation Onchain transactions combine payment and settlement into a single event. This creates a transparent audit trail and enables automated reconciliation, replacing the manual processes required to match payments across correspondent banking chains. ### Efficient idle balance deployment Real-time visibility into global cash positions means treasury teams can deploy idle balances immediately rather than waiting for end-of-day reports. Working capital that was trapped in transit or pre-funded accounts can be redeployed productively. ### Automated treasury workflows Smart contracts enable treasury logic that runs automatically: threshold-based sweeps between accounts, scheduled intercompany settlements, and rules-based liquidity rebalancing. This replaces manual processes and custom integrations with multiple banking partners. ## Tokenized deposits vs stablecoins These two instruments serve complementary roles in enterprise treasury. Understanding the distinction matters for choosing the right approach. **Tokenized deposits** are traditional bank deposits represented as tokens on a blockchain. They remain a bank liability: the depositor has a claim on the bank, and the deposit is protected by the same regulatory framework as any other bank deposit. JPMorgan's JPM Coin and similar initiatives are examples. Tokenized deposits work best for intrabank or consortium settlement where both parties bank with the same institution. **Stablecoins** are issued by non-bank entities (Circle, Tether, Paxos) and backed by reserves, typically US Treasuries and cash equivalents. They are not bank liabilities. Stablecoins work across banks and function more like digital cash, making them suited for cross-bank, cross-border settlement. Both instruments coexist in enterprise treasury: ||Tokenized deposits|Stablecoins| |-|-|-| |Issuer|Bank|Non-bank issuer| |Liability type|Bank deposit|Claim on reserves| |Regulatory framework|Existing banking regulation|GENIUS Act, MiCA| |Best for|Intrabank settlement|Cross-bank, cross-border| |Interoperability|Within issuing bank's network|Any compatible wallet or exchange| For treasury teams, the practical takeaway: stablecoins are available today with broad interoperability, while tokenized deposits are emerging within specific banking networks. Many enterprises will use both. ## Key treasury use cases ### Intercompany settlements Stablecoins enable real-time settlement between parent companies and subsidiaries, or between subsidiaries. Instead of initiating SWIFT transfers and waiting days for clearance, treasury teams move stablecoins between entities and settle against bank accounts on their own schedule. A multinational with subsidiaries in 15 countries can consolidate and redistribute cash globally in minutes rather than days. The working capital freed by eliminating multi-day settlement delays drops directly to the bottom line. ### Cash positioning and forecasting Stablecoins provide real-time visibility into global cash positions. Treasury teams can see liquidity across all entities regardless of time zone or banking hours, replacing end-of-day reports with current data for forecasting and liquidity management. For a company with $500M in global cash balances, even a one-day improvement in cash positioning accuracy can translate to meaningful interest income or reduced borrowing costs. ### International payouts Stablecoins reduce the complexity of international payouts by bypassing correspondent banks and FX conversions. This is particularly valuable for high-volume, low-value payments or payouts to regions with limited banking infrastructure. Recipients can receive stablecoins directly, or providers can convert to local currency so the stablecoin leg is invisible to the recipient. See our [global payouts guide](/learn/global-payouts) for details. ## The opportunity for financial institutions Banks that issue tokenized deposits on public blockchain networks gain an interoperability advantage. Instead of being limited to proprietary settlement networks, tokenized deposits on public chains can interact with stablecoins, DeFi protocols, and other onchain assets. This matters for two reasons. First, corporate clients increasingly expect 24/7 settlement capability. Banks that offer it retain treasury relationships; those that do not risk disintermediation by stablecoin infrastructure providers. Second, tokenized deposits on public chains create new product opportunities: programmable escrow, automated sweep accounts, and real-time collateral management. Large banks (JPMorgan, Standard Chartered, Societe Generale) are already exploring this direction. Smaller banks can participate through partnerships with infrastructure providers rather than building from scratch. [Coastal Bank](/blog/coastal-bank-partners-with-tempo-to-build-stablecoin-settled-cross-border-payments) is one example of this partnership model. ## Current limitations Tokenized deposits and stablecoins complement bank accounts rather than replace them. Several limitations are worth acknowledging: - **Limited non-USD liquidity.** Stablecoins are predominantly dollar-denominated. EUR, GBP, and other major currency liquidity remains limited, though euro-denominated stablecoins are emerging. - **Off-ramping constraints.** Converting stablecoins to local currency via bank accounts is not available in all markets. Coverage is expanding but not yet universal. - **Custody complexity.** Treasury teams must choose between self-custody and institutional custody, with implications for multi-signature controls, insurance, and internal governance. - **Systems integration.** Some blockchains require custom integration with treasury management systems. Provider and network selection can simplify this significantly. - **Operational risk varies.** Risk profiles differ by asset and network. Stablecoins backed 1:1 by US Treasuries and repo have lower risk profiles than algorithmic alternatives. ## Getting started The most successful treasury implementations follow a methodical approach: 1. **Assess pain points.** Identify where cash is trapped, which corridors have the highest fees, and where settlement delays create the most friction. Start with a single high-value use case. 2. **Build the business case.** Map current costs (wire fees, FX spreads, intermediary charges, trapped working capital) against projected savings using your actual transaction data. 3. **Choose buy vs build.** In a buy model, a provider manages licensing, custody, wallets, and blockchain connectivity. In a build model, you integrate directly with custodians, wallet providers, and blockchain networks. Most enterprises start with buy and bring specific corridors in-house as they scale. 4. **Pilot a contained flow.** Start with a contained use case that delivers clear value, such as moving working capital between two subsidiaries or settling intercompany invoices. Measure results, then expand. ## Why Tempo for treasury Tempo is designed for payment and settlement use cases that matter most in corporate treasury: - **Near-instant settlement.** Onchain payments settle without re-orgs or batch windows. Bank transfers and off-ramps follow their providers’ timelines. - **Stablecoin fees.** Pay network fees in stablecoins. No volatile gas tokens on your balance sheet. [Learn more](/blog/stablecoin-fees). - **TIP-20 for reconciliation.** Attach a 32-byte payment reference, such as an invoice or customer ID, via the [TIP-20 standard](/blog/tip20). Integrations can map that reference to ERP and treasury records to support automated reconciliation. - **Payment references for existing messaging.** Transfer memos can link onchain payments to offchain records, including ISO 20022 messages, through integration logic. - **Compliance controls.** Issuer-defined transfer policies, allowlists, and role-based permissions for regulated use cases. For treasury teams, this means a single network that handles global settlement, compliance, and reconciliation without correspondent banks, volatile tokens, or multi-day delays. **Next steps:** - Read the full [corporate treasury guide](/blog/corporate-treasury) - Explore [cross-border payments with stablecoins](/learn/cross-border-payments) - Learn about [stablecoin payments](/learn/stablecoin-payments) end-to-end - Review [stablecoins for business](/learn/stablecoins-for-business) for the enterprise evaluation framework - [Contact our team](/contact) to discuss a treasury pilot --- ## Frequently asked questions **Do I need to hold stablecoins on my balance sheet?** No. You can use stablecoins purely as a settlement rail without holding balances directly. Third-party providers manage the stablecoins while your existing bank relationships remain central to day-to-day operations. Over time, you may choose to hold stablecoins directly or expand into other onchain assets such as tokenized treasuries. **Will my bank support tokenized deposits?** Many banks are actively developing tokenized deposit capabilities. JPMorgan (JPM Coin), Standard Chartered, and others have live or planned initiatives. In the meantime, infrastructure providers like Bridge and BVNK enable seamless movement between traditional bank accounts and stablecoins. Contact your banking partner for their current roadmap. **How does this integrate with our ERP or TMS?** Most TMS platforms (Kyriba, TreasuryXpress, GTreasury) support native integrations or API connections. A typical flow: payment instruction originates in the ERP/TMS, routes to a stablecoin infrastructure provider, settles onchain, and confirmation data flows back to the TMS. Integration software can use those records to generate accounting entries. Tempo’s transfer memos can link onchain payments to offchain records, including ISO 20022 messages, through integration logic. **What about regulatory concerns?** In the US, the GENIUS Act provides a federal framework for stablecoin issuers. The EU's MiCA regulations are in force. The UAE and Singapore have established frameworks. Tokenized deposits remain bank liabilities and fall under existing banking regulation. Onchain transactions provide a permanent audit trail with timestamps and cryptographic proof. Work with providers offering transaction monitoring, sanctions screening, and AML tools. **What are the risk considerations?** Primary risks fall into three categories. Counterparty risk: stablecoin issuer solvency and infrastructure provider stability, mitigated by choosing stablecoins backed 1:1 by HQLA under regulatory frameworks like GENIUS. Operational risk: variable fee structures and network performance, mitigated by selecting providers with fee consistency and proven reliability. Regulatory risk: potential restrictions in certain jurisdictions, mitigated by starting with dollar-based movements between your own entities before expanding to external use cases. **Should we use existing stablecoins or issue our own?** USDC and USDT are liquid and widely accepted for off-ramping, making them practical for immediate use cases. Issuing your own stablecoin (or tokenized deposit) lets you move value between entities while maintaining yield on reserves, without converting to money market funds. The right choice depends on your scale, regulatory posture, and whether you need interbank or intrabank settlement. Many enterprises start with existing stablecoins and evaluate issuance as volumes grow. --- ## The true cost of correspondent banking services for payouts > Source: https://tempo.xyz/learn/correspondent-banking-services-for-payouts/ > Language: en _Cross-border payouts often carry costs beyond transaction fees: settlement delays, manual reconciliation, payment investigations, and trapped liquidity. Stablecoin rails can reduce that operational burden by moving value 24/7 with clearer status and more structured payment data. This guide explains where correspondent banking still works, where its costs compound, and [how Tempo supports global payout flows](/learn/global-payouts/)._ Many global B2B payouts still rely on correspondent banking. In these flows, a payment may pass through one or more intermediary financial institutions before reaching its final destination. The system has worked for more than a century. It also comes with costs that are easy to underestimate. Transaction fees are visible. Operational costs are less obvious: settlement delays tie up working capital, payment investigations take time, and finance teams may need to reconcile each payout against invoices and internal records. This guide breaks down the strengths and commonly overlooked costs of correspondent banking services for cross-border payouts. It also explains what modern payout infrastructure is designed to improve. ## What is correspondent banking? Correspondent banking services are part of the infrastructure behind many international payments. ### What is a correspondent bank, and how does it work? A bank cannot have a direct relationship with every other bank in the world. When a payment needs to move to an out-of-network bank, intermediary financial institutions called correspondent banks help close the gap. For example, suppose a U.S. company needs to pay a manufacturer in India. The company's U.S.-based bank may not have a direct relationship with the manufacturer's Indian bank, so the payment may route through a U.S. correspondent bank and another regional intermediary before reaching the manufacturer. ### Why correspondent banking became the global standard There are practical reasons correspondent banking remains central to cross-border payments. It gives financial institutions a way to make international payouts in foreign currencies without building direct relationships with every bank in every market. A regional bank can support global transfers without opening branches around the world. Correspondent banks also conduct due diligence on the financial institutions they work with, including reviews related to anti-money laundering (AML) and know-your-customer (KYC) programs. These relationships can help smaller institutions participate in the global financial system, but each institution remains responsible for understanding and meeting the legal and regulatory obligations that apply to its activities. Finally, correspondent banking runs on established infrastructure that has facilitated cross-border transactions for decades. For many banks and businesses, that reliability and reach are important. ## The visible costs of correspondent banking The correspondent banking system works, but it comes with costs. These are the easiest to see, though not always the easiest to predict. ### Intermediary bank fees Each cross-border payment can pass through multiple intermediaries, and each intermediary may charge a fee. In one [Tempo global payouts example](/blog/global-payouts/), a $1,000 contractor payment sent through traditional rails includes a $10-40 payment processor fee, intermediary bank costs, and FX spread. Across a high volume of payouts, even small per-payment costs can materially affect margins. ### Foreign exchange (FX) spreads Most countries have their own currency, which means many international payments require currency conversion. Banks and payment providers may apply a spread over the mid-market exchange rate. Tempo's global payouts analysis uses a 0.1% to 4.0% FX spread range for traditional cross-border payout examples. The actual cost depends on corridor, currency, provider, transfer size, and timing. ### Payment investigation and exception fees Correspondent banking can also create costs when something goes wrong. A returned, amended, or canceled payment may trigger additional fees. If a payment requires review, funds can be delayed while banks investigate the issue. ## The hidden operational costs most businesses overlook Some costs do not show up as line items on a bank statement. They can still be expensive for finance and operations teams. ### Settlement uncertainty Traditional international payouts often take several business days to arrive, and timing can be affected by time zones, bank holidays, local cut-off times, and compliance checks. That may be manageable for low-volume or non-urgent payments. It becomes harder for businesses that need predictable payout timing across many countries. These variables can make vendor, merchant, or contractor payments harder to plan. Marketplaces are especially exposed because payout timing affects many recipients across many local payment systems. Uncertain settlement windows also complicate treasury forecasting. When payment status depends on updates from multiple intermediaries, finance teams may have incomplete information about when funds will arrive. ### Limited payment visibility Because correspondent banking payments move through multiple financial institutions, B2B teams may have limited visibility into which intermediary currently holds the funds or what is causing a delay. Modern payment infrastructure can improve visibility. With stablecoin transfers, the onchain leg is recorded on a shared ledger and can be tracked in real time. ### Reconciliation complexity Payment information does not always travel cleanly across systems. Missing references, inconsistent remittance details, or provider-specific formatting can force teams to manually match payments to invoices, purchase orders, customers, or internal cost centers. That manual work becomes harder as payout volume grows. A process that works for 100 payments per month may break down at 10,000 or 100,000. ### Working capital and trapped liquidity Cross-currency correspondent banking often relies on nostro accounts: accounts a bank holds in another country with funds denominated in that country's currency. To the correspondent bank that holds those funds, the same account is a vostro account. Banks may need to prefund these accounts so foreign correspondent banks have liquidity available to cover transactions. Prefunding can tie up capital that could otherwise be used elsewhere. Banks often prefund conservatively because failed payments are costly and disruptive. ## The hidden costs of payment infrastructure Payment fees are the most straightforward costs to calculate, but they rarely tell the whole story. ### The cost of delayed payments Repeated delays can lead vendors, contractors, or merchants to ask for different payment terms to protect their own cash flow. Marketplaces also manage settlement timing from both sides: incoming funds from buyers and outgoing payouts to sellers, merchants, or service providers. ### The cost of manual reconciliation Reconciling payments by hand takes finance teams away from higher-value work. When something goes wrong, those teams may also need to coordinate with multiple banks or payment providers to locate funds and correct records. Reporting and audit preparation can also suffer when reconciliation depends on manual matching. Human error can introduce discrepancies that require additional review. ### Infrastructure decisions compound at scale A business that processes 100 payments each month has a different operational reality than one that processes 100,000. As transaction volume scales, costs compound across fees, settlement timing, exception handling, support, and reconciliation. ## What modern payout infrastructure is optimizing for Modern payout infrastructure is designed to improve speed, transparency, and programmability. ### Faster and more predictable settlement Stablecoin transfers move value onchain over networks that operate 24/7. They are not constrained by banking hours, weekend closures, or local holiday calendars. Stablecoin rails often settle in seconds. On Tempo, blocks finalize in about 0.6 seconds with deterministic settlement, which can make payout timing more predictable for teams building global payment flows. ### Structured payment data and reconciliation On Tempo, [TIP-20 tokens can include structured memo fields](/blog/tip20/), such as invoice numbers, customer IDs, cost centers, or payment references. These memos help finance and operations teams connect stablecoin transfers to ERP records, invoices, and internal ledgers. This matters at scale. [DoorDash is building stablecoin-powered payment infrastructure on Tempo](/customer-stories/doordash/) for its global marketplace across 40+ countries, starting with flows where faster and more affordable settlement can create value for merchants and Dashers. ### Programmable payout operations Stablecoin rails can support programmable payment flows. Smart contracts can execute payments based on predefined rules, and payment applications can use onchain logic to automate routine actions. [Tempo Transactions](/blog/tempo-transactions/) add payment-oriented primitives directly at the protocol level, including configurable fee tokens, fee sponsorship, batch calls, concurrent transactions, scheduled transactions, and passkey authentication. For payout teams, batch transactions can make large payout runs easier to process, while scheduled transactions can support recurring or time-windowed payments. ### Dedicated infrastructure for payment traffic Some blockchain infrastructure can become congested during periods of heavy use, leading to slower confirmation times or less predictable fees. Tempo addresses this with [dedicated payment lanes](https://docs.tempo.xyz/protocol/blockspace/payment-lane-specification): reserved blockspace for qualifying payment transactions. This reduces the risk that payment traffic competes with unrelated network activity. ## Tempo: payments infrastructure for global payouts Correspondent banking remains relevant and functional in global finance. At the same time, its operational costs can add up. Manual reconciliation, unpredictable settlement timing, and prefunded liquidity all affect how quickly businesses can move and account for money across borders. Tempo is a payments-first blockchain designed for stablecoin payment flows at scale. For fintechs, marketplaces, and global businesses, Tempo offers sub-second finality, predictable low stablecoin transfer fees, dedicated payment lanes, Tempo Transactions, and optional structured memos for TIP-20 transfers. These capabilities can help teams reduce settlement delays, improve payment traceability, and simplify reconciliation workflows. If you are evaluating stablecoins for global payouts, start with Tempo's [global payouts guide](/blog/global-payouts/), learn how [TIP-20 supports payment memos](/blog/tip20/) and [payment lanes](https://docs.tempo.xyz/protocol/blockspace/payment-lane-specification), or [talk to the Tempo team](/contact/). --- ## FAQ ### Why are international business payments expensive? International payments often travel between multiple intermediary banks, and each institution or provider may add fees. Many cross-border payments also include FX spreads and exception-handling costs. The total cost depends on the payment corridor, currency pair, provider, transfer amount, and timing. ### What are the hidden costs of cross-border payments? Direct costs like transaction fees often sit alongside less visible operational costs: settlement uncertainty, limited payment visibility, manual reconciliation, payment investigations, and trapped liquidity from prefunding requirements. ### Why do international wire transfers take multiple days? International wires can take multiple business days because each institution in the chain may process, screen, and settle the payment separately. Timing can also be affected by bank cut-off times, weekends, local holidays, currency conversion, and compliance checks. ### Do stablecoins remove all operational requirements? No. Stablecoins can improve settlement speed, traceability, and programmability, but teams still need to manage custody, liquidity, off-ramps, recipient experience, tax reporting, accounting treatment, and regulatory requirements. Requirements vary by jurisdiction and use case, so teams should involve legal, compliance, tax, and finance stakeholders before launching a stablecoin payout program. --- **Continue learning:** [Stablecoins for business](/learn/stablecoins-for-business/) · [Stablecoins for payroll](/blog/stablecoins-for-payroll/) · [Global payouts](/learn/global-payouts/) --- ## Cross-border payments in Latin America: where stablecoin rails fit > Source: https://tempo.xyz/learn/cross-border-payments-latin-america/ > Language: en _Cross-border payments in Latin America are growing quickly, but companies still manage currency fragmentation, local settlement windows, FX costs, and limited visibility across providers. Stablecoin rails can complement banks and local payment networks by giving teams a 24/7 settlement layer for regional payouts, treasury movement, and supplier payments. If your team is evaluating stablecoin infrastructure for Latin American payment flows, [talk to Tempo](/contact)._ Latin America is one of the clearest markets for modern cross-border payment infrastructure. Remittances are one visible signal: [Mastercard and PCMI found](https://www.mastercard.com/global/en/news-and-trends/press/2024/march/new-mastercard-report-reveals-key-trends-opportunities-to-digitize-remittances-in-latin-america-and-the-caribbean.html) that remittances in Latin America have grown 10% annually since 2014, compared with 4% globally. Business payments are under similar pressure. Companies that pay suppliers, contractors, sellers, and subsidiaries across the region often work across multiple currencies, banking partners, tax requirements, and domestic payment systems. That fragmentation creates cost and operational drag. A [2026 Mastercard and FXC Intelligence study](https://www.mastercard.com/news/latin-america/en/newsroom/press-releases/pr-en/2026/june/cross-border-payments-become-a-battleground-for-loyalty-in-latin-america-and-the-caribbean-mastercard-and-fxc-intelligence-research-shows/) found that approximately one in nine cross-border payments for small and medium-sized businesses in Latin America and the Caribbean requires investigation, repair, or follow-up. Stablecoins offer a potential way to improve cross-border payments by acting as a faster, programmable settlement layer between currencies and local payment systems. Because they are digital tokens designed to maintain a stable value, often against the U.S. dollar, they can help businesses move funds across borders more quickly and with fewer intermediaries. They do not replace local banking, compliance, or currency controls, but they can work alongside existing financial infrastructure by connecting onchain settlement to local bank accounts, wallets, cards, or real-time payment systems where partners provide those endpoints. ## Why cross-border payments are difficult in Latin America The core challenge is fragmentation. Businesses moving money across Latin America have to manage different currencies, banking hours, settlement systems, reporting requirements, and local payment methods. A payment flow that works in Brazil may need a different provider, currency workflow, or reconciliation process in Mexico, Colombia, Argentina, or Peru. The friction usually shows up in five places. ### Settlement timing across multiple payment systems Cross-border payments often move through banking hours, correspondent banking relationships, batch files, and country-specific settlement windows. That can delay funds availability and make cash forecasting harder. Always-on settlement helps reduce that timing gap. Stablecoin transfers can settle 24/7, which gives finance teams a more predictable way to move value before funds are converted or paid out through local rails. ### FX conversion and multi-currency operations Companies operating across Latin America often manage several currencies at once. FX spreads, timing differences, and volatile exchange rates can affect margins, especially when payments sit in transit. USD-denominated stablecoins can reduce exposure during the settlement leg by keeping value in a dollar-pegged asset. This does not remove FX risk entirely. Businesses still need to manage local currency conversion, issuer risk, off-ramp availability, and jurisdiction-specific requirements. ### Fragmented local payment infrastructure Latin America has strong domestic payment systems, including real-time networks such as Pix in Brazil. The challenge is that these systems are local. They do not automatically create a unified regional network for cross-border settlement. Stablecoin rails can provide a common settlement layer between markets. Local partners can then connect that settlement layer to domestic payment systems, bank accounts, or wallets in each country. ### Reconciliation and payment visibility Cross-border operations often involve multiple payment providers and bank accounts. That makes it hard to track payment status, identify failed transfers, and reconcile payments against invoices or payroll records. Onchain transaction records can give payment teams a shared source of settlement data. For enterprise workflows, the benefit is not only speed. It is also clearer status tracking, structured payment references, and fewer manual follow-ups. ### Regional payout coverage Paying contractors, sellers, creators, or suppliers across the region often requires separate payout methods in each country. Every additional provider adds operational complexity. Stablecoin infrastructure can help companies standardize the settlement layer while still using local payout partners for last-mile delivery. This gives teams one operating model for cross-border value movement without forcing every recipient to use the same bank or wallet. ## Why stablecoin adoption is growing in Latin America Stablecoins are becoming part of the regional payments stack because they address practical business problems: settlement speed, access to dollar-denominated value, and simpler cross-border coordination. [The Digital Chamber reported](https://digitalchamber.org/latin-americas-surge-in-the-global-race-to-adopt-stablecoins/) that 71% of Latin American institutions have begun using stablecoins for cross-border payments, and that stablecoin transaction volume across the region reached $324 billion in 2025. Those figures point to a broader shift: stablecoins are moving from crypto-native use cases into business payments, remittances, treasury operations, and embedded finance. Three forces are driving the shift. ### Global accessibility Stablecoins move over internet-native networks rather than country-specific banking systems. For companies operating across Brazil, Colombia, Mexico, Argentina, Peru, and other markets, that creates a more consistent way to move value between approved wallets and payment partners. The recipient experience does not have to feel crypto-native. A platform can settle in stablecoins behind the scenes, then let recipients hold a dollar-denominated balance, withdraw to a local bank account, or spend through a card depending on the product and market. ### Settlement efficiency Speed matters, but the larger benefit is operational consistency. Stablecoin rails can reduce the need for batch processing, banking cutoffs, and multi-hop correspondent paths. For a company paying contractors every two weeks across several Latin American countries, that means payout workflows can be funded, scheduled, and tracked on a unified settlement layer. Finance teams can see when funds move, where they are, and when settlement is complete. [Tempo Transactions](/blog/tempo-transactions/) extend this model with payment-specific capabilities such as batching, fee sponsorship, scheduled payments, and passkey authentication. For teams running large payout jobs, batching and structured transaction data can make payment operations easier to automate and reconcile. ### Demand for dollar-denominated payment options In markets where local currencies can be volatile, workers and businesses often want access to dollar-denominated balances. Stablecoins can support that demand while keeping the user experience inside familiar products. Deel is one example. In June 2026, [Stripe announced](https://stripe.com/newsroom/news/deel-and-stripe) that Deel was using Stripe, Bridge, Privy, and Tempo to let contractors hold earnings in DLUSD, a USD-denominated digital balance. [Deel later said](https://www.deel.com/blog/introducing-stablecoin-wallet/) the wallet was live across 80+ countries in Latin America, Africa, the Middle East, and APAC for eligible contractors. ## How businesses use stablecoins in Latin America Stablecoins are most useful when they solve a specific payment workflow. In Latin America, the strongest use cases are cross-border payouts, platform settlement, treasury movement, remittances, and supplier payments. ### Payroll and contractor payouts Hiring across borders creates compliance, tax, and labor-law complexity. Payments add another layer: intermediary bank fees, local banking cutoffs, and inconsistent delivery times. Stablecoins give platforms and employers an alternative settlement route. Funds can move onchain with predictable fees and fast finality, then be held as a dollar-denominated balance or routed into local payout methods. For contractors, the best products hide the blockchain mechanics and present a simple account experience. Tempo is designed for these kinds of high-volume payout flows. Native batching, fee abstraction, transfer memos, and private settlement options help platforms move from ad hoc payment operations toward programmable payout infrastructure. ### Marketplace and platform settlements Marketplaces, gig platforms, creator platforms, and commerce networks often need to collect payments in one market and pay sellers or service providers in another. The operational burden grows as platforms expand country by country. Stablecoin rails can give platforms one settlement layer across markets. Users can then receive funds through the local experience that makes sense for them: a balance, a bank withdrawal, a card, or a domestic payment rail such as Pix where supported by local partners. This reduces regional operating complexity. It also gives platforms more flexibility to offer faster payouts, loyalty rewards, working capital products, or embedded financial accounts. ### Treasury and internal fund management Companies operating across several Latin American markets often leave cash sitting in local accounts while payments clear. That can make liquidity harder to manage and increase the need for short-term borrowing. Stablecoins can help treasury teams move funds between approved entities, wallets, and partners faster than many traditional routes. This gives teams more current visibility into cash positions and can reduce the time working capital spends in transit. The caveat is important: treasury teams still need clear controls for custody, authorization, accounting, compliance, FX conversion, and off-ramping. Stablecoin rails improve settlement mechanics, but they do not remove the need for treasury governance. ### Remittance and supplier payments [The Inter-American Development Bank projected](https://publications.iadb.org/en/remittances-latin-america-and-caribbean-2024-diminishing-rates-growth) that remittances received in Latin America and the Caribbean would reach $160.9 billion in 2024. Traditional corridors can still involve high fees, limited transparency, and multi-day settlement. Stablecoin rails can help remittance providers lower settlement costs and improve delivery speed behind the scenes. Recipients can still receive funds through familiar channels if the provider connects stablecoin settlement to local payout networks. Supplier payments work similarly. Importers and exporters can use stablecoins as a shared settlement rail, then convert to local currency when needed. This can reduce reliance on correspondent banking for certain corridors, but companies still need to manage invoices, sanctions screening, local tax rules, and currency conversion. ## Where Tempo fits Latin America's cross-border payment challenge is not just speed; it is fragmentation. Businesses need to move money across currencies, banking partners, wallets, and compliance regimes without adding more operational complexity. Tempo is built for that environment: a payments-focused Layer 1 designed for stablecoin-native flows with high throughput, low fees, and sub-second settlement. For companies paying contractors, suppliers, sellers, employees, or subsidiaries across the region, Tempo can provide a common settlement layer between global treasury and local payment endpoints. Instead of stitching together separate systems for payouts, payroll, remittances, supplier payments, and liquidity movement, businesses can use stablecoin settlement as shared infrastructure while still connecting into the local products users already trust. Tempo also brings payment-specific features into the infrastructure itself. Tempo Transactions support workflows such as batching, scheduled payments, fee sponsorship, and passkey-based authentication. [Tempo's native token standard](/blog/tip20/) adds token-level features like transfer memos and compliance controls, helping businesses connect stablecoin transfers to reconciliation, reporting, and risk workflows. For enterprise B2B flows, [Tempo Zones](/blog/introducing-tempo-zones/) add a practical privacy model for cases where transaction details should not be visible on a public ledger. Zones do not remove compliance obligations, and zone operators can see activity inside the zone, but they make private business payment flows more feasible than fully public settlement. Together, these capabilities position Tempo as infrastructure for making cross-border payments in Latin America faster, more programmable, and easier to operate at scale. ## Build Latin American payment operations on stablecoin rails For companies operating across Latin America, stablecoin rails are most useful as part of a hybrid payments strategy. Banks, local payment networks, FX providers, and compliance systems remain essential. Stablecoins improve the settlement layer that connects those systems. Tempo provides infrastructure for teams that need faster, lower-cost, and more programmable money movement across markets. With native support for stablecoin payments, batching, memos, privacy, and low-cost settlement, Tempo helps businesses modernize regional payment operations without asking users to manage crypto infrastructure themselves. [Explore Tempo for cross-border payments](/solutions/cross-border-payments/) or get in touch at [partners@tempo.xyz](mailto:partners@tempo.xyz). ## Frequently asked questions **How do businesses send money across Latin America?** Businesses usually use a mix of banks, money transmitters, fintech providers, local payment networks, and cross-border payment platforms. Some are adding stablecoin rails as a settlement layer that works alongside those systems. **What should companies evaluate before using stablecoin payment rails?** Companies should evaluate compliance, custody, privacy, reconciliation, local payout coverage, FX conversion, off-ramp availability, and issuer risk. The right infrastructure should fit into existing finance operations rather than create a separate crypto-native workflow. **What are the main challenges of cross-border payments in Latin America?** The main challenges are currency fragmentation, settlement delays, FX costs, local regulatory differences, limited payment visibility, and the need to support different domestic payment systems in each country. --- **Continue learning:** [Stablecoin Payments](/learn/stablecoin-payments) · [Payment Rails Compared](/learn/payment-rails) · [Blockchain Payments](/learn/blockchain-payments) --- ## Cross-border payments with stablecoins > Source: https://tempo.xyz/learn/cross-border-payments/ > Language: en _Cross-border payments are the most expensive and slowest part of most businesses' payment operations. Correspondent banking chains add 3–5 days of delay, $25–$50+ in fees per transfer, and hidden FX spreads. Stablecoins bypass this entire infrastructure, delivering same-day settlement at a fraction of the cost._ ## The problem with traditional cross-border payments Moving money across borders today means navigating a chain of intermediaries. When a US company pays a supplier in Vietnam, the payment does not travel directly. It passes through the sending bank, one or more correspondent banks, and finally the receiving bank, each adding cost and delay. ### Cost A single international wire typically costs $25–$50 in explicit fees. On top of that, each intermediary takes a spread on the foreign exchange conversion, often 1–3% of the transfer amount. For a $100,000 payment, the total cost can exceed $3,000. Multiply that across hundreds of monthly cross-border payments and the expense becomes material. ### Speed SWIFT transfers take 1–5 business days depending on the corridor, the number of intermediary banks, and whether the payment crosses time zones on a weekend. A Friday afternoon transfer from New York to a bank in Southeast Asia may not begin processing until Monday morning local time. ### Trapped liquidity To ensure timely delivery, many businesses pre-fund nostro accounts in destination countries. McKinsey estimates this trapped capital represents 34% of international payment costs. That is working capital sitting idle in accounts around the world instead of being deployed productively. ### Opacity Tracking a SWIFT payment in transit is difficult. Each correspondent bank processes the payment on its own timeline, and status updates are inconsistent. Finance teams often resort to manual follow-ups with banking partners to determine where a payment is in the chain. ## How stablecoins fix cross-border payments Stablecoins fundamentally change the architecture of cross-border payments by removing intermediaries from the transfer itself: ### Direct transfers Instead of routing through a chain of correspondent banks, stablecoin payments move value directly from sender to receiver on a blockchain. One transaction, one confirmation, one fee, regardless of whether the recipient is across town or across the world. ### No intermediaries There are no correspondent banks, no nostro accounts, and no intermediary fees. The blockchain is both the messaging layer and the settlement layer. This eliminates the cost and delay that each intermediary adds. ### 24/7 settlement Blockchain networks operate continuously. Cross-border stablecoin payments settle on weekends, holidays, and outside banking hours. A Friday evening payment to a supplier in Asia arrives in seconds, not the following Monday or Tuesday. ### Predictable costs On-chain fees are sub-cent per transaction on efficient networks like Tempo. There are no surprise intermediary deductions or opaque FX markups. The cost of sending $100 is the same as sending $1,000,000. ## Real impact: 60–80% cost reduction Businesses replacing SWIFT with stablecoin rails for cross-border payments typically see **60–80% cost reductions**. The savings come from three sources: - **Eliminated intermediary fees.** No correspondent bank charges. No intermediary deductions from the transfer amount. - **Reduced FX spreads.** Stablecoin on/off-ramp providers operate in competitive markets with tighter spreads than correspondent banking desks. - **Freed working capital.** No need to pre-fund nostro accounts in every destination country. Capital that was trapped in intermediary accounts can be deployed productively. For high-volume corridors (payments to manufacturing partners in Asia, contractor payouts across Latin America, subsidiary funding in Europe), the savings compound quickly. ## Key use cases ### International vendor payments Pay suppliers in any country with same-day settlement and full cost transparency. Eliminate the $25–$50 wire fee and 1–3% FX markup on every invoice. Suppliers receive funds faster, which can improve your negotiating position and supply chain reliability. ### Subsidiary and intercompany transfers Move liquidity between subsidiaries globally in real time. No more waiting for SWIFT to clear or pre-funding local accounts. Treasury teams get real-time visibility into global cash positions and can rebalance instantly. ### Contractor and freelancer payouts Pay international contractors and freelancers without the $15–$40 wire fee that makes small payments uneconomical. A $200 payment to a designer in Argentina no longer costs $40 in fees. It costs fractions of a penny. ### Remittances Enable consumers and businesses to send money home at a fraction of traditional costs. The average cost of sending a $200 remittance is 6.5% through traditional channels. With stablecoins, total cost drops below 1%. Read more in our [blog on stablecoin remittances](/blog/remittances). ## Customer stories Companies are already using Tempo for cross-border stablecoin payments at scale: - **DoorDash** partnered with Tempo to bring stablecoin payments to its global marketplace, enabling faster merchant payouts across borders. [Read the story](/blog/doordash-partners-with-tempo-to-bring-stablecoin-payments-to-its-global-marketplace) - **Felix** powers instant remittance settlement on Tempo, delivering sub-1% total costs on US-to-Mexico transfers. [Read the story](/blog/felix-brings-instant-remittance-settlement-on-tempo) - **Arq** is building cross-border payment infrastructure on Tempo, connecting businesses across Latin America to faster, cheaper rails. [Read the story](/blog/arq-is-building-cross-border-payment-infrastructure-on-tempo) ## Getting started: the pilot approach Adopting stablecoin rails for cross-border payments does not require a full infrastructure overhaul. The most successful approach is a focused pilot: 1. **Identify one corridor.** Choose a high-volume, high-cost payment corridor, for example US-to-Philippines vendor payments or US-to-Mexico contractor payouts. 2. **Measure the baseline.** Document current costs (wire fees, FX spreads, intermediary charges) and settlement times for that corridor. 3. **Run a parallel pilot.** Process a subset of payments through stablecoin rails alongside your existing workflow. Compare cost, speed, and operational overhead. 4. **Evaluate and expand.** Once the pilot demonstrates results, expand to additional corridors and use cases. This approach lets you validate the benefits with real data before committing to broader adoption. ## Why Tempo for cross-border payments Tempo is purpose-built for the payment use cases that matter most in cross-border: - **Sub-second finality.** Transactions finalize in under one second, with no batch windows or confirmation delays. - **Stablecoin fees.** Pay network fees in stablecoins. No volatile gas tokens on your balance sheet. [Learn more](/blog/stablecoin-fees) - **Transfer memos.** Attach invoice numbers, PO references, and reconciliation data directly to transactions via the TIP-20 standard. - **Compliance controls.** Built-in freeze, seize, and allowlist operations for regulated entities. - **Global ecosystem.** Infrastructure partners providing on/off-ramps across major corridors. [Explore the ecosystem](/ecosystem) For treasury and payments teams, this means a single network that handles cross-border settlement, compliance, and reconciliation without correspondent banks, volatile tokens, or multi-day delays. For a detailed look at how Tempo supports cross-border use cases, visit [Cross-Border Payments on Tempo](/solutions/cross-border-payments). ## Why this matters for finance teams Cross-border payments represent the highest-cost, highest-friction area of most businesses' payment operations. Every dollar saved on wire fees, FX spreads, and trapped liquidity drops directly to the bottom line. Stablecoins do not just reduce cost. They change the operational model. Real-time settlement means better working capital management. 24/7 availability means no more timing payments around banking hours and time zones. Full on-chain traceability means faster reconciliation and cleaner audits. The technology is production-ready, the regulatory frameworks are in place, and the infrastructure ecosystem is mature. The question for most finance teams is not whether to adopt stablecoin rails for cross-border payments, but which corridor to start with. **Next steps:** - Understand [how stablecoin payments work](/learn/stablecoin-payments) end-to-end - Compare [ACH, wires, SWIFT, and stablecoins](/learn/payment-rails) side by side - Read the [stablecoin fundamentals](/learn/what-are-stablecoins) - [Contact our team](/contact) to start a cross-border pilot --- ## Frequently asked questions **How long do cross-border stablecoin payments take?** On-chain settlement takes seconds. On Tempo, transactions finalize in under one second. End-to-end timing including fiat on-ramp and local currency off-ramp is typically same-day, compared to 3–5 business days for traditional SWIFT transfers. **What currencies are supported?** Stablecoin transfers are primarily denominated in USD via USDC, USDT, and other USD-pegged stablecoins. At the off-ramp, recipients can convert to local currency through their provider. Euro-denominated stablecoins are also emerging. Non-USD stablecoin fee support on Tempo is planned as those markets develop. **Do I need a crypto exchange to send cross-border stablecoin payments?** No. Orchestration platforms like Tempo and infrastructure partners handle the fiat-to-stablecoin conversion and routing. You operate entirely in fiat on both ends. No exchange account, crypto wallet, or blockchain expertise is required. **What about sanctions screening and compliance?** Stablecoin payment platforms enforce KYC/KYB onboarding, real-time transaction monitoring, and sanctions screening against OFAC, EU, and other watchlists. On Tempo, compliance controls are built directly into the TIP-20 token standard, supporting freeze, seize, and allowlist operations required by regulated institutions. **How much can I save compared to SWIFT and correspondent banking?** Businesses typically see 60–80% cost reductions on cross-border payments by replacing SWIFT with stablecoin rails. Savings come from eliminating intermediary bank fees ($25–$50+ per transfer), reducing FX spreads (1–3%), and removing the need for pre-funded nostro accounts. The exact savings depend on your current corridors and volume. --- ## Embedded finance for gig economy payments: a payout-routing blueprint > Source: https://tempo.xyz/learn/embedded-finance-gig-economy-payments/ > Language: en _Gig marketplaces need payout systems that can handle different countries, currencies, payment methods, and compliance requirements without turning every transfer into manual work. Embedded finance brings onboarding, funding, payout execution, and reconciliation into the product, while stablecoin settlement can make eligible cross-border routes faster and more predictable. If you are evaluating stablecoin payment infrastructure for global marketplace payouts, [talk to Tempo](/contact/)._ Gig economy payments are the systems marketplaces use to pay independent contractors, creators, drivers, sellers, and other nonemployee workers after work is completed or sales are settled. In one market, that can be a straightforward payment process. Across countries, payouts become harder to manage. Each transaction may involve a different currency, deposit method, provider, compliance check, funding source, and reconciliation record. Embedded finance helps marketplaces bring those workflows into the product itself. Instead of treating payouts as a separate back-office process, platforms can connect account setup, funding, payment execution, and transaction records inside one operating model. For global contractor and creator payments, [stablecoin payment rails](/learn/stablecoin-payments/) can support faster onchain settlement and more direct cross-border money movement when the route is a good fit. This article explains how global gig marketplaces can design payout routing and build automated, reconciliation-ready payment architecture. ## Why global payouts are difficult for gig marketplaces Global gig marketplaces pay contractors across different local markets and timelines. Workers usually see only the final deposit, but the platform has to choose the rail, manage currency conversion, fund the route, apply controls, and connect the payout to internal records. The friction falls into three common categories. ### Contractors want local payout options Contractors expect payout options that match their market, such as bank transfers, instant payouts, digital wallets, or stablecoins. These options can improve the worker experience, but they create more backend work for the platform. Teams have to manage providers, track funding flows, handle support issues, and reconcile transactions across systems that may not share the same identifiers or status model. ### Cross-border payouts add more dependencies International money movement often depends on multiple providers, intermediary banks, local payment rails, and currency markets. Currency conversion is not just a pricing question. Timing, liquidity, and exchange-rate spreads can affect the amount a worker receives. Visibility can also become fragmented. If a payment stalls, the marketplace may have to investigate across providers, banking partners, and internal systems before it can tell a contractor what happened. That creates support work and makes payout reliability harder to measure. ### Scale turns payment operations into infrastructure Manual payout workflows can work with a small contractor base. When volume grows to thousands or hundreds of thousands of transactions, manual review creates more room for errors such as duplicate payments, incorrect recipient details, and missed exceptions. At that scale, marketplaces need well-defined payout logic. The system should determine who gets paid, when funds move, which route to use, when to pause a transaction, and how each payout connects to the marketplace's ledger, ERP, or accounting system. ## What payout routing does Payout routing is the logic that decides where each payout should go, which rail should carry it, and when settlement should happen. It helps a marketplace choose the right path for each transaction instead of sending every payout through the same workflow. Most routing decisions start with location. A platform may use one path for domestic payouts, another for Latin America, and another for Southeast Asia. Routing logic can also account for deposit preference, transaction size, urgency, supported currencies, compliance status, and provider availability. For example, a domestic payout might stay on a local real-time payment rail. A cross-border payout might use stablecoin settlement when speed, operating hours, or cost predictability matter. A higher-risk transaction might pause for review before funds move. If a contractor's tax forms or identity checks are incomplete, the system can hold the payout until the required information is resolved. Better routing gives platforms more control over payment cost, timing, and reliability. It also reduces the number of decisions finance and operations teams have to make manually. ## How Tempo fits into a payout stack Tempo acts as the network and settlement layer for stablecoin payment flows. In a production payout stack, a marketplace or its payment provider typically owns the routing logic: the rules that determine which transactions use domestic rails, which use stablecoin settlement, which require manual review, and which need local-currency delivery. Tempo can provide the stablecoin settlement layer for routes where onchain settlement improves the workflow. That distinction matters. A stablecoin transfer can settle quickly onchain, but the complete payout may still depend on onboarding, custody, compliance checks, fiat conversion, liquidity, off-ramp coverage, and local payment rails. The right comparison is the full route from sender funding to recipient delivery, not the network leg alone. Tempo is built for payment use cases that require predictable settlement, low fees, stablecoin-denominated network fees, payment references, and dedicated payment capacity. Those features can help marketplaces build payout routes that are easier to operate and reconcile. ## The building blocks of an embedded payout stack An embedded payout stack lets marketplaces handle contractor earnings directly inside their own product. This gives contractors a clearer payment experience and gives internal teams more control over how funds move. ### User onboarding and account setup Payout infrastructure starts with verification. Marketplaces need to identify the worker, create or connect the right account, and set permissions for how that user can receive funds. The experience should be simple for contractors. They should be able to join the marketplace, confirm payout details, and see available compensation options without moving through a separate finance workflow. ### Balance management and funding Once the marketplace knows who can receive funds, it has to manage the balances available for payout. The system needs to match the platform's available cash or stablecoin balances against what it owes to workers. Treasury teams also need to make sure enough funds are available in the right accounts, currencies, and corridors. Global transfers often involve different settlement paths. A marketplace may prefund one corridor for real-time payments and use another route for scheduled payouts. To avoid funding gaps, automated systems should track balances, expected payout volume, and regional funding needs before a route runs short. ### Routing rules and controls Routing rules determine which path a payout takes. A rule might send domestic payouts through a local bank rail, send eligible cross-border payouts through stablecoin settlement, route small payouts through a lower-cost provider, or require manual review before sending funds to a new contractor account. Controls should run before funds move. These can include identity checks, sanctions screening, transaction monitoring, supported-asset rules, velocity limits, approval policies, and tax or documentation requirements. ### Payout execution Payout execution is the moment the platform releases funds. A completed job, an approved invoice, or a scheduled transfer window can trigger the payout. Marketplaces can also run batch or conditional payouts, such as releasing funds only after a contractor reaches a minimum earnings threshold or passes required checks. ### Monitoring and reconciliation A payout stack also needs to track what happened after funds move. Teams need visibility into payment status, settlement confirmation, rejected transfers, fees, exchange rates, and provider responses. They also need audit trails that connect each payout to the correct internal record. That connection matters for support, month-end close, compliance reviews, and financial reporting. ## A five-step payout-routing blueprint Use these steps to design payout rules that are specific enough to automate and transparent enough to audit. ### 1. Define your payout corridors Map the routes money needs to take. For each corridor, define: - Funding source - Contractor location - Recipient delivery method - Settlement currency - Delivery currency - Required payout speed - Compliance and tax requirements - On-ramp or off-ramp partners, if needed A U.S. to Latin America payout flow, for example, may start with dollar funding, use stablecoin settlement for the cross-border leg, and rely on a local off-ramp partner when the contractor wants to receive local currency. ### 2. Define routing rules Define the conditions that tell the platform which path to use, when to use it, and when to pause the payout before funds move. A routing rule might use a domestic rail for same-country payouts, use stablecoin settlement for eligible cross-border routes, send small payouts through a lower-cost provider, or require review before sending money to a newly added account. The goal is to make the decision repeatable instead of relying on manual judgment for each payout. ### 3. Choose where stablecoin settlement improves the route Stablecoin settlement is most useful where existing rails create measurable friction: bank cutoffs, limited operating hours, multiple intermediaries, high cross-border fees, slow settlement, or difficult reconciliation. For those routes, the marketplace can keep routing logic in its application or provider stack and use payment infrastructure like Tempo for the eligible stablecoin settlement leg. This lets the platform apply payout rules at the application level while using Tempo for fast, predictable onchain settlement. ### 4. Embed reconciliation from day one Design payout infrastructure to handle reconciliation automatically instead of leaving cleanup for the accounting team later. Each transfer should carry the reference finance teams need to match the transaction, such as an invoice ID, order ID, contractor ID, or settlement reference. Tempo has [transfer memos](/blog/tip20/) that let payment applications attach a payment reference to the transfer so internal systems can connect settlement to the right record with less manual work. Do not put sensitive customer, contractor, or invoice data directly onchain. Use references that connect back to secure internal systems. ### 5. Monitor and optimize routing performance Track failed payouts, delayed payouts, settlement times, support tickets, fees, exchange-rate spreads, and corridor-level performance. These metrics help teams improve routing rules over time. The system can then steer transactions away from unreliable or expensive paths and shift volume toward routes that perform better for the platform and the contractor. ## What modern payout infrastructure enables Modern payout infrastructure helps gig marketplaces turn complex operations into repeatable payment flows. ### Faster settlement for global workers Payout speed affects platform preference. According to [Everee's 2025 Gig Driver Report](https://www.everee.com/blog/gig-report/), 84% of gig drivers said fast access to earnings is important or very important when deciding which platform to work for. Stablecoin settlement can help platforms meet that expectation on eligible cross-border routes. This is especially relevant when existing rails involve bank cutoffs, weekend delays, or multiple intermediaries. The end-to-end delivery time still depends on the full route, including conversion, off-ramp coverage, and local payout partners. ### More predictable payout operations When thousands of contractors expect compensation at the same time, the platform needs infrastructure designed for high-volume payment traffic. Tempo's dedicated payment capacity reserves blockspace for payment transactions. This helps payment operators maintain predictable execution and fees as network activity changes. ### Better reconciliation Payment references help finance teams connect settlement activity to invoices, orders, contractor balances, and accounting entries. This reduces manual matching and gives support teams clearer information when a contractor asks about a payout. ### Integrated controls Marketplaces can apply payout rules before funds move, including supported-asset rules, identity requirements, transaction controls, and approval policies. This helps teams enforce payout guidelines inside the payment flow instead of reviewing every exception manually. ## Risks and limitations Stablecoin settlement can improve payout routes, but it does not remove every dependency. Production systems still need to account for: - Off-ramp coverage in the markets where contractors want local currency - Liquidity and foreign exchange costs for the required currencies - Custody and key management - Compliance, sanctions screening, tax, and reporting requirements - Privacy rules for transaction metadata - Reversals, refunds, and error handling - Provider reliability across wallets, banks, payment processors, and local rails Stablecoins complement bank accounts and local payment rails rather than replace them. For marketplace payouts, the strongest architecture usually combines routing logic, local providers, stablecoin settlement where it helps, and reconciliation data that connects every transfer back to internal records. ## Embedded finance as a marketplace growth strategy Global payouts are infrastructure challenges, not just payment tasks. As marketplaces grow across countries and payout methods, they need more control over how contractors onboard, how funds move, and how each transaction connects to internal records. Embedded finance gives marketplaces that control inside the product. Payout routing becomes the blueprint for choosing the right path, while automated rules and transaction references help teams handle high-volume payout operations without adding manual work at the same rate. The result is operational leverage. Platforms can support more payout flexibility, improve the contractor experience, and reduce manual work across finance and operations without rebuilding the payment process for every new corridor. [Discover how Tempo's payments-first architecture can provide the settlement foundation for marketplaces designing custom payout flows with programmable routing, predictable settlement, and reconciliation-ready workflows](https://tempo.xyz/). --- ## Frequently asked questions **How do gig economy platforms pay workers globally?** Gig economy platforms use a mix of payment methods, including direct deposit, local bank rails, card payouts, digital wallets, payment providers, and stablecoin settlement. The right route depends on the contractor's location, delivery currency, payout speed, cost, compliance requirements, and available local infrastructure. **How can marketplaces automate global payouts?** Marketplaces can automate global payouts by embedding routing rules into their payout logic. The system can determine when a payout triggers, which route to use, whether approval is required, and which reference data should travel with the transaction for reconciliation. --- ## Global payouts for neobanks: Faster, more predictable settlement with stablecoins > Source: https://tempo.xyz/learn/global-payouts-for-neobanks/ > Language: en **_Stablecoin settlement can make global payouts faster and more predictable for neobanks expanding across corridors. Tempo gives businesses and developers a payments-first Layer 1 with stablecoin-native fees, dedicated payment lanes, payment metadata, and near-instant onchain settlement._** [_Explore Tempo's cross-border payment infrastructure_](/solutions/cross-border-payments/). Neobanks and fintech apps have mastered the frontend experience, allowing customers to open accounts and manage money in minutes. The backend of global payouts is harder to modernize. Cross-border payment operations still face familiar constraints: variable costs, delayed settlement, prefunding requirements, and manual reconciliation. Traditional banking systems rely on regulated, resilient batch-based settlement that routes payments through local clearinghouses such as ACH and SEPA. These frameworks are essential to global financial infrastructure, but fixed settlement windows do not always align with the 24/7 expectations of digital financial products. Batch-based settlement was built for a different operating model. It can be a poor fit for real-time, high-frequency global payouts where neobanks need predictable costs, faster settlement, and clearer reconciliation across many markets. Stablecoin rails can provide an additional settlement layer that works alongside sponsor banks, local payment partners, and existing compliance programs. This article explains why global payout costs are difficult to forecast, how stablecoins can make the settlement layer more predictable, and what infrastructure fintechs need to use them effectively. ## Why global payout costs are hard to forecast The core challenge with [global payout](/blog/global-payouts/) costs is predictability. Instead of one flat cost, [cross-border transactions](/learn/cross-border-payments/) often involve several variables: intermediary bank fees, FX spreads, local payment processing, and timing differences by corridor. As neobanks expand into more regions, that variability makes payout economics harder to forecast. ### Intermediary bank fees vary by route The sending and receiving banks are the most visible participants in a cross-border payout, but messaging and settlement often happen on different layers. Payment instructions may travel separately from the actual funds, and funds can move through multiple correspondent or intermediary banks before reaching the destination. Each intermediary can add fees based on the route, currencies, and institutions involved. Because routes can vary by corridor and provider, the final cost is often harder to forecast before execution. ### FX spreads change by corridor and timing The foreign exchange spread is the markup added to an exchange rate when converting one currency into another. Some providers quote FX before a payment is sent, but spreads still vary by corridor, currency pair, provider, and timing. For neobanks operating across many markets, that makes FX one of the most variable components of payout cost. ### Prefunding ties up working capital To support fast local payouts without waiting for cross-border wires, neobanks often prefund local bank accounts by holding pools of capital in multiple countries. This can help recipients get paid quickly, but it fragments funds across corridors. As neobanks add more payout destinations, prefunding can tie up working capital that could otherwise be used elsewhere in the business. It also creates operational overhead for treasury teams that need to monitor balances, replenish accounts, and reconcile movements across many local partners. ## How stablecoins make payout costs more predictable Stablecoin rails are not always the right fit. For neobanks running high-volume domestic payouts through ACH or low-frequency payouts to a small number of stable corridors, existing rails may already be cost efficient and predictable enough that a stablecoin settlement layer adds limited value. The case becomes stronger as corridor count, currency mix, and payout frequency increase. In those settings, [stablecoins](/learn/what-are-stablecoins/) can simplify the settlement leg by moving value over a shared digital ledger before funds are delivered through local partners. ### A shared settlement layer can reduce intermediary cost variability On a stablecoin rail, value can move directly between counterparties on a shared ledger rather than through a long chain of correspondent banks. This can reduce the number of intermediaries involved in the settlement leg and make network-layer costs easier to estimate. For payments on Tempo, [transaction fees](https://docs.tempo.xyz/protocol/fees) can be paid in supported USD-denominated TIP-20 stablecoins instead of a volatile gas token. Standard stablecoin transfers on Tempo have sub-cent fees. For a neobank sending $500 or $500,000 through the same standard transfer flow, the network fee is not a percentage of the amount moved. ### Off-ramp fees still affect total payout cost Stablecoin [payment rails](/learn/payment-rails/) complement traditional financial infrastructure rather than replacing it. Local banks and payment partners still handle account relationships, off-ramp delivery, local payment processing, and the compliance programs required for their roles. This matters for accuracy: stablecoin settlement can reduce unpredictable fees during the cross-border settlement leg, but FX conversion, local payment processing, and partner fees may still apply. The benefit is a more predictable network layer, not the disappearance of every downstream cost. [DoorDash is building stablecoin-powered payment infrastructure on Tempo](/customer-stories/doordash/) for merchants and Dashers across 40+ countries. For a global marketplace, that means faster settlement, more predictable network costs, and payment infrastructure designed for complex multi-party payout flows. ### Faster settlement can reduce prefunding pressure Faster settlement can also improve capital efficiency. Tempo provides near-instant onchain settlement with no re-orgs, giving payment teams clearer settlement timing for cross-border movement. While prefunding will not disappear entirely, faster settlement can help treasury teams replenish local accounts more frequently instead of parking larger balances across many corridors. ## Stablecoin infrastructure neobanks need Stablecoin rails can speed up global payouts, but they need to work with existing operational systems. A complete payment stack connects the blockchain settlement layer to financial partners, treasury processes, and reconciliation workflows. ### Funding and liquidity Neobanks need access to supported stablecoins for settlement and partners that can handle fiat on-ramps and off-ramps. Local banks and payment partners still deliver funds to recipients in local currency where required. ### Programmable payment execution [Tempo Transactions](https://docs.tempo.xyz/guide/tempo-transaction) give developers native capabilities for payment workflows, including fee sponsorship, batch calls, concurrent transactions, scheduled transactions, access keys, and passkey authentication. For global payout platforms, these features can reduce operational complexity by letting applications sponsor fees, process payout batches, and automate recurring payment windows without adding separate infrastructure for each capability. ### Compliance and reconciliation Stablecoin payouts still need clear controls and records. [Tempo's native token standard](https://docs.tempo.xyz/protocol/tip20/overview) can include transfer memos for payment references, invoice IDs, and transaction notes, helping teams match onchain settlement activity to internal financial records. Tempo also supports issuer-defined transfer controls through [TIP-403 transfer policies](https://docs.tempo.xyz/protocol/tip403/spec), including allowlists and blocklists. These controls can support compliance workflows, but they do not replace a neobank's, issuer's, or banking partner's Know Your Customer, anti-money laundering, or sanctions-screening programs. [Coastal partnered with Tempo](/customer-stories/coastal/) to build stablecoin-settled payment infrastructure for its fintech clients. The model keeps existing institutional messaging and compliance infrastructure in place while using Tempo as a faster settlement layer underneath. That is the core value of Tempo for regulated financial institutions: modern settlement infrastructure that can work with the systems they already rely on. ## How Tempo supports cost-predictable global payouts Neobanks rely on traditional financial rails for trusted account relationships, local reach, and regulated financial services. As global payout demand grows, correspondent banking systems can still create speed, cost, and capacity constraints. Supported stablecoins can help address those constraints by providing a high-speed settlement layer for international movement. [Tempo](/) is a Layer 1 blockchain purpose-built for stablecoin payments at scale. Its design gives neobanks and fintechs several advantages for global payouts: stablecoin-native gas, dedicated payment lanes, payment metadata for reconciliation, programmable transaction features, and near-instant onchain settlement. Together, these features make the network layer of global payouts easier to forecast. Fees are paid in supported stablecoins rather than volatile gas tokens. Payment lanes help keep payment throughput predictable during network activity spikes. Memo fields support reconciliation. Fee sponsorship and batch transactions help platforms hide network complexity from end users while processing payouts at scale. Ready to see how stablecoins fit into your global payout strategy? See how [Tempo brings cost predictability](/solutions/cross-border-payments/) to your cross-border payouts today. ## FAQ ### Do neobanks need a separate gas token to run stablecoin payouts? No. Tempo has no native gas token. Transaction fees can be paid directly in supported USD-denominated TIP-20 stablecoins, and applications can use fee sponsorship so the platform or another fee payer covers network fees on behalf of users. Neobanks still need access to supported stablecoins or partners that manage the stablecoin leg of the payout flow. ### How many countries can neobanks reach with stablecoin payouts? The answer depends on the off-ramp network, local partners, and the payout model. Blockchains operate globally over the internet, but local partners still need to convert stablecoins into the recipient's local currency where that is the desired payout experience. ### Do recipients need a special wallet or technical setup to get paid? Not necessarily. In a payout flow where the neobank or payout provider manages the stablecoin settlement leg and a local partner handles last-mile delivery, recipients can receive funds in local currency through familiar rails. With Tempo's [fee sponsorship](https://docs.tempo.xyz/guide/payments/sponsor-user-fees), the platform can also cover network fees so recipients do not need to buy or manage a separate gas token. --- ## Global payouts with stablecoins: a guide for platforms and enterprises > Source: https://tempo.xyz/learn/global-payouts/ > Language: en _Global payouts to contractors, merchants, affiliates, and partners are one of the highest-friction financial operations for platforms and enterprises. Stablecoins reduce that friction dramatically: instant settlement, 60–80% lower costs, full traceability, and dollar-denominated stability for recipients in 140+ countries._ ## The challenge with traditional global payouts If your business pays people across borders, whether a marketplace paying thousands of merchants or a company with a distributed team, you know the friction: - **High fees.** A single cross-border payment can pass through three or four intermediary banks, each taking a cut. A $1,000 payout to a contractor might lose $80 or more to fees before it arrives. - **Slow, unpredictable settlement.** Payouts take 3–5 business days, complicated by time zones, bank holidays, and compliance checks. Recipients don't know when funds will arrive. - **FX complexity.** Managing multiple currencies, exchange rate risk, and opaque bank FX spreads adds cost and operational overhead. - **Reconciliation overhead.** Tracking thousands of individual payments across different banking rails, currencies, and providers creates a significant operational burden for finance teams. - **Payout failures.** A simple data entry error can cause a payment to fail, triggering manual reconciliation that takes days to resolve. These problems multiply with scale. A platform processing 10,000 payouts per month across 30 countries is managing an extraordinary amount of operational complexity through traditional rails. ## How stablecoins fix payouts Stablecoins bypass the correspondent banking system entirely, enabling direct payouts to any recipient with a compatible wallet. The improvements are concrete and measurable. ### The contractor in Brazil Consider the example from our [global payouts blog post](/blog/global-payouts): when you send $1,000 to a contractor in Brazil using traditional rails, your payment processor charges $10–40, intermediary banks take 0.1–4.0% on the FX spread, and the payment takes 3–5 days. The contractor receives roughly $920 after all fees. With stablecoin rails, the same payment costs 0.1–0.4% in onramp and transfer fees, a **60–80% cost reduction**. The contractor receives funds in seconds, not days, and gets dollar-denominated stablecoins they can convert to reais on their own terms. ### Instant settlement Stablecoin payouts settle in seconds, 24/7/365. No banking hours, no weekend delays, no holiday calendars. Workers and merchants get paid on time, every time. For platforms where payout speed is a competitive advantage (gig economy, creator economy, freelance marketplaces), instant settlement directly improves retention. ### Lower costs By eliminating intermediary banks, stablecoins reduce per-payment costs from dollars to cents. At scale, the savings are substantial: a platform processing $50M in annual cross-border payouts could save $3–4M per year in transaction fees alone. ### Traceability Every stablecoin transaction is recorded on the blockchain, creating an immutable audit trail trackable in real time by both payers and payees. This dramatically simplifies reconciliation. No more chasing payment status across multiple banking partners. ### Dollar-based stability Payouts in US dollar-denominated stablecoins protect recipients from local currency devaluation. A contractor in Argentina or Nigeria receives a stable store of value and converts to local currency when and how they choose, rather than absorbing FX risk during multi-day settlement. ### Broader access Stablecoins can be sent to any compatible digital wallet, anywhere in the world. This extends payout access to recipients in countries underserved by traditional banking, markets where your business may have been unable to operate cost-effectively. ## Getting started: a 4-step framework ### Step 1: Clarify the business case Pick your highest-friction payout corridor. Identify a segment of recipients frustrated with delays and fees. Quantify the current cost (per-payment fees, FX spreads, operational overhead) and model the improvement stablecoins would deliver. A single corridor with clear pain makes the strongest pilot candidate. ### Step 2: Choose an integration approach Decide whether to partner with an orchestration provider or build infrastructure in-house. **Orchestration providers** (Bridge, BVNK, ZeroHash) simplify implementation by handling blockchain selection, liquidity, custody, and compliance. Integration can take as little as two weeks via API. **Building in-house** gives more control and lower per-transaction costs at scale, but requires managing wallets, custody, banking relationships, and licensing. Most enterprises start with a partner and bring capabilities in-house as volumes grow. ### Step 3: Pilot Run stablecoin payouts alongside your existing system for 60 days. Start with a small number of recipients in your target corridor. Pilots quickly reveal the benefits and surface operational considerations like support needs, integration gaps, and reconciliation workflows that need updating. ### Step 4: Operationalize Turn the pilot into a standard payout flow. Lock in processes across finance, operations, support, and compliance, including SLAs, reconciliation, treasury management, and exception handling. Train support teams on stablecoin payouts. Then expand to new corridors and recipient segments. For a more detailed walkthrough, see our [global payouts blog post](/blog/global-payouts). ## Use cases ### Marketplace payouts Multi-sided marketplaces can deliver instant payouts to merchants, sellers, and service providers worldwide. DoorDash is [building stablecoin-powered payouts on Tempo](/blog/doordash-partners-with-tempo-to-bring-stablecoin-payments-to-its-global-marketplace) for its global merchant network across 40+ countries. ### Contractor and freelancer payments Companies with distributed teams can use stablecoins to pay contractors across markets. Near-instant onchain settlement can reduce payment uncertainty, while bank and off-ramp legs keep their own timelines. See our [stablecoin payroll guide](/learn/stablecoin-payroll). ### Affiliate and partner payments Programs with thousands of affiliates or partners across multiple countries can consolidate their payout infrastructure onto a single set of stablecoin rails, eliminating the need for country-by-country payment configurations. ### Emergency and humanitarian payouts When speed matters most (disaster relief, emergency contractor payments, or crisis response), stablecoin payouts deliver funds in seconds to any recipient with a mobile phone, regardless of local banking infrastructure. ## Customer proof Enterprises are already running stablecoin payout operations at scale: - **DoorDash** operates a three-sided marketplace across 40+ countries. They're working with Tempo to bring stablecoin-powered payouts to merchants where faster, more affordable settlement creates the most value. [Read the story](/blog/doordash-partners-with-tempo-to-bring-stablecoin-payments-to-its-global-marketplace) - **Felix** brings instant remittance settlement to Latin America, using Tempo's stablecoin rails to deliver funds in seconds instead of days. [Read the story](/blog/felix-brings-instant-remittance-settlement-on-tempo) ## Why Tempo for global payouts Tempo is the blockchain purpose-built for payment use cases like global payouts: - **Sub-second finality.** Payouts settle in under a second. Recipients get paid instantly, not in days. - **Stablecoin fees.** Fees paid in stablecoins, not volatile tokens. No gas token management, no crypto on your books. [Learn how](/blog/stablecoin-fees) - **Compliance controls.** Native [TIP-20 controls](/blog/compliance-controls) for sanctions screening, allowlists, blocklists, and Travel Rule compliance, critical for regulated payout operations. - **Privacy.** [Tempo Zones](/blog/introducing-tempo-zones) ensure payment details remain confidential between payer and payee. - **Global reach.** Dollar-denominated stablecoins on Tempo reach 140+ countries through the platform's ecosystem of on/off-ramp providers, exchanges, and fintech partners. Explore the [Tempo ecosystem](/ecosystem) For platforms and enterprises, this means faster payouts at lower cost with built-in compliance, all on a single set of rails. ## Why this matters for finance teams Global payouts are one of the cleanest entry points for enterprise stablecoin adoption: easy to pilot, deliver immediate measurable impact, and scale naturally to other payment flows once the business case is proven. Stablecoins can improve your payout operations. The next step is choosing which corridor to start with. [Contact Tempo's advisory team](/contact) to evaluate stablecoin payouts for your business. --- ## Frequently asked questions **Do I have to hold stablecoins to make payouts?** No. Orchestration providers like Bridge, BVNK, and ZeroHash handle the conversion between fiat and stablecoins. You send fiat from your bank account through their API, they handle the stablecoin transfer onchain, and the recipient receives funds in their preferred format, whether stablecoins or local currency. You never hold or manage stablecoins directly. **Will recipients understand stablecoins?** They don't have to. Modern payout infrastructure (embedded wallets, fintech apps, automated off-ramps) can make the stablecoin layer completely invisible. The recipient gets a notification that payment arrived and sees a balance in US dollars on a mobile app. As [our global payouts blog](/blog/global-payouts) notes, the experience is changing as new fintech apps hide the underlying complexity. **What about local currency conversion?** Recipients can convert stablecoins to local currency through supported off-ramps, often a one-click experience inside a fintech app or exchange, with fees typically far lower than traditional bank FX spreads (0.1–2.0% vs. 1–4%). Orchestration platforms can also automate conversion end-to-end so recipients receive local currency directly in their bank account or mobile wallet. **Is this only useful for emerging markets?** No. While cost savings are most visible in emerging markets with high fees and volatile currencies, stablecoin payouts are increasingly used in developed markets as well, especially for instant payouts, weekend payments, or premium payout features. Any corridor where traditional rails add friction is a candidate. **Is this regulated?** Yes, increasingly so. The GENIUS Act in the US and MiCA in the EU provide clear regulatory frameworks for stablecoins. Money transmitters and financial institutions must comply with Travel Rule requirements for transfers above jurisdictional thresholds. In practice, payout use cases are lower-risk because the payer is the corporation itself, and KYC/KYB is typically handled at onboarding. **How does reconciliation work with stablecoin payouts?** Every stablecoin transaction is recorded on the blockchain with a unique transaction hash, creating an immutable audit trail. This makes reconciliation significantly simpler than traditional rails, where payment status must be tracked across multiple banking partners. Tempo also supports [virtual addresses](/blog/virtual-addresses) for clean reconciliation at scale: each payout can be mapped to a unique address for automatic matching. --- **Continue learning:** [Stablecoins for Business](/learn/stablecoins-for-business) · [Cross-Border Payments](/learn/cross-border-payments) · [Payment Rails Compared](/learn/payment-rails) --- ## Rethinking GPU marketplaces for real-time agentic payments > Source: https://tempo.xyz/learn/gpu-marketplace/ > Language: en _GPU marketplaces are becoming more dynamic, but fine-grained metering is not the same as real-time payment settlement. The_ [_Machine Payments Protocol_](https://mpp.dev/) _(MPP) gives agents a standard way to discover paid services, authorize spend, and pay for usage._ [_Tempo_](/solutions/agentic-payments/) _provides low-fee stablecoin settlement and wallet infrastructure for agent workflows._ [Goldman Sachs estimates](https://www.goldmansachs.com/insights/articles/tracking-trillions-the-assumptions-shaping-scale-of-the-ai-build-out) a baseline of roughly $7.6 trillion in cumulative AI infrastructure investment across compute, data centers, and power between 2026 and 2031, that scale helps explain why access to GPU capacity is becoming a more active, price-sensitive market. The market for graphics processing unit (GPU) power has historically been shaped by long-term cloud contracts and human-operated procurement. That is changing as developers, applications, and AI agents look to compute one job at a time. When an agent can compare available capacity, choose a provider, and start work immediately, payments need to move just as quickly. As GPU capacity becomes more liquid and price-sensitive, another bottleneck appears: payment infrastructure built for aggregated billing, not high-frequency machine payments. Existing cloud providers and GPU marketplaces can match available compute with buyers, but many payment systems still rely on prepaid balances, cards, invoices, or month-end reconciliation. Agents need a way to pay for compute without waiting on human-centered billing workflows. MPP introduces a standardized way for agents and services to coordinate payments over HTTP. For GPU marketplaces, that means agents can discover paid compute services, understand payment terms, authorize a budget, and pay as they consume resources. ## What is a GPU compute marketplace? GPU compute marketplaces connect people or companies with available GPU capacity to developers and teams that need to rent it for workloads. Through these markets, buyers can compare GPU types, pricing, availability, provider reputation, region, and other requirements before choosing a resource. The category includes centralized and decentralized approaches. Examples include [Vast.ai](https://vast.ai/), [Runpod](https://www.runpod.io/), [Spheron](https://www.spheron.network/), and [Akash](https://akash.network/). Some focus on developer-friendly cloud instances. Others emphasize distributed infrastructure, decentralized provider networks, or programmable access for AI workloads. For agents, this means not only that more capacity is available, but that compute is becoming easier to compare and consume programmatically. ## How GPU spot-style pricing works Buying GPU compute on some platforms is starting to resemble a real-time market, where prices can change with supply and demand. There are two broad pricing patterns: - **Spot-style or dynamic pricing.** Prices can move based on availability, demand, provider preferences, and workload flexibility. When capacity is idle, prices may fall to attract buyers. When more workloads compete for the same resource, prices may rise. Flexible workloads like non-urgent inference jobs or training runs are best positioned to benefit. - **Fixed or on-demand pricing.** Buyers pay a set rate for a GPU over a defined period. This can make costs easier to forecast and may improve access to capacity, but it can also cost more than opportunistic spot-style pricing. Even when two listings advertise the same GPU model, quoted rates can vary. The hardware name is only part of the price. Memory configuration, networking, provider reliability, region, data center costs, duration, and interruption risk can all affect what a buyer pays. For a human developer, comparing those tradeoffs may be manageable. For an AI agent buying compute repeatedly across providers, the payment flow becomes part of the execution path. ## From fine-grained metering to real-time payment GPU and inference platforms already support fine-grained usage models. A provider may meter compute by second, token, API call, byte transferred, or another unit of consumption. But metering usage in small increments is different from settling payment for each unit as it is consumed. When a platform advertises per-millisecond or fine-grained billing, it usually means usage is measured in small increments and later charged through a billing cycle, prepaid balance, card, or invoice. The compute may be metered continuously, while payment settlement remains batched. That model works for many human-operated cloud services. It is less natural for autonomous agents that need to make frequent purchasing decisions, switch providers, and stay within a clear budget without requiring a person to approve each charge. ## What enables machine-native payments for compute? MPP gives paid services a standard HTTP payment flow. A service can return a 402 Payment Required challenge with supported payment options. The agent can respond with a payment credential, and the service can return a receipt once payment is accepted. For fixed-price operations, an MPP charge can support a one-time payment, such as paying for a single API request. For continuous usage, [MPP Sessions](/blog/mpp-sessions/) let an agent open a funded session with a defined spending cap, consume the service, and authorize incremental usage through signed offchain vouchers. That distinction matters for GPU compute. Instead of sending an onchain transaction for every millisecond of usage, the provider verifies vouchers as usage accrues, then settlement happens onchain at the end of the session or on a settlement schedule. The result is usage-based payment without forcing every small unit of compute into a separate payment transaction. ## How agents procure and pay for compute An agentic compute payment flow can work in a few steps: 1. **Discover a provider.** The agent finds a GPU provider, inference endpoint, or other paid compute service through a marketplace, an API, or the [MPP services directory](https://mpp.dev/services). 2. **Review payment terms.** The service presents payment details through an MPP challenge, including the amount, unit, method, and currency. 3. **Open a funded session.** For continuous usage, the agent opens an MPP Session with a defined spending cap. This gives the provider confidence that funds are available and gives the agent a clear budget. 4. **Consume compute.** As the agent sends requests, streams tokens, or runs jobs, it signs cumulative vouchers for the amount used. The provider can verify each voucher locally before continuing to deliver service. 5. **Settle and reconcile.** At the end of the session, or according to a settlement schedule, the final voucher is settled onchain. Unused funds can be released back to the agent's wallet. This flow keeps the payment step close to the service request. It also gives developers a cleaner way to connect metering, budgets, receipts, and settlement. ## How MPP and Tempo power agentic compute payments MPP is an open standard for machine payments co-authored by Tempo and Stripe. It is designed to be extensible across payment methods, and it runs on Tempo. Tempo is a payments-first layer-1 built for stablecoin settlement, predictable fees, and high-throughput payment flows. For agentic compute payments, several Tempo features matter: - **Stablecoin-denominated fees.** Tempo has no native gas token. [Transaction fees](https://docs.tempo.xyz/protocol/fees) can be paid directly in supported stablecoins, and standard TIP-20 transfers have sub-cent fees. - **Sub-second finality.** Tempo is designed for fast settlement, with [sub-second finality](https://docs.tempo.xyz/learn/tempo/performance) in normal conditions. - **Tempo Transactions.** [Tempo Transactions](https://docs.tempo.xyz/guide/tempo-transaction) support capabilities such as configurable fee tokens, fee sponsorship, batch calls, access keys, concurrent transactions, and scheduled transactions. - **Agent wallets and spending controls.** Agents can use Tempo Wallet or a Tempo-compatible wallet to transact within defined permissions and budgets. For GPU marketplaces, this means MPP can define how agents and services coordinate payment, while Tempo provides settlement infrastructure designed for stablecoin payments at high volume and low cost. ## The GPU market's missing layer: machine-native payments Fine-grained metering makes GPU markets more flexible. Machine-native payments make that flexibility usable by agents. An agent that can compare compute providers, switch as prices change, and pay within a defined budget can make GPU capacity more efficient to allocate. Providers can monetize usage directly, receive payment faster, and reduce reliance on manual invoicing or generic card flows. Developers get a payment primitive that fits how agent workloads actually run. Tempo and MPP were built for this shift because they connect three pieces of the workflow: agent discovery, usage-based authorization, and stablecoin settlement. That gives GPU marketplaces a path from "meter usage precisely" to "let agents pay for usage programmatically." Explore [MPP](https://mpp.dev/) and Tempo's [agentic payments overview](/solutions/agentic-payments/) to start building agentic compute payments. ## FAQ ### Do AI training workloads benefit from real-time GPU bidding markets? Some do. Flexible workloads that can pause, resume, or move between providers are better suited to spot-style pricing because they can respond to changing availability. Long-running workloads that require uninterrupted access may still be better served by reserved, dedicated, or fixed-price capacity. ### Do stablecoin and MPP payments replace existing billing or payment rails? Not necessarily. MPP and Tempo can complement existing billing systems by adding a machine-readable payment layer for high-frequency, usage-based transactions. A marketplace can still maintain its existing customer accounts, invoices, reporting, or procurement flows while using MPP for agentic payment interactions. ### How do I keep an agent from overspending on compute? With [MPP Sessions](/blog/mpp-sessions/), an agent can open a funded session with a defined spending cap before it starts using a service. The provider can verify incremental vouchers as usage accrues, and the agent cannot spend beyond the session's available funds. Tempo-compatible wallets and access keys can also help developers set permissions and limits for agent workflows. ### How can agents pay for per-millisecond compute usage? A provider can use [MPP Sessions](/blog/mpp-sessions/) to meter compute in fine-grained units while the agent authorizes usage through signed offchain vouchers. The session then settles onchain at close or on a settlement schedule, avoiding a separate onchain transaction for every unit of usage. --- ## How to accept stablecoin payments: integration for B2B companies > Source: https://tempo.xyz/learn/how-to-accept-stablecoin-payments/ > Language: en _B2B companies looking into accepting digital payments need user-friendly payment portals they can rely on, whether they're handling invoices or cross-border remittances. Stablecoins offer the flexibility, settlement speed, and security of blockchain infrastructure without the volatility of variable cryptocurrencies._ Accepting stablecoin payments adds a faster, fully programmable payment rail to your existing stack. It doesn't replace your existing banking relationships. It operates alongside them. This guide covers the core benefits of stablecoins for B2B operations and how to accept stablecoin payments by integrating with Tempo. ## Why stablecoins instead of ACH payments or wires? You don't have to choose between the two. Adding stablecoin payment infrastructure to your payment stack doesn't mean you can't offer traditional methods like ACH payments or bank transfers. You're adding a faster lane, not rebuilding the entire highway. Accepting stablecoin payments eliminates many of the pain points B2B companies face with traditional payment methods, especially across global or multi-party payment flows. Here are some of the most significant ways stablecoin payment gateways add value to B2B payment infrastructure. ### More predictable payment operations One disadvantage of traditional payment processors is unpredictable settlement times. A wire transfer made on Monday might clear the same day, or the funds might not be available until Thursday. You're at the mercy of the banks involved and their cut-off times. Stablecoin payments allow you to settle in seconds, no matter when you send them. Tempo makes settlement even faster by providing Dedicated Payment Lanes. When networks get congested, often due to heavy NFT or memecoin trading, payments slow down and transaction fees spike. Dedicated Payment Lanes isolate payment-only traffic at the protocol level, sidestepping those delays and inflated fees. Transaction costs are also much more affordable than typical vendor processing fees. Tempo charges less than a tenth of a cent per transaction. ### Programmable payment logic Traditional payment solutions excel at moving money from A to B, but customization is limited. Smart contracts on Tempo let you define exactly how money moves. You can automate routing decisions, program fee logic, and configure customer-specific payment rules with no manual intervention required. ### Transparent payment records and metadata Traditional payments move funds with minimal context. Payments arrive with basic details like the transacting parties and amount sent, but supporting context such as timestamps and audit trails typically lives in disconnected systems. That means you have to manually reconcile the data after every transaction. Stablecoin payments are verifiable onchain, so you can always check whether they've settled without asking a bank or other intermediary for updates. Tempo takes this a step further by embedding structured metadata into each transaction. Payments come with everything businesses need to audit and verify payments, including: - Transfer memos for easy reconciliation and record-keeping - Tamper-proof history - Precise timestamps - Cryptographic signatures verifying authenticity ## How do I accept stablecoin payments for my business? A five-step Tempo integration guide Here's how to accept stablecoin payments on your website by partnering with Tempo. ### 1. Map your B2B payment use case Start with the goal: what problem are you trying to solve, or what do you want stablecoin payments to unlock for you? This might be: - Accepting invoice payments from B2B customers - Enabling cross-border payments, [global payouts](/blog/global-payouts), and [remittances](/blog/remittances) - Settling marketplace participants - Funding embedded accounts ### 2. Choose your integration model B2B platforms and payment companies that want to control every part of the integration can build directly on Tempo using our [developer documentation and SDKs](https://docs.tempo.xyz). With this approach, accepting a stablecoin payment happens automatically onchain. The platform watches for and reconciles transactions automatically, so you don't have to make a separate API call to accept each payment. If you don't need to run your own infrastructure, [ecosystem partners](https://docs.tempo.xyz/ecosystem) can layer a no-code dashboard on top of Tempo. The platform adds checkout flows and higher-level APIs to get you up and running without the time and expense of developing a custom solution. ### 3. Configure payment, compliance, and settlement rules Tempo gives you granular control over a wide range of parameters, including: - **Who can make and receive payments.** This is governed by Tempo's [Policy Registry (TIP-403) specification](https://docs.tempo.xyz/protocol/tip403/spec). By configuring allowlist and blocklist policies, you maintain control over who can interact with your platform. - **Supported digital assets.** Tempo supports payments in [supported stablecoins](https://tokenlist.tempo.xyz/list/4217) bridged to or [issued on Tempo](/blog/stablecoin-issuance) from blockchains across the Web3 ecosystem. Users can also [pay transaction fees in any supported stablecoin](https://docs.tempo.xyz/guide/payments/pay-fees-in-any-stablecoin), such as USDC.e or USDT0. - **Settlement destinations.** Predefine where funds should land after a payment goes through. You can also use [virtual addresses](https://docs.tempo.xyz/guide/payments/virtual-addresses) for each customer to manage funds without creating separate onchain TIP-20 balances. - **Conversion rules.** If your payment flow requires converting between stablecoins, use the [built-in decentralized exchange](https://docs.tempo.xyz/protocol/exchange) to make the swaps automatically. - **Gas sponsorship.** Tempo lets you cover transaction fees on behalf of customers, removing one of the biggest obstacles to user adoption. ### 4. Connect payment data to finance workflows The next step is automating reconciliation by using [transfer memos](https://docs.tempo.xyz/guide/payments/transfer-memos). These 32-byte payment identifiers embed key data like customer IDs and order numbers into each transaction. That means each payment links cleanly to your existing finance systems. You can reconcile at scale without the heavy lifting of manual matching. Tempo's reconciliation process is based on onchain events. Every time a stablecoin transfer happens with an attached memo, a `TransferWithMemo` event is emitted. The event is indexed so teams can filter for the values they need, simplifying payment matching. This onchain event flow is the core of Tempo's native reconciliation features. If you need additional tooling, you have [ecosystem partners](/ecosystem) to choose from. ### 5. Test, monitor, and scale the payment flow The final step before going live is ensuring everything functions as it should. That means: - Sandbox testing to validate your integration on Tempo's testnet before handling real money - Monitoring for failed or delayed payments so you can act quickly when issues arise - Setting up exception handling to catch and triage issues automatically - Running reconciliation checks to confirm that onchain transactions map cleanly to internal records - Defining finance team standard operating procedures so your team can integrate the new payment rail into its daily workflows - Scaling to more customers or payment types ## Build faster, programmable payment flows with Tempo Stablecoin payments aren't just another cryptocurrency checkout solution for retail merchants on ecommerce platforms. For B2B companies, they're a fast, fully programmable way to accept structured payments with detailed metadata. With stablecoins, each transaction is simple and easy to reconcile. These benefits are compelling on their own, but Tempo raises the bar with Dedicated Payment Lanes, protocol-level compliance controls through TIP-403, and native fee sponsorship for gasless payment experiences. [Find out more about embedding B2B-first stablecoin infrastructure into your products with Tempo today.](/contact) --- **Continue learning:** [Stablecoins for business](/learn/stablecoins-for-business) · [Stablecoin payments](/learn/stablecoin-payments) · [Cross-border payments](/learn/cross-border-payments) --- ## Managing payout complexity for global payroll processing companies > Source: https://tempo.xyz/learn/managing-payout-complexity-global-payroll/ > Language: en _As companies hire beyond their home markets, their payroll providers are expected to make cross-border payments feel routine. That's hard to deliver, because traditional networks were built for large corporate transfers rather than high-frequency global payouts._ Providers want an infrastructure layer that makes settlements predictable and reliable. [Stablecoin rails](/learn/stablecoin-payroll/) work alongside traditional banking, giving you another way to move money internationally. ## 6 factors creating payroll settlement complexity Payment settlement complexity builds as you expand across borders and navigate local tax laws. Here are the 6 factors that complicate international payroll operations. ### Fragmented systems and data silos Global settlement platforms rely on separate local payroll service providers in each country. That setup works for local payroll management, but it complicates payment coordination across multiple markets. For example, one provider might send confirmation only after funds arrive, while another uses reference data that conflicts with your internal records. Your team ends up manually matching transactions inside your payroll software after the payout. A single payment network fixes that. [Tempo](/blog/mainnet/) centralizes all payment activity and reconciliation data into one hub, so you can track analytics and map them back to the original payroll instruction. ### FX exposure and payroll predictability Multi-currency payroll needs clear rules for when conversion happens, which rate applies, and who absorbs FX movement. A payout approved on Monday may settle days later, changing employer costs even if the worker receives the same local-currency amount. Local wage rules add another constraint: in some markets, employers may need to state or pay wages in local currency while managing devaluation exposure where permitted. Tempo can shorten the exposure window when payroll funds move instantly in stablecoins and a regulated local payout partner converts them or locks a rate. Recording the timestamp, rate, fees, and payroll ID onchain creates an audit trail. ### Compliance complexity at scale Payroll rules change constantly across borders. To maintain global payroll compliance, you need to account for: - Local tax laws - Worker classifications - Statutory benefits - Reporting deadlines - Pay frequency mandates Even then, tax rates, documentation requirements, and other factors can change in real time. Payment infrastructure doesn't replace legal or HR expertise, but it can help you enforce global payroll compliance controls more consistently across markets. Tempo's [Policy Registry](https://docs.tempo.xyz/docs/protocol/tip403/overview), for instance, gives TIP-20 token issuers a standardized route to reference transfer policies. The registry lets you add policies once and share them across multiple tokens automatically. ### Real-time employee expectations (EWA) Traditional payroll runs on fixed semi-monthly payment cycles where platforms settle wages in batches. Earned wage access (EWA) changes expectations: employees and contractors want instant access to wages they've already earned. That timeline pushes employers of record managing cross-border teams to abandon rigid schedules and process payouts immediately. To support earned wage access, your system has to track deductions and failed or partial payments daily to maintain an accurate real-time ledger and prevent costly overpayments. Systems built for batch cycles struggle with daily wage access, especially across borders. Legacy banks route international payments through multiple intermediary banks across time zones, charge flat transaction fees, and separate the money from accounting data during batch processing. Tempo settles payments instantly, around the clock, with the accounting data attached to each transaction. A worker can pull earned wages when they want and your ledger stays accurate without a batch run. ### Reconciliation and accounting integration After the money reaches the recipient, finance teams must match the payment to the correct payroll record, employee account, and ledger entry. Global settlements increase the risk of data mismatches. Bank statements often display inconsistent reference codes, and legacy accounting systems group payouts into vague batches rather than listing individual recipients. Tempo solves this by attaching a [structured memo](https://tempo.xyz/developers/docs/protocol/tip20/overview#transfer-memos) to every transaction, mapping it directly back to your platform's internal records. Automated workflows can filter and match payments instantly, reducing manual audits of faulty settlements. ### Cost unpredictability Cross-border payment fees pile up quickly, and the final bill rarely matches the baseline transaction fee. Add-ons like intermediary bank charges or return fees inflate settlement costs, making it difficult to forecast gross margins across thousands of payouts. Tempo uses dedicated payment lanes to keep fees low and predictable, even during peak network activity. [Paying recipients in USD stablecoins](/learn/global-payouts/) rather than volatile tokens lets you predict transaction costs before authorizing payments. ## The modern infrastructure layer A unified payroll system gives you a single interface to view payouts and standardize global operations. But efficiency comes from the layer underneath: the network routing the funds and the infrastructure supporting it. ### Why the underlying network matters This is where many payroll providers hit a wall. They can centralize the front-end user experience, but they can't influence the legacy payment systems running beneath it. Correspondent banks move money across borders reliably for one-off corporate transfers. High-volume payroll providers move thousands of scheduled payments simultaneously and attach contextual data to every transaction. Modern infrastructure runs alongside traditional banking and is purpose-built for that workload. ### What payroll-specific infrastructure adds Modern payment infrastructure gives the settlement layer more functionality, including: - **Real-time settlement.** Confirms payments instantly rather than processing through end-of-day banking schedules. - **Programmable logic.** Builds payment rules directly into the network so your team isn't managing scattered manual workflows. - **Reconciliation metadata.** Attaches structured, standardized references to every transaction, making automated payment matching easy. A dedicated payment lane like Tempo combines all three. Fees stay low and stable when activity rises, giving you more control over cross-border payments. ## What to evaluate when choosing a payroll settlement rail Keep an eye out for these features when choosing a payroll settlement rail: - **Production proof.** Look for infrastructure that's been tested in real payment environments beyond pilots and demos. Payroll is time-sensitive, and a network that buckles under live load creates immediate funding delays. - **Finality and throughput.** Prioritize networks with instant payment finality and the throughput to process thousands of concurrent payouts without slowing down during peak cycles. - **Cost predictability.** Make sure you know the exact cost of a payout before running it. Fluctuating transaction fees quickly erode margins. - **Stablecoin support.** Check which stablecoins the settlement rail supports and how those assets fit your payout markets. The right assets protect purchasing power for employers and international workers. - **Compliance infrastructure.** Choose a settlement rail that natively supports automated policy enforcement and permission-based approvals, so compliance work doesn't grow with your volume. - **Privacy.** Standard stablecoin transactions are publicly visible, which means anyone could see employee salary amounts. Pick a platform that protects this data. [Tempo Zones](https://tempo.xyz/developers/docs/protocol/zones) create a separate, secure environment for sensitive details: users within each zone can see specific transaction information, while the general public only sees cryptographic proofs of each payment. ## Modernize the settlement layer behind global payroll with Tempo These six challenges point to the same issue: many payroll platforms are trying to run real-time, multi-currency payout workflows on legacy networks built for slower, fragmented settlement. [Deel's collaboration with Tempo](/customer-stories/deel/) shows what changes when that layer is rebuilt. Deel, a global payroll and contractor management platform used by 40,000+ businesses across the world, built its [dollar-backed stablecoin wallet on Tempo](/blog/deel-launches-dlusd-stablecoin-wallet-for-global-contractors/) for eligible contractors in 80+ countries. A single chain now supports the stablecoin payout loop: businesses can fund payroll in stablecoins, contractors can receive earnings into a Tempo wallet, hold DLUSD, opt into earn, and spend by card. Upgrading the settlement layer changes what your platform can offer: faster payouts, predictable costs, and clean reconciliation records. Tempo helps payroll platforms move global payouts onto [stablecoin payment rails](/blog/stablecoin-fees/) with programmable transaction logic and rich metadata built directly into the network, so cross-border volume can scale without adding manual work behind the scenes. [Learn how Tempo can help you modernize your global payroll infrastructure](/contact/). --- ## Microtransactions with stablecoins: sub-cent payments at scale > Source: https://tempo.xyz/learn/microtransactions/ > Language: en _Card networks make payments under $1 uneconomical. Stablecoins enable sub-cent transactions that settle in seconds, unlocking pay-per-use pricing for APIs, content, and machine-to-machine commerce. The minimum viable payment drops from $0.30 to a fraction of a penny._ ## Why traditional rails cannot support microtransactions Every payment rail has a minimum viable transaction size, defined by its fixed fees. Below that threshold, the cost of processing the payment exceeds the payment itself. - **Card networks charge $0.30+ per transaction** as a fixed fee, plus a percentage. A $0.10 payment costs $0.30 to process. A $0.01 payment is out of the question. - **ACH costs $0.20-$0.50 per transaction.** Even for domestic payments, sub-dollar transactions are uneconomical. - **FedNow** improves speed but still carries per-transaction costs that make sub-cent payments impractical. This fee floor forces businesses into pricing models that do not match how their products are actually consumed. APIs get priced in monthly subscriptions rather than per-request. Content gets bundled into all-you-can-read plans. IoT data gets batched into hourly or daily invoices. In each case, the pricing model exists because the payment rail cannot support the natural unit of value exchange. ## How stablecoins enable microtransactions Stablecoins on efficient networks remove the fee floor that makes microtransactions impossible on traditional rails. - **Sub-cent fees.** On Tempo, transaction fees are denominated in stablecoins and measured in fractions of a penny. A $0.001 payment is economically viable. - **Instant settlement.** Payments finalize in under one second. No batch windows, no pending states, no multi-day settlement cycles. - **Programmable metering.** Smart contracts and access keys enable automated billing logic: charge per request, per minute, per byte, or per any unit of consumption. No invoicing, no reconciliation lag. - **No intermediaries.** Payments move directly from payer to payee. No card network, no payment processor, no acquiring bank extracting fees from each transaction. ## Key use cases ### API and compute billing Cloud providers and API services currently price by the hour, by the GB, or by monthly tier. With sub-cent stablecoin payments, billing can match actual consumption: charge per API request, per compute cycle, per inference call. A developer using an LLM API pays $0.002 per request as they make requests, not $200/month for a tier they may underuse. The service provider receives revenue immediately rather than at month-end. Both parties benefit from pricing that reflects actual usage. ### Content monetization Subscriptions bundle content into all-or-nothing packages. Microtransactions enable true unbundling: pay $0.05 to read one article, $0.01 per minute of video, $0.001 per song stream. For publishers, this opens revenue from the large audience that will not commit to a subscription but will pay for individual pieces. For creators, it enables direct monetization of every unit of content without platform intermediaries taking 30-50%. ### Machine-to-machine payments As IoT networks grow and AI agents become more autonomous, machine-to-machine commerce requires payment rails that operate at machine speed and machine scale. - **IoT sensor data.** A weather station sells real-time data to subscribers at $0.001 per reading. An autonomous vehicle pays for traffic data per intersection. - **AI inference.** An AI agent pays for LLM tokens, image generation, or code execution per unit consumed. [MPP Sessions](/blog/mpp-sessions) collapse unlimited micropayments into just two onchain transactions, enabling agents to transact at speeds that traditional payment rails cannot support. - **Autonomous agents.** Agents that book services, purchase resources, or transact with other agents need payment primitives that work without human approval for each transaction. Tempo access keys provide scoped, time-limited authorization for exactly this purpose. ### Subscriptions and recurring billing Microtransaction infrastructure also supports subscription models. Tempo [access keys with periodic spending limits](/blog/subscriptions-on-tempo) let users authorize recurring charges without re-prompting or holding their keys. A user subscribes by authorizing an access key scoped to a specific service with a per-period cap (for example, $50 per week for 50 weeks). The protocol validates each charge against the current period's remaining allowance and resets automatically. The user sets terms once, the service charges on schedule, and the user can revoke at any time. This same mechanism works for both human subscribers and AI agents. ## Benefits beyond cost Microtransactions with stablecoins deliver advantages beyond lower fees. ### Simplified reconciliation Every microtransaction is recorded on an immutable ledger with a unique hash, timestamp, sender, receiver, and amount. For businesses that currently batch thousands of small-value interactions into periodic invoices, per-transaction settlement eliminates the reconciliation overhead entirely. Each payment is its own receipt. ### New business models Sub-cent payments enable pricing models that were previously impossible: true pay-as-you-go APIs, per-article content access, real-time data feeds priced per data point, and machine-to-machine commerce where autonomous agents transact continuously. ### Developer-friendly primitives Tempo provides native primitives for metered billing (access keys with spending limits), streaming payments ([MPP Sessions](/blog/mpp-sessions)), and programmable payment logic (smart contracts). Developers integrate billing directly into their application logic rather than bolting on a separate payment provider. ## Why Tempo for microtransactions Tempo is designed for the high-volume, low-value payment patterns that microtransactions require: - **Sub-cent fees in stablecoins.** Transaction fees are fractions of a penny, paid in stablecoins. No volatile gas tokens required. [Learn more](/blog/stablecoin-fees). - **Sub-second finality.** Transactions settle in under one second with deterministic confirmation. Critical for real-time metered billing. - **Programmable access keys.** [Access keys](/blog/subscriptions-on-tempo) with periodic spending limits enable metered and subscription billing onchain without re-prompting users. - **MPP Sessions for streaming payments.** [MPP Sessions](/blog/mpp-sessions) collapse unlimited micropayments into two onchain transactions, scaling to machine speed for AI agent and IoT use cases. - **No account rent.** Provisioning wallets for millions of users or devices incurs no per-account fees on Tempo. This matters when wallet provisioning is a prerequisite for receiving microtransactions at scale. For developers and product teams, this means a payment network where billing logic, settlement, and reconciliation are native primitives, not external services bolted on after the fact. ## Next steps - Read about [MPP Sessions](/blog/mpp-sessions) for machine-to-machine payments - Learn how [subscriptions on Tempo](/blog/subscriptions-on-tempo) work with access keys - Explore [stablecoin payments](/learn/stablecoin-payments) end-to-end - Compare [payment rails](/learn/payment-rails) side by side - [Contact our team](/contact) to discuss your microtransaction use case --- ## Frequently asked questions **How small can a payment be on Tempo?** Tempo supports sub-cent transactions. Fees are denominated in stablecoins and measured in fractions of a penny, making payments of $0.001 or less economically viable. For high-frequency use cases, [MPP Sessions](/blog/mpp-sessions) collapse unlimited micropayments into just two onchain transactions, reducing per-payment cost effectively to zero. **Do users need a crypto wallet?** Not necessarily. For consumer-facing products, wallets can be embedded and abstracted so users interact with familiar interfaces (tap to pay, one-click purchase) without managing keys or understanding blockchain. For developer and machine-to-machine use cases, programmatic wallets are provisioned automatically. Tempo charges no account rent for wallet creation. **How does metered billing work on Tempo?** Tempo [access keys](/blog/subscriptions-on-tempo) let users authorize a service to pull funds within defined constraints: a maximum amount, specific tokens, and an expiry. With periodic spending limits, access keys support recurring caps that reset automatically (for example, $50 per week). The protocol validates each charge against the current period's remaining allowance. **Can this support subscription models?** Yes. Tempo access keys with periodic spending limits enable subscription billing onchain without re-prompting users or holding their keys. A user authorizes an access key with a per-period cap, and the service charges on schedule. The user can revoke at any time. See the [subscriptions on Tempo guide](/blog/subscriptions-on-tempo) for details. **Is this suitable for consumer-facing products?** Yes, with the right abstraction layer. Consumers do not need to understand stablecoins or blockchain. Embedded wallets, fee sponsorship (so users never see network fees), and familiar payment interfaces make sub-cent payments invisible to the end user. The infrastructure handles conversion, custody, and settlement behind the scenes. **How do MPP Sessions work for machine payments?** [MPP Sessions](/blog/mpp-sessions) let an AI agent or machine deposit funds into an onchain escrow with one transaction, then exchange signed offchain vouchers for each unit of service consumed. When the session ends, a single settlement transaction closes the channel. This collapses unlimited micropayments into two onchain transactions regardless of session length. Voucher verification is a signature check that runs in microseconds. --- ## Onchain credit: how it works for payments and receivables > Source: https://tempo.xyz/learn/onchain-credit/ > Language: en _Onchain credit uses blockchain infrastructure to fund, record, or repay loans. For payment platforms and businesses with receivables, stablecoin funding can connect financing to an existing payment workflow. Underwriting, repayment rights, and credit risk remain central to the arrangement._ A payment provider may need to fund a payout before its customer collections arrive. A supplier may need cash for an invoice due in 30 days. Both face a timing gap between an obligation and the money expected to cover it. Credit bridges that gap. Using stablecoins for funding and repayment gives businesses another way to move the money and track its progress against the underlying obligation. ## What makes credit onchain Onchain credit describes how a credit arrangement operates. A blockchain can record a loan balance, transfer funds to a borrower, distribute repayments, or represent an investor's interest in a pool of loans. An arrangement may use only some of these functions. Three related terms describe different parts of the market: |Term|What it describes| |-|-| |Onchain credit|Credit that uses blockchain infrastructure for part of its lifecycle| |Crypto-backed lending|Borrowing secured by digital assets, often worth more than the loan| |Tokenized private credit|Privately negotiated debt, or an interest in a debt portfolio, represented through tokens| These categories overlap. The technology used to record a loan does not determine its collateral, pricing, or legal structure. Where a debt instrument or fund interest is a security, representing it as a token does not remove applicable securities obligations. [SEC staff describes this principle](https://www.sec.gov/newsroom/speeches-statements/corp-fin-statement-tokenized-securities-012826-statement-tokenized-securities) in its discussion of tokenized securities. ## Funding payments before collections arrive Consider a hypothetical payment provider with approved payouts due today and corresponding collections available tomorrow. Under an approved credit facility, it draws stablecoins, sends them to a settlement partner, and repays the facility when collections arrive. This can reduce the provider's own cash committed to prefunding, depending on collateral and liquidity requirements. The credit must be available and the receiving partner must accept the stablecoin. A local-currency payout still depends on conversion and local payment rails. [Huma describes this use case through Arf](https://blog.huma.finance/huma-built-payfi.-now-institutions-build-on-huma?hs_amp=true), which supplies short-duration stablecoin credit to licensed payment institutions. Eligibility and terms belong to the provider. ## Advancing cash against receivables A receivable is money a customer owes a business. In a hypothetical invoice-financing arrangement, a lender verifies an invoice, evaluates the customer's ability to pay, and advances part of its value. Stablecoins carry the advance and repayment, while an onchain record links those movements to the financed receivable. [Huma's loan-management documentation](https://docs.huma.finance/products/huma-institutional/user-manuals/borrowers/loan-management) illustrates the mechanics: borrowers obtain credit approval, draw against eligible receivables, and repay through the protocol. The contract coordinates these actions. Invoice verification and the legal rights attached to the receivable remain essential. ## What the infrastructure changes A shared record of transfers helps participants track funding and repayments. Smart contracts can automate agreed calculations and distributions. For operations teams, a potential benefit is matching those movements to the right facility with less manual reconciliation, provided the payment data connects to internal records. Origination, underwriting, servicing, and collections remain separate responsibilities. [Maple's borrower process](https://docs.maple.finance/maple-for-borrowers/introduction), for example, includes identity checks, a credit review, and agreed loan terms. Its [legal documentation](https://docs.maple.finance/legal/borrower-mla) establishes remedies following default. An onchain payment record confirms that funds moved. It does not establish that an invoice is genuine or that a borrower's financial statements are complete. ## Evaluating a credit workflow Start with a specific timing gap and an identifiable source of repayment. Establish who supplies capital, makes the credit decision, services the loan, and holds the rights to recover money after default. Compare the full cost: interest, origination fees, conversion, servicing, and required collateral. Lower network fees alone do not establish cheaper borrowing. Assess borrower losses, withdrawal restrictions, smart contract failures, stablecoin risk, and any dependence on bridges or external data. Define the operational result before choosing the infrastructure, such as less cash committed to prefunding or fewer unmatched repayments. Measure that result against the existing workflow. ## FAQ ### Is onchain credit always secured by crypto? No. Onchain describes the infrastructure used for part of a credit arrangement. Collateral can include digital assets or receivables, and some facilities rely on other forms of underwriting. The facility's terms determine its security and repayment rights. ### Does stablecoin funding mean an instant bank payout? No. Stablecoin settlement covers the onchain transfer. Delivery to a bank account depends on conversion, the payout provider, local payment rails, and applicable checks. ### Does putting a loan onchain reduce its risk? An onchain record can make transfers easier to track, but it does not verify an invoice or guarantee repayment. Borrower, legal, liquidity, smart contract, and stablecoin risks still need to be assessed. ## Explore credit use cases with Tempo If you're interested in credit use cases, [get in touch](/contact/?interest=credit&source_article=onchain-credit&cta_location=article_footer). --- ## What is Open USD (OUSD)? > Source: https://tempo.xyz/learn/open-usd-ousd/ > Language: en _Open USD (OUSD) is a US dollar stablecoin designed for global money movement. It combines no-cost minting and redemption with shared reserve economics and governance shaped by the businesses that use it._ Like other dollar-denominated [stablecoins](/learn/what-are-stablecoins/), OUSD lets businesses hold and move dollar value on a blockchain. Its design focuses on three questions for businesses using stablecoins at scale: what it costs to move between dollars and stablecoins, who receives the revenue from reserves, and how decisions about the stablecoin are made. ## Who is behind OUSD [Open Standard](https://joinopenstandard.com/about) is the independent company behind OUSD. Its founding partners include Coinbase, Mastercard, Shopify, Stripe, and Visa. Open Standard governs and operates OUSD, while Bridge Building Inc. is its issuer. These are distinct roles: Open Standard establishes the shared economic and governance model, and Bridge provides issuance infrastructure. ## How OUSD works OUSD is backed by reserves. The [OUSD reserve dashboard](https://ousd.fyi/) shows holdings of cash and US Treasuries. Open Standard's [launch announcement](https://joinopenstandard.com/blog/ousd-is-live) names BlackRock, Lead Bank, and BNY as institutions holding the reserves. Businesses access OUSD through providers that support minting and redemption at a 1:1 US dollar conversion rate: 1. **Minting:** A business converts US dollars into OUSD through a supported provider. 2. **Transferring:** OUSD moves between wallets on a supported blockchain, allowing businesses to send payments or move funds between accounts. 3. **Redemption:** A business converts OUSD back into US dollars. The redeemed tokens are removed from circulation through a process called burning. Open Standard's [integration paths](https://joinopenstandard.com/integrate) offer minting and burning at no cost. That applies to conversion into and out of OUSD. Network fees and charges for other provider services are separate. ## How reserve revenue is shared The assets held in a stablecoin's reserves can generate revenue. OUSD's model shares nearly all of that revenue with the companies growing its adoption. According to Open Standard's [launch announcement](https://joinopenstandard.com/blog/ousd-is-live), partners earn rewards in proportion to the OUSD supply and activity they drive on their platforms. For a payment provider or financial platform, this creates a way to participate in the economics of the stablecoin it distributes and uses. Businesses must sign up as Open Standard partners to earn these rewards. Rewards are part of that partner relationship, rather than an automatic return for anyone holding OUSD. ## How governance is structured Open Standard is designed to give participating businesses a role in OUSD's direction. Its [published governance structure](https://joinopenstandard.com/blog/company-structure-and-leadership) calls for a board of directors drawn from its founders and representing its shareholders. Founders and participating partners have the opportunity to earn equity based on the supply and activity they generate. The aim is to give businesses contributing to OUSD's adoption a stake in the company and a voice in how the infrastructure develops. ## What businesses can use OUSD for OUSD is designed for financial activity across payments, settlement, treasury, and trading. These uses include: - **Payments and payouts:** Fund accounts, pay suppliers, and send funds to customers or other recipients. - **Settlement:** Move dollar value between businesses and financial platforms using a shared onchain asset. - **Treasury:** Hold operating balances and move funds between accounts as payment needs change. - **Trading:** Use OUSD as a dollar-denominated asset on supported trading venues. The stablecoin is one part of these workflows. The blockchain determines how the onchain transfer settles, while providers handle services such as custody, currency conversion, and delivery to bank accounts. Onchain settlement and receipt of funds in a bank account are separate steps. ## How to access OUSD Open Standard lists integration options through Stripe, Bridge, Privy, Mastercard, Coinbase, and Visa. Businesses complete onboarding and account setup with their selected provider, and access depends on that provider's terms, eligibility requirements, and geographic coverage. OUSD is supported natively on Base, Ethereum, Solana, and Tempo. Open Standard's [integration page](https://joinopenstandard.com/integrate) lists the official contract addresses and current access options. Provider support can vary by network and service. ## Put OUSD to work on Tempo Tempo brings together native OUSD, near-instant onchain settlement, and sub-cent network fees on a blockchain built for payments. OUSD [launched on Tempo with $400M+ in liquidity](/blog/ousd-is-live-on-tempo/), deployed with partners across decentralized exchanges, stablecoin swaps, and bridges. Businesses can use OUSD on Tempo to fund accounts, hold operating balances, make payments and payouts, and swap into other supported stablecoins. Infrastructure partners support these flows across ramps, wallets, custody, security, and liquidity. To put OUSD to work across payments, settlement, and treasury, [explore OUSD on Tempo](/ousd/) or [get in touch](/contact/) to discuss your integration. --- ## Payment rails compared: ACH vs wire vs SWIFT vs stablecoins > Source: https://tempo.xyz/learn/payment-rails/ > Language: en _Every business payment travels over a rail: the infrastructure that moves money from sender to receiver. ACH, Fedwire, and SWIFT have served this purpose for decades, but each carries tradeoffs in speed, cost, and availability. Stablecoins introduce a fourth option: instant, final, 24/7, and low-cost._ ## What are payment rails? A payment rail is the underlying infrastructure that transfers funds between parties. It defines how fast money moves, what it costs, when it is available, and whether a payment can be reversed after the fact. Most businesses use multiple rails depending on the transaction: ACH for payroll, wires for high-value transfers, SWIFT for international payments. Each rail was designed for a specific era and set of constraints. Understanding their tradeoffs is essential for optimizing your payment operations. ## ACH (Automated Clearing House) **ACH** is the backbone of routine US domestic payments. It is a batch-based system operated by the Federal Reserve and The Clearing House, processing payments like payroll, vendor payments, and subscription billing. - **Speed.** Same-day ACH processes in batches with multiple daily cutoffs. Standard ACH settles in 1–2 business days. - **Cost.** Typically under $0.50 per transaction, the cheapest traditional rail. - **Finality.** Reversible. ACH transactions can be returned or disputed for up to 60 days, creating clawback risk for businesses. - **Availability.** Business hours only, with batch processing windows. No weekends or holidays. - **Best for.** High-volume, routine domestic payments where timing is not critical: payroll, subscriptions, recurring vendor payments. The hidden cost of ACH is the settlement gap. You may release goods or services before the payment is truly final, exposing your business to reversal risk. ## Wires (Fedwire) **Fedwire** is the US real-time gross settlement (RTGS) system operated by the Federal Reserve. Each wire settles individually and immediately at the central bank level. - **Speed.** Instant settlement for domestic transfers during operating hours. - **Cost.** $3–$5 per domestic wire. International wires cost $25–$50+ when accounting for intermediary bank fees. - **Finality.** Irrevocable once settled. No clawback risk. - **Availability.** 22 hours per day, Monday through Friday. Closed on weekends and Federal holidays. - **Best for.** High-value transactions requiring absolute finality: real estate closings, legal settlements, large treasury transfers. The tradeoff is cost and operational overhead. Wires are expensive for high-volume use and often require manual initiation and approval workflows. ## SWIFT (international messaging) **SWIFT** is not a payment rail. It is a messaging network that connects banks worldwide. When you send an international wire, SWIFT routes the payment instruction through a chain of correspondent banks, each of which processes, holds, and forwards the funds. - **Speed.** 1–5 business days depending on the corridor and number of intermediaries. - **Cost.** $25–$50+ per transfer, including originating bank fees, intermediary bank fees, and recipient bank fees. FX spreads add 1–3% on top. - **Finality.** Final once settled, but settlement is delayed and opaque. - **Availability.** Business hours of each bank in the chain. A Friday afternoon transfer may not begin processing until Monday in the destination country. - **Best for.** International payments when no alternative is available. Increasingly being supplemented or replaced by faster options. The core problem with SWIFT is the correspondent banking chain. Each intermediary adds cost, delay, and opacity. Funds can sit in intermediate accounts for days, and tracking payment status requires manual follow-up. ## Stablecoins **Stablecoins** are blockchain-based digital assets pegged to fiat currencies, backed 1:1 by reserves. As a payment rail, they combine the finality of wires with the low cost of ACH, and add 24/7 availability and global reach. - **Speed.** Seconds. On Tempo, transactions finalize in under one second. - **Cost.** Sub-cent per transaction. No intermediary fees. - **Finality.** Irrevocable once confirmed on-chain. No clawback risk. - **Availability.** 24/7/365. No banking hours, cutoffs, or holiday schedules. - **Programmability.** Smart contracts enable automated escrow, conditional payments, and batch operations. - **Best for.** Cross-border payments, time-sensitive settlement, mass payouts, weekend/holiday operations, and any scenario where the speed-cost tradeoff of legacy rails is unacceptable. For a deeper look at how stablecoins maintain their value, see [What Are Stablecoins?](/learn/what-are-stablecoins). ## Comparison table |Feature|ACH|Wires (Fedwire)|SWIFT|Stablecoins| |-|-|-|-|-| |**Cost**|Under $0.50|$3–$5 domestic; $25–$50+ international|$25–$50+ plus FX spreads|Sub-cent| |**Speed**|Same-day to T+2|Instant (business hours)|1–5 business days|Seconds (24/7)| |**Finality**|Reversible (up to 60 days)|Final|Final (once settled)|Final| |**Operating hours**|Business hours, batch windows|22 hrs/day, M–F|Business hours per bank|24/7/365| |**Programmability**|None|None|None|Smart contracts| |**Global reach**|US domestic only|US domestic (international via SWIFT)|200+ countries|Global (any internet connection)| |**Best for**|Payroll, subscriptions, routine payments|High-value treasury, legal settlements|International payments (legacy)|Cross-border, mass payouts, real-time settlement| ## Choosing the right rail No single payment rail is optimal for every transaction. The right approach is selecting the best rail for each use case: - **ACH** remains the right choice for high-volume, routine domestic payments where timing is not critical and cost is the primary concern. - **Wires** are necessary for high-value domestic transactions that require immediate, irrevocable finality during business hours. - **SWIFT** is still required for international payments into corridors where stablecoin off-ramps are not yet available. - **Stablecoins** are optimal for cross-border transfers, time-sensitive payments, off-hours settlement, and high-volume payouts where legacy fees add up. Many enterprises are adopting a multi-rail strategy: ACH for payroll, wires for large domestic transfers, and stablecoins for everything cross-border and time-sensitive. ## The stablecoin sandwich The most common enterprise model for stablecoin payments does not require holding crypto. The **stablecoin sandwich** uses stablecoins as a transport layer while keeping both ends in fiat: 1. **Fiat in.** Your bank or payment provider converts USD to a stablecoin like USDC. 2. **Transfer.** The stablecoin moves over the blockchain in seconds for sub-cent fees. 3. **Fiat out.** The recipient's provider converts back to local currency and deposits into their bank account. This model delivers wire-speed finality at ACH-level cost for international payments. Neither party manages crypto. Learn more about how this works in practice in our [stablecoin payments guide](/learn/stablecoin-payments). ## Why this matters for finance teams Payment rail selection directly impacts your cost structure, working capital, and operational efficiency. Finance teams that optimize rail selection can: - **Reduce payment costs by 60–80%** on cross-border transactions by replacing SWIFT with stablecoin rails - **Eliminate settlement delays** that tie up working capital for days - **Extend operations** to 24/7 without banking-hours constraints - **Improve auditability** with immutable, on-chain transaction records The shift is not about replacing all legacy rails overnight. It is about adding stablecoins to your payment toolkit and routing each transaction to the optimal rail based on cost, speed, and finality requirements. **Next steps:** - Learn how [stablecoin payments](/learn/stablecoin-payments) work end-to-end - Explore [cross-border payments with stablecoins](/learn/cross-border-payments) - Read the [stablecoin fundamentals](/learn/what-are-stablecoins) - [Talk to our team](/contact) about optimizing your payment rails --- ## Frequently asked questions **Can stablecoins replace ACH?** Stablecoins complement ACH rather than replace it entirely. ACH remains cost-effective for high-volume routine domestic payments like payroll and subscriptions. Stablecoins are superior for cross-border transfers, time-sensitive payments, weekend and holiday settlement, and scenarios where finality matters. Most enterprises adopt a multi-rail strategy. **What about same-day ACH?** Same-day ACH improves speed but still operates in batch windows during business hours, has a $1 million per-transaction cap, and remains reversible. Stablecoins settle in seconds, 24/7, with no transaction cap and immediate finality. For time-sensitive or high-value payments, stablecoins offer a meaningfully better profile. **Do I need to manage crypto to use stablecoin rails?** No. The stablecoin sandwich model means you start and end in fiat. Your payment provider or bank handles the on-chain conversion and transfer. Neither the sender nor the receiver needs crypto wallets, private keys, or blockchain expertise. **Is stablecoin payment infrastructure regulated?** Yes. The US GENIUS Act and the EU's MiCA framework establish reserve, disclosure, and licensing requirements for stablecoin issuers. Payment platforms like Tempo enforce KYC/KYB onboarding, transaction monitoring, and sanctions screening, the same compliance standards applied to traditional payment rails. **How do stablecoins handle cross-border payments differently than SWIFT?** SWIFT is a messaging network that routes through a chain of correspondent banks, adding 3–5 days of delay and $25–$50+ in fees per transfer. Stablecoins transfer value directly between parties on a blockchain in seconds for sub-cent fees, with no intermediary chain. Read our [cross-border payments guide](/learn/cross-border-payments) for a detailed comparison. --- ## Payment reconciliation: Bridging onchain with ERP > Source: https://tempo.xyz/learn/payment-reconciliation/ > Language: en Payment reconciliation still runs on the logic finance teams already know: Match settlement data to expected payments, tie transactions back to invoices and vendors, and close the books on a predictable cadence. [Stablecoins add a new settlement](https://tempo.xyz/learn/stablecoin-settlement/) source that today’s reconciliation tooling wasn’t built to ingest. It’s not a replacement for ACH, wires, or SWIFT, but rather a rail that works alongside them. A confirmed onchain transaction doesn’t arrive as a journal entry; it arrives as a transaction hash, and someone still has to connect that hash to an invoice and an account in the ERP. Payment-focused blockchains like Tempo’s Layer 1 show how to build a reconciliation-ready settlement layer without forcing finance to rebuild ERP, treasury, and accounting systems. ## What kinds of systems are used to reconcile stablecoin payments? There’s no single tool or platform that handles every aspect of [stablecoin reconciliation](https://tempo.xyz/learn/what-are-stablecoins/). In practice, several layers perform complementary functions. While these layers won’t all look the same for every organization, the primary goal remains the same: Translate onchain activity into more familiar finance systems. ### Digital-asset subledgers produce audit-ready records Blockchains prove transactions happened. Digital-asset subledgers add in the missing business context by mapping onchain activity directly to your accounting system. With these protocols, you can link [stablecoin settlements](https://tempo.xyz/learn/stablecoin-payments/) to different events like invoices or internal transfers and generate journal entries that align with your chart of accounts. Without this layer, someone is manually tracing entries back to blockchain explorers to build an audit trail. With it, every accounting entry carries its underlying [blockchain transaction](https://tempo.xyz/learn/blockchain-payments/) reference natively. If your audit process still involves manually cross-referencing transaction records, evaluate this layer first. ### Treasury orchestration layers track and route funds Enterprises don’t keep their stablecoin treasury parked in one account. Funds constantly flow between different operational wallets and custodial partners, sometimes hopping across multiple blockchains. Treasury orchestration layers coordinate automated movements between accounts while providing constant visibility into stablecoin treasury management. Consolidated balances from your [treasury layer](https://tempo.xyz/blog/corporate-treasury/) highlight the latest liquidity across your organization while keeping internal transfers clearly separate from stablecoin-related revenue and expenses. Teams managing stablecoin liquidity across multiple accounts should treat this as mandatory tooling. ### Native ERP integrations record stablecoin flows No matter where a transaction settles, finance closes the books on ERP. The most efficient way to bring stablecoins directly into an existing ERP system is with native integrations. That way, finance doesn’t have to create a custom reporting process that separates digital assets from the entire financial picture. Teams with native ERP integrations use the same controls and approval workflows for [traditional rails](https://tempo.xyz/learn/payment-rails/) plus all stablecoin payments, fees, and journal entries. Without this integration, finance teams have to track digital assets on separate spreadsheets and tools, creating double the work and a messy parallel reporting process. This increases the risk of human error and compliance mistakes. ## How do companies connect stablecoin activity to ERP systems? Blockchain behaves very differently than traditional payment rails, but many enterprises nowadays want ways to bring stablecoins into their finance stack with minimal friction. Combining the right metadata with direct ERP integrations is proving to be a winning strategy for smooth stablecoin reconciliation. ### Structured metadata maps payment to records Before sending or receiving stablecoins, enterprises give each payment meaning by attaching structured metadata. Whether this includes invoice numbers, customer or vendor IDs, or purchase order references depends on the nature of the transfer, but these identifiers will always point to the business context. Because the metadata stays with the onchain settlement throughout its journey, reconciliation systems can use it to determine what happened when an onchain transaction settled. So, while the blockchain provides proof of settlement, the metadata covers the context required for accounting. ### Connectors and APIs sync activity into the ERP Connectors and APIs handle the literal data exchange between a blockchain infrastructure and existing enterprise financial systems. Once one of these integrations detects new onchain settlements, it can retrieve all the transaction details and translate them into journal entries or payment records that ERP systems expect. Depending on the implementation, APIs and ERP connectors can synchronize records through event-driven updates, polling, or scheduled batches. In either case, there’s no need for slow manual tasks like exporting blockchain transactions. Finance teams enjoy automated payment reconciliation alongside other traditional transactions like [wire transfers](https://tempo.xyz/learn/wire-transfer-fees/) and ACH. ## What accounting and treasury issues can these systems help address? The value of adding these layers of stablecoin reconciliation to a tech stack extends beyond just keeping accurate records. With these integrations in place, enterprises can actually realize many of the operational benefits often ascribed to these digital assets: - **Settlement timing becomes predictable:** With stablecoins, transactions finalize onchain rather than sitting in a pending state waiting on a settlement window. This means enterprises have visibility into confirmed onchain balances and a more accurate picture for forecasting and liquidity management. However, redeeming those stablecoins and delivering fiat funds to a bank account still depend on offchain processes from issuers and payment providers. - **Manual reconciliation work drops:** Since stablecoin rails with structured metadata and integrations automatically sync with accounting and ERP, there’s less back-and-forth resolving mismatches at month end. Neither of these is unique to any one chain, and neither replaces the rails finance already runs on. However, what differs by provider is how much of that infrastructure you have to build yourself versus how much comes structured from the start. ## How Tempo supports reconciliation with existing treasury and ERP systems The gap between instant settlement and automated reconciliation is usually filled by custom integration work. This involves interpreting payment data after settlement happens, then reconstructing context that wasn’t captured at the time. Tempo captures payment references at the protocol level, giving integrations a consistent starting point for reconciliation. ### Metadata that supports mapping into existing finance systems For metadata to be useful downstream, it has to survive the settlement process intact and map cleanly into whatever finance system receives it. [TIP-20 transfer memos](https://tempo.xyz/developers/docs/guide/payments/transfer-memos) carry 32-byte references that integration logic can map to offchain ERP systems or ISO 20022 payment records. Note that while this feature links onchain transactions to existing financial workflows, it doesn’t provide a complete ISO 20022 message or eliminate the need for data mapping or translation. Your ERP and accounting systems remain the source of truth for financial controls and accounting. Tempo provides payment references that integrations can use for reconciliation to reduce operational work dealing with onchain transactions. ### Settlement without re-orgs Closing the books also requires certainty that settlement records won’t be altered by chain reorganizations. Chains with probabilistic finality carry a small but real risk that a re-org alters a confirmed transaction after the fact. Once finalized on Tempo, onchain transactions are not reversed by chain reorganizations. This feature gives finance teams the certainty they need for their onchain settlement records. ### Predictable fees in the context of total payment cost Cost predictability matters, too, for financial forecasting. [Tempo’s transaction fees](https://tempo.xyz/blog/stablecoin-fees/) can be sub-cent and always paid in USD-denominated stablecoins, so accounting teams don’t have to factor in volatile digital assets. Actual fees depend on gas usage and the applicable fee, so costs can vary by transaction. That said, transaction fees are one line in a larger economic picture. FX conversion, as well as intermediary costs, prefunding requirements, and reconciliation labor all still factor into the total cost of a payment stack. ### Case study: Coastal Financial Corporation [Coastal Financial Corporation](https://tempo.xyz/customer-stories/coastal/) is building stablecoin-settled payment infrastructure with Tempo while keeping all its financial partnerships and regulatory checks in place. Tempo’s memo fields can help Coastal’s finance teams link onchain transactions to offchain financial records, while wallet allowlisting can limit participation in the planned payment flow to approved wallets. As Brian Hamilton, President of CCBX at Coastal Bank, put it, “By integrating stablecoin capabilities and Tempo's blockchain-based infrastructure into our platform, we're enabling our partners to build more seamless, efficient experiences for their customers while staying grounded in the trust and reliability of the banking system.” If you’re exploring stablecoin payments, Tempo’s features like memo fields and allowlisting can support your cross-border payment workflows with cleaner data transfer and defined participation controls. [See how Tempo](https://tempo.xyz/) can bring smoother stablecoin settlement to treasury and ERP systems. ## FAQ ### How is reconciling stablecoin payments different from bank reconciliation? The reconciliation process is largely the same for stablecoins and traditional bank transfers. What changes is the source of the settlement data. Rather than matching transactions against a bank statement, finance reconciles payments against onchain settlement records with the help of structured metadata. This supplies business context a bank statement line item wouldn’t otherwise carry. ### Do stablecoin payments replace treasury or ERP systems? No. Onchain settlements still need to flow into the same systems finance uses for cash management and reporting. Stablecoins are an additional settlement source, not a replacement system. ### Can an existing ERP or TMS handle stablecoin reconciliation, or is additional tooling needed? In most cases, APIs and connectors extend existing ERP and treasury systems to handle stablecoin settlement. Alongside integration tools, structured metadata tied to onchain transactions communicates the business context of each stablecoin settlement so legacy accounting systems can recognize it. --- ## Session keys: Speeding up onchain agentic settlement > Source: https://tempo.xyz/learn/session-keys/ > Language: en Autonomous onchain payments won’t flourish with externally owned account (EOA) wallets. Even though EOA wallets can let software sign transactions, that’s not enough to prepare them for the demands of machine-to-machine commerce. For autonomous payments to work in an onchain environment, there needs to be a safe, reliable way to delegate authority. Only bounded delegation gives AI agents the independence to make payments while limiting their authority through clear rules over spending power. Ethereum’s shift toward “Account Abstraction” through ERC-4337 provided a framework to put bounded delegation into practice. With smart accounts, it’s possible to use programmable validation logic that brings predictability to an agent’s activities. Account abstraction wallets also bring new functionalities like session keys and gas abstraction that give developers even greater power to authorize their agentic payment flows. ## What permissions can a session key have? Session keys give AI agents the power to pay on blockchains without the constant need to approve every transaction. Although this frees up [agentic payment flows](https://tempo.xyz/solutions/agentic-payments/), it doesn’t mean agents can do whatever they want. Users set the parameters in their smart accounts for what, where, and how long an agent can pay with these special keys. ### Payments up to a set limit The first way to create boundaries in a session key is to set a clear spending budget. These rules could include a total session amount a session key can’t exceed, as well as per-transaction caps to keep individual purchases in check. For example, a session key might have a spending budget of \$5,000 and a per-transaction cap of \$50; in that case, the agent can spend up to \$5,000 over its lifecycle and will never exceed \$50 for a single transaction. Note that the above example depends on an implementation system that enforces both the total budget and per-transaction limits. The per-token spending budgets on [Tempo’s Account Keychain](https://tempo.xyz/developers/docs/protocol/transactions/AccountKeychain) don’t automatically impose a per-transaction cap. Spending-limit checks cover direct TIP-20 transfers and approval increases, account-paid fees, and supported protocol spending paths. They don’t cover every token movement through arbitrary contracts. Developers need to verify which transactions these checks cover and combine token budgets with call scopes and safeguards for transactions they don’t. ### Calls to approved contracts only Developers can add even more safeguards to their session keys with allowlists. Whatever functions, smart contracts, or wallet addresses in these allowlists tell the session key exactly where it can go, which naturally bars unwanted interactions. ### Expiry adds time dimension Besides telling session keys what they can and can’t do, these tools also have time limitations. Adding a “Time-to-Live” (TTL) expiration window means a session key will automatically expire within a predefined timeframe. Even if the session key didn’t reach its max budget, it would automatically become worthless once the set deadline passed. ### Users are always in control Even though session keys and AI agents may seem to have a life of their own, encoded parameters ensure the wallet owner stays in the driver’s seat. With a limited key, permissions restrict which actions an agent performs while the key can’t change its own permissions to expand authority. However, these protections depend on the [type of key](https://tempo.xyz/developers/docs/protocol/transactions/AccountKeychain) and the rules enforced. For instance, admin keys have broader permissions, while limited keys operate within configured token budgets and call scopes. Call scopes constrain top-level calls and complement spending limits. As a final safeguard, an authorized root or admin key can revoke access to manually stop a misbehaving agent. ## How abstraction changes who pays for gas Along with session keys, gas abstraction removes a huge hurdle for agentic payment flows by softening the rules on what counts as a valid gas payment. Senders no longer need to hold a blockchain’s native token to pay gas fees. Here’s how that works. ### A paymaster can cover the gas for the user One way some developers are getting rid of the friction [gas fees](https://tempo.xyz/blog/stablecoin-fees) often bring to blockchain payments is through a paymaster, which is a service that sponsors transaction fees on the user’s behalf. In this fee model, the application covers gas fees for interactions on its platform, so agents never need to buy and manage protocol-specific gas tokens. On the user’s end, the payment simply clears for a fast and simple transaction experience. Individuals and agents can interact with different applications without thinking about these costs. ### Users can pay gas in the token they already hold Even if applications don’t want to cover their users’ gas fees, [account abstraction](https://tempo.xyz/blog/account-abstraction/) still makes the checkout experience simpler by broadening out what counts as a gas token. Users and agents don’t need to constantly hold a reserve of volatile digital assets tied to a blockchain just to make a purchase. Where supported by the wallet, paymaster, or chain, they can cover gas fees with the same [stablecoins they used to pay](https://tempo.xyz/learn/stablecoin-settlement/) for a product or service. This feature is especially beneficial in agentic payment flows since agents don’t have to constantly monitor and adjust wallet balances, and developers don’t have to write in a long list of extra parameters to top off their wallets with native digital assets. Using stablecoins for gas fees also adds greater cost predictability by taking volatile price movements out of the equation. ## How do session keys and gas abstraction work together? On the surface, session keys and gas abstraction solve different problems that may seem unrelated. It’s true that each of these features plays a different role in the payment experience, but they’re complementary within an agentic payment flow. The shared theme is reducing repeated user intervention. Session keys let applications sign authorized transactions without repeated owner approval, while gas abstraction removes the need for users to manage a separate gas token. Lifting these two restrictions makes building payment experiences feel more like working on familiar Web applications versus considering all the intricacies of traditional crypto wallets. A few of the onchain payment possibilities that account abstraction opens up include: - **Recurring charges.** Session keys can authorize recurring payments within a configured budget and expiry, reducing repeated approval prompts. Gas abstraction lets an application sponsor fees or support a fee token the user already holds. - **Batch payouts.** For businesses that want to use stablecoins for [global transactions](https://tempo.xyz/learn/managing-payout-complexity-global-payroll/), manually approving individual payments won't work at scale. [Batch payouts](https://tempo.xyz/learn/batch-payments/) make this process manageable by grouping multiple payouts into a single transaction. Session keys step in to speed up this process with authorized applications that can sign transactions within their permissions. That way, businesses can automate recurring payment workflows. Gas abstraction simplifies these flows even further by eliminating the need to manage a separate fee balance of the network’s native token. - **Agent-initiated payments.** Account abstraction simplifies authorization and fee handling for agent-initiated payments. Session keys authorize agents to make payments while still respecting preapproved boundaries set by the user. At the same time, gas abstraction means agents don’t have to constantly scramble to acquire a second asset just to keep operating. ## Does Tempo support gas fee sponsorship and session keys? Session keys and gas abstraction have a lot to offer, but they’re only as useful as the infrastructure behind them. Stitching together multiple services isn’t the most efficient way to get the most benefit out of account abstraction when setting up autonomous payments. Tempo helps overcome this issue by providing native access keys through its Account Keychain. That way, developers can grant their applications and agents permissions natively. Our Layer 1 blockchain solution comes with built-in [gas sponsorship](https://tempo.xyz/developers/docs/guide/payments/sponsor-user-fees) via Fee Payer and transaction submission, so there’s no need to deploy a separate bundler or paymaster infrastructure. [Tempo’s Fee Payer API](https://tempo.xyz/developers/docs/api/fee-payer) covers gas and submits the transaction as part of one payment flow. From the user’s perspective, there’s nothing extra to buy, bridge, or manage, making it an ideal solution for onboarding. Plus, since Tempo uses stablecoins to pay transaction fees, developers don’t need to factor in volatile gas tokens to their budgets. Gas fees on Tempo are typically sub-cent for payments and paid in USD-denominated stablecoins. Looking for an easy way to explore account abstraction? Tempo can help. [Reach out today](https://tempo.xyz/contact/) to see how features like our native session keys and Tempo Fee Payer can transform your payment workflows. ## FAQ ### Do session keys require giving up custody or a seed phrase? No, you don’t have to share your seed phrase or private key to use a session key. You still retain control over your smart account while the smart key operates within its specific permissions. ### Can a session key be revoked before it expires? You have the right to revoke your session key at any time to terminate its permissions ahead of its expiration or budget limit. ### Does the underlying chain matter, or can I add this to any chain? Blockchains that support account abstraction and smart accounts should be able to handle smart keys. However, the average gas fees to use this feature will vary from chain to chain. --- ## How settlement works with a stablecoin debit card > Source: https://tempo.xyz/learn/stablecoin-debit-card/ > Language: en Stablecoin debit cards are a hybrid approach between blockchain payments and traditional banking. With them, users can buy goods and services like they would with a regular debit or credit card. Behind every stablecoin debit card is a settlement rail that moves each payment from initial card authorization to final settlement. They still rely on the existing card networks, sponsor banks, and fiat payment rails. This guide explores the settlement flow of a typical stablecoin debit card end to end. ## What’s a stablecoin debit card? A stablecoin debit card is a payment card connected to a stablecoin balance or wallet instead of a traditional bank account. For consumers and merchants, it functions just like a regular card, working through established networks like Visa or Mastercard. The existing card and acquiring infrastructure remains the same, with stablecoin activity confined to the funding or settlement layer. Despite the name, stablecoin debit cards don’t necessarily run on a debit-issuing model. They can also be prefunded or credit-based. ## How stablecoin cards move from authorization to final settlement The front end phase of a typical stablecoin-funded card transaction is familiar to any fintech because it stays on conventional rails. Once a cardholder [initiates a payment](https://tempo.xyz/learn/stablecoin-payments/) to a merchant, the merchant’s acquiring bank sends an authorization request through the card network to the cardholder’s issuer processor. The issuer processor checks the program ledger to verify that the cardholder has sufficient funds. Then, they reserve the requested amount and relay an approval message back through the card network to the merchant. At the clearing stage, the network compiles approved transactions into a clearing file and determines financial obligations between the issuer and the acquirer. The issuer processor matches cleared transactions against the original authorizations and reconciles discrepancies. Liquidity management and conversion are where the flow diverges from traditional rails. Here, the treasury, custody, or liquidity provider (depending on the program) converts stablecoins from the balance or wallet the stablecoin debit card connects to into fiat currency. Settlement itself is handled by the sponsor bank, card network, stablecoin settlement rail, or a combination, depending on the model. Finally, the acquirer or acquiring bank deposits the settled fiat funds into the merchant’s account. The authorized amount and the final cleared amount aren’t always equal, which means the settlement rail has to keep transaction records linked to facilitate accurate reconciliation. Timing can also differ depending on which model is used, especially when it comes to stablecoin reservation, conversion, and transfer. ## The infrastructure powering the card settlement flow Stablecoin payment infrastructure is a hybrid model combining traditional card infrastructure with a stablecoin-specific funding and settlement layer. Not every provider handles every function, which means a transaction passes through many hands before reaching settlement: - **Issuer processors** manage the technology that underpins authorization, clearing, and settlement. - **BIN sponsors** are institutions like [sponsor banks](https://tempo.xyz/blog/stablecoin-opportunity-for-sponsor-banks/) that provide fintechs access to their card-network license and regulatory coverage. This allows fintechs to issue cards without the heavy lift of joining Visa or Mastercard directly. - **Program managers** facilitate the relationship between sponsor banks, issuer processors, and the fintechs that use them. They also manage the core operational mechanics of the underlying card program. - **Card networks** like Visa or Mastercard create pathways between issuers and acquirers. - **Custody or wallet infrastructure** holds the actual stablecoins the card is backed by. - **Internal ledgers** track balances and holds. - **Liquidity and conversion infrastructure** handles the conversion of stablecoins into fiat currencies and vice versa. - **Banking and fiat rails** like ACH systems and bank wires move fiat funds post-conversion. - **Onchain settlement rails** are the blockchain infrastructure that moves stablecoins from one party to another, such as from the issuer to the sponsor bank in the settlement stage. ## Compliance and control checks settlement rails must support Compliance considerations touch many components of a stablecoin debit card stack. While the exact financial controls involved at any stage of the transaction lifecycle depend on the specific program, jurisdiction, stablecoin, and regulated partners involved, there are a few common elements typical to these flows, including: - **Customer and business onboarding.** Know Your Customer and Know Your Business regulations apply for stablecoin debit cards just like they do for most payment cards. - **Card authorization.** The issuer processor checks the cardholder’s balance during authorization, then confirms their identity and runs risk and fraud checks. - **Stablecoin settlement.** Financial controls at this layer focus on mitigating stablecoin-specific risks like the underlying stablecoin losing its peg or running into reserve trouble. - **Treasury and administrative access.** Whoever manages the program’s stablecoin reserves should have role-based access control and multi-party approval. No single person has unfettered jurisdiction over moving funds. - **Operational intervention.** Card programs need levers for acting on specific risks, such as blacklisting high-risk wallet addresses or accounts. Like other payment cards, stablecoin debit cards must follow applicable regulatory requirements and the Payment Card Industry Data Security Standard (PCI DSS). Cardholder data is basic information like the cardholder’s name and primary account number (PAN). A card’s stripe or chip includes sensitive authentication data (SAD), which shows up in the cardholder entry and authorization stage. SAD must not be stored after authorization, even if encrypted, except by issuers and companies supporting issuing services with a documented, legitimate issuing business need. Any permitted storage must be secured and encrypted in line with PCI DSS. Settlement and reconciliation systems should only reference cardholder data, never sensitive authentication data. For better auditability and simpler reconciliation, every stage of a transaction needs durable identifiers and mappings to connect: - Authorization. - Clearing record. - Funding event. - Settlement obligation. - Stablecoin transfer stages. - Any later adjustments. ## Other card flows the settlement rail must handle Stablecoin payment rails have to account for edge cases and settlement adjustments beyond the forward purchase flow. Authorization reversals are one of the simpler cases. If a payment needs to be canceled and the charge hasn’t yet settled, the merchant can simply reverse the authorization. Refunds for settled charges are a little different because conversion from stablecoins to fiat has already taken place. Onchain settlement does not prevent refunds: the original transfer remains final, while a separate transfer or ledger credit returns funds. Card-network refunds still follow the program’s existing process. Nothing changes for the merchant, either: They send the refund through the card network in fiat currency, just as they would for any other type of refund. The program then credits the cardholder’s balance or wallet according to its refund and conversion model. Chargebacks and disputes can take weeks to months to settle, but how the process works depends largely on program-specific policies. Stablecoin card issuers don’t necessarily manage the entire dispute workflow. Handling these exceptions smoothly takes enough transaction data to link the original authorization, clearing record, settlement transfer, and any later adjustments into one connected record. ## Post-settlement liquidity, reconciliation, and replenishment A card program’s obligations don’t stop at settlement; they also include ongoing liquidity, reconciliation, and replenishment considerations. Treasury teams are responsible for ensuring both stablecoin and fiat balances are sufficient for upcoming settlement needs. That means continually replenishing those balances as transactions settle so funds are available for the next cycle. It’s also critical to match card-network, processor, ledger, banking, and onchain records to create an audit trail and gather the transaction data needed for reconciliation. ## Tempo’s place in the stablecoin card settlement flow Tempo is a payment rail built specifically to support a stablecoin settlement layer right alongside the issuer processors, card networks, and existing banking infrastructure you’re used to working with. If you’re building a stablecoin debit card stack and need a seamless way to enable stablecoin transfers in settlement or treasury movement, Tempo was designed with you in mind. With Tempo, you can use transfer memos to generate references that keep onchain transfers connected for easy reconciliation downstream, with no need to waste time manually hunting down records. Layer in Tempo Policies and TIP-20 functions to create custom token-level allowlists, blocklists, transfer restrictions, and role-based permissions to control exactly who can move funds and how. If that’s not enough, Tempo’s dedicated payment lanes enable reliable payment execution at scale so you can easily handle the volume a stablecoin debit card requires. Leave card authorization, clearing, acquiring, and merchant payout with the existing program partners you trust, and leave the stablecoin layer to Tempo. HR platform [Deel’s stablecoin wallet](https://tempo.xyz/customer-stories/deel/) for contractors shows how a stablecoin wallet can support holding, earning, and spending within an existing platform. Deel supports businesses in more than 150 countries, and they wanted to give contractors a way to hold dollar balances within the platform, earn rewards on them, and [spend across borders](https://tempo.xyz/solutions/institutional-money-movement/) without switching to a new app. What they didn’t want was to build an entire stablecoin settlement layer from scratch, so they chose Tempo for its native account abstraction, predictable fees, and fee sponsorship. See how [Tempo](https://tempo.xyz/) slots into your current card stack without sacrificing the existing infrastructure you already know and love. ## FAQ ### Does a merchant need to accept stablecoins for a stablecoin card to work? No, merchants don’t have to take any special steps to accept stablecoin debit cards. From the consumer and merchant perspective, they work just like any other type of debit card. ### Does every stablecoin card purchase require an onchain transaction? No, some stablecoin debit card programs use an internal ledger at the moment of purchase and only convert or settle stablecoins in periodic batches. ### What determines which blockchain can support stablecoin card settlement? The chain must support the program’s stablecoin, wallet, security, liquidity, and timing requirements. Programs can batch settlement or pull funds from a wallet at authorization, with onchain completion handled according to the integration. There is no universal block-time threshold for all stablecoin cards. --- ## Stablecoin liquidity for exchanges: What it takes > Source: https://tempo.xyz/learn/stablecoin-liquidity-for-exchanges/ > Language: en Managing stablecoin liquidity for exchanges is about enabling customers to reliably move in and out of a stablecoin at the expected price without unpredictable delays. This relies on two core pillars: market liquidity through active trading and redemption liquidity through minting and redeeming stablecoins with the issuer. While stablecoins settle onchain 24/7, minting, redemption, and fiat deposits and withdrawals still lean on traditional banking systems like ACH and wire transfers. Exchange settlement must work alongside these traditional rails rather than replacing them. Maintaining operational continuity requires balancing liquidity, configuring treasury controls, and managing multichain supply. This guide explores the infrastructure exchanges need to settle stablecoin activity predictably under enterprise-grade operational conditions. ## What exchanges need from stablecoin settlement infrastructure At a practical level, exchanges that support stablecoins [need infrastructure](https://tempo.xyz/learn/stablecoin-payment-infrastructure-enterprise-scale/) that connects market liquidity to the underlying operations that make it usable. That includes: - Customer funding - Asset movement - Treasury oversight - Compliance - Settlement A deep order book and active trading pairs can help customers buy and sell supported assets with less slippage. By itself, however, the order book isn’t enough to support the deposits and withdrawals, redemptions, and cross-chain transfers that underpin a reliable exchange. These flows require a broader stack that coordinates stablecoin issuers, banks and custodians, and compliance providers alongside resilient [settlement rails](https://tempo.xyz/learn/stablecoin-settlement/). Here’s a breakdown of the fundamental building blocks exchanges need to settle stablecoin activity with confidence and consistency. ### Deposits and withdrawals to connect funding and settlement Settlement infrastructure should support deposit and withdrawal operations so customers can move stablecoins into and out of the exchange smoothly. This includes: - Stablecoin and network support: Exchanges must recognize the correct token contract on each supported network. Customer attribution can use dedicated addresses, virtual addresses, or shared addresses with payment references; a separate address per token is not always required. - Confirmation thresholds: When a customer sends funds to a deposit address, they must wait for onchain confirmation based on the exchange’s network finality threshold. - Screening and ledger updates: Post-confirmation, the exchange verifies the correct asset has been deposited, runs compliance and risk screening, and updates its internal ledger to credit the user balance. Withdrawals follow reverse screening and approval procedures. - Redemption levers: Eligible exchanges may mint or redeem through an issuer or authorized intermediary, subject to onboarding, limits, and banking arrangements. Exchanges without direct access can source liquidity through market makers or secondary markets. ### Wallet and treasury controls to keep liquidity available Stablecoin exchanges need to handle wallet and treasury management tasks to keep funds secure and accessible without introducing capital inefficiency. Exchanges typically keep most funds in cold storage, where assets are less exposed to online threats. Hot wallets are reserved for just the funds necessary to cover day-to-day withdrawals. To keep everything in balance, exchanges track liquidity across wallets, custodians, and networks, rebalancing when a hot wallet runs low or holds more than it needs to. On the security side, exchanges set permissions, enforce transaction limits, and use multiparty computation (MPC) or multisignature approvals to ensure no one person can move funds on their own. Once funds have moved, keeping comprehensive transaction records creates a verifiable audit trail for regulators and auditors. ### Compliance and reconciliation to keep settlement flows sound Meeting jurisdictional obligations requires embedding robust [compliance controls](https://tempo.xyz/blog/compliance-controls/) directly into the settlement path, including: - Screening and monitoring: Systems must support data feeds for KYC, sanctions screening, and continuous transaction monitoring on every deposit and withdrawal to flag anomalies. - Ledger synchronization: Since asset states are reflected across user accounts, internal ledgers, and treasury records, operations teams must keep three independent data sets in strict sync so holdings and customer balances stay aligned. - Metadata and reconciliation: Short, opaque withdrawal references can support [payment reconciliation](https://tempo.xyz/learn/payment-reconciliation/) by linking confirmed transfers to internal records. Applications must still verify the asset, recipient, amount, and transaction status before updating their ledgers. ## Liquidity management across fiat and stablecoins Stablecoin liquidity depends on [where funds actually live](https://tempo.xyz/blog/creating-more-liquidity-mobility-in-markets), not just on an exchange’s total balance. If its stablecoin supply is trapped in the wrong wallet or network, an exchange can’t honor withdrawal demands regardless of its total holdings. To prevent liquidity crunches, exchanges constantly monitor cross-network balances. When a network runs short, operations teams can transfer funds from a surplus wallet on the same network or use burn-and-mint transfers where issuers support them. Alternatively, working with market makers allows exchanges to swap supply from one network to another. When an exchange lacks a particular stablecoin, it may acquire it through a liquidity pool if sufficient depth is available. A pool redistributes existing inventory; it does not solve a system-wide shortage. They might also mint new stablecoins directly through the issuer. If it has a surplus of a different stablecoin, it may choose to redeem some of those holdings for fiat and use the proceeds to mint more of the stablecoin it’s lacking. Regardless of the method an exchange uses, evaluating timing, fees, slippage, and counterparty or bridge risk helps teams make the optimal choice. True cost efficiency goes beyond baseline transaction fees. Operations teams must factor in the hidden expenses of capital locked in multitoken prefunding, the engineering overhead of manual reconciliation, and the friction of failed transactions during network surges. Minimizing these variables requires infrastructure built specifically to keep transaction and treasury mechanics predictable as volume scales. ## Operational risks that can constrain exchange liquidity Exchanges can hold sufficient assets in theory while lacking usable liquidity in practice if funds aren’t in the right wallet, network, or currency. Shortages can also happen if funds fail to clear within the required settlement window. The main risks that lead to these shortfalls are: - Issuer, reserve, and redemption delays: Unplanned slowdowns or halts in issuer redemptions prevent desks from converting surplus stablecoins back to fiat when they need to. Teams can evaluate additional issuers and secondary-market access, while recognizing that other stablecoins have different issuer, liquidity, and redemption risks. - Banking-hour and fiat gateway mismatches: A withdrawal spike occurring over a weekend or on a bank holiday can drain an exchange’s stablecoin reserves before minting channels reopen on the next business day. Teams can size liquidity buffers around withdrawal demand, issuer availability, banking cutoffs, and the cost of prefunding. - Network congestion, outages, and bridge failures: Chain congestion and outages can delay settlement, while bridge failures can lock or lose funds in transit. Teams should define procedures for pausing affected routes and using supported alternatives, where available; alternative routes introduce their own costs and risks. - Wallet, key-management, and address errors: A compromised signing workflow or an incorrect routing address can make funds inaccessible, often permanently. Controls may include appropriate signing policies, address validation, destination checks, and spending limits implemented across custody, wallet, and application systems. MPC alone does not guarantee multi-person approval. - Flagged balances and state isolation: Automated security triggers can block individual payouts, while sudden configuration updates can halt activity for a specific asset. Ledger systems should distinguish restricted balances from usable funds while preserving an accurate record of total holdings and customer obligations. ## Where stablecoins and onchain rails might not be the right choice While stablecoins solve many [cross-border payout](https://tempo.xyz/learn/cross-border-payments/) and 24/7 liquidity challenges, they aren’t a universal fix for exchange operations. In regions with highly efficient local banking rails like domestic account-to-account systems, introducing stablecoin conversion steps can add unnecessary foreign exchange or conversion friction. When local operating licenses prohibit digital asset holdings or require native fiat custody within domestic Tier-1 banks, maintaining onchain inventory introduces unwanted legal exposure. Additionally, when an exchange deals heavily in localized fiat pairs where user demand for stablecoins is negligible, the overhead of managing stablecoin rails may outweigh the settlement benefits. ## Tempo: The onchain layer for exchange funding and settlement Tempo is a payments-focused Layer 1 that supports stablecoin transfers, payment references, and stablecoin-denominated transaction fees. Exchanges still need their own custody, treasury, compliance, and ledger systems. ### Supports ledger reconciliation [Tempo transfer memos](https://tempo.xyz/developers/docs/guide/payments/transfer-memos) let exchange teams attach a short, opaque payment reference to a stablecoin transfer. Memos are fixed 32-byte fields and public transaction data, so customer details should remain offchain. Applications store the reference with their internal record, verify the token, recipient, amount, and receipt, then match confirmed transfer events to the ledger. Recording the transaction hash and log index helps prevent duplicate credits. Memos support this workflow; they do not replace the exchange’s database or automatically reconcile payments. ### Mitigates fee management overhead and cost volatility Operating across multiple networks forces treasury teams to forecast, acquire, and prefund separate, volatile native tokens to move USD stablecoins. Tempo enables [stablecoin-native fees](https://tempo.xyz/blog/stablecoin-fees/), allowing fees to be paid in an eligible USD-denominated TIP-20 stablecoin, subject to fee-token support and available fee liquidity. Typical payment fees are sub-cent, while actual fees depend on the transaction and applicable fee schedule. Exchange teams should account for these fees separately from trading, custody, conversion, and banking costs. ### Protects throughput during volatility Public network congestion can stall critical exchange rebalancing and payout flows alongside retail traffic. Tempo features [dedicated payment lanes](https://tempo.xyz/developers/docs/protocol/blockspace/payment-lane-specification) that reserve blockspace for eligible TIP-20 payment traffic, reducing contention with other activity. This does not guarantee every exchange operation will complete during an outage or eliminate application, custody, or issuer bottlenecks. [See how Tempo](https://tempo.xyz/) gives you the onchain settlement layer you need for reliable stablecoin deposits, withdrawals, and treasury operations without giving up the banking relationships you already trust. ## FAQ ### Can an exchange support a stablecoin without direct issuer redemption access? Yes, exchanges aren’t required to mint or redeem stablecoins directly with the issuer to support a particular stablecoin. They can buy from secondary markets and market makers to manage liquidity instead. However, this can come with thinner liquidity, less favorable pricing, and increased counterparty risk. ### How much stablecoin liquidity should an exchange hold? The amount of stablecoin liquidity an exchange should hold depends on several different factors, including: - Historical withdrawal demand for the stablecoin - Immediate settlement and payout obligations - Redemption processing timelines, especially over weekends and bank holidays - Market stress, such as withdrawal spikes in times of volatility - Backup liquidity access, such as active market maker lines and direct issuer minting capacity ### What should exchanges test before supporting a stablecoin on a new network? Before going live on a new network, exchanges should thoroughly test each component of the integration, including: - Custody and wallet infrastructure compatibility - Deposit recognition logic and user account mapping accuracy - Withdrawal routing to correct addresses and networks - Network finality behavior to establish safe confirmation thresholds - Available liquidity depth and secondary market access - Integrated compliance controls like screening and risk flags - Outage procedures like pausing transfers --- ## What stablecoin payment infrastructure needs to work at enterprise scale > Source: https://tempo.xyz/learn/stablecoin-payment-infrastructure-enterprise-scale/ > Language: en _Stablecoin payments are moving from pilots into enterprise payment operations. For teams evaluating stablecoin rails, the question is not only whether value can move onchain. It is whether the infrastructure can support predictable settlement, transparent costs, reconciliation, and compliance workflows at production volume._ The enterprise stablecoin conversation has changed. Payment teams no longer need to be convinced that tokenized dollars can move across a blockchain. They need to know whether the underlying rail can support the operations attached to real payment products: when funds settle, what each transfer costs, how exceptions are handled, and how records flow back into finance systems. McKinsey and Artemis estimate that actual stablecoin payments were running at about [$390 billion on an annualized basis](https://www.mckinsey.com/industries/financial-services/our-insights/stablecoins-in-payments-what-the-raw-transaction-numbers-miss), based on December 2025 activity. That is still a small share of global payments, but it reflects meaningful usage in B2B payments, remittances, payroll, settlement, and card-linked flows. Stablecoin rails do not replace banks across every workflow. Banks and regulated financial institutions remain central to fiat access, account relationships, custody, liquidity, and compliance operations. Stablecoin settlement adds another rail where 24/7 availability, fast finality, and programmable payment data can improve specific flows. This article focuses on the settlement layer underneath stablecoin payment products. The goal is to look beyond whether a vendor can process a transfer and evaluate whether the infrastructure can keep payment operations predictable as volume grows. ## What is stablecoin payment infrastructure? Stablecoin payment infrastructure is the set of systems that lets a business send, receive, hold, reconcile, and convert stablecoin payments. The stack usually includes: - **Settlement layer.** Records transfers, finalizes transactions, and determines settlement speed, reliability, and fee mechanics. - **Custody and wallet access.** Controls how institutions hold assets and authorize movement. - **Issuance and liquidity.** Determines which stablecoins can be used, how they are backed or redeemed, and how liquidity moves between assets. - **Compliance and risk tooling.** Supports onboarding, screening, monitoring, policy controls, case management, and reporting. - **Fiat ramps.** Connect stablecoin flows to bank accounts and local payment systems. - **APIs and reporting.** Connect stablecoin movement to payment, treasury, accounting, and ledger systems. For enterprise teams, the settlement layer is foundational. It defines when settlement is final, how costs are calculated, what transaction data can travel with a payment, and whether payment volume competes with unrelated network activity. Application vendors can improve the user experience around a rail, but they cannot fully compensate for settlement behavior that is volatile underneath. ## What blockchain rails decide Blockchain rails are the networks that settle stablecoin transfers. They confirm that tokens moved from one party to another and define when that movement can be treated as final. General-purpose blockchains support many activities at once: trading, consumer applications, smart contracts, payments, and other workloads. That flexibility can be useful, but it also means unrelated activity may compete for the same capacity. When network demand rises, transaction fees and confirmation timing can become harder to forecast. For enterprise payments, that matters. A business may still be able to send funds, but it can struggle to commit to delivery windows, forecast unit economics, or reconcile payments if the underlying rail behaves differently from one period to the next. [Tempo](/) is a payments-first Layer 1 blockchain designed for stablecoin payments at scale. Its public materials describe dedicated payment lanes, stablecoin-denominated fees, deterministic settlement, payment metadata, and modern transaction features built around payment workflows. The key distinction is not whether a chain can transfer a stablecoin. Many can. The question is whether the rail has the primitives enterprise payment teams need when transfer volume, operational scrutiny, and customer expectations increase. ## Why enterprise scale changes the evaluation At small volumes, payment issues can be handled manually. An analyst can chase a missing reference. A support team can explain a delayed payout. A finance team can reconcile a handful of exceptions. At enterprise volume, the same issues become product and operating constraints. Fees need to be forecastable because transaction costs become part of margin, pricing, and customer economics. A fee spike that looks minor in a test can matter across millions of transfers. Timing becomes a customer commitment. Marketplaces, payroll platforms, neobanks, remittance companies, and merchant processors commit to delivery windows. Settlement infrastructure has to support the service level behind those commitments. Reconciliation needs structured data. Finance teams need to match transfers to invoices, payouts, orders, cost centers, or ledger entries without manual cleanup. Controls need to fit the workflow. Different assets, corridors, counterparties, products, and jurisdictions introduce different risk and compliance requirements. Integration surface matters. Payment teams need wallets, custody providers, ramps, compliance systems, orchestration tools, reporting, and internal ledgers to work together without creating new manual processes. ## The requirements for enterprise-grade stablecoin infrastructure Enterprise teams can evaluate stablecoin payment infrastructure through four practical requirements: settlement reliability, cost predictability, transaction-level controls, and reconciliation. ### Settlement finality and reliability Finality is the point when a payment can be treated as finalized by the network. In a blockchain context, finalized transactions should not be reorganized out of the chain. For payments, finality needs to arrive quickly and consistently. Speed matters, but dependable timing is what lets teams design payout windows, merchant settlement expectations, and payment status updates. A marketplace, bank, or payout platform cannot build a reliable product promise around a rail whose confirmation timing changes materially whenever network activity rises. Enterprise teams should ask how finality works, how the network behaves under congestion, and what assumptions are needed before treating funds as settled. Tempo is designed for deterministic settlement, with sub-second finality and blocks finalized in roughly 0.5 seconds. For payment teams, that creates a clearer foundation for payment status, customer communications, and downstream settlement workflows. ### Cost predictability at any volume At enterprise scale, predictable fees often matter more than the lowest advertised fee. A payout that costs very little one day and materially more the next is difficult to price into a durable payment product. On many blockchains, transaction costs depend on network demand and the price of the asset used to pay gas. This introduces two forms of uncertainty: variable network fees and exposure to a separate, volatile fee token. Payment-optimized rails reduce that operational burden. On Tempo, transaction fees can be paid in [supported USD-denominated TIP-20 stablecoins](https://docs.tempo.xyz/protocol/fees), as long as the token meets fee-token requirements and has sufficient Fee AMM liquidity. This allows businesses to view fees in familiar dollar terms instead of managing a separate gas asset. Tempo's [Fee AMM](https://docs.tempo.xyz/protocol/fees/fee-amm) converts between supported fee tokens when the payer and validator prefer different stablecoins. For payment teams, the practical benefit is simpler accounting: the fee can stay inside the stablecoin payment flow instead of requiring a parallel process to acquire, fund, and reconcile another token. ### Compliance and risk controls in the payment flow Stablecoin infrastructure should support appropriate controls before, during, and after funds move. The right control set depends on the business model, asset, counterparty, market, and jurisdiction, so legal and compliance review should happen before any production launch. Common workflows include onboarding checks, sanctions screening, transaction monitoring, case management, Travel Rule workflows where applicable, issuer transfer policies, and reporting. Not every control belongs at the blockchain layer. Some are handled by issuers, banks, custodians, wallets, compliance providers, or internal risk teams. The settlement layer still matters because it can make controls easier or harder to implement consistently. Tempo supports the token-level part of this model through [TIP-20](https://docs.tempo.xyz/protocol/tip20/overview) and the [TIP-403 Policy Registry](https://docs.tempo.xyz/protocol/tip403/spec). TIP-20 includes role-based controls, pause and unpause functions, and transfer policy support. TIP-403 lets issuers define whitelist or blacklist policies that tokens check when transfers occur. ### Reporting and reconciliation for finance systems Fast settlement is not enough if every payment creates cleanup work afterward. Finance teams need payment data they can match to internal systems. Reconciliation means turning each onchain transfer into a record that maps to an invoice, payout, order, customer, cost center, or ledger entry. Without reliable references, teams are left matching payments manually. That may work in a pilot. It does not work for high-volume payouts, marketplace settlement, card programs, or global treasury movement. Tempo supports reconciliation through [TIP-20 transfer memos](https://docs.tempo.xyz/guide/payments/transfer-memos). A TIP-20 transfer can include a 32-byte memo for payment references, invoice IDs, customer IDs, or transaction notes. For larger or sensitive payloads, applications can keep data offchain and use a commitment, hash, or short locator onchain. This gives payment systems a way to connect stablecoin settlement to treasury, ERP, accounting, and internal ledger workflows without exposing more data than necessary. ## How Tempo approaches enterprise-scale settlement At enterprise volume, stablecoin settlement has massive utility. Tempo focuses on the settlement-layer primitives that make stablecoin payments more usable for production workflows. - **Dedicated payment lanes.** Payment transactions using Tempo's [TIP-20 token standard](/blog/tip20/) can access reserved blockspace, so payment throughput is not consumed by unrelated application activity. - **Deterministic settlement.** Tempo's public materials describe sub-second finality and no re-orgs for finalized blocks, giving payment platforms a clearer basis for payment status and settlement expectations. - **Stablecoin-denominated fees.** Tempo has no native gas token. Fees can be paid in supported USD-denominated TIP-20 stablecoins when fee-token and liquidity requirements are met. - **Tempo Transactions.** [Tempo Transactions](/blog/tempo-transactions/) support configurable fee tokens, batch calls, concurrent transactions, fee sponsorship, scheduled transactions, and passkey authentication. These features help payment applications coordinate high-volume flows without building custom workarounds for each capability. - **Transfer memos.** TIP-20 transfers can include [memo fields](https://docs.tempo.xyz/guide/payments/transfer-memos) for invoice IDs, customer IDs, cost centers, or other payment references that downstream systems can use for reconciliation. - **Policy Registry.** The [TIP-403 Policy Registry](https://docs.tempo.xyz/protocol/tip403/spec) lets issuers define whitelist or blacklist transfer policies at the token level. This supports consistent issuer policy enforcement across tokens and applications that use the registry. - **Tempo Zones.** [Tempo Zones](/blog/introducing-tempo-zones/) are private execution environments connected to Tempo. They are designed for use cases where payment details should not be publicly visible, while still enabling enterprise-defined compliance and operator controls to be preserved. Teams should evaluate the operator trust model, token support, and visibility requirements before using a Zone in production. - **Ecosystem partners.** [Tempo's ecosystem](/ecosystem/) includes providers across asset issuance, onramps, offramps, risk and compliance, wallets and custody, privacy, and developer infrastructure. For enterprise teams, that surrounding ecosystem matters because production payment flows depend on more than the settlement layer alone. Stablecoin payment infrastructure works at enterprise scale when the rail supports the commitments payment teams make around it: settlement windows, unit economics, controls, and reconciliation. Tempo is designed around those requirements with a payments-first Layer 1, TIP-20 tokens, Tempo Transactions, and an ecosystem of infrastructure partners. ## Getting started Teams evaluating production stablecoin payment flows should map the full operating model before launch: - Which issuer and stablecoin will support the flow? - What custody model, wallet permissions, and signing controls are required? - Which corridors, currencies, onramps, and offramps need coverage? - What liquidity is required for settlement, redemption, fees, and FX? - What payment references need to flow into ERP, treasury, accounting, or ledger systems? - Which compliance obligations apply by product, counterparty, and jurisdiction? To explore an enterprise workflow, [contact Tempo](/contact/) or start with the [Tempo documentation](https://docs.tempo.xyz/). --- ## Stablecoin payments: how they work, benefits, and risks > Source: https://tempo.xyz/learn/stablecoin-payments/ > Language: en _Stablecoin payments move fiat-referenced digital assets over blockchain networks. For businesses, they can make cross-border, time-sensitive, and high-volume money movement more direct, but the onchain transfer is only one part of the end-to-end payment. [Talk to Tempo about stablecoin payment infrastructure](/contact)._ ## What are stablecoin payments? A stablecoin payment is a transfer of a fiat-referenced digital asset over a blockchain network to pay a person or business. The stablecoin is the asset being transferred. The blockchain records and settles the transfer, while wallets, custodians, payment providers, and banks may connect it to the rest of the payment flow. This distinction matters. A stablecoin is not automatically a payment, just as a bank deposit is not automatically a wire transfer. Stablecoins are also used for trading, collateral, and other financial activity. A [2026 analysis from the Federal Reserve Bank of Kansas City](https://www.kansascityfed.org/research/payments-system-research-briefings/what-are-stablecoins-used-for-today-estimating-the-distribution-of-stablecoins/) found that payments still represent a minority of stablecoin activity. For a primer on the assets themselves, read [What are stablecoins?](/learn/what-are-stablecoins). ## The three layers of stablecoin payment infrastructure Every production stablecoin payment depends on three layers. Businesses need to evaluate all three because a fast blockchain cannot compensate for weak liquidity, poor custody, or an unreliable bank payout. |Layer|What it does|What a business should evaluate| |-|-|-| |Stablecoin|Represents the value being transferred|Issuer, reserves, redemption terms, liquidity, currencies, and supported jurisdictions| |Blockchain network|Authorizes, records, and settles the onchain transfer|Settlement certainty, network fees, capacity, uptime, supported stablecoins, and payment features| |Service providers|Connect the payment to users, bank accounts, and internal systems|Wallets, custody, compliance, fiat conversion, foreign exchange, payouts, reporting, and support| The asset, network, and provider can introduce different risks and costs. Treating them as one product makes it harder to diagnose failures or compare vendors accurately. ## How stablecoin payments work The exact flow depends on whether the sender and recipient want to use stablecoins or fiat. Most business payments follow six steps: 1. **Create the payment.** The sender, an application, or a payment provider specifies the amount, recipient, supported stablecoin and network, and any payment reference. 2. **Fund the payment.** The sender uses an existing stablecoin balance or converts fiat through an on-ramp, exchange, or payment provider. 3. **Apply controls.** The business or its provider completes the required approvals, address checks, sanctions screening, and other compliance steps. 4. **Authorize the transfer.** A wallet, custodian, or application signs the transaction and submits it to the blockchain network. 5. **Settle onchain.** The network confirms the transfer. Onchain settlement does not require a separate clearing step after the transfer is final on that network. 6. **Deliver and reconcile.** The recipient keeps the stablecoin or converts it into fiat. The payment operator records the transaction identifier, fees, exchange rate, and reference data in its internal ledger, ERP, or accounting system. The onchain transfer may settle before the recipient receives money in a bank account. Fiat conversion and bank delivery still depend on liquidity, compliance reviews, local payment rails, and operating hours. Any speed or cost comparison should separate the onchain leg from the complete payment. ## Four common stablecoin payment models Businesses do not need the same asset at both ends of the flow. The best model depends on how the sender funds the payment and how the recipient wants to receive it. |Model|Sender uses|Recipient receives|Common use| |-|-|-|-| |Stablecoin to stablecoin|Stablecoin balance|Stablecoin balance|Treasury transfers, supplier payments, and payments between digital wallets| |Fiat to stablecoin|Bank balance or local payment method|Stablecoin balance|Global payouts and access to fiat-referenced digital money| |Stablecoin to fiat|Stablecoin balance|Bank deposit or local currency|Merchant acceptance, treasury conversion, and supplier payments| |Fiat to fiat using stablecoins|Bank balance or local currency|Bank deposit or local currency|Cross-border payments where a stablecoin handles the onchain settlement leg| The last model is often called the **stablecoin sandwich**. Neither party needs to manage a stablecoin directly, but the providers at both ends remain essential to the end-to-end experience. ## Benefits of stablecoin payments ### Continuous onchain settlement Blockchain networks operate outside bank cutoffs, weekends, and holidays. For global treasury and payment teams, that means the onchain leg can settle when the business needs it rather than waiting for the next banking window. ### Faster access to working capital Direct onchain settlement can reduce the time money spends moving through correspondent banks or sitting in prefunded accounts. This matters most when the existing route crosses several institutions or currencies. Domestic real-time payment systems may already perform well, so the benefit depends on the corridor. ### A different cost structure Stablecoin payments replace some per-payment intermediaries with a blockchain network fee and a smaller set of service providers. This can lower costs, especially for cross-border and high-volume flows. Businesses should compare the full cost, including conversion, foreign exchange, custody, compliance, and bank payout fees, rather than quoting the network fee by itself. ### Programmable payment flows Applications can initiate payments from software, sponsor network fees, batch payouts, or apply approval logic before funds move. For payment operators, that means more of the workflow can run through APIs instead of files and manual bank portals. ### Traceable settlement Onchain transfers create a shared record of the sending address, receiving address, asset, amount, and settlement status. This can improve auditability, but a transaction identifier alone does not explain the business purpose of a payment. Production systems still need customer, invoice, or account references that connect the transfer to internal records. ## Stablecoin payment use cases Stablecoin payments create the most value where existing rails impose high costs, limited operating hours, or several intermediaries. - **Cross-border B2B payments.** Businesses can pay suppliers or settle invoices across markets without relying on the same chain of correspondent banks. The fiat legs still require local partners. Read the [guide to cross-border payments with stablecoins](/learn/cross-border-payments). - **Treasury and liquidity movement.** Companies can move balances between entities, providers, or markets continuously, which can reduce prefunding and improve access to working capital. - **Global payouts and payroll.** Platforms can pay merchants, contractors, or employees in stablecoins or local currency. Explore [global payouts](/learn/global-payouts) and [stablecoin payroll](/learn/stablecoin-payroll). - **Remittances.** Providers can use stablecoins for the settlement leg while senders pay in fiat and recipients collect local currency. [Felix is adding Tempo to its settlement infrastructure](/blog/felix-brings-instant-remittance-settlement-on-tempo) for remittance corridors across Latin America. - **Merchant acceptance and embedded finance.** A business can accept a stablecoin from a customer, keep it onchain, or use a provider to settle the proceeds into fiat. [DoorDash is working with Tempo on stablecoin-powered payment infrastructure](/blog/doordash-partners-with-tempo-to-bring-stablecoin-payments-to-its-global-marketplace) for marketplace payment flows across merchants and Dashers. These examples are valuable because they start with an operating problem, not a requirement to use a stablecoin. ## Stablecoin payments compared with bank and card rails Stablecoin payments do not replace every payment method. Cards provide broad consumer acceptance, dispute processes, and credit. Domestic bank rails can offer low-cost or real-time transfers within a market. Stablecoins are strongest when a payment needs to cross borders, operate continuously, settle directly between digital wallets, or integrate into programmable financial products. The right comparison is between complete workflows. A stablecoin route should include the cost and time required to acquire the asset, settle onchain, convert currencies, complete compliance checks, and deliver usable funds. For a detailed comparison, see [ACH, wires, SWIFT, and stablecoins](/learn/payment-rails). ## Risks and limitations Stablecoin payments introduce a different set of dependencies than bank and card payments. A production evaluation should cover: - **Asset and issuer risk.** Review reserve quality, redemption rights, transparency, regulatory status, and the stablecoin's ability to maintain its reference value. - **Network risk.** Confirm that the network provides the settlement certainty, capacity, uptime, fees, and operational support the payment requires. - **Custody and security risk.** Define who controls keys, how approvals work, how wallet addresses are verified, and how the business responds to compromised credentials or an incorrect transfer. - **Liquidity and conversion risk.** Confirm that the stablecoin can be acquired and redeemed in the required size, currency, jurisdiction, and time window without unacceptable spread or delay. - **Compliance, tax, and accounting risk.** Requirements vary by activity and jurisdiction. Map customer due diligence, sanctions screening, transaction monitoring, recordkeeping, tax treatment, and financial reporting before launch. - **Reversals and support.** Onchain payments do not include a card-style chargeback process. Refunds usually require a new transfer, and recovery from an incorrect address or network may not be possible. - **Privacy and data risk.** Public blockchains make transfers visible. Businesses should avoid placing sensitive customer or invoice data directly onchain and use references when needed. Stablecoins complement bank accounts and local payment rails rather than eliminate them. Non-USD liquidity, bank connectivity, and off-ramp coverage remain uneven across markets. ## How to evaluate stablecoin payments for a business Start with the payment problem and work backward to the infrastructure: 1. **Choose one workflow.** Identify a payment where bank cutoffs, cross-border complexity, prefunding, cost, or reconciliation creates measurable friction. 2. **Define the endpoints.** Decide what the sender will use and what the recipient must receive. This determines whether the flow needs an on-ramp, off-ramp, or both. 3. **Select the stablecoin.** Evaluate the issuer, reserves, redemption, liquidity, currency, and availability in every relevant jurisdiction. 4. **Select the network.** Evaluate settlement certainty, fees, capacity, reliability, payment data, stablecoin support, and wallet or custodian compatibility. 5. **Select the service providers.** Map custody, compliance, conversion, foreign exchange, bank payouts, reporting, and support across the complete flow. 6. **Design reconciliation and controls.** Record the business reference, payment status, asset, network, exchange rate, fees, and accounting entries in the systems finance teams already use. 7. **Run a focused pilot.** Test small amounts across the full route, including failures and refunds. Measure delivery time, total cost, operational effort, and recipient experience before expanding. ## Why Tempo is built for stablecoin payments Tempo is a payments-first Layer 1 blockchain incubated by Stripe and Paradigm. It provides the network and settlement layer for stablecoin payments. Wallets, custodians, payment providers, exchanges, and banks connect that layer to users and fiat systems. - **Near-instant settlement with no re-orgs.** Tempo gives payment operators a clear completion point for the onchain leg. Learn how [settlement works on Tempo](/developers/performance). - **Sub-cent fees paid in stablecoins.** Businesses can pay network fees in supported USD-denominated stablecoins instead of managing a separate volatile gas token. Read the [Tempo fee documentation](/developers/docs/protocol/fees). - **Payment references.** [TIP-20 transfer memos](/developers/docs/protocol/tip20/overview#transfer-memos) let payment applications attach a reference to a transfer. This means finance systems can connect settlement to an invoice, account, or internal record. - **Issuer controls.** [TIP-20 and TIP-403 policies](/developers/docs/protocol/tip20/overview#tip-403-transfer-policies) support configurable transfer policies and separate administrative roles for regulated stablecoin issuers. - **Dedicated payment capacity.** Payment transactions use reserved blockspace, which helps payment operators maintain predictable fees and execution as network activity changes. Explore [Tempo's ecosystem partners](/ecosystem) for custody, wallets, compliance, and fiat connectivity. If you are evaluating a stablecoin payment flow, [contact the Tempo team](/contact) to scope a focused pilot. --- ## Frequently asked questions **What are stablecoin payments?** Stablecoin payments transfer fiat-referenced digital assets over a blockchain network to pay a person or business. The stablecoin is the asset, the blockchain records and settles the transfer, and service providers may handle wallets, custody, compliance, conversion, and bank payouts. **How fast are stablecoin payments?** The onchain leg can settle near-instantly or within minutes, depending on the network. End-to-end timing also depends on compliance checks, fiat conversion, liquidity, and the bank or local payment rail used at either end. **Do businesses need to hold stablecoins?** Not always. A business can hold and send stablecoins directly, or use a provider that converts fiat into stablecoins for the onchain transfer and converts the recipient's funds back into fiat. The right model depends on the payment workflow and where each party wants funds to land. **How much do stablecoin payments cost?** The total cost can include a blockchain network fee, provider fees, custody, fiat conversion, foreign exchange, and bank payout charges. Stablecoin payments can lower costs when they remove expensive intermediaries, but the network fee alone does not represent the end-to-end cost. **Are stablecoin payments safe?** Stablecoin payments introduce asset, issuer, custody, network, liquidity, compliance, and operational risks. Businesses should evaluate reserve and redemption terms, key management, supported networks, address controls, provider reliability, and the rules in every relevant jurisdiction. **How should a business start using stablecoin payments?** Start with one payment flow where bank cutoffs, cross-border complexity, or reconciliation create measurable friction. Define the desired delivery currency and timing, select the stablecoin, network, and providers, map compliance and accounting requirements, then test the complete flow with small amounts. --- ## A guide to stablecoin payroll for global teams > Source: https://tempo.xyz/learn/stablecoin-payroll-for-global-teams/ > Language: en _Companies now hire remote employees and international contractors across more markets than ever. That gives businesses access to broader talent, but it also puts more pressure on payroll infrastructure._ A payroll process that worked for a local team can start to crumble once payments cross borders. Finance teams need to manage currency differences and banking systems, while compliance teams make sure each payment fits the worker's classification and local requirements. In response, many teams are exploring stablecoin payroll. According to [recent reports](https://www.forbes.com/sites/roomykhan/2025/11/16/stablecoins-and-blockchain-becoming-the-backbone-of-finance/), stablecoins processed over $9 trillion in payments in 2025, showing that stablecoin rails are becoming a settlement layer for certain payroll and contractor payment workflows. In this article, we'll explain how stablecoin payroll works and what the benefits are. We'll also cover the infrastructure businesses should have before implementing stablecoin-based payroll workflows. ## Why payroll becomes more difficult as companies become global Global payroll is challenging because each market has its own banking infrastructure and currency. Not all banks have direct relationships with one another, so many businesses rely on correspondent banks to send global payments. Each transfer comes with a fee, which adds up quickly as enterprises enter more markets. This process also slows down payments. The more banks that get involved, the longer it can take for the money to reach its destination. Once funds arrive, workers need to be able to use them. Businesses have to convert paychecks from their country's currency to the workers' currencies. On average, [international wire fees run between $35 and $50 per transaction](https://www.westernunion.com/blog/en/us/how-much-are-money-transfer-fees/). For large enterprises paying hundreds or thousands of workers a month, those fees start to eat into the budget. Reconciliation adds another layer to this complex system. Varying settlement pathways, timing, and recordkeeping methods all make month-end harder. Without a unified platform, finance teams have to manually reconcile payments against the right worker and payroll period across locations. Overall, companies need systems that flex to each region. Otherwise, they'll have to use different workflows for every new location where they do business. ## What is stablecoin payroll? Stablecoin payroll involves sending payments to employees or independent contractors through a blockchain. The payroll provider still determines the worker, amount, pay period, and approval status. Stablecoin rails handle the settlement path. ### How stablecoin payroll works Businesses that use this system pay workers in stablecoins. They fund the payment run and send stablecoins to an approved destination, with payment details finance can use to track the payout. The recipient might receive funds directly in a wallet. In other workflows, a payout partner may convert the stablecoins into a local payment method. ### Why companies are exploring stablecoin payroll Traditional payroll systems can work well for local teams, but global businesses may have trouble supporting workers in markets where local payout coverage takes time to build. Stablecoin payroll can help companies reach those long-tail markets faster by giving workers a dollar-denominated payout option through wallet-based rails. It can also create value after the payout lands. When workers receive funds in a wallet, businesses can build balance-based features into the experience, including permitted earn options where available. For companies that manage large contractor or contributor networks, that makes stablecoin payroll part of market expansion and user engagement, not just payment delivery. ## The benefits of stablecoin payroll for global businesses Stablecoin payroll makes global workforce payments easier to manage after approval. Funds move within seconds, teams build payout rules directly into the workflow, and finance gets a verifiable record instead of another status update to chase. ### More stability for global contractors Global contractors often struggle with volatile local currencies. Because the value changes frequently, wages have less spending power from one day to the next. Deel found this out firsthand when nearly 85% of its contractors in Argentina asked to be paid in USD rather than pesos. In response, [Deel partnered with Tempo to build a USD-backed stablecoin payroll system](/blog/deel-launches-dlusd-stablecoin-wallet-for-global-contractors/). Contractors access secure wallets to withdraw funds, redeem them as USD, or transfer them to external wallets as needed. The company issued Deel Cards so contractors can make international stablecoin purchases in a single swipe. With stablecoins, contractors can build savings they can rely on. ### Faster cross-border settlement Stablecoin rails shorten the time between payment approval and settlement. That's especially important for international workforce payments, where payout timing often depends on local banking cutoff times and intermediary processing. Faster settlement also improves the worker experience because contractors can access funds sooner. ### Stronger product value around payouts Stablecoin payroll can also turn payouts into a product experience. A contractor platform can offer wallet access, balance management, or earn features where permitted. That gives workers more reason to keep using the platform after the payout lands. For businesses, this changes the role of payroll infrastructure. The payout no longer ends at payment delivery. It becomes part of the user relationship and can create new ways to support retention. ### Programmable payroll workflows Stablecoin payroll can turn payout rules into payment logic. A company can schedule contractor payments right after approval or release funds only after a milestone clears review. Payment workflows can also reflect approval limits or department budgets before funds leave the account. This gives finance more control without adding manual coordination before every run. ## Infrastructure requirements for stablecoin payroll Stablecoin payroll depends on more than the payment rail. Businesses also need onboarding, compliance, treasury, and reconciliation systems that can support the workflow at scale. Below are the features to look for when choosing a stablecoin payroll system. ### Worker onboarding and payment preferences Before launching a stablecoin payroll system, workers need to choose their preferred payment options and provide destination details. Some may want to receive stablecoins directly, while others prefer local currency through a payout partner. ### Compliance and reporting Stablecoin payroll changes the payment rail, not the nature of the payment. Businesses still need to treat employee salary and contractor payouts as compensation, with the right classification and reporting process in place. In the U.S., independent contractors can be paid in stablecoins. However, state or federal law may restrict employees from receiving certain compensation directly in stablecoins. In addition, if people receive any property, including cryptocurrency, for performing a service, the [IRS recognizes it as income](https://www.irs.gov/individuals/international-taxpayers/frequently-asked-questions-on-virtual-currency-transactions). In both cases, the value is generally measured in U.S. dollars at the time of receipt. International rules may vary. Tempo helps businesses operationalize those decisions once payroll, tax, and legal teams define the rules. Companies can support wallet-based payouts or work through payout partners where local currency delivery is required. That gives teams a controlled way to use stablecoin rails while keeping compensation decisions inside their existing payroll and reporting process. ### Liquidity and treasury management Like any system, stablecoin payroll needs access to available funds before sending payments. Finance teams need to decide when to fund stablecoin balances and how much liquidity to hold. It's a delicate balance: funding payroll too early puts strain on liquid cash flow, but waiting too long means payouts might fail. ### Reconciliation systems A stablecoin payroll system only works at scale when the payment record fits the systems finance already uses. Each transfer needs to connect back to the employee or contractor who received it. It should also show which payroll period and cost center the payout belongs to. Tempo keeps that context attached to the payment. Transfer references and structured metadata carry details like payroll IDs or invoice numbers with the stablecoin transaction. ISO 20022-compatible payment references make that data easier to map into internal finance systems. That turns settlement activity into reconciliation-ready records. Finance can see what moved, who received it, and which internal record approved it without rebuilding the payment trail after funds settle. ## What businesses should evaluate before implementing stablecoin payroll Before comparing providers and deciding whether stablecoins for cross-border payroll are right for them, businesses should evaluate the following: - **Payment volume and cadence.** Stablecoin payroll solutions make the most sense for companies that send recurring cross-border payouts, especially to large contractor groups or distributed teams. - **Recipient payment readiness.** The business needs to know whether workers can receive stablecoins directly or need local currency through an off-ramp. A fast settlement rail is only useful if the recipient can access and use the funds. - **Error controls and support ownership.** Companies need clear controls for wallet validation, approval limits, and failed payouts. Otherwise, they risk creating approval bottlenecks and sending incorrect payouts. - **Compliance.** Companies should confirm which local wage rules, tax reporting requirements, and recordkeeping standards apply. ## Global payroll needs reliable payment delivery Global hiring has exposed the difference between good payroll and reliable payment delivery. A company can calculate pay correctly and approve the run on time, then lose predictability once funds move across markets or payout partners. At the same time, finance has to prove where the money went and which internal records it belongs to. Stablecoin rails address that delivery problem directly. They settle approved payments faster, apply payout rules before funds move, and create onchain records that finance can verify during reconciliation. Tempo helps businesses build that infrastructure for global workforce payments. With stablecoin-native settlement, Dedicated Payment Lanes, and payment references built for reconciliation, Tempo gives finance teams a more controlled way to move payroll funds from approval to close. Learn more about [stablecoins for payroll](/blog/stablecoins-for-payroll/), [global payouts](/blog/global-payouts/), and Tempo's [cross-border payment infrastructure](/solutions/cross-border-payments/). --- ## Stablecoin payroll for funding and global payouts > Source: https://tempo.xyz/learn/stablecoin-payroll/ > Language: en _Stablecoin payroll can support different parts of a payroll flow. Providers can use stablecoins for account funding, cross-border payouts, or an employee wallet experience. This guide explains how those models differ, what to evaluate before integrating, and how Tempo supports the onchain payment leg._ [Discuss a stablecoin payroll pilot](/contact/?message=I%27m%20evaluating%20stablecoin%20payroll%20for%20my%20organization%20and%20would%20like%20to%20discuss%20a%20pilot.) ## What stablecoin payroll means Stablecoin payroll uses stablecoins in one or more stages of payroll funding and payout. It does not require every participant or every leg to move onchain. Providers can keep fiat collection, bank payouts, or off-ramp services where needed. Those legs retain their own costs, timelines, and availability. The right starting point depends on the problem a provider is trying to solve. Stablecoins can change how an employer funds payroll, how a worker receives a cross-border payout, or how a worker holds and uses a balance after being paid. ## How stablecoin payroll works ### Payroll account funding An employer can fund a payroll provider with stablecoins while the provider keeps its existing employee payout methods. Near-instant onchain settlement can shorten the gap between initiating and confirming the funding leg without requiring employees to change how they receive money. This model keeps the stablecoin integration behind the scenes. The payroll provider still needs to manage treasury, reconciliation, and any fiat payout legs separately. ### Cross-border payouts A provider can send dollar-denominated stablecoins to eligible custodial or self-custodial wallets. Recipients can hold the stablecoin or use available services to convert it, depending on their market and provider. The onchain transfer can settle near instantly. Fiat conversion, off-ramp processing, and bank delivery follow separate timelines and may introduce additional costs or requirements. ### Embedded employee wallets A payroll provider can include a wallet in its product so recipients can receive and hold stablecoins without leaving the payroll experience. Depending on the provider's operating model and integrations, the wallet may also connect to conversion, payment, or other financial services. An embedded wallet adds product and operating decisions. Providers need to define custody, security, compliance, liquidity, customer support, and account recovery before launch. ## What to evaluate before integrating - **Where stablecoins enter the flow.** Decide whether the first use case is employer funding, direct payouts, or an embedded wallet. Each choice changes a different part of the payroll experience. - **Recipient choice.** Some recipients may want stablecoins while others prefer existing payout methods. Supporting both can reduce adoption friction but adds operational complexity. - **Market coverage.** Wallet, custody, conversion, and off-ramp availability vary by jurisdiction. Evaluate the complete payment path, not only the onchain transfer. - **Custody and control.** Determine who controls wallets and keys, how accounts are recovered, and which parties can approve or restrict payments. - **Compliance and reporting.** Tax, labor, licensing, sanctions, anti-money laundering, and reporting requirements vary across markets and operating models. - **Reconciliation and support.** Plan how payroll records map to onchain payments, how exceptions are handled, and which team supports employers and recipients. ## Why Tempo for payroll Tempo is a payments-first Layer 1 designed for stablecoin payment flows. Several network capabilities are relevant to payroll providers: - **Near-instant onchain settlement with no re-orgs.** The onchain payment leg reaches a settled state without later chain reorganization. Bank, fiat, and off-ramp legs remain separate. - **Fees paid in stablecoins.** Tempo supports sub-cent network fees paid in stablecoins, and applications can sponsor those fees so recipients do not need a separate gas token. [Learn more about fees on Tempo](/blog/stablecoin-fees). - **Payment metadata.** [TIP-20 transfer memos](/blog/tip20) can attach reconciliation information to a payment, helping providers map onchain activity to payroll records. - **Dedicated payment lanes.** Payment lanes are designed to keep payment processing predictable when network demand changes. - **Optional controlled visibility.** [Tempo Zones](/blog/introducing-tempo-zones) are designed for payment flows that require approved participants to see different information. For payroll teams, this means the onchain payment leg can combine settlement, reconciliation, fee handling, and optional privacy controls in one network. Bank, fiat, and off-ramp legs remain separate. ## Next steps - Read the full [stablecoins for payroll](/blog/stablecoins-for-payroll) blog post - Explore [cross-border payments with stablecoins](/learn/cross-border-payments) - Compare [ACH, wires, and stablecoins](/learn/payment-rails) side by side - Learn about [global payouts with stablecoins](/learn/global-payouts) [Discuss a stablecoin payroll pilot](/contact/?message=I%27m%20evaluating%20stablecoin%20payroll%20for%20my%20organization%20and%20would%20like%20to%20discuss%20a%20pilot.) --- ## Frequently asked questions **Do employees need stablecoin wallets?** Not always. A provider can use stablecoins only for payroll account funding while keeping employee-facing payout methods unchanged. Direct stablecoin payouts require an eligible custodial or self-custodial wallet, while an embedded wallet can be part of the payroll product. **How does stablecoin payroll affect tax withholding?** Using a stablecoin does not remove tax, labor, withholding, or reporting obligations. Requirements vary by jurisdiction and by where stablecoins enter the payroll flow. Providers should assess each market with qualified counsel. **Can a provider start with payroll account funding?** Yes. A provider can use stablecoins for account funding while keeping employee-facing payout methods unchanged. This separates the onchain funding leg from any bank, fiat, or off-ramp legs used to pay recipients. **How should providers approach payroll data privacy?** Payroll data requires careful controls over who can see balances, amounts, identities, and payment activity. [Tempo Zones](/blog/introducing-tempo-zones) are an opt-in option designed for payment flows that require controlled visibility. The right architecture depends on each provider's legal, compliance, and operating requirements. **What should payroll providers evaluate before integrating stablecoins?** Providers should evaluate where stablecoins enter the flow, recipient preferences, wallet and custody models, market coverage, liquidity and conversion partners, compliance requirements, reconciliation, and customer support. --- ## How stablecoin rails help Banking-as-a-Service scale globally > Source: https://tempo.xyz/learn/stablecoin-rails-banking-as-a-service/ > Language: en _Banking-as-a-Service helps fintechs launch financial products through regulated partners and APIs. As those platforms expand across countries, currencies, and payout corridors, the settlement layer can become harder to scale. Stablecoin rails do not replace banks or BaaS infrastructure, but they can add a complementary payment layer for flows that need continuous availability, faster finality, and more predictable costs. Learn how [Tempo's payment infrastructure](/) supports stablecoin settlement, reconciliation, and programmable payment workflows._ Banking-as-a-Service (BaaS) lets fintechs offer financial products without obtaining a banking charter or certain licenses themselves, depending on the product model and jurisdiction. Through APIs, BaaS providers give fintechs access to core functions such as accounts, payments, and cards. Embedded finance is the customer-facing layer: the experience users see when financial services appear inside a marketplace, payroll platform, or SaaS product. That model works well when money movement stays inside familiar markets and rails. It becomes harder to manage when a platform needs to move funds across more countries, currencies, and payout corridors. Each new market can add settlement delays, cross-border fees, compliance requirements, prefunding needs, and reconciliation work. Stablecoin rails can help address some of those pressure points. They do not replace bank relationships, sponsor banks, or regulated financial infrastructure. They add another settlement layer for payment flows that need to operate globally and around the clock. This article explains where BaaS platforms face cross-border limitations, how stablecoin rails can help, and where Tempo fits into the stack. ## Where BaaS platforms face cross-border limits BaaS can help fintechs launch financial products faster, but global payment expansion puts pressure on the infrastructure underneath. The friction tends to show up in three areas: settlement, partner dependency, and operational control. ### Cross-border settlement is slow and operationally heavy BaaS can expose accounts and payments through APIs, but cross-border settlement still depends on the networks that connect banks across markets. A payment may pass through several intermediaries before reaching the recipient, and each step can add fees, processing time, and operational uncertainty. That creates practical problems for fintechs. Payments can take days to clear. Teams may have limited visibility into funds while they are in motion. Banking hours, holidays, and local cutoff times add more complexity. A transfer that misses one country's processing window may sit idle until the next local business day. ### Sponsor-bank dependency can create bottlenecks Many fintechs rely on sponsor banks to access regulated banking services. Those relationships are essential, but they also shape how quickly a fintech can expand. When a platform enters a new corridor, its launch timeline depends on what its banking and infrastructure partners can support. Geographic reach affects which markets the platform can serve. Risk appetite affects onboarding, approvals, transaction monitoring, and exception handling. Stablecoin rails can extend this stack when paired with appropriate regulated partners, custody, on/off-ramps, and compliance workflows. Tempo's [payment guide](https://docs.tempo.xyz/guide/payments/send-a-payment) and [Tempo Transactions](https://docs.tempo.xyz/guide/tempo-transaction) give developers tools for building stablecoin payment flows on Tempo. On Tempo, transactions finalize onchain in under one second. End-to-end payment timing still depends on the full flow, including wallets, issuers, on/off-ramps, and any local payment rails involved. ### Compliance and reconciliation get harder across jurisdictions Every new market comes with rules a platform needs to evaluate, including licensing, reporting, KYC/KYB, sanctions screening, consumer protection, and local expectations for how funds move. Stablecoin rails do not remove those obligations. Teams should still confirm requirements with legal and compliance counsel before launching in a new market. Reconciliation also becomes more complicated as payment flows span multiple systems. A payout may start in one ledger, settle through another provider, and return with a reference that does not match the original transaction. At small volumes, operations teams can often resolve those gaps manually. At scale, manual reconciliation becomes expensive and error-prone. Tempo includes features that can help support regulated payment workflows: - **Private transaction environments.** [Tempo Zones](/blog/introducing-tempo-zones/) are private execution environments connected to Tempo Mainnet. Activity inside a Zone is private from the public. The Zone operator can see activity inside the Zone, and users can see their own transactions and balances. Assets can move between Zones and Tempo Mainnet, which helps preserve access to broader network liquidity. - **Issuer-defined compliance controls.** Tempo's [compliance controls](/blog/compliance-controls/) include TIP-20 functions and TIP-403 policies for issuer-managed transfer rules such as allowlists and blocklists. In Zones, issuer-defined policies can be mirrored and enforced across the environments where the token is used. - **Transfer memos for reconciliation.** TIP-20 tokens can include [short transfer memos](https://docs.tempo.xyz/guide/payments/send-a-payment) for references such as invoice IDs, customer IDs, cost centers, or transaction notes. Larger payloads can be stored offchain with a hash or locator onchain. This helps payment teams match onchain transfers to internal records without putting sensitive customer data directly onchain. ## How stablecoin rails help BaaS platforms scale globally Stablecoin rails add a settlement layer for global fintech operations where speed, availability, and automation matter. For BaaS platforms, that can support faster payout flows, more consistent cross-border settlement, and more programmable money movement. ### 24/7 onchain settlement Stablecoin rails settle value onchain, so payments can move outside the constraints of local banking hours. When a platform serves customers across time zones, a Friday afternoon payment in one market can become a Monday processing issue in another. Stablecoin settlement can continue through weekends and holidays. For BaaS platforms, faster onchain settlement can support use cases such as real-time payouts, account funding, merchant settlement, and cross-border treasury movement. On Tempo, transactions finalize in under one second, which can give payment applications a faster settlement layer underneath the user experience. The exact customer-facing timing depends on the full payment path, especially when fiat on-ramps or off-ramps are involved. ### More predictable costs as volume grows Cross-border payments often become more expensive as platforms add markets. Each new corridor can introduce more intermediaries, FX spreads, prefunding requirements, and operational exceptions. Stablecoin rails can reduce some of that cost by moving value onchain instead of relying on correspondent banking chains for every leg of a transfer. Depending on the corridor and implementation, this may reduce the need to prefund balances in multiple destination markets. Platforms can move funds closer to when settlement occurs rather than leaving capital idle across many local accounts. Tempo is designed for predictable payment throughput. Dedicated payment lanes reserve blockspace for qualifying TIP-20 payment transactions, so payment flows are less exposed to unrelated network activity. Tempo also supports stablecoin-denominated fees. With [Tempo Transactions](/blog/tempo-transactions/), applications can pay network fees in supported USD-denominated TIP-20 stablecoins. Applications can also sponsor fees for users, which removes gas management from the customer experience. ### Programmable payment logic Stablecoins are blockchain-based payment assets, so applications can combine settlement with programmable logic. A platform can use smart contracts and payment workflows to route funds, automate treasury actions, split revenue, or release payments when defined conditions are met. Tempo Transactions provide native tools for payment workflows: - **Complete related actions together.** Batch calls bundle multiple steps into one atomic transaction. A multi-step payout either completes in full or reverts, reducing the risk of partial execution. - **Delegate signing authority.** Access keys let an account delegate transaction signing to a secondary key with defined permissions, reducing the need to repeatedly use a primary key for routine actions. - **Control when transactions execute.** Scheduled transactions let users define a future execution window. Validity windows and nonce tools help prevent outdated transactions from remaining valid longer than intended. - **Process payments in parallel.** Concurrent transactions use independent nonce streams so high-activity accounts can submit multiple transactions without waiting for a single sequential nonce. Together, these features can help BaaS platforms automate high-volume payment workflows without building custom contracts or middleware for every use case. ### Dollar-denominated flows where supported Stablecoin rails can support dollar-denominated payment flows in markets where local rails are fragmented, expensive, or volatile. For customers and businesses that transact across borders, a [stablecoin-denominated balance](/developers/docs/protocol/tip20/overview/) can provide a consistent settlement asset. This does not mean stablecoins are available or appropriate in every market. Platforms still need to evaluate local licensing, custody, sanctions screening, issuer risk, redemption, tax, reporting, and off-ramp requirements. Where permitted and supported by the right partners, stablecoins can make the settlement layer more consistent across markets. ## Extend BaaS infrastructure with stablecoin rails on Tempo Stablecoin rails work alongside banks and Banking-as-a-Service. Banks provide the regulated foundation many fintechs depend on, while BaaS gives platforms API access to launch accounts, cards, and payment products. Stablecoins add a complementary settlement layer for payment flows that need to move across borders faster, operate outside banking hours, or execute with more automation. [Tempo](/) is a payments-first Layer 1 blockchain built for stablecoin payments. For BaaS platforms, that matters because payment operations depend on more than moving value from one address to another. Platforms need predictable settlement, clear reconciliation data, policy controls, and reliable execution at scale. Tempo is designed around those requirements. Fees can be paid in stablecoins, so platforms do not need to manage a separate volatile token to process payments. Dedicated payment lanes help high-volume flows settle more predictably. Tempo Transactions support workflows such as sponsored fees, batch payments, and scheduled transfers. TIP-20 transfer memos let structured payment references travel with each transaction, giving accounting, ERP, and payment systems the data they need to reconcile payments cleanly. Compliance controls can support issuer-defined transfer policies, while Tempo Zones provide private execution environments for flows that require more control. Legal and regulatory obligations remain with the institutions and providers operating the payment flow. Explore [Tempo's work with Coastal](/customer-stories/coastal/) to see how stablecoin and traditional rails can operate side by side. For a broader overview, read [Cross-border payments with stablecoins](/learn/cross-border-payments/). --- ## Frequently asked questions ### What is Banking-as-a-Service? Banking-as-a-Service is infrastructure that lets fintechs and other platforms offer financial products through regulated banking partners and APIs. Depending on the model, BaaS programs may support payments, accounts, cards, identity checks, compliance operations, and ledger functionality. The specific regulatory obligations vary by product, market, and partner structure. ### What is the difference between Banking-as-a-Service and embedded finance? BaaS is the behind-the-scenes infrastructure that exposes core banking and payment capabilities through APIs. Embedded finance is the customer-facing experience, where those capabilities appear inside a nonfinancial product such as a marketplace, payroll platform, or SaaS tool. In other words, BaaS powers the infrastructure. Embedded finance turns that infrastructure into financial tools users can access inside products they already use. ### How do stablecoin rails help fintechs scale across borders? Stablecoin rails can help fintechs move value across markets with faster onchain settlement, fewer intermediary steps, and more consistent transaction records. They can support use cases such as global payouts, merchant settlement, account funding, and treasury movement. Cost, speed, and availability depend on the corridor, partners, local rails, and compliance requirements involved. ### Why are stablecoin rails useful for BaaS platforms? BaaS platforms often support multiple products, customer segments, and payment flows. Stablecoin rails can give those platforms an additional settlement layer for cross-border flows that need continuous availability, faster finality, and programmable execution. They can complement BaaS and open banking strategies by extending how platforms move money after users connect accounts, initiate payments, or access embedded financial products. ### Do stablecoin rails replace banks? No. Stablecoin rails complement bank and BaaS infrastructure. Banks and regulated providers still play critical roles in fiat on/off-ramps, custody, compliance programs, account access, local payment rails, and card networks. Stablecoin rails add another way to settle value across markets. --- **Continue learning:** [Stablecoins for Business](/learn/stablecoins-for-business) · [Cross-Border Payments](/learn/cross-border-payments) · [Beyond Sponsor Banks](/learn/beyond-sponsor-banks) --- ## Stablecoin settlement: An enterprise evaluation guide > Source: https://tempo.xyz/learn/stablecoin-settlement/ > Language: en _Stablecoins make payment settlement available 24/7, but enterprise teams still need predictable fees, reliable finality, and reconciliation data. Tempo is built for these payment flows with near-instant settlement, stablecoin-native fees, payment lanes, and TIP-20 memos. Start with the_ [_Tempo payments docs_](https://docs.tempo.xyz/guide/payments) _or_ [_contact the Tempo team_](/contact) _to discuss settlement use cases._ Interest in stablecoins as an enterprise payment rail is growing. McKinsey estimates that annual stablecoin B2B payments [have already hit $226 billion](https://www.mckinsey.com/industries/financial-services/our-insights/stablecoins-in-payments-what-the-raw-transaction-numbers-miss), highlighting just how many businesses are actively exploring, and benefitting from, blockchain. Although stablecoin rails are becoming more attractive, choosing which protocol to integrate with goes beyond surface-level stats like transaction speeds and network popularity. Any company seriously considering stablecoin adoption needs a structured evaluation process to be sure their partner meets operational and regulatory requirements. The first step in choosing your stablecoin settlement layer is to clarify evaluation criteria. Learning more about core attributes of rails such as finality and reconciliation makes the stablecoin selection process far simpler. ## What stablecoin settlement means for institutions For banks and enterprises, [stablecoin settlement](/learn/stablecoin-payments/) means more than moving digital assets between wallets. Sending value on-chain is part of this process, but the feature that differentiates stablecoin settlement is that transactions can finalize in under one second. When values settle almost instantly on-chain, institutions no longer have to perform delay-prone end-of-day batch processing or wait for payments to confirm through a chain of intermediaries. Stablecoin settlements between sender and receiver banks occur on a single distributed ledger, which offers predictable settlement speed and fee structure. ## What should institutions look for when evaluating a stablecoin settlement infrastructure? While factors like speed and average fees matter when choosing [enterprise-ready blockchain](/learn/blockchain-payments/), businesses need to hold these settlement layers to a [higher standard for compliance](/blog/compliance-controls/) and operational readiness in all situations. Here’s what they should look for. ### Settlement finality When a stablecoin transaction is “final,” that means it’s irreversibly recorded on its distributed ledger. Senders and recipients only have confidence in their payments after passing this stage, making it a nonnegotiable feature for institutional stablecoin rails. Not all blockchains achieve settlement finality in the same way. For instance, some use probabilistic finality models. In this case, there’s always a possibility of chain reorganizations that could reverse a transaction, even though confidence generally increases as more blocks get added to the payment ledger. Other blockchains provide finality with no re-orgs, where transactions instantly finalize after passing the chain’s consensus mechanism. Of these two, enterprises need the certainty of finality with no re-orgs. This model is more reliable, even during periods of high network congestion. Tempo’s layer-1 blockchain is purpose-built for institutional payments with sub-second finality. The combination of reliability and fast settlement speeds gives finance teams the assurance they need to run their production payment operations without constant check-ins. ### Cost predictability When you’re dealing with enterprise-scale transactions, finding a stablecoin infrastructure with predictable low fees is arguably more important than gravitating to the lowest advertised transaction fees. Treasury and finance teams need to model unit economics before a payment flow goes live, and unexpected fee spikes can make forecasting harder. Tempo has no native gas token. [Transaction fees](https://docs.tempo.xyz/protocol/fees), including gas fees and priority fees, can be paid directly in supported USD-denominated TIP-20 stablecoins. Standard TIP-20 transfers have sub-cent fees. This means enterprises do not need to acquire or manage a volatile token just to move stablecoins. Tempo also uses [payment lanes](https://docs.tempo.xyz/protocol/blockspace/payment-lane-specification), which reserve blockspace for eligible TIP-20 payment transactions. Payment flows do not have to compete with all general smart contract activity on the network, helping fees stay low and stable during spikes in other types of activity. One of the primary reasons [Deel partnered with Tempo](/customer-stories/deel/) was the fee transparency and predictability our blockchain offers. With this infrastructure, Deel’s team can better forecast their operating costs while reducing the total fee expense for their thousands of global contractors. ### Controls at transfer For enterprises moving stablecoins, controlling who can send and receive funds is a core part of risk management. Enforcing access rules at the point of transfer helps prevent payments from settling when the sender or recipient does not meet the issuer’s policy. Tempo’s [TIP-20 token standard](https://docs.tempo.xyz/protocol/tip20/overview) integrates with the [TIP-403 Policy Registry](https://docs.tempo.xyz/protocol/tip403/overview), so issuers can allow or block addresses from sending and receiving their tokens. Policies can be shared across multiple tokens, giving issuers a consistent way to apply access rules. These controls are designed to support broader governance, risk, and compliance programs. Issuers and payment platforms decide how to connect them to identity verification, approval workflows, and other requirements. ### Reconciliation data For finance teams, it’s not enough to know a specific token value transferred between accounts on a blockchain. While data like timestamps and wallet addresses provide proof of payment, they don’t explain the [business context](/learn/stablecoins-for-business/) to reconcile each payment with your financial systems. To overcome this hurdle, enterprises look for stablecoin solutions that carry standardized business references compatible with their ERP and accounting platforms. Tempo addresses this with [TIP-20 transfer memos](https://docs.tempo.xyz/protocol/tip20/overview). A TIP-20 transfer can include a 32-byte memo for payment references such as invoice IDs, customer IDs, order numbers, or transaction notes. For larger or sensitive data, teams can keep the full detail offchain and place a commitment or locator onchain. For reconciliation, that means the payment reference can travel with the transfer instead of being stitched together later from separate systems. Payment processors and treasury teams can connect onchain settlement events to the ERP, accounting, or payment operations tools they already use. ## How stablecoin rails complement SWIFT and correspondent banking In practice, most institutions integrate blockchain rails into their existing infrastructure to make cross-border settlement more efficient while maintaining traditional payment pathways. SWIFT and correspondent banking provide messaging, bank connectivity, currency coverage, and established operational processes. Stablecoin rails provide an additional settlement path that operates 24/7 and can include programmable payment logic. Separating messaging from settlement helps clarify where each system fits. SWIFT can transmit payment instructions and status information between financial institutions. Stablecoin settlement rails can move value onchain when a payment flow benefits from faster finality, stablecoin-denominated fees, or programmable execution. This is especially relevant for cross-border payouts, treasury transfers, remittances, and embedded finance. Teams can keep familiar banking relationships and controls while adding a settlement option for flows where speed, availability, and payment metadata matter. ## Risks and limitations to account for Stablecoin settlement can reduce friction, but it does not remove every operational or regulatory consideration. Teams should evaluate the full payment flow before moving production volume. - **Issuer and reserve risk.** A stablecoin's reliability depends on the issuer, redemption terms, reserve practices, transparency, and applicable licensing. Teams should review these factors with their legal, risk, and compliance advisors. - **Custody and key management.** Wallet administration, signing policies, access recovery, and transaction approvals need clear ownership. Some teams manage this in-house, while others work with custodians or wallet infrastructure providers. - **Liquidity and coverage.** On-ramps, off-ramps, supported currencies, and counterparty readiness can vary by market. A fast rail still needs practical liquidity at both ends of the payment flow. - **Data and privacy.** Reconciliation metadata is useful, but teams should avoid placing sensitive data directly onchain. For larger or private data, Tempo supports patterns where the memo carries a reference while the full record stays offchain. - **Policy controls.** Whitelists, blocklists, and role-based permissions can support governance workflows, but they are not a substitute for a compliance program. ## How Tempo approaches stablecoin settlement Tempo brings the core requirements for stablecoin payments into the protocol layer. - [Near-instant settlement](https://docs.tempo.xyz/learn/tempo/performance) gives enterprises a fast finality signal. Blocks finalize in about 0.5 to 0.6 seconds in normal conditions, so teams can move settled payments into downstream workflows with more confidence. - [Stablecoin-native fees](https://docs.tempo.xyz/protocol/fees) remove the need for a volatile gas token. Supported USD-denominated TIP-20 stablecoins can pay transaction fees directly, and standard TIP-20 transfers have sub-cent fees. - [Dedicated payment lanes](https://docs.tempo.xyz/protocol/blockspace/payment-lane-specification) reserve blockspace for eligible payment transactions. This helps high-volume payout, payroll, treasury, and embedded finance flows avoid congestion created by unrelated activity. - [TIP-20 memos](https://docs.tempo.xyz/guide/payments/send-a-payment) attach payment references to transfers. This helps teams reconcile stablecoin payments with invoices, accounts, and internal records. - [TIP-403 policies](https://docs.tempo.xyz/protocol/tip403/overview) provide shared whitelist and blacklist primitives for tokens that need access-control rules. Issuers can apply consistent policy logic without building one-off controls for every token. - [Tempo Transactions](https://docs.tempo.xyz/guide/tempo-transaction) add payment-specific capabilities such as batch calls, fee sponsorship, concurrent transactions, scheduled transactions, and passkey authentication. For payment applications, that means more of the mechanics needed for real-world workflows are available natively. Companies such as [Deel](/customer-stories/deel/) and [Coastal](/customer-stories/coastal/) show how enterprise teams are exploring Tempo to improve payment operations while preserving familiar operating models. ## Getting started Teams evaluating stablecoin settlement should start with the use case, then work backward to the infrastructure requirements. A payout flow, treasury transfer, subscription payment, and interbank settlement workflow may all need different controls, liquidity paths, and integration patterns. ## FAQ ### How quickly can a stablecoin payment be settled? The exact timing depends on the rail. On Tempo, blocks finalize in about ~0.5 seconds in normal conditions, and finalized blocks include the transactions in them. That gives payment teams a fast finality signal for downstream workflows. ### What makes a settlement rail enterprise-ready? Enterprise teams usually evaluate finality, fee predictability, operational controls, reconciliation data, liquidity, custody, and integration with existing systems. For stablecoin payments, the strongest infrastructure makes these requirements easier to manage in production. ### How is settlement finality different from clearing or confirmation? Clearing generally refers to validating and preparing a payment for settlement. A confirmation can mean a transaction was accepted or observed on a network. Settlement finality is stronger: it is the point when the payment can no longer be reordered or removed from the canonical chain. ### Can stablecoin settlement replace SWIFT or correspondent banking? In many enterprise workflows, stablecoin settlement is being utilized as a complement not a replacement. SWIFT and correspondent banks provide messaging, currency coverage, and established operational processes. Stablecoin rails can add 24/7 settlement, programmable execution, and payment metadata for flows where those capabilities matter. --- ## Can stablecoins and tokenized deposits coexist? > Source: https://tempo.xyz/learn/stablecoins-and-tokenized-deposits/ > Language: en _Stablecoins and tokenized deposits both make money programmable, faster to move, and easier to reconcile. They differ in issuer model, network access, liquidity, and operational control. For teams evaluating stablecoin payments, Tempo provides infrastructure designed for high-volume, low-cost payment flows._ Stablecoins have moved beyond crypto trading infrastructure. The [IMF reported](https://www.imf.org/en/blogs/articles/2025/12/04/how-stablecoins-can-improve-payments-and-global-finance) that the two largest stablecoins, USDT and USDC, reached a combined market capitalization of $260 billion and processed $23 trillion in trading volume in 2024. The [BIS has also found](https://www.bis.org/publ/bppdf/bispap147.pdf) that many jurisdictions now have, or are developing, stablecoin regulatory frameworks. At the same time, banks are bringing deposits onto blockchain-based systems. [J.P. Morgan describes JPM Coin](https://www.jpmorgan.com/kinexys/jpm-coin) as a bank-issued deposit token for institutional payments. [Citi Token Services](https://www.citigroup.com/global/businesses/services/services-digital-assets) uses blockchain-based infrastructure for 24/7 liquidity movement and trade finance workflows. For corporate finance, treasury, and payment teams, the question is not which model wins. The more useful question is where each one fits. ## The basic difference Stablecoins are digital tokens designed to maintain a stable value against a reference asset, most often the U.S. dollar. Major fiat-backed stablecoins are issued by private companies and backed by reserves such as cash, bank deposits, or short-term government securities. Tokenized deposits are digital representations of commercial bank deposits. They are issued by banks and remain tied to the bank's balance sheet, account infrastructure, and compliance controls. Both can use blockchain technology. But they are not the same instrument. |Operational feature|Stablecoins|Tokenized deposits| |-|-|-| |Issuer|Stablecoin issuer|Commercial bank| |Claim|Claim backed by reserve assets|Deposit claim on a bank| |Access|Broad wallet and platform access, subject to compliance and product availability|Approved bank clients and counterparties| |Network model|Often public blockchain networks|Bank-controlled systems, private networks, or permissioned activity on public networks| |Liquidity|Deepest in USD stablecoins and major on/off-ramps|Tied to bank accounts, supported currencies, and bank network coverage| |Controls|Businesses manage custody, wallet screening, accounting, and local requirements|Bank manages onboarding, monitoring, and operational controls| |Best fit|Open, global payment flows|Bank-managed treasury and institutional workflows| ## Why businesses compare them B2B payments often break down at the same points: settlement delays, cut-off times, high cross-border fees, poor payment visibility, and manual reconciliation. Both stablecoins and tokenized deposits address parts of that problem. Stablecoins are useful when a business needs to send value across a broad network of wallets, platforms, countries, or counterparties. They can settle around the clock and move without relying on every participant using the same bank. Tokenized deposits are useful when a business wants blockchain-based settlement while staying inside existing bank relationships. They can support treasury workflows, institutional transfers, and controlled liquidity movement between approved participants. The tradeoff is reach versus control. Stablecoins are more open. Tokenized deposits are more bank-managed. ## Settlement and operating hours Stablecoins settle on blockchain networks. Once a transaction is confirmed, both sender and recipient can see the transfer on a shared ledger. This gives payment teams faster settlement and clearer transaction status than many traditional cross-border flows. That does not remove every dependency. Businesses still need custody, compliance checks, liquidity, and on/off-ramps when funds need to move between stablecoins and local bank accounts. Tokenized deposits can also support near-real-time or 24/7 movement, depending on the bank product and supported markets. The advantage is that settlement, risk controls, and account relationships stay within a regulated bank environment. The limitation is that access usually depends on the bank's client network, supported currencies, and product coverage. ## Programmability Both models can support programmable payments. With stablecoins, businesses can automate transfers across open networks. This is useful for marketplaces, global payouts, supplier payments, remittances, embedded finance, and other flows where recipients may sit outside one banking network. With tokenized deposits, banks can add programmability to institutional workflows. This is useful for treasury operations, liquidity movement, collateral workflows, and settlement between approved counterparties. The distinction matters for product design. Stablecoins work well when a payment product needs broad distribution. Tokenized deposits work well when a workflow depends on bank-grade controls and known participants. ## Reconciliation and metadata Fast settlement is not enough for B2B payments. Finance teams also need to know what a payment was for, who sent it, and how to record it. Stablecoin infrastructure can attach references such as invoice IDs, customer IDs, or internal payment identifiers to transactions. On Tempo, [TIP-20 transfers support payment memos](https://docs.tempo.xyz/protocol/tip20/overview#transfer-memos) for reconciliation, which helps connect onchain payments to offchain accounting and ledger systems. Tokenized deposit systems can also support structured payment information through bank channels and enterprise integrations. For treasury teams, that can make adoption easier when the business already relies on bank reporting, ERP connections, and internal approval workflows. ## Cross-border payments Stablecoins are often strongest where payment reach matters most. A company can pay contractors, suppliers, merchants, or platform users across markets without waiting for bank operating hours in every jurisdiction. For payment operators, that can reduce prefunding needs and improve access to working capital. The constraints are practical. Businesses still need to manage sanctions screening, wallet risk, local rules, custody, tax treatment, and conversion into local currency where needed. Tokenized deposits can simplify cross-border liquidity movement inside a bank's supported network. They may also connect more naturally to bank FX, reporting, and account structures. The constraint is coverage: the payment flow works only where the bank, currency, and counterparties are supported. ## Where Tempo fits Tempo is built for payment flows that use stablecoins, tokenized deposits, or both. Stablecoins can support open, global payment flows across wallets, platforms, and markets. Tokenized deposits can support bank-issued money movement for institutions that want blockchain-based settlement while preserving bank controls. Tempo provides the infrastructure layer for these models to move at payment scale. Transaction fees can be paid in supported stablecoins, so businesses do not need to manage a separate volatile gas token. Transfers can also include payment memos, helping teams connect onchain movement to invoices, customer records, and internal ledgers. For payment teams, this means stablecoins and tokenized deposits can operate more like modern payment infrastructure: high-volume, low-cost, programmable, and easier to reconcile. Tempo is designed for use cases such as global payouts, remittances, marketplace settlement, embedded finance, microtransactions, and bank-issued tokenized deposit flows. ## Stablecoins and tokenized deposits solve different problems Stablecoins and tokenized deposits are likely to coexist because they optimize for different environments. Stablecoins are better suited to open, global payment flows where reach, speed, and interoperability matter. Tokenized deposits are better suited to bank-managed workflows where institutional controls, account relationships, and regulated access matter. For businesses, the right choice depends on the payment flow. A marketplace paying sellers across many countries may prefer stablecoins. A corporate treasury team moving liquidity within an existing bank relationship may prefer tokenized deposits. Many companies will use both. ## Getting started If you are evaluating stablecoins for global payment flows, start with the operational requirements: recipient coverage, settlement speed, compliance obligations, custody model, reconciliation needs, and local currency conversion. To learn how Tempo supports stablecoin payments, explore the [Tempo docs](https://docs.tempo.xyz/) or get in touch at [partners@tempo.xyz](mailto:partners@tempo.xyz). --- ## Frequently asked questions **What are tokenized deposits?** Tokenized deposits are a digital representation of money issued by a bank. A tokenized deposit represents a deposit claim on the issuing bank and operates within that bank's controls and supported network. **Are tokenized deposits the same as stablecoins?** No. Stablecoins are issued by stablecoin issuers and backed by reserve assets. Tokenized deposits are issued by banks and represent commercial bank deposits. **Will tokenized deposits replace stablecoins?** Tokenized deposits and stablecoins serve different needs. Tokenized deposits fit bank-managed institutional workflows. Stablecoins fit broader payment flows across wallets, platforms, and markets. **Why do businesses use stablecoins for payments?** Businesses use stablecoins for faster settlement, 24/7 availability, programmable transfers, and broader cross-border reach. They are especially useful when recipients are spread across countries, platforms, or banking systems. **What should businesses evaluate before using stablecoins?** Businesses should evaluate compliance requirements, wallet and custody operations, liquidity, off-ramp coverage, accounting treatment, reconciliation workflows, and supported jurisdictions. --- **Continue learning:** [Stablecoins for business](/learn/stablecoins-for-business) · [Tokenized deposits](/learn/tokenized-deposits) · [Cross-border payments](/learn/cross-border-payments) --- ## Stablecoins for business: a practical guide for finance teams > Source: https://tempo.xyz/learn/stablecoins-for-business/ > Language: en _Finance teams at companies from startups to the Fortune 500 are evaluating stablecoins for cross-border payments, treasury management, and global operations. Stablecoins work for enterprise use cases. The remaining step is getting started._ Three shifts have moved stablecoins from crypto experiment to enterprise infrastructure: regulatory clarity (the GENIUS Act in the US, MiCA in the EU), bank integration (Stripe, Visa, and major banks building on stablecoin rails), and real-world proof (companies like DoorDash, Felix, and Coastal Bank running production payment flows). If your finance team hasn't evaluated stablecoins yet, your competitors likely have. ## Key business use cases ### Treasury management Global treasury teams manage cash across dozens of accounts, currencies, and banking relationships. Stablecoins enable 24/7, instant movement of dollar-denominated value between entities, eliminating the correspondent banking delays that trap working capital. Learn more in our [corporate treasury guide](/blog/corporate-treasury). ### Vendor and supplier payments Cross-border vendor payments are slow and expensive. A $10,000 payment to a supplier in Southeast Asia can cost $40–150 in fees and take 3–5 days to settle. Stablecoins reduce that to seconds and a fraction of the cost, with a full audit trail for reconciliation. ### Cross-border transfers Stablecoins bypass the correspondent banking system entirely: no intermediary banks, no pre-funded nostro accounts, no weekend delays. Payments settle in seconds with [sub-cent fees](/blog/stablecoin-fees). See our [cross-border payments guide](/learn/cross-border-payments) for a detailed comparison. ### Payroll and contractor payments Companies with distributed teams can use stablecoins to pay international contractors. Recipients can hold dollar-denominated value and choose when to convert through the services available to them. Read more in our [stablecoin payroll guide](/learn/stablecoin-payroll). ### Marketplace and platform payouts Multi-sided marketplaces, from gig economy platforms to creator economy apps, can deliver instant payouts to merchants, drivers, and creators worldwide. DoorDash is [building this on Tempo](/blog/doordash-partners-with-tempo-to-bring-stablecoin-payments-to-its-global-marketplace) for its global merchant network. ## The stablecoin sandwich One of the biggest misconceptions about enterprise stablecoin adoption is that it requires holding crypto on your balance sheet. It doesn't. The "stablecoin sandwich" model works like this: 1. **Fiat in.** Your business sends USD (or local currency) from your existing bank account to an orchestration provider. 2. **Stablecoin transfer.** The provider converts to stablecoins, executes the transfer onchain, and delivers to the recipient's provider. 3. **Fiat out.** The recipient receives local currency in their bank account or mobile wallet. Your business never touches stablecoins directly. You send fiat, the recipient receives fiat, and stablecoins handle the movement in between, delivering the speed and cost advantages without the balance sheet complexity. ## The cost advantage The cost savings from stablecoin payments are well-documented. Traditional cross-border wires cost $10–40 per transaction plus 0.1–4.0% in FX spreads. Stablecoin onramp and transfer fees typically range from 0.1–0.4%, delivering a **60–80% cost reduction** on a per-transaction basis. At scale, the savings compound: - **A company processing 1,000 cross-border payments/month** at an average of $5,000 per payment could save $120,000–$400,000 annually in transaction fees alone. - **Working capital improvements** from instant settlement can free up millions in cash previously trapped in transit. - **Operational savings** from reduced reconciliation effort, fewer payment failures, and eliminated pre-funding requirements. For a detailed cost comparison, see our guide on [ACH, wire, and stablecoin rails compared](/blog/ach-vs-wire-vs-stablecoins-a-guide-for-finance-teams). ## Getting started: an assessment framework Before selecting a provider or integration approach, finance teams should evaluate three areas: ### 1. Identify high-friction corridors Identify your highest-cost or highest-friction payment corridors. Stablecoins deliver the most value where traditional rails are slowest and most expensive, typically US-to-Latin America, US-to-Africa, or cross-border B2B payments between multiple regions. ### 2. Map your pain points Common pain points include cost, settlement speed, reconciliation overhead, trapped working capital, and payment failures. Each pain point may lead to a different starting use case. ### 3. Choose buy or build Most enterprises start with a "buy" approach using orchestration providers, then evaluate building in-house as volumes grow. ## Integration approaches ### Buy: orchestration providers Providers like [Bridge](https://www.bridge.xyz/), BVNK, and ZeroHash offer APIs that abstract the stablecoin complexity. You integrate their API into your existing payment flow, send fiat, and they handle on/off-ramp, custody, compliance, and liquidity. Integration can take as little as two weeks. **Best for:** Companies that want to test stablecoins quickly without building blockchain expertise in-house. ### Build: direct integration Building directly on stablecoin infrastructure gives you more control over the payment flow, lower per-transaction costs at scale, and the ability to customize for your specific use case. This requires managing wallets, custody, banking relationships, and compliance tooling. **Best for:** Companies with high transaction volumes, technical teams, and specific requirements that off-the-shelf solutions don't meet. ### Hybrid Many enterprises start with an orchestration provider for speed, then bring specific corridors or use cases in-house as they scale. This is the approach most enterprise design partners on Tempo have followed. ## Risk considerations ### Counterparty risk Not all stablecoins are created equal. Evaluate the issuer's reserve composition, attestation frequency, regulatory status, and track record. The GENIUS Act and MiCA now provide regulatory minimums for licensed issuers. ### Operational risk New payment rails introduce new operational considerations: wallet management, key security, provider uptime, and support processes. Start with a pilot to identify and address these before scaling. ### Regulatory risk The regulatory landscape is stabilizing but still evolving. Work with counsel familiar with stablecoin regulation in your operating jurisdictions. ## Why Tempo for enterprise stablecoin payments Tempo is the blockchain purpose-built for payments. Unlike general-purpose blockchains designed for trading and DeFi, Tempo was built with enterprise payment requirements from day one: - **Sub-second finality.** Payments settle in under a second, matching the speed expectations of modern payment systems. - **Stablecoin fees.** Transaction fees are paid in stablecoins, not volatile gas tokens. No separate token balances, no crypto on your books. See [how stablecoin fees work](/blog/stablecoin-fees). - **Compliance controls.** Native [TIP-20 controls](/blog/compliance-controls) for sanctions screening, allowlists, blocklists, and Travel Rule compliance built into the protocol. - **Privacy.** [Tempo Zones](/blog/introducing-tempo-zones) enable private payments where only the parties to a transaction see the details, critical for enterprise payment confidentiality. - **Enterprise design partners.** Tempo is built with input from companies like DoorDash, Stripe, Coastal Bank, and ARQ. Read about their work in our [enterprise announcement](/blog/enterprise). For finance teams, this means cross-border payments can be faster, cheaper, and compliant out of the box, without managing crypto infrastructure. ## Enterprise proof points Leading companies are already running stablecoin payment operations on Tempo: - **DoorDash** is bringing stablecoin-powered payouts to its global marketplace across 40+ countries. [Read the story](/blog/doordash-partners-with-tempo-to-bring-stablecoin-payments-to-its-global-marketplace) - **Felix** delivers instant remittance settlement to Latin America using stablecoin rails on Tempo. [Read the story](/blog/felix-brings-instant-remittance-settlement-on-tempo) - **ARQ** is building cross-border payment infrastructure for Latin American businesses on Tempo. [Read the story](/blog/arq-is-building-cross-border-payment-infrastructure-on-tempo) - **Coastal Bank** partners with Tempo for stablecoin-settled cross-border payments. [Read the story](/blog/coastal-bank-partners-with-tempo-to-build-stablecoin-settled-cross-border-payments) ## Why this matters for finance teams Stablecoins are not a future technology. They are live infrastructure being adopted by enterprise finance teams today. The companies gaining an advantage are those that move from evaluation to pilot while competitors are still debating whether stablecoins are "ready." The practical next step: pick your highest-friction payment corridor, quantify the cost and speed improvements stablecoins could deliver, and run a 60-day pilot. If you need help structuring that evaluation, [contact Tempo's advisory team](/contact). --- ## Frequently asked questions **Do we need to hold crypto on our balance sheet?** No. Most stablecoin orchestration providers (Bridge, BVNK, ZeroHash) handle the conversion between fiat and stablecoins. Your business sends and receives fiat through your existing bank accounts. Stablecoins handle the transfer in the middle. This "stablecoin sandwich" model avoids balance sheet complexity entirely. **Which banks support stablecoins?** A growing number of banks support stablecoin settlement, either directly or through partnerships. [Coastal Bank](/blog/coastal-bank-partners-with-tempo-to-build-stablecoin-settled-cross-border-payments) partners with Tempo for stablecoin-settled cross-border payments. Major banks including JPMorgan and Standard Chartered have stablecoin or tokenized deposit initiatives. [Stripe](/blog/stripe-and-tempo-stablecoin-settlement-for-global-money-movement) supports stablecoin settlement for its merchant base. Contact your banking partner to understand their current capabilities. **How does using stablecoins affect our accounting?** US dollar-denominated stablecoins avoid the FX complexity of foreign currency holdings. If you use a fiat-in, fiat-out model through an orchestration provider, your accounting treatment is similar to your existing payment flows because you're sending and receiving dollars. If you hold stablecoins directly, accounting standards are evolving; consult with your auditor for the latest guidance. **What's the minimum volume to justify stablecoin adoption?** There is no hard minimum. Companies processing as few as 50–100 cross-border payments per month can see meaningful cost savings, especially in high-fee corridors. The ROI depends on your current payment costs and friction, not absolute volume. A single high-friction corridor can justify a pilot. **How do I pitch stablecoins to my CFO?** Lead with the business case, not the technology. Quantify your current cross-border payment costs (fees, FX spreads, trapped working capital, operational overhead), then model the 60–80% cost reduction stablecoins deliver. Reference enterprise adopters (DoorDash, Stripe, Coastal Bank) to show this is mainstream infrastructure, not experimental crypto. Frame it as a payment infrastructure upgrade. [Contact Tempo](/contact) for help building the business case. **Is this just for cross-border payments?** No. While cross-border payments are the most common starting point because the cost and speed advantages are most dramatic, enterprises also use stablecoins for domestic B2B settlement (instant, 24/7), treasury management (real-time cash positioning), and [marketplace payouts](/learn/global-payouts) (instant delivery to merchants and contractors). --- **Continue learning:** [Global Payouts with Stablecoins](/learn/global-payouts) · [Cross-Border Payments](/learn/cross-border-payments) · [Blockchain Payments](/learn/blockchain-payments) --- ## SWIFT message types (MT) and ISO 20022 MX for developers > Source: https://tempo.xyz/learn/swift-message-types/ > Language: en The Society for Worldwide Interbank Financial Telecommunication (SWIFT) network facilitates the sending and receiving of messages between financial institutions. SWIFT messages contain payment instructions and financial data, while the actual movement of funds happens elsewhere. Until recently, the legacy SWIFT MT format defined the structure and content of these messages. Today, the more robust SWIFT MX message format, which follows the ISO 20022 international standard, has replaced MT for CBPR+ cross-border interbank payment instructions. MT messages remain supported in other workflows, including corporate-to-bank and reporting. This guide covers the structure, mappings, and integration requirements of both SWIFT message types and the SWIFT MX format to help payment integration developers understand how to work with them. By grasping the core differences, developers can avoid the manual investigation work and downstream reconciliation issues that often come with using the wrong standard or formatting. ## What is the SWIFT MT (message type) format? Message types in SWIFT are the legacy standardized format for SWIFT messages. These were the default until the migration to the MX standard started in March 2023. Like MX messages, message types carry payment instructions and financial data between financial institutions. In other words, SWIFT is the instruction layer, not the settlement layer. ### Reading a SWIFT message code Each SWIFT MT message comes with a label to identify its purpose. These labels contain a three-digit string. The first digit identifies the category, the second the group, and the third the specific function. [The categories each initial digit maps to are](https://www2.swift.com/knowledgecentre/rest/v1/publications/usgi_20250718/2.0/usgi_20250718.pdf): - **1xx**: Customer Payments and Cheques - **2xx**: Financial Institution Transfers - **3xx**: Treasury Markets — FX, Money Markets, and Derivatives - **4xx**: Collections and Cash Letters - **5xx**: Securities Markets - **6xx**: Treasury Markets — Commodities — Reference Data - **7xx**: Documentary Credits and Guarantees/Standby Letters of Credit - **8xx**: Travellers Cheques - **9xx**: Cash Management and Customer Status - **nxx**: Common Group Messages ### The five-block structure SWIFT message types are organized into five blocks: - **Block 1 (basic header)** contains information about the financial institution’s identity and session control. - **Block 2 (application header)** contains information about the message type, direction, and counterparty address. - **Block 3 (user header)** contains metadata like tracking identifiers. - **Block 4 (text/body)** contains the actual payment instructions or business data. - **Block 5 (trailer)** contains information needed for integrity checks. Field tags structure MT messages by labeling each piece of data. For instance, :32A: marks the field containing the transaction’s value date, currency, and amount. MT messages also have to follow validation rules. For example, fields must appear in the correct sequence, use the correct character set and content type, and adhere to length restrictions. To illustrate, take Field 70 (Remittance Information), which allows up to 4 lines of 35 characters each from the SWIFT X character set. In the following example, the first line hits the character limit, so the text wraps to the next line: ```text :70:/INV/abc/SDF-96//1234-234///ROC/98I U87 ``` In ISO 20022 MX messages for cross-border payments, structured remittance details in the corresponding RmtInf element have a limit of 9,000 characters of business information under CBPR+ usage guidelines, excluding XML tags. While these validation rules are enforced by the SWIFT network, there may be other usage requirements depending on the services, market practices, or counterparties involved in a transaction. ## What is the SWIFT MX (message XML) format? SWIFT MT vs. MX SWIFT introduced the MX standard to let financial institutions send messages with more detailed and structured data. The critical distinction between these two SWIFT message formats is how they organize this data. MT messages are plain text containing tagged fields with fixed formats and tight length limitations. MX messages follow the ISO 20022 standard and are written in XML. This keeps data organized as nested, labeled elements with meanings defined by the ISO 20022 [central data dictionary](https://www.iso20022.org/financial-repository). Because MX messages allow for many more labeled, dedicated elements, they support more granular payment, remittance, and party data. This also facilitates downstream reconciliation in ERP and treasury systems. It’s possible to convert an MX message to an MT message if necessary, but doing so can result in data truncation and loss of structured detail. This may drop information other parties need to process and reconcile payments. ## Common SWIFT message types in payment integrations Even after the end of CBPR+ coexistence in November 2025, developers may still come across SWIFT MT messages in specific areas like corporate-to-bank and reporting workflows. Here’s how some of the most common SWIFT MT messages map to their SWIFT MX equivalents and what each message means. The [migration plans](https://www.swift.com/swift-resource/252463/download) below apply to FI-to-FI traffic within CBPR+. Corporate SCORE traffic follows separate requirements. |**SWIFT MT message**|**ISO 20022 MX equivalent**|**Purpose**|**Typical payment workflow**|**Current status**| |-|-|-|-|-| |MT103|pacs.008|Single Customer Credit Transfer|Customer payment sent from the customer’s bank to the recipient’s bank|Replaced by pacs.008 for cross-border interbank payments| |MT202 MT202 COV|pacs.009 pacs.009 COV|General Financial Institution Transfer|Bank-to-bank transfers and settlement|Replaced by pacs.009 for cross-border interbank payments| |MT101|pain.001|Request for Transfer|Requests relayed between banks|Still supported Single: Contingency conversion to pain.001 planned for SR 2026; timetable under review Multiple: Removal planned for SR 2026; timetable under review| |MT900 MT910|camt.054|Confirmation of Debit/Credit|Notifying an account owner about a new debit or credit|Still supported Phase-out planned for SR 2028; timetable under review| |MT940|camt.053|Customer Statement Message|Daily account reporting and reconciliation|Still supported Phase-out planned for SR 2028; timetable under review| Keep in mind that these aren’t always perfect one-to-one mappings. ISO 20022 MX messages can carry far richer and more structured data, which means some of that data may get lost in translation. ## How developers format and validate MT and MX messages The SWIFT guidelines for formatting MT messages require tagged text fields validated against SWIFT’s character limits, sequencing, and network rules, as outlined above. MX messages are formatted as nested XML and validated against XML schemas from the ISO 20022 website. For cross-border payments and reporting, they’re also validated against the stricter rules of CBPR+, which are SWIFT’s own usage guidelines. Finally, messages must adhere to any service- or counterparty-specific requirements. ## Why developers may still need to support both MT and MX Developers can still run into MT messages in legacy corporate, tracking, or contingency workflows. Since converting richer MX messages to more rigid and limited MT messages risks losing information, this presents a challenge for integration teams. Instead of trying to support every possible type of message, developers should design for the specific messages and counterparties they actually interact with. Note which MT messages the institution still sends and receives to understand which workflows and counterparties still rely on the legacy format, and build around those. If a counterparty is in the process of switching standards, supporting both in parallel helps verify the data’s accuracy and consistency. The principle of keeping what works and only changing what doesn’t applies beyond messaging standards. Coastal is working with Tempo to build a [cross-border payment corridor](https://tempo.xyz/customer-stories/coastal/) that leaves its proven compliance and messaging infrastructure intact while swapping out the settlement layer for stablecoin rails. ## Pair SWIFT with stablecoin payment flows on Tempo A blockchain built for stablecoin payments, Tempo is [interoperable infrastructure](https://tempo.xyz/solutions/institutional-money-movement/) that teams can connect with ACH, wires, SWIFT, and ISO 20022 workflows through payment providers and integrations. It doesn’t replace the existing infra you’re accustomed to. It makes it better. Here’s how: - [TIP-20 transfer memos](https://tempo.xyz/blog/tip20/) carry reconciliation references instead of full ISO 20022 payloads to simplify downstream reconciliation. - Tempo offers 24/7, near-instant onchain settlement and no re-orgs. Fintechs are no longer chained to banking windows but stay subject to issuer, custody, ramp, and jurisdiction constraints. - Teams working with high-volume payout or treasury workflows can process them efficiently using batch and concurrent transactions, with fewer individually submitted transactions. - Transaction fees can be covered using supported stablecoins, which cuts down on unnecessary gas-token steps for developers. - [Tokenized deposits](https://tempo.xyz/learn/tokenized-deposits/) truly blend traditional bank infrastructure and onchain settlement. [Try Tempo today](https://tempo.xyz/) to add stablecoins to your payment stack without rebuilding the rest of it. ## FAQ ### What is used for an intraday transaction report? In the legacy SWIFT MT format, intraday reporting is covered by MT942 (Interim Transaction Report). The equivalent SWIFT MX ISO 20022 message is camt.052 (Bank To Customer Account Report). ### Can one payment workflow use multiple SWIFT message types? Yes, a single payment workflow often involves multiple messages to cover each stage, such as payment and funding instructions, confirmations, and statements. ### Is MT103 only used for international payments? No. MT103 (Single Customer Credit Transfer), replaced by pacs.008 in SWIFT MX ISO 20022 for cross-border payments between banks, is primarily associated with cross-border payments. Actual usage depends on the payment setup and counterparties. --- ## Settling tokenized deposits and RWAs with stablecoin rails > Source: https://tempo.xyz/learn/tokenized-deposits/ > Language: en Tokenization is one of the most talked-about trends in blockchain tech. Whether it’s creating onchain representations of real-world assets (RWAs) or banks issuing tokenized deposits, more analysts than ever before agree this field could reshape global financial markets. For instance, a [report from CitiGroup](https://www.citigroup.com/rcs/citigpa/storage/public/Citi_Institute_GPS_Report_Tokenization_2030.pdf) suggested the current market cap for tokenized assets could rise from roughly $17 billion at the time of the report to anywhere between $2.7 trillion and $8.2 trillion by 2030. Although the excitement surrounding tokenized assets is palpable, issuers can’t neglect the need for a cash layer for their new onchain transactions to settle against. Adding this infrastructure is the only way to ensure both tokenized assets and cash finalize at the same time. As blockchain-native assets designed to maintain a stable value, stablecoins are an attractive choice for this cash leg that has potential to support the ongoing tokenization transformation. ## How do stablecoins act as the payment leg onchain? Stablecoins can provide the cash leg for RWA transfers and liquidity between approved [tokenized deposit](https://tempo.xyz/solutions/tokenized-deposits/) systems. Banks and RWA issuers create their respective tokens, while the settlement design determines how value moves between counterparties. Tokenized deposits are themselves bank money and can also serve as a cash leg. ### Stablecoin rails as the cash leg for tokenized deposits [Stablecoin rails](https://tempo.xyz/learn/what-are-stablecoins/) don’t create tokenized deposits or RWAs. Instead, issuance and tokenization take place outside of this stablecoin [payment rail](https://tempo.xyz/learn/payment-rails/), either from the bank or RWA issuer. What stablecoins offer is a secure onchain way to settle the cash leg between these digital assets. Where assets and settlement tokens are supported on a compatible network, issuers can share a payment mechanism. ### Delivery-versus-payment locks both legs Onchain delivery-versus-payment (DvP) means the asset and payment move together. Put another way, both legs of this transaction either complete together or not at all. The advantage is that there’s no lag in this transaction flow for tokens. Buyers don’t send stablecoins and wait for their tokenized asset to arrive later, nor do sellers deliver their digital assets before receiving payment. Once the transaction settles onchain, the payment leg and the token transfer complete together. ### Settlement triggers reconciliation and payouts As another benefit, stablecoin settlements for tokenized deposits or RWAs can carry structured payment references that integrations map to reconciliation records. These references help treasury, ERP, and accounting teams connect onchain settlement records to the underlying business activity. With the help of programmable logic on smart contracts, there’s also a way to automatically trigger routine distributions or reconciliation checks and the next steps for transactions. Payout logic works directly in the settlement process for everything from supplier payments to updating treasury positions, so there’s less and less need for inefficient manual intervention. ## Tokenized deposits and real-world assets settle differently Just because tokenizing an asset puts it onchain doesn’t solve how value moves between buyers and sellers. In the case of tokenized deposits and RWAs, this gets extra complicated because each token moves within distinct ecosystems. That’s why stablecoin rails have potential as a shared settlement layer that helps bring greater flexibility into tokenized transaction flows. ### Tokenized deposits settle as bank money As digital representations of funds held at [commercial banks](https://tempo.xyz/blog/tokenized-money-for-banks/), tokenized deposits remain bank liabilities subject to applicable banking regulation and issuer-defined transfer controls. In some cases, this may mean tokenized deposits only move within an institution’s permissioned chain, but they might also work on a shared network with preapproved bank partners. When buyers and sellers use the same banking network, settlement with tokenized deposits is a smooth process. The challenge comes when value needs to move between different institutions or payment protocols. Since tokenized deposits are still tied to their issuing bank, there isn’t as much flexibility to use these tokens as a universal payment method. Note that this doesn’t mean stablecoins are inherently “better” than tokenized bank deposits because they offer broader support for blockchain settlement. Stablecoin rails provide a secure and easily accessible way to settle this new form of bank deposits while still respecting their high standards for regulatory compliance and transparency. ### RWAs settle via DvP RWAs don’t follow the same rules as banks do for their tokenized deposits. Issuers can release these digital representations of other assets onchain and use stablecoins as their payment leg through DvP. In this arrangement, the buyer’s stablecoins and the seller’s RWA tokens stay in their respective accounts until both are ready to make a transaction. Once the agreed conditions are recognized onchain, the RWA and stablecoins swap at the same time. For security, neither transfer happens in cases where one or both sides don’t fulfill all of the requirements beforehand. ## Where onchain settlement stops Moving tokenized deposits and RWAs with a stablecoin settlement layer has many advantages in terms of speed and global liquidity. However, that doesn’t mean stablecoins do away with all offchain processes. There are still a few areas where the traditional financial system takes over to finalize the transaction after onchain settlement ends. Where a payment flow includes these offchain steps, they must be integrated and reconciled separately from onchain settlement: - **Fiat off-ramp is a liquidity step, not an atomic one.** Onchain settlement with stablecoins can happen instantly, but converting these stablecoins into fiat currency is an entirely different process that depends on whether there’s enough prefunded liquidity available. If there’s a funding gap between the stablecoin settlement and the available fiat, there could be a delay between when the onchain transaction finalizes and how long it takes recipients to actually see fiat appear in their bank account. - **Legal rights depend on the asset’s legal framework.** A blockchain record does not automatically establish ownership of the underlying asset. Depending on the structure, official ownership records may be maintained onchain or offchain, while custody arrangements and securities obligations still apply. ## How Tempo supports settlement for tokenized deposits and real-world assets Stablecoin rails seem to embody everything token issuers want for an onchain settlement layer. However, stablecoins by themselves aren’t necessarily the solution. If the framework backing stablecoins isn’t enterprise-ready, it doesn’t matter how fast or cheap they complete transactions. The institutions issuing tokenized deposits and RWAs need a [stablecoin payment](https://tempo.xyz/learn/stablecoin-payments/) partner that has compliance checks and reconciliation built into its model to make communication between onchain and offchain sources a simple, reliable process. Tempo designed our layer-1 blockchain to perform as a neutral stablecoin settlement layer that’s enterprise-ready for the increasingly tokenized economy. Beyond settlement-specific features like near-instant onchain settlement without re-orgs and sub-cent fees paid in stablecoins, Tempo helps partners with protocol-level controls for a regulated and reconciliation-friendly process. For example, [Tempo Zones](https://tempo.xyz/blog/introducing-tempo-zones/) are designed to offer a private institutional settlement environment with selective disclosure to keep sensitive information off the public blockchain ledger. [Tempo’s native token standard](https://tempo.xyz/blog/tip20/) also supports a 32-byte transfer memo that can carry payment references, such as invoice or customer IDs. Integrations can map those references to records in ERP and treasury systems. [Coastal Financial Corporation](https://tempo.xyz/customer-stories/coastal/) is building stablecoin-settled payment infrastructure with Tempo while keeping its compliance checks, including KYC/AML and bank confirmations, in place. Its planned corridor uses whitelisted wallets to limit participation to known financial institutions. Whether you’re curious about RWA tokenization or you already issue tokenized assets or deposits, see how Tempo could be your onchain settlement solution. ## FAQ ### Does settling onchain remove counterparty risk entirely? No. DvP helps with settlement and counterparty risk for the onchain parts of each transaction. However, there are still risks you have to manage with fiat off-ramps and all of the offchain legal or operational steps in your payment flow. ### Can Tempo issue tokenized deposits or tokenize assets? Tempo can’t act as the issuer for tokenized deposits or RWAs. However, official asset issuers could use Tempo’s token standard to create their assets and use Tempo’s settlement infrastructure for transaction processing. ### How do tokenized asset settlements reconcile with existing systems? Tokenized asset settlements can include structured payment references. Integrations can map those references to ERP, treasury, and accounting records to support automated reconciliation. ### What infrastructure exists for settling tokenized deposits and real-world assets on stablecoin rails? You need purpose-built stablecoin settlement infrastructure, complete with token standards and smart contracts, to coordinate the exchange of tokenized assets for payments. These features make it possible to include programmability and necessary features like DvP and automated reconciliation. ### What can smart contracts enforce during settlement? Smart contracts help with many aspects of the settlement process, such as enforcing business rules and compliance requirements, automating DvP, and ensuring both sides of a transaction complete together. ### What limits the full settlement of real-world assets onchain? Even though blockchains can settle transactions instantly, not every part of these transfers lives onchain. Some aspects of the payment process, such as regulatory obligations, fiat off-ramps, and legal ownership requirements, may still involve offchain processes. --- ## What are tokenized stocks? A guide for fintech teams > Source: https://tempo.xyz/learn/tokenized-stocks/ > Language: en _Tokenized stocks bring shares or exposure to shares onto a blockchain. For fintech teams, the opportunity is to connect investing with customer balances, while making ownership rights, funding, and access to proceeds clear._ For a wallet that supports stablecoin balances, adding investing creates a practical challenge. A customer needs to fund a purchase, hold the investment, and use the proceeds after selling. Each step crosses systems with their own eligibility rules, custody arrangements, and operating hours. Tokenized stocks offer another way to connect those steps. Evaluating them starts with the instrument behind the token. ## What are tokenized stocks? Tokenized stocks are blockchain-based representations of shares, interests in shares, or financial instruments linked to share prices. The term covers several structures. A familiar company ticker alone does not establish what an investor owns. |Structure|What the investor holds|What to establish| |-|-|-| |Issuer-sponsored tokenized shares|Shares issued by, or tokenized on behalf of, the company|Share-class rights and how transfers update the ownership register| |Custodial interests|An interest in shares held through a custodian or intermediary|The ownership claim, custody arrangement, and transfer or redemption terms| |Third-party exposure products|A separate instrument whose return references a stock|The token issuer's obligations, collateral, and investor rights| These distinctions reflect the [SEC staff's taxonomy of tokenized securities](https://www.sec.gov/newsroom/speeches-statements/corp-fin-statement-tokenized-securities-012826-statement-tokenized-securities). In the U.S., tokenization does not remove applicable securities-law requirements. Offers and sales must be registered or qualify for an available exemption. Backing and ownership are separate questions. [Ondo Stocks](https://ondo.finance/ondo-stocks), for example, provides economic exposure through tokens backed by the corresponding stocks or ETFs and cash in transit. Its tokens do not make holders shareholders of the referenced company or give them a right to receive the underlying shares. ## How tokenized stock settlement works When a customer buys a tokenized stock, the buyer receives the token and the seller receives payment. Where supported, [stablecoins can fund purchases and carry sale proceeds](https://tempo.xyz/learn/stablecoin-settlement/), allowing money to move onchain alongside the asset. In a compatible settlement arrangement, delivery of the asset can be conditional on payment. This is delivery versus payment. Product teams still need to distinguish a completed token transfer from completion of every obligation associated with the investment. For example, an issuer may need to acquire underlying shares or update a separate ownership register. A withdrawal to a bank account introduces another payment step. Each dependency affects when the customer can use the money, even if the onchain transfer has settled. ## What product teams need to evaluate ### Eligibility and custody Establish who can buy, hold, transfer, and redeem the instrument, and who safeguards the tokens and underlying assets. Those permissions can differ. Ondo Stocks is offered only outside the United States to eligible non-U.S. persons, with additional product and jurisdiction restrictions. Direct minting and redemption require completed onboarding. Holding a token acquired elsewhere does not establish redemption eligibility. Check [Ondo's current eligibility terms](https://docs.ondo.finance/ondo-stocks/eligibility) when defining the supported customer segment. ### Trading hours and liquidity A running blockchain does not guarantee a buyer, a narrow spread, or an open redemption window. Compare transfers, trading, minting, and redemption separately. Ondo distinguishes round-the-clock transfers from asset-specific minting and redemption schedules. Corporate actions, market conditions, and system controls can interrupt availability. Its [current operating terms](https://docs.ondo.finance/ondo-stocks/market-hours-and-trading-availability) describe these dependencies. ### Dividends and corporate actions The app should explain how dividends, splits, and other corporate actions affect a holding. Treatment varies by instrument. Ondo describes its tokens as total-return trackers: [dividends are reinvested](https://docs.ondo.finance/ondo-stocks/corporate-actions) after applicable withholding taxes. The customer receives that exposure through the token rather than a cash dividend payment. ## Test the complete customer journey Choose one supported customer segment and jurisdiction. Trace a purchase and sale from an available balance through to usable proceeds, including custody, transfers, and withdrawal. Test a closed market, a failed payment, and a corporate action. Make sure the app distinguishes the value of a holding from the amount available to spend or withdraw. This work reveals where onchain settlement simplifies the experience and where other dependencies remain. ## FAQ ### Are tokenized stocks a type of stablecoin? No. Tokenized stocks represent shares, interests in shares, or instruments linked to share prices. Their value can rise or fall with the investment. A [fiat-backed stablecoin](https://tempo.xyz/learn/what-are-stablecoins/) is designed to track a currency, although its market price and redemption value are not guaranteed. Stablecoins can serve as the payment asset when buying or selling a tokenized stock. ### Does asset backing guarantee investors can recover their money? No. Backing describes assets supporting an instrument. Recovery depends on the investor's legal claim, the custody arrangement, and the procedures that apply if an intermediary fails. Investors can also lose money when the referenced stock falls in value. ## Explore tokenized stock use cases with Tempo If you're interested in tokenized stock use cases, [get in touch](/contact/?interest=tokenized_stocks&source_article=tokenized-stocks&cta_location=article_footer). --- ## What are stablecoins? A guide for finance teams > Source: https://tempo.xyz/learn/what-are-stablecoins/ > Language: en _Stablecoins are blockchain-based digital assets pegged to fiat currencies like the US dollar, backed 1:1 by reserves of cash and government securities. For finance teams, they represent a new payment rail: one that settles instantly, operates around the clock, and costs a fraction of traditional wire transfers._ ## What are stablecoins? A stablecoin is a digital asset issued on a blockchain and designed to maintain a stable value, typically pegged 1:1 to a fiat currency such as the US dollar. Unlike volatile cryptocurrencies like Bitcoin or Ether, stablecoins combine the programmability and settlement speed of blockchain with the price stability businesses need for everyday operations. The most widely used stablecoins today, USDC (issued by Circle) and USDT (issued by Tether), are backed by reserves of cash, cash equivalents, and short-term US Treasury securities held at regulated financial institutions. Together they represent the majority of the roughly $300 billion stablecoin market. ## How stablecoins work Fully reserved fiat-backed stablecoins operate on a straightforward mint-and-burn model that keeps supply aligned with reserves: - **Minting.** A user deposits fiat currency with an issuer. The issuer mints the corresponding amount of stablecoins on-chain and sends them to the user's wallet. - **Transferring.** Stablecoins move between wallets on a blockchain in seconds, at any time of day, for negligible fees. - **Burning.** When a user redeems stablecoins for fiat, the issuer burns the tokens and returns the equivalent fiat from reserves. This model means every circulating stablecoin has a corresponding dollar (or dollar-equivalent asset) held in reserve. Major issuers publish regular attestation reports to verify this backing. ## Types of stablecoins Not all stablecoins are built the same. The three primary models differ in how they maintain their peg: ### Fiat-backed stablecoins The dominant model for enterprise use. Each token is backed 1:1 by reserves of cash and short-term government securities held at regulated financial institutions. Examples include USDC and USDT. These offer the clearest risk profile and the most straightforward regulatory treatment. ### Crypto-collateralized stablecoins Backed by other crypto assets, typically over-collateralized to absorb price volatility. MakerDAO's DAI is the best-known example. These introduce additional complexity and collateral risk that make them less common in enterprise treasury workflows. ### Algorithmic stablecoins Maintain their peg through automated supply adjustments rather than reserves. These carry the highest risk profile and have experienced notable failures. They are not suitable for enterprise payment or treasury use cases. **For enterprise finance teams, fiat-backed stablecoins are the relevant category.** The remainder of this guide focuses on reserve-backed stablecoins from regulated issuers. ## Market growth Stablecoin adoption is accelerating. The circulating supply has grown more than tenfold over the past five years, reaching roughly $300 billion today. The US Treasury projects this figure could rise to **$3 trillion by 2030**. This growth is driven by real commercial activity: cross-border payments, vendor settlement, marketplace payouts, and treasury operations. Stablecoins processed over $30 trillion in on-chain transfer volume in the past year, more than Visa and Mastercard combined. ## Why stablecoins matter for businesses For finance teams, stablecoins address specific pain points in legacy payment infrastructure: - **Instant settlement.** Transactions finalize in seconds, not days. No more waiting for T+1 ACH batches or 3–5 day SWIFT transfers. - **24/7 operations.** Blockchain networks never close. Settle vendor payments on a Saturday. Fund a subsidiary at midnight. No banking-hours constraints. - **Low cost.** On-chain transaction fees are typically sub-cent, compared to $15–$45 for international wires and $3–$5 for domestic wires. - **Programmable money.** Smart contracts can automate payment logic (escrow, conditional releases, automated sweeps), replacing manual processes and custom bank integrations. - **Full traceability.** Every transaction is recorded on an immutable ledger, simplifying reconciliation and audit trails. - **Global reach.** A single stablecoin transfer works the same whether the recipient is across town or across the world, with no correspondent banking chain. To see how stablecoins compare directly against ACH, wires, and SWIFT, read our [payment rails comparison](/learn/payment-rails). ## The regulatory landscape Stablecoin regulation is maturing rapidly, giving enterprises greater confidence to adopt: - **United States.** The GENIUS Act establishes a federal framework for stablecoin issuance, including reserve requirements, disclosure standards, and issuer licensing. Banks can now offer stablecoin services within existing regulatory structures. - **European Union.** The Markets in Crypto-Assets (MiCA) regulation sets comprehensive requirements for stablecoin issuers operating in the EU, including reserve mandates and consumer protections. - **Global convergence.** Jurisdictions from Singapore to the UAE are implementing their own stablecoin frameworks, creating a clearer operating environment for cross-border use. Regulatory clarity is a significant driver of enterprise adoption. As frameworks mature, the compliance and legal barriers that previously slowed institutional use are diminishing. ## Stablecoins on Tempo Tempo is a blockchain purpose-built for stablecoin payments. Key features for enterprise teams: - **Stablecoin-native fees.** Pay transaction fees in stablecoins, with no volatile gas tokens on your balance sheet. Read more in [Stablecoin Fees on Tempo](/blog/stablecoin-fees). - **TIP-20 token standard.** Tempo's native token standard includes transfer memos for reconciliation, built-in compliance controls, and reward distribution. - **Sub-second finality.** Transactions finalize in under a second with predictable, low fees. - **Compliance controls.** Built-in mechanisms for freeze, seize, and allowlist operations that enterprises and regulated issuers require. For enterprise finance teams, this means a single network that handles fees, compliance, reconciliation, and settlement without requiring volatile token management or multiple vendor integrations. Explore the [Tempo ecosystem](/ecosystem) to see infrastructure partners already building on Tempo, or [contact our enterprise team](/contact) to discuss your use case. ## Why this matters for finance teams Stablecoins are a payment instrument that settles faster, costs less, and operates more transparently than legacy rails. Finance teams evaluating stablecoins should focus on reserve quality, issuer regulation, and infrastructure maturity rather than market hype. The business case is straightforward: lower payment costs, faster settlement, fewer intermediaries, and 24/7 availability. With regulatory frameworks now in place, the operational and compliance barriers to adoption are lower than they have ever been. **Next steps:** - Learn [how stablecoin payments work](/learn/stablecoin-payments) end-to-end - Compare [ACH, wires, SWIFT, and stablecoins](/learn/payment-rails) side by side - Explore [cross-border payments with stablecoins](/learn/cross-border-payments) - [Talk to our team](/contact) about a pilot --- ## Frequently asked questions **What is a stablecoin?** A stablecoin is a blockchain-based digital asset designed to maintain a stable value, typically pegged 1:1 to a fiat currency like the US dollar. Issuers hold reserves of cash and short-term government securities to back each token. This makes stablecoins practical for payments, settlement, and treasury operations that require predictable amounts. **Are stablecoins safe?** Safety depends on the issuer's reserve composition, redemption terms, and regulatory status. Major USD stablecoins like USDC and USDT publish regular reserve attestations. The frequency, detail, and regulatory regime vary by issuer and jurisdiction. Evaluate each issuer's disclosures, audit frequency, and licensing before use. **How are stablecoins different from crypto?** Stablecoins maintain a fixed value pegged to fiat currency, while cryptocurrencies like Bitcoin and Ether fluctuate based on market demand. This price stability makes stablecoins practical for payments, payroll, and treasury operations. Most enterprises use fiat-backed stablecoins from regulated issuers, not volatile crypto assets. **What are stablecoins used for?** Businesses use stablecoins for cross-border payments, vendor settlement, global payouts, payroll, treasury management, and remittances. They settle in seconds, operate 24/7, and cost a fraction of traditional wire transfers. Read about specific [stablecoin payment use cases](/learn/stablecoin-payments). **How do I get stablecoins?** Businesses typically acquire stablecoins through regulated exchanges, direct onboarding with issuers like Circle or Tether, or payment providers that support stablecoin on-ramps. Enterprise teams often use licensed custodians for custody and settlement. Orchestration platforms like Tempo simplify the process by handling conversion and routing. **Are stablecoins regulated?** Regulation varies by jurisdiction and is evolving rapidly. The US GENIUS Act and the EU's MiCA framework establish reserve, disclosure, and licensing requirements for stablecoin issuers. Confirm the rules that apply to your entity, counterparties, and operating geographies before adoption. --- ## How much are wire transfer fees? > Source: https://tempo.xyz/learn/wire-transfer-fees/ > Language: en _International wire transfer fees include more than the sending bank's headline charge. Businesses also need to account for receiving-bank deductions, correspondent-bank charges, FX spread, settlement delays, and reconciliation work. For a broader comparison of payment rails, see Tempo's guide to [ACH, wires, and stablecoins](/blog/ach-vs-wire-vs-stablecoins-a-guide-for-finance-teams/)._ Businesses often treat international wire transfer fees as a single charge listed by their bank. In practice, moving money across borders can also include recipient deductions, currency conversion costs, and correspondent-bank fees. Senders and recipients may both absorb these costs. For finance teams, the goal is to understand the total cost of a payment: the visible fees, the effective exchange rate, the settlement timeline, and the operational work required to track and reconcile the transfer. ## How international wire transfers work International wire transfers move funds across borders through a network of financial institutions. ### What happens when a business sends an international transfer? A business starts an international wire by submitting payment instructions to its bank. The bank checks the details and sends the payment message to the recipient's bank. If the two banks have a direct relationship in the relevant currency, the payment can move more directly. If they do not, one or more correspondent banks route the funds. The recipient's bank credits the final account after its internal checks. ### Why correspondent banking exists Correspondent banks act as intermediaries between financial institutions. They give banks access to markets where they do not operate directly. For example, a U.S.-based bank can send funds through a correspondent bank to reach a financial institution in Brazil. Each bank involved can apply fees or deductions. That means the final cost depends on the full payment path, not only the sender's bank fee. ## The visible costs of an international wire transfer |Cost category|Where it appears|Definition|Business impact| |-|-|-|-| |Sending bank fee|The sender's bank|The headline fee most teams see first|Easiest to plan for| |Receiving bank fee|The recipient's bank|The cost recipients may pay to receive funds|Can reduce the amount credited| |Correspondent bank charge|An intermediary bank|The cost of routing funds across institutions|Can create deductions the sender may not see upfront| |Foreign exchange (FX) spread|The bank or provider converting currency|The difference between the mid-market exchange rate and the offered rate|Can exceed the visible transfer fee on larger payments| ### Sending bank fees The sending bank usually charges a flat fee to initiate an international wire. Finance teams may see this charge in a treasury portal, fee schedule, or monthly statement. ### Receiving bank fees The receiving bank may charge the recipient to accept the incoming wire. This fee can reduce the credited amount even when the sender paid the sending bank fee. ### Correspondent bank charges Intermediary banks may charge for helping route the payment. The sender may not know or choose the exact path the money takes, so these charges can vary by corridor, currency, and bank relationship. ### FX spread An FX spread is the difference between the mid-market exchange rate and the rate a bank or provider offers during currency conversion. The offered rate includes a margin that can grow with payment size. ### Why FX spreads are often larger than wire fees A transfer fee is visible and usually fixed. The FX spread is tied to the exchange rate and scales with the size of the payment. For example, a $10 transfer fee on a $10,000 payment appears small. But if the provider applies a 2% FX spread, the cost of conversion is $200. On a $100,000 payment, the same 2% spread becomes $2,000. That is why finance teams evaluate the effective exchange rate, not just the upfront wire fee. ### How FX costs affect global payout programs FX costs become more material when businesses repeat the same payout flow across many recipients and markets. A small spread on one payment may look manageable. The same spread across thousands of contractor payouts or marketplace settlements can materially change the total cost of the program. When conversion costs vary by currency, corridor, or provider, treasury teams also lose predictability. ## The hidden costs most businesses overlook International wires include obvious fees, but less visible costs can also affect finance operations. |Hidden cost|What creates it|Business impact| |-|-|-| |Settlement delay|Cutoffs, routing, local banking days, and reviews|Cash flow uncertainty| |Payment exceptions|Missing or incorrect beneficiary details|Manual investigation| |Limited visibility|Fragmented status updates across institutions|More support requests| |Reconciliation gaps|Missing references or inconsistent formats|Slower accounting close| ### Settlement delays International wire speed depends on banking cutoffs, local operating days, routing, and review processes. These delays can create issues when vendors or recipients expect funds by a specific deadline. ### Payment investigations and exceptions Returned payments or missing beneficiary information often create manual repair work. Each exception adds time and increases the cost per completed payout. ### Limited payment visibility Many businesses know when they sent a payment, but have limited visibility between initiation and receipt. That gap can make it harder to confirm when obligations have been settled. ### Reconciliation overhead Payments are easier to reconcile when references travel with the funds. Tempo's [transfer memos](/blog/tip20/) let teams attach payment references, invoice IDs, or transaction notes to stablecoin transfers. Tempo also supports [virtual addresses for invoice-level reconciliation](/blog/new-features-for-enterprise-payments/), which can help teams attribute inbound payments to customers, invoices, or platform records. ## Why businesses should think beyond transaction fees A wire fee shows only the cost to initiate a payment. Companies also spend time tracking status, resolving exceptions, managing FX, and reconciling each payout. Reporting and compliance obligations vary by payment type, corridor, amount, parties, and business model. Teams should confirm applicable requirements with their legal, tax, and compliance advisors. ### Predictability can be more valuable than lower fees Many businesses value predictable cash flow and fewer manual reconciliations as much as lower headline fees. Unclear timelines and reference errors can create more disruption than the transfer charge itself. ### Payment infrastructure decisions compound at scale A team can usually manage a small number of annual payments with manual checks. As volume grows to hundreds or thousands of payments, manual processes become slower, less predictable, and more error-prone. ## What modern payment infrastructure is optimizing for Modern payment infrastructure is designed to make global transactions faster, clearer, and easier to reconcile. ### More predictable settlement [Stablecoin payment infrastructure](/learn/stablecoin-payments/) can provide faster confirmations and clearer network fees than traditional cross-border wires. On Tempo, stablecoin transfers are designed for low, predictable network costs and fast settlement. Funding, off-ramp, and local-currency conversion costs still depend on providers, corridors, and recipient preferences. ### Better payment transparency Payment transparency, including the visibility available through [blockchain payment systems](/learn/blockchain-payments/), helps teams track transactions from initiation through settlement. A shared payment record can reduce status ambiguity and support cleaner downstream operations. ### Reconciliation-ready payments Payments become easier to match when structured references travel with the funds. Tempo's [native token standard](/developers/docs/protocol/tip20/overview/#transfer-memos) supports short transfer memos for references such as invoice IDs, customer IDs, cost centers, or transaction notes. This helps connect stablecoin settlements to existing payment engines and finance systems. ### Programmable payment workflows Programmable workflows let applications define when and how payments execute. [Tempo Transactions](/blog/tempo-transactions/) support capabilities such as batch transactions, scheduled transactions, configurable fee tokens, fee sponsorship, and access keys. These features can support payout runs, recurring payments, and approved automated payment flows within predefined authorization rules. ## Ways to evaluate and reduce wire transfer costs To reduce international wire transfer costs, finance teams need to look beyond each standalone bank fee and identify where costs repeat or where payments get stuck. Practical steps include: - **Consolidating payout volume:** Group payments by corridor or payout cycle when the business model allows it. Higher volume may make pricing easier to negotiate and reduce one-off processing work. - **Reducing unnecessary currency conversions:** Review when funds actually need to convert. In some flows, stablecoin settlement can reduce intermediary and FX steps, especially when the recipient can accept a dollar-denominated stablecoin or when a provider handles conversion. - **Improving payment data quality:** Accurate beneficiary and reference data can reduce payment repair work and manual review. - **Optimizing payout corridors:** Review each route before choosing a payment method. Depending on the market, local rails, stablecoin settlement, or partner-supported orchestration may reduce cost or delay compared with a standard wire. |Payout approach|Cost pattern|Impact on global payout programs| |-|-|-| |International wire|Sending fees, receiving fees, FX spreads, correspondent-bank charges|Familiar bank-to-bank flow, but cost and delivery amounts can vary by route| |Domestic wire transfer|Corridor-specific pricing and local settlement rules|Can reduce cost in supported markets, but may require different setups by region| |Stablecoin-native payment infrastructure|Predictable network fees, plus any funding, off-ramp, or conversion costs|Supports fast settlement, programmable workflows, structured metadata, and easier reconciliation when integrated with internal systems| ## Payment cost is an infrastructure decision International wire transfers can cost more than the listed bank fee. FX spreads can exceed the visible transfer fee, correspondent-bank charges can lower the final payout, and operational work can add cost when teams investigate delays or reconcile incomplete records. Payment costs still shape decisions, especially for businesses moving money across markets at scale. But the more useful comparison is total cost: fees, FX, settlement time, visibility, exception handling, and reconciliation. Tempo's [cross-border payments resources](/solutions/cross-border-payments/) explain how businesses can use stablecoin-native infrastructure for faster settlement, predictable network fees, and reconciliation-ready payment workflows. --- ## Meet Tempo at Money 20/20 2026 > Source: https://tempo.xyz/money2020/ > Language: en # Meet Tempo at Money 20/20 Request a meeting with Tempo at Money 20/20. Our team will follow up by email to arrange a time. Provide your first name, last name, work email address, company name, company website, and interest. All fields are required. [Request a meeting](/money2020/) We’ll use these details to follow up on your meeting request. [Privacy Policy](/privacy-policy/) --- ## Open USD (OUSD) on Tempo > Source: https://tempo.xyz/ousd/ > Language: en # OUSD on Tempo Open USD (OUSD) is live on Tempo, with $500M+ in liquidity for enterprise payments. Issued natively on Tempo, OUSD gives businesses a new stablecoin for payments, settlement, and treasury, with liquidity deployed across decentralized exchanges, stablecoin swaps, and bridges. ## $500M+: Liquidity for OUSD Across decentralized exchanges, stablecoin swaps, and bridges. ## Native: Issued on Tempo OUSD is issued natively on Tempo, a network built for payments. ## Access: Mint and burn Available via Coinbase, Stripe, Visa, and soon Mastercard. [View live reserves](https://ousd.fyi/) ## Put OUSD to work across payments and treasury ### Privacy Keep balances and payment activity out of public view with opt-in privacy through Tempo Zones. Authorized parties retain defined access. Mainnet deposits and withdrawals remain visible. ### Earn Create revenue streams by letting users earn on existing balances, with control over reward splits. OUSD support for Tempo Earn is coming soon. ### Stablecoin swaps Swap OUSD into supported stablecoins on Tempo. We are working to connect more currencies, liquidity providers, and ramps so businesses can collect in one currency and pay out in another with fewer integrations. ## Featured providers Mint and burn OUSD on Tempo at no cost. ### [Stripe](https://docs.stripe.com/ousd) Hold OUSD balances and send payouts through supported Stripe products. ### [Coinbase](https://www.coinbase.com/) Mint and burn ### [Visa (VSP)](https://www.visa.com/en-us/products/visa-stablecoin-platform) Limited availability. Eligibility applies. ### [Mastercard](https://form.mastercard.com/jfe/form/SV_9uxcX9XTu2H5cSq) Orchestration Coming soon ## Connect to the OUSD ecosystem on Tempo Connect ramps, wallets, custody, and payment infrastructure for your business. ## Wallets & Custody ### [Anchorage Digital](https://www.anchorage.com/) Custody ### [Blockradar](https://blockradar.co/) Wallet infrastructure ### [Crossmint](https://crossmint.com/) Wallet infrastructure ### [Fireblocks](https://fireblocks.com/) Wallet infrastructure ### [Privy](https://docs.stripe.com/ousd) Wallet infrastructure ### [Utila](https://utila.io/) Wallet infrastructure ## Orchestration & Ramps ### [Blindpay](https://blindpay.com/) On and off ramps ### [Bridge](https://docs.stripe.com/ousd) Orchestration ### [Coinbase](https://www.coinbase.com/) Mint and burn ### [Fonbnk](https://fonbnk.com/) On and off ramps ### [Infinia](https://www.infinia.xyz/) Payment infrastructure ### [Mastercard](https://form.mastercard.com/jfe/form/SV_9uxcX9XTu2H5cSq) Orchestration Coming soon ### [Relay](https://relay.link/) Crosschain routing ### [Stripe](https://docs.stripe.com/ousd) Hold OUSD balances and send payouts through supported Stripe products. ### [Visa (VSP)](https://www.visa.com/en-us/products/visa-stablecoin-platform) Limited availability. Eligibility applies. ## Security & Compliance ### [Blockaid](https://blockaid.io/) Security ### [Chainalysis](https://chainalysis.com/) Compliance ### [Elliptic](https://elliptic.co/) Compliance ### [Hypernative](https://www.hypernative.io/) Monitoring ### [TRM Labs](https://trmlabs.com/) Compliance ## Liquidity, swaps, and oracles ### [Chainlink](https://docs.chain.link/data-feeds/price-feeds/addresses?network=tempo) Oracle infrastructure ### [Uniswap](https://developers.uniswap.org/docs/trading/overview) Swaps through the API ## DeFi ### [Morpho](https://app.morpho.org/tempo/vault/0x0D136e26B4D9e4836fc5cb202baeb49Cb6f5df48/sentora-ousd-main) Lending ### [Sentora](https://app.morpho.org/tempo/vault/0x0D136e26B4D9e4836fc5cb202baeb49Cb6f5df48/sentora-ousd-main) Vaults ### [Aave](https://aave.com/) Lending Coming soon ### [Figure](https://www.figuremarkets.com/c/ylds/) Tokenized assets Coming soon ### [Gauntlet](https://www.gauntlet.xyz/) DeFi and earn Coming soon [Explore the full Tempo ecosystem](/ecosystem/) ## Move money around the clock with OUSD Move OUSD across payments, payouts, and treasury with near-instant onchain settlement and sub-cent network fees. [Talk with our team](/contact/) [Integrate OUSD on Tempo](https://docs.tempo.xyz/) [Testnet faucet](/developers/docs/quickstart/faucet) [View OUSD reserves](https://ousd.fyi/) --- ## Skontaktuj się z Tempo > Source: https://tempo.xyz/pl/contact/ > Language: pl # Skontaktuj się z nami Opowiedz nam trochę o sobie i o tym, co tworzysz. Pomożemy Ci odkryć, jak Tempo może przyspieszyć rozwój Twojej infrastruktury płatniczej. Jeżeli potrzebujesz wsparcia lub pomocy technicznej skontaktuj się z nami pod adresem [support@tempo.xyz](mailto:support@tempo.xyz). W sprawach prasowych skontaktuj się z nami pod adresem [press@tempo.xyz](mailto:press@tempo.xyz). > Interactive contact form is available on the HTML page. --- ## Website Privacy Policy | Tempo > Source: https://tempo.xyz/privacy-policy/ > Language: en # Tempo Privacy Policy Last Updated: July 31, 2026 This Privacy Policy (the “Privacy Policy” or “Policy”) describes the types of information Tempo Labs Inc. dba Tempo and its affiliates (“Tempo,” “we,” “our,” or “us”) collects and processes from and about you when you use our website or any other online services we make available (collectively, the “Services”). By using the Services, you are agreeing to the practices described in this Privacy Policy. If you do not agree to the practices described in this Privacy Policy, please do not access or use the Services. ## Information We Collect We collect information about you when you use our Services. The types of information we collect depend on how you use our Services. We need certain types of information to provide the Services to you. If you do not provide us with such information, or if you ask us to delete that information, you may no longer be able to access or use certain Services. The information we collect may include data you directly provide to us, data we obtain automatically from your interactions with our Services, and data we obtain from other sources. ### Information You Provide Directly to Us We may collect information directly from you when you use the Services, including when you communicate with us or use our Services. The types of information we may collect from you directly include: (1) name; (2) employer/associated entity; (3) wallet address; (4) email address; (5) phone number; (6) information in communications with us; and (7) information related to requests and transactions you make on Tempo. ### Information We Collect Automatically We or our third-party vendors may also collect certain information about your use of the Services and the devices you use to access the Services, including through cookies and other tracking technologies. This information may include your IP address, browser types, browser language, operating system, the state or country from which you accessed the Services, software and hardware attributes (including device IDs), referring and exit pages and URLs, platform type, the number of clicks, files you download, domain names, landing pages, pages viewed and the order of those pages, the amount of time spent on particular pages, the terms you use in searches on our sites, the date and time you used the Services, error logs, and other similar information. You can choose to accept or decline cookies. Most web browsers automatically accept cookies, but your browser may allow you to modify your browser settings to decline cookies if you prefer. If you disable cookies, you may be prevented from taking full advantage of the Services, because the Services may not function properly. As we adopt additional technologies, we may also gather additional information through other methods. ### Information We Collect from Other Sources When you submit transactions to a blockchain network through the Services, your wallet address, transaction amounts, and other transaction data are permanently and publicly recorded on that blockchain network. This data is not controlled by Tempo and cannot be modified, hidden, or deleted by Tempo or by you. Your rights to access, correction, and deletion described in this Policy apply only to information controlled by Tempo and do not extend to data recorded on public blockchain networks. We may also collect information about you from other parties. For example, we may collect information when you communicate with us on third-party platforms, such as Telegram and X. We may combine information that we collect through the Services with information that we obtain from other parties and information derived from other products or services we provide. ## How We Use Your Information We may use your information to: - Provide the Services. - Administer and troubleshoot the Services. - Personalize and improve the Services. - Analyze, improve, modify, customize, and measure the Services. - Provide support, and otherwise to respond to your comments, questions, and requests. - Communicate with you about Tempo’s products, experiments, services, surveys, events, content, and other news and information we think may be of interest to you. - Comply with our legal obligations or as permitted by law. - Protect the safety and/or integrity of our users, employees, third parties, members of the public, and/or our Services, including to prevent, detect, investigate, and respond to fraud, unauthorized access/use of the Services, breaches of terms and policies, or other wrongful behavior. - Enforce any terms of use and any other agreements between you (or your employer/associated entity) and Tempo. - As directed by you and/or to carry out any other purpose disclosed to you at or before the time of collection. We may combine information that we collect from you through the Services with information that we obtain from other sources. We may also aggregate and/or de-identify information collected through the Services. We may use and disclose de-identified or aggregated data for any purpose, including without limitation for research and marketing purposes. ## When We Disclose Your Information We may disclose your information for various reasons as described below. - **Vendors.** We may disclose your information to employees, consultants, and other vendors who need access to such information to carry out work or perform services on our behalf, such as those who provide data storage, payment, technology support and services, customer service, analytics, fraud prevention, legal services, and marketing services. - **Affiliates.** We may disclose your information to our affiliates. - **Safety and Law Enforcement.** We may need to disclose or provide access to information if Tempo has a good faith belief that such action is necessary to (i) comply with the law; (ii) comply with legal processes or governmental requests; (iii) prevent, investigate, detect, or prosecute criminal offenses or attacks on the technical integrity of our website or our network; and/or (iv) to protect the rights, property, safety and security of Tempo, our employees, our users, and/or the public. - **Business Transactions.** We may disclose your information in connection with, or during negotiations of, any merger, acquisition, sale of assets or any business, other change of control transaction or financing; between any future parent, subsidiary, and/or affiliated company. - **At Your Direction/Consent.** We may disclose your information as otherwise permitted or required by law or as authorized by you. - **Aggregate/De-Identified Information.** We reserve the right to create aggregate/de-identified data from the information we collect through the Services and our disclosure of such aggregate/de-identified data is at our discretion. ## Analytics We may use third-party web analytics services on the Services, such as PostHog. These service providers use the sort of technology described in the “Information we collect automatically” section above to help us analyze how users use the Services, including by noting the third-party website from which you arrive. The information collected by the technology will be disclosed to or collected directly by these service providers, who use the information to evaluate your use of the Services. ## Do Not Track Statement Our website does not respond differently or limit its practices under the terms of this Policy when you access our site with a browser that uses a do not track signal. ## Third-Party Websites or Services Tempo may maintain links or access to other websites or services and other websites may maintain links to the Services. This Privacy Policy applies only to the Services and not to other websites or services accessible from Tempo or that you use to access Tempo, each of which may have privacy policies materially different from this Privacy Policy. If you visit other websites or use other services, directly or through any software, automated system, smart contract, artificial intelligence model, machine learning model, or AI agent (“AI Systems”), Tempo is not responsible for the privacy practices or content of those sites or services. It is your responsibility to review the privacy policies of non-Tempo websites and services to confirm that you understand and agree with them. ## Your Choices - **Cookies.** Most web browsers are set to accept cookies by default. If you prefer, you can usually choose to set your browser to remove or reject browser cookies. The method for disabling cookies may vary by device and browser, but can usually be found in your device or browser preferences or security settings. If you choose to remove or reject cookies, this could affect the availability and functionality of the Services. - **Marketing Emails.** You may opt out of receiving marketing emails from us by following the instructions in those marketing emails. If you choose to opt out, we will still send you non-marketing communications, such as those about your account or our ongoing business relations. ## Your Privacy Rights Depending on your location, you may have certain rights regarding your personal information. These may include the right to: - Access the personal information we hold about you. - Correct inaccurate or incomplete personal information. - Delete your personal information, subject to certain exceptions. - Receive a copy of your personal information in a portable format. - Object to or restrict certain processing of your personal information. - Withdraw consent where we rely on your consent to process your information. - Opt out of the sale or sharing of your personal information for cross-context behavioral advertising (Tempo does not engage in this practice). - Not be discriminated against for exercising your rights. To exercise any of these rights, please contact us at [support@tempo.xyz](mailto:support@tempo.xyz). We may need to verify your identity before processing your request and will respond within the timeframe required by applicable law. You also have the right to lodge a complaint with a data protection authority in your jurisdiction if you believe your rights have been violated. Please note that information recorded on public blockchain networks cannot be modified or deleted by Tempo, and these rights do not extend to such data. ## Data Security We maintain administrative, technical, and physical safeguards that are designed to protect the privacy and security of personal information. However, the internet and blockchains are not a fully secure environment, and we cannot ensure or warrant the security of any information transmitted to or generated by Tempo in connection with the Services or any other service offered by Tempo. ## Data Retention We retain your personal information for as long as necessary to provide the Services, fulfill the purposes described in this Policy, and comply with our legal obligations. The specific retention period depends on the type of information and the purpose for which it was collected. When your information is no longer needed, we will delete or anonymize it in accordance with applicable law. As a reminder, information recorded on public blockchain networks is permanent and cannot be deleted by Tempo or by you, regardless of any retention period that would otherwise apply. ## Personal Information of Children The Services and Tempo’s other services are not directed to individuals under the age of 18 (“Minors”). We do not knowingly solicit or collect personal information about Minors. If you are a parent or guardian and you learn that your Minor has provided us with personal information, please contact us. If we discover that a Minor has provided us with personal information, we will delete such information if required by applicable law. ## Notice to California Residents – Shine the Light Under California Civil Code Section 1798.83 (also known as the “Shine the Light” law), users who are residents of California may request information regarding the disclosure of their personal information by us to third parties for the third parties’ direct marketing purposes. ## Notice to Persons Located Outside the United States – Data Transfer If you are located in the European Economic Area, United Kingdom, or other regions with data protection laws, please note that we may transfer your personal information to countries outside your jurisdiction, including the United States, that may not provide the same level of data protection as your home country. Where required by applicable law, we implement appropriate safeguards for such transfers, including Standard Contractual Clauses approved by the European Commission and, where applicable, reliance on the EU-U.S. Data Privacy Framework or other lawful transfer mechanisms. We also implement appropriate technical and organizational measures to protect your personal information. You may contact us for additional information about these safeguards. ## Legal Basis for Processing – EEA and UK Users For users in the European Economic Area or the United Kingdom, we process personal information on the following legal bases: - **Contract Performance:** to provide the Services you have requested, process transactions, and manage your access to the Services. - **Legitimate Interests:** to improve and personalize the Services, conduct analytics, prevent fraud, and ensure the security of the Services, where our interests are not overridden by your rights. - **Legal Obligation:** to comply with applicable laws, regulations, and legal processes. - **Consent:** for specific activities such as marketing communications. You may withdraw consent at any time by contacting us at [support@tempo.xyz](mailto:support@tempo.xyz) or following the opt-out instructions in any marketing communication. Withdrawal does not affect the lawfulness of processing carried out prior to withdrawal. ## Changes to the Privacy Policy We may change this Policy to reflect changes in the law, our information practices, or the features of the Services. At the top of our Policy, we will indicate the date of the most recent update. If we make a material change to the Policy, you will be provided with appropriate notice in accordance with legal requirements. By continuing to use the Services, you are confirming that you have read and understood the latest version of this Policy. ## Contact Us If you have questions or concerns regarding this Privacy Policy, you should contact us by email at [support@tempo.xyz](mailto:support@tempo.xyz). --- ## Receive Policies | Tempo > Source: https://tempo.xyz/product/receive-policies/ > Language: en # Control what accounts receive Receive policies let accounts specify which tokens and senders they accept. When a transfer does not match the policy, funds are held by Tempo's protocol guard with a receipt, so the designated authority can recover them. ## Accepted tokens Accept only the stablecoins a wallet, deposit address, or payment flow supports. ## Accepted senders Limit inbound transfers to approved counterparties before funds enter the account. ## Recovery authority Designate who can recover funds when a transfer does not match the policy. > Interactive receive policy demo flow is available on the HTML page. [Integrate receive policies](https://tempo.xyz/developers/docs/guide/payments/configure-receive-policies) [Contact us](/contact/) --- ## Creating More Liquidity in Markets: Why the next generation of market infrastructure has to get the trade-offs right > Source: https://tempo.xyz/report/creating-more-liquidity-mobility-in-markets/ > Language: en # Creating More Liquidity in Markets: Why the next generation of market infrastructure has to get the trade-offs right A market-structure report on why liquidity mobility should be the primary lens for evaluating tokenized settlement infrastructure. **For:** FMIs, bank strategists, market infrastructure teams, and institutional settlement leaders ## A mobility-first frame for institutional settlement The report argues that speed and privacy are table stakes, while liquidity mobility is the variable that determines whether tokenized infrastructure unlocks value or recreates market silos. - How legacy market infrastructure trapped and released liquidity - Why public chains proved mobility but fragmented liquidity - How private-chain silos bought privacy at the cost of mobility - Why shared settlement with private execution can balance all three ## Key metrics - **$120B** — Annual cost attributed to trapped liquidity, fees, and delays - **$25.5T** — Assets estimated to sit idle as deadweight capital - **$385B** — Average daily repo volume in a major private DLT example ## Read the report - [Report landing page](/report/creating-more-liquidity-mobility-in-markets) - [Download the PDF](/reports/creating-more-liquidity-mobility-in-markets.pdf) - [Open the reader](/report/creating-more-liquidity-mobility-in-markets/print) --- ### **_Thesis_** _Liquidity mobility is the critical variable to judge tokenized infrastructure on. Speed and privacy are the enabling support. Architectures that collapse mobility to optimize for one of the other two are re-creating the same fragmentation problem that DLT was supposed to solve. This piece explores the balance required to deliver the maximum value to market participants._ ## Creating More Liquidity Mobility in Markets ### Why the next generation of market infrastructure has to get the trade-offs right **Executive summary** Every generation of market infrastructure gets built in response to a similar problem: liquidity gets trapped. It is trapped in nostro accounts, trapped behind operating hours, trapped inside one asset class, trapped on the wrong venue at the wrong moment. Market structures like CLS, RTGS systems, tri-party repo, central clearing were all fixes for a specific instance of trapping that succeeded. However, in aggregate, the general problem remains unsolved across venues. The original promise of blockchains was to enable the mobility of collateral. A shared ledger with atomic settlement, programmable assets, cash, and collateral on the same substrate could move liquidity where it's needed, when it's needed, instantly. The public-chain world has delivered a partial version of this promise. You can arbitrage across venues in minutes. You can route a payment through three chains and two stablecoins in one transaction. There are, however, drawbacks, such as bridging, which creates new risks, and liquidity fragmentation across those chains. But the mobility does work, sometimes too well (as seen during times of stress and deleveraging). The private-chain world has delivered mostly siloed ledgers built around a single market. These solutions solved for privacy as their primary constraint and produced enormous throughput but the liquidity once again became trapped. The cash leg is usually an afterthought. Synchronization between environments is bolted on rather than native. The result is a very fast, very private, very trapped pool. This essay argues that the primary frame for evaluating the next generation of settlement infrastructure is liquidity mobility — the ability for cash and collateral to move across venues, institutions, and use cases without rebuilding trust at every hop. Speed and privacy matter. They are table stakes. But they have been delivered at the cost of liquidity mobility. Modern blockchains can now deliver all three. ### Liquidity always gets trapped Pick any era of market infrastructure and the story rhymes. During the late 1960s paperwork crisis, trades still settled on physical stock certificates that had to be moved between firms by clerks, reconciled by hand, and signed off in triplicate. As volumes climbed past the system's capacity, the NYSE began closing on Wednesdays so firms could catch up on the paperwork. During this time, dozens of brokerages went under because they could not track their assets. The fix that eventually emerged, the DTC, was a central depository that immobilized certificates. This freed the liquidity that had been trapped inside the choreography of moving paper from one vault to another. Two decades later, the trap moved into FX. Because banks settled the two legs of a currency trade hours apart and across time zones, the system had a structural exposure that finally crystallized when Bankhaus Herstatt was wound up by German regulators on a Wednesday afternoon in June 1974\. The core issue was a liquidity timing mismatch. The bank had received Deutsche Mark payments from its counterparties that morning, but its New York correspondent had not yet released the matching dollars. Counterparties were left holding nothing on one leg of trades they had already paid for on the other. CLS arrived in 2002 to close that gap for the major currency pairs by imposing a payment-versus-payment settlement window and a central counterparty, and within a few years, it had largely succeeded. The trap closed for those pairs. It quietly stayed open everywhere else, including weekends, holidays, and any currency that didn't make it into the CLS cohort. The 2000s gave the same dynamic another form in tri-party repo. Collateral was tied up in bilateral relationships and couldn't be efficiently reused across counterparties without the clearing bank intermediating every move, which meant a security pledged to one lender on Monday couldn't easily be redeployed against a different counterparty on Tuesday. Tri-party solved the intermediation problem and the operational drag that came with it. What it didn't solve — and arguably wasn't trying to — was the deeper issue: collateral sitting inside one silo still couldn't migrate to another without manual choreography between custodians. The pattern is so consistent that it should probably be treated as the fundamental problem of market infrastructure rather than a series of separate crises. Cash sits in the wrong place. Collateral is pledged to one counterparty when another counterparty needs it more. Margin requirements across venues can't be netted because the venues don't talk to each other. We waste $120B yearly on fees and delays linked to trapped liquidity ([Oliver Wyman](https://www.google.com/search?q=https://www.oliverwyman.com/our-expertise/insights/2021/sep/unlocking-120-billion-in-cross-border-payments.html), 2021). $25.5T in assets sits idle as deadweight capital not being put to productive use ([GFMA](https://www.google.com/search?q=https://www.gfma.org/policies-resources/gfma-and-bcg-report-on-global-collateral-management/), 2024). Moving to T+1 would free 41% of the "safety cash" banks must lock up as insurance in the US alone ([DTCC](https://www.google.com/search?q=https://www.dtcc.com/dtcc-connection/articles/2024/january/23/t1-settlement-is-coming), 2024). Now scale this out to globally, and across all venues. This trapped liquidity is a tax on the world; it is capital frozen by legacy infrastructure that fuels the global economy when freed. Every solution to trapped liquidity in one place has pushed the trap somewhere else. DLT's original promise was that a shared ledger could finally end the game. Not by closing one trap faster than the next opens, but by making the underlying architecture mobile by default. ### The public-chain proof of concept Whatever one thinks of crypto, the empirical observation is hard to argue with. On public chains, liquidity moves. A trader on Arbitrum can route funds to Base, swap into a different stablecoin, and deploy into a yield strategy on Solana inside a single coffee break. The infrastructure is still early and somewhat unreliable. Bridges have been hacked for billions, as seen in the [$292m KelpDAO exploit](https://www.coindesk.com/tech/2026/05/09/layerzero-says-it-made-a-mistake-in-usd292-million-kelp-exploit). Cross-chain messaging has variable finality depending on the receiving ledger's nature. And the practice of bridges “wrapping” tokens (by locking them on one chain and minting them on another) fragments the canonical version of the same asset. Researchers writing about L2 fragmentation are not wrong; over twenty active L2s collectively secure nearly $40 billion in TVL, with capital and users dispersed across isolated environments.\[^1\] With all of that said, a user on a public chain today can move value across execution environments in a way that a bank moving dollars from London to Singapore over the weekend cannot. The public-chain world has imperfect liquidity mobility. The legacy world has none. Historically, there has been a direct correlation between the strength of a ledger's privacy and its latency. Generating zero-knowledge proofs or ensuring transaction anonymity required a heavy "computational tax," resulting in longer bridging windows ranging from several hours to several days. This created a real mobility tax: - **High Privacy / High Math:** Slower finality, as the system waits for complex proofs to be generated and verified. - **Low Privacy / Optimistic:** Faster perceived speed, often relying on "optimistic" assumptions or trusted liquidity-pool bridges to bypass waiting periods. The trade-off was clear: privacy and mobility were levers pulled in opposite directions. If you wanted the speed of an optimistic rollup, you often had to sacrifice the privacy or immediate mathematical certainty of a ZK-based environment. This matters. The design space for private settlement is not "pick one of privacy or mobility." It is: what architecture minimizes the tax each imposes on the other? ### The semi-private-chain trap The dominant institutional DLT pattern today is what we might call the "vertical silo." A permissioned chain. Built for one market. Privacy is enforced by giving each participant visibility only into transactions they're a party to. The largest live example of this pattern processed $385 billion in average daily repo volume in October 2025, running on a private-chain architecture that handles roughly $8 trillion in transactions per month for a single market.\[^5\] The technology works. The volumes are real. The institutions running these environments are not wrong to believe that there is business value here. However, the architectural choice embedded in this pattern is worth examining carefully for margin, collateral, and settlement. It is usually not articulated as a choice. It is presented as a technical necessity. In this model, each institution runs its own node, and transactions are distributed only to parties who need to see them, on a need-to-know basis enforced by the protocol. An ordering service sequences encrypted messages across participants. Atomic transactions can be composed across applications connected to a common synchronization domain.\[^6\] This delivers sub-transaction privacy and selective disclosure rather than pseudonymity. That is a genuine achievement. For a securities transaction where the custodian should only see the securities leg and the bank should only see the cash leg, this is the right property to optimize for. The problem is what the architecture does to liquidity mobility. It does three things. **Synchronization is per-domain.** Two applications that share a single centralized synchronizer can compose atomically. Applications that straddle multiple networks or ledgers cannot do so without significant infrastructure work on top. The "network of networks" framing is accurate. That is the limitation as much as it is the feature. Liquidity within a synchronization domain is mobile. Liquidity across domains is the engineering problem the industry is now retrofitting solutions for, after the fact. **Cash is usually an afterthought.** The dominant institutional DLT deployments have focused on a single asset classes like repo, tokenized securities, a particular derivative, and the cash leg has typically been solved last. A tokenized deposit or a settlement coin built primarily to clear that one market. The cash is captive to the venue. A treasurer who wants to move the same dollar from a repo platform to an FX venue to a corporate payout cannot. They need three different cash instruments, three different reconciliation paths, and three different operating models. **The privacy model constrains the liquidity pool.** If only the parties to a transaction can see it, liquidity providers outside those parties cannot price it or provide depth for it. Market-making inside a fully bilateral, fully private environment is structurally thin. The workaround is to concentrate activity inside a synchronization domain large enough to have its own depth, which is exactly what creates the silo. None of this is a criticism of the engineers who built these systems. They made defensible choices given the constraints they faced and the specific market they were solving for. The point is that those choices encoded a trade-off — privacy and throughput purchased at the cost of cross-market liquidity mobility — and that trade-off was never put to the test because it seemed like the only option available at the time. It isn't anymore. ### The three properties a cash settlement chain has to balance Three properties matter for a chain that wants to be the settlement layer for cash at an institutional scale. 1. **Speed and reliability.** Sub-second finality without re-orgs. Dedicated blockspace so that a meme coin going viral on the same infrastructure cannot starve payments. Predictable, fixed-denomination fees that a treasury team can model. This is the easiest property to deliver and, critically, it is no longer the differentiator. 2. **Privacy zones.** Where payment amounts, counterparty identities, and balances not visible to the public. The issuer, the regulator, and the parties to a transaction each get exactly the visibility they need and no more. Payroll ledgers stay private. Treasury movements stay private. Settlement details between two institutions stay between those two institutions. 3. **Liquidity mobility.** Cash moves across use cases and venues from payroll, treasury, settlement, FX, to wider tokenized asset markets without fragmenting into a separate pool for each. An asset issued once is usable anywhere inside the environment and any privacy zone without losing speed. The mobility is not just "cross-chain bridging works." It is "the cash leg doesn't re-fragment every time it enters a new use case." The architectural move that unlocks the third property without sacrificing the second is the separation of _execution_ from _settlement_. Private execution environments run as parallel chains where participants transact without public visibility. Funds remain locked in contracts on a common mainnet. Assets stay interoperable across environments. Liquidity pools on the mainnet remain accessible through deposit and withdrawal flows that are themselves private. ![Figure 1](/reports/figures/creating-more-liquidity-mobility-in-markets-figure-01.png) This is a different shape from the vertical silo. The silo makes privacy and liquidity adversarial. This architecture makes them orthogonal. Privacy is handled at the execution layer. Liquidity is handled at the settlement layer. The two stop fighting each other. ### What this means for the build decision For FMIs and bank strategists evaluating where to put institutional cash infrastructure, the questions worth asking are different from the ones the industry has been asking. It is not primarily _how fast?_ Sub-second finality is available from multiple vendors. It is not primarily _how private?_ Strong privacy with selective disclosure is achievable on several architectures. The questions that actually separate the options are about mobility. Can the same cash instrument clear a repo trade, fund a cross-border payment, post margin at a derivatives venue, and settle a tokenized securities trade without being re-issued, re-tokenized, or reconciled separately at each venue? Can a compliance policy set by the issuer once be enforced everywhere the token goes, including within a private execution environment, without custom integration? Can liquidity pools used for price discovery on the public side of the environment remain accessible to participants transacting privately? Does the cash leg actually treat cash as first-class, or is it a bolt-on to whatever the chain was really built for? An infrastructure that answers yes to these questions is optimizing for liquidity mobility. One that answers no, no matter how strong its privacy appears, is building a new silo. Tokenization is live and in production, and increasingly delivering value over weekends during geopolitical crises. Much of this activity is happening in stablecoins. The FMIs and banks that architect their next-generation infrastructure for mobility first, and solve privacy and speed as engineering problems on top of that foundation, are the ones that get to stay in the center of the flow. ### A note on the trade-offs Nothing here is cost-free. Architectures that achieve mobility through a shared settlement layer with private execution environments inherit trust assumptions from that settlement layer. Zone-style operators in such architectures see more than they would in a fully cryptographically hidden environment. This is a deliberate choice that works for institutional use cases with existing compliance mandates and works less well for retail privacy. Interoperability across environments adds operational surface area that a single-application silo does not have. These are real trade-offs, and any responsible evaluation should name them. The argument is not that mobility is free. The argument is that the cost of the alternative, rebuilding the silo at a new layer, is higher, and the industry is not yet pricing it correctly. **Closing** Every generation builds to fix the trap the last generation created. The question for the next build cycle is whether the architecture chosen solves the general problem or kicks it one layer down. Tempo has consistently strived to find the balance between mobility at the settlement layer, privacy at the execution layer, with compliance policies that travel with the token. We welcome discussion and feedback on these points. --- \[^1\]: Gate News, "$40 billion in liquidity fragmentation, Ethereum L2 economic zone proposal presents an integration path," March 2026, citing L2BEAT data. \[^2\]: CoinDesk, "How To Fix Ethereum's Fragmentation Problem," February 2025\. \[^3\]: Ethereum Economic Zone (EEZ) proposal, Gnosis and Zisk, Ethereum Foundation, 2026\. \[^4\]: Espresso Systems, "Defragmenting Liquidity with Asynchronous and Synchronous Composability." Trust-minimised cross-rollup messaging requires waiting at least 12–15 minutes for L1 finalisation, and up to several days for most rollups. \[^5\]: Broadridge press release, November 2025: Distributed Ledger Repo platform processed an average of $385 billion in daily repo transactions in October 2025\. Canton ecosystem references $8T+/month in DLR repo volume; Q4 2025 figures from Blockworks indicate Canton has processed $6 trillion in tokenised real-world assets to date, handling \~$350 billion per day in US Treasury activity. \[^6\]: Digital Asset, "Canton Network Overview"; Canton DeFi technical documentation on Global Synchroniser architecture. \[^7\]: Canton Foundation, "How Canton Network Delivers Institutional-Grade Privacy"; technical primers describe synchronisation domains as the unit of atomic composability, with cross-domain interoperability handled by the Global Synchroniser as a separate orchestration layer. > Interactive report gate is available on the HTML page. --- ## The Enterprise Guide to Stablecoin Earn Programs > Source: https://tempo.xyz/report/enterprise-guide-to-stablecoin-earn-programs/ > Language: en # The Enterprise Guide to Stablecoin Earn Programs Stablecoin Advisory ## Inside the report A practical guide to choosing assets, designing the customer experience, and planning the launch of a stablecoin Earn program. - Evaluate Earn sources, liquidity, and the risks customers take - Design onboarding, privacy, and reward distribution - Connect Earn to cards, payroll, and other core product features - Compare plug-and-play and custom paths to launch > Interactive report gate is available on the HTML page. [Download the full report (PDF)](/reports/enterprise-guide-to-stablecoin-earn-programs.pdf) --- ## Launching Stablecoin Payment Products > Source: https://tempo.xyz/report/launching-stablecoin-payment-products/ > Language: en # Launching Stablecoin Payment Products A practical guide for banks evaluating stablecoin payments, from outgoing transfers and prefunded liquidity to compliance, economics, and expansion into collections. **For:** Banks building stablecoin payment and treasury products ## A practical path into stablecoin payments The report explains how banks can start with outgoing stablecoin payments through their existing banking channels, then build toward collections and multi-currency treasury. - Why outgoing stablecoin payments are the simplest first use case - How to connect FX, onramp, custody, compliance, and Travel Rule partners - How a prefunded operational pool enables immediate settlement - How to expand from payouts into collections and multi-currency treasury ## Key metrics - **10–30 bps** — Estimated total cost of providing a stablecoin transfer - **5–15 bps** — Typical onramp fee range - **5** — Specialist partner categories in the launch stack ## Read the report - [Report landing page](/report/launching-stablecoin-payment-products) - [Download the PDF](/reports/launching-stablecoin-payment-products.pdf) - [Open the reader](/report/launching-stablecoin-payment-products/print) > Interactive report gate is available on the HTML page. --- ## Off-Hours Cash: The settlement gap banks can own by adopting stablecoins > Source: https://tempo.xyz/report/off-hours-cash/ > Language: en # Off-Hours Cash: The settlement gap banks can own by adopting stablecoins A commercial case for stablecoin settlement by banks, written for bank treasurers, ALM leads, and transaction banking heads. **For:** Bank treasurers, ALM leads, and transaction banking heads ## A bank-owned path into weekend settlement The report models a tightly sized, prefunded, KYC'd stablecoin sleeve backed by wholesale deposits and automatically swept back to deposit form on Monday morning. - Why wholesale deposits change the stablecoin P&L - Where closed settlement windows create client demand - How a 48-hour sleeve can clear break-even at 1.4-1.6 bps - Why Tempo fits as a neutral cash-leg orchestration layer ## Key metrics - **$260B** — Annualized sleeve flow in the worked illustration - **$38M** — Total annual cost under the conservative case - **48 hrs** — Transactional liquidity window from Friday to Monday ## Read the report - [Report landing page](/report/off-hours-cash) - [Download the PDF](/reports/off-hours-cash-the-settlement-gap-banks-can-own.pdf) - [Open the reader](/report/off-hours-cash/print) > Interactive report gate is available on the HTML page. --- ## Stablecoins as cash on the balance sheet > Source: https://tempo.xyz/report/stablecoins-as-cash/ > Language: en # Stablecoins as cash on the balance sheet By [Simon Taylor](https://www.linkedin.com/in/sytaylor/) ## Inside the analysis The analysis explains FASB’s proposal and the questions finance teams should assess as they evaluate stablecoins for treasury operations. - How FASB’s proposal applies the existing cash-equivalent definition - Why issuer redemption terms and reserves matter - What the proposed disclosure changes mean for finance teams - How to assess the implications for treasury operations > Interactive analysis gate is available on the HTML page. [Download the full analysis (PDF)](/reports/stablecoins-as-cash.pdf) --- ## Tokenized Deposits for Banks: A Primer > Source: https://tempo.xyz/report/tokenized-deposits-primer/ > Language: en # Tokenized Deposits for Banks: A Primer ## Inside the report This primer examines two core decisions for banks developing tokenized deposits: which ledger serves as the source of truth for client balances, and how payments settle with other banks. It traces the accounting flows and compares the trade-offs across credit risk, liquidity, operational complexity, and network reach. - Understand tokenized deposits, deposit tokens, and tokenized central bank reserves - Follow payments through operating accounts, omnibus accounts, and on-chain deposit accounts - Compare bilateral settlement, shared clearing infrastructure, and settlement in central bank money - Assess the commercial, legal, liquidity, and reconciliation requirements for launch > Interactive report gate is available on the HTML page. [Download the full report (PDF)](/reports/tokenized-deposits-for-banks.pdf) --- ## Tokenized Money for Banks: A Bank Treasury Guide to Institutional Settlement on Tokenized Rails > Source: https://tempo.xyz/report/tokenized-money-for-banks/ > Language: en # Tokenized Money for Banks: A Bank Treasury Guide to Institutional Settlement on Tokenized Rails A primer for banks evaluating tokenized deposits, first-party stablecoins, and third-party stablecoin settlement products. **For:** Bank treasury, ALCO, transaction banking, and digital asset teams ## Three product families, three balance-sheet outcomes The report works through the tokenized money choices available to banks and shows how each product changes the deposit claim, liquidity ratios, venue reach, and operational burden. - How tokenized deposits preserve the bank claim - Where first-party stablecoins re-engineer the liability profile - When third-party stablecoins reach venues bank claims cannot - How LCR, NSFR, and RWA shape the product decision ## Key metrics - **3** — Product families for bank tokenized money - **100%** — Stablecoin redemption-liability LCR outflow under SCO60 - **85%** — NSFR required stable funding for principal third-party stablecoin inventory ## Read the report - [Report landing page](/report/tokenized-money-for-banks) - [Download the PDF](/reports/tokenized-money-for-banks.pdf) - [Open the reader](/report/tokenized-money-for-banks/print) --- **_A Bank Treasury Guide to Institutional Settlement on Tokenized Rails._** ## **Executive Summary** Tokenized money is becoming a bank product because the cash leg is being pulled into new market infrastructure. GFMA’s April 2026 report identifies three active capital-markets use cases for digital money: securities settlement, repo and securities finance, and derivatives margin. In each, the same issue appears: assets, collateral and margin can move faster than the bank money used to fund them. DTCC’s May 2026 collateral work puts numbers behind the problem, estimating that intraday repo on digital rails could cut intraday funding costs roughly in half while reducing liquidity buffers and capital requirements. Institutional clients now require settlement assets that match this velocity to address innovations directly impacting their positions. This primer covers the three products a bank can offer in response. The first family keeps the claim as a deposit. The second converts the claim into a redemption contract against a segregated reserve pool. The third routes the claim through a third-party stablecoin issuer. Balance-sheet constraints dictate product architecture. Retaining the claim as a deposit defends core funding but degrades token velocity. Building an internal rail via segregated reserves fixes mobility, but fundamentally re-engineers the bank's liability profile. Relying on a third-party asset accesses broader liquidity pools at the cost of leaking the deposit completely off-balance sheet. Every structural pivot is a strict trade-off, hard-coding a distinct penalty or capacity release across LCR, NSFR, and RWA. **Family 1: Tokenized Deposits: Bank claim tokens** that represent a customer's deposit at the bank. A bank in this family issues a token, the customer holds it in a wallet, and the underlying claim against the bank stays a deposit. **Family 2: 1st party stablecoin** Stablecoins the bank issues itself, with a segregated pool of reserves backing the redemption obligation. **Family 3: 3rd party stablecoin.** Products a bank can offer using a 3rd party stablecoin, the dominant institutional dollar stablecoin, as the settlement asset The rest of the primer covers each family in depth. Section 1 explains why tokenized money is now on the bank product agenda. Section 2 introduces the three families together. Sections 3, 4, and 5 walk through each family product by product, with the journal entries, the ratio impacts, and the conditions under which each fits a bank's franchise. Section 6 names the strategic, regulatory, and operational questions a bank should answer before committing. Section 7 covers the infrastructure layer underneath whichever product the bank chooses. ## **1\. Why we are here** Bank tokenized money is not a new idea. The first internal blockchain settlement systems at major banks went live in 2019, beginning with J.P. Morgan's JPM Coin, which moved wholesale payments between institutional clients on a private ledger. Citi launched Citi Token Services for internal liquidity management in 2023\. HSBC and BNY Mellon ran parallel pilots over the same period. In all of these, the bank tokenized its own deposit liabilities on infrastructure it controlled, the tokens never left the bank's network, and the customer's experience was a more efficient version of the same wholesale payment the bank had been offering for decades. The technology worked. The customer relationship was preserved. The regulatory questions were small because the products were closed-loop. What changed between 2024 and late 2025 was the regulatory and product environment around bank tokenized money. The GENIUS Act, enacted in July 2025, created a federal framework in the United States for bank-issued payment stablecoins, requiring issuance through a permitted issuer subsidiary with 1:1 reserves in high-quality liquid assets. In Europe, MiCA’s stablecoin regime began applying in June 2024, creating a harmonized framework for asset-referenced tokens and e-money tokens across the EU. The Basel Committee finalized SCO60, the cryptoasset chapter of the prudential framework, with implementation effective 1 January 2026\. These frameworks together gave banks a defined regulatory perimeter for issuing tokenized money to institutional clients on public infrastructure, not just on internal networks. The market arrived in parallel. Institutional weekend volume on digital-asset venues passed an inflection point in late 2025\. Hyperliquid's HIP-3 markets, which let qualified builders launch perpetual futures markets on synthetic indices and equities, reached $500 million in daily volume within weeks of launch in October 2025\. Trade.XYZ, an institutional perpetual venue built on Hyperliquid, has cleared the S\&P 500 perpetual under license from S\&P Dow Jones Indices since March 2026, with cumulative volume above $100 billion on an annualized run rate of $600 billion. Every contract on these venues is margined in stablecoins. ## **2\. The families of products** ![Figure 1](/reports/figures/tokenized-money-for-banks-figure-01.png) **The first family is tokenized deposits.** A bank in this family issues a token that represents a customer's deposit. The customer holds the token in a wallet, and the underlying claim against the bank stays a deposit. Two product variants are possible: a tokenized deposit that moves only within a permissioned garden (1A), and a deposit token that moves “freely” across wallets on a public or institutional blockchain (1B). The bank's deposit franchise is preserved in both cases. The legal nature of the claim, the deposit guarantee, and the regulatory capital framework continue to apply. **The second family is a 1st party stablecoin.** A bank in this family issues a coin against a segregated reserve pool. The customer's claim converts from a deposit at the bank into a redemption contract against the reserve pool. Three structural choices are possible: the bank can issue on its consolidated balance sheet (2A), through a separately incorporated permitted issuer subsidiary (2B), or through a consortium with peer banks (2C). The strategic value of the family is a settlement rail the bank controls, denominated in money it issues. The cost is the regulatory treatment of the issued liability under Basel SCO60. **The third family is a 3rd party stablecoin.** A bank in this family offers settlement using a third-party stablecoin as the settlement asset. The customer settles on a digital-asset venue using a stablecoin issued by a third-party, and the claim leaves the bank's balance sheet entirely. Two structural choices are possible: the bank can hold the stablecoin inventory on its balance sheet for delivery on demand (3A, prefunded), or it can extend a fiat loan secured by a blocked customer deposit with the stablecoin delivered to the venue directly from Circle (3B, secured loan). The bank's role is intermediation rather than issuance. The three families are not interchangeable. Each carries a different prudential cost, fits a different range of institutional venues, and serves a different strategic position for the bank. The next three sections cover each family in depth. ## **3\. Family 1: Tokenized Deposits** ![Figure 2](/reports/figures/tokenized-money-for-banks-figure-02.png) A bank claim token is a digital representation of a customer's deposit at the bank. The bank issues a token that the customer holds in a wallet, and the underlying claim against the bank remains a deposit on the bank's balance sheet. The token is the wrapper. The wrapper changes nothing about the legal nature of the underlying instrument. The customer's relationship with the bank is preserved, the deposit guarantee continues to apply, and the regulatory capital framework continues to apply unchanged. Under SCO60.107, the tokenized claim is treated as an unsecured funding instrument when four conditions hold: the token is issued by a regulated and supervised bank, it represents a legally binding claim on the bank, it is redeemable in fiat currency at par value, and its value is supported by the creditworthiness and asset-liability profile of the issuing bank rather than by a segregated pool of reserves. When those conditions hold, the LCR runoff factor and the NSFR ASF category map to the underlying deposit type, with two important constraints. The maturity is set by the earliest contractual redemption right available to the holder. The liability cannot be classified as a stable retail deposit, which means a 24/7 transferable token attached to an institutional operating deposit requires the bank's internal LCR overlay to price the additional velocity. There are two products in this family. Both keep the claim as a deposit. The difference is transferability, and that difference shapes the venue compatibility and the operational requirements of each. ### **1A. Tokenized deposit** A tokenized deposit is the first variant in the family. The bank issues a token that moves only within a defined garden of vetted participants. Wallets are KYC'd. Transferability is restricted to permitted counterparties. The network can be the bank's own ledger (the simplest configuration), a permissioned shared ledger between participating banks, or a consortium chain. In all three configurations, the token's lifecycle is closed-loop: the bank mints the token into a customer wallet, the token transfers between wallets inside the network, and the bank redeems the token back into a deposit at the customer's request. The journal entry is a reclassification of an existing deposit line. No new liability is created. No reserve pool needs to be funded. **![Figure 3](/reports/figures/tokenized-money-for-banks-figure-03.png)** The ratio impact is calibrated by the underlying deposit type. An institutional operating deposit moving into a tokenized deposit retains the Basel 25% LCR runoff and the 50% NSFR ASF category for operational wholesale funding below one year, provided the deposit's operating-relationship character is preserved. The bank loses no funding stability by tokenizing the deposit, because no funding stability has been added or removed in the journal entry. The customer's claim and the bank's funding base are unchanged. A bank can choose 1A when the institutional client's settlement need is within the bank's network. Common use cases are intra-bank treasury movements, settlement between participating banks on a permissioned consortium chain, and atomic delivery-versus-payment exchange of tokenized securities for tokenized cash on a permissioned settlement venue. ### **1B. Deposit token** A deposit token is the second variant in the family. The bank issues a token that is transferable across wallets the bank does not directly supervise, including institutional custody addresses, vetted counterparty wallets, and (in some configurations) institutional wallets on public blockchains. The token still represents a legally binding claim against the issuing bank. What changes from 1A is the velocity of redemption and the surface area of operational risk. The journal entry is still a reclassification, identical to 1A. The ratio impact is not: **![Figure 4](/reports/figures/tokenized-money-for-banks-figure-04.png)** A deposit token that can move from the bank's network to a counterparty wallet on a Saturday morning faces a stress profile that a tokenized deposit recorded on the bank's ledger does not. The counterparty can post the token as margin on a venue the bank does not operate. The token can be redeemed back into a deposit at the bank on the same Saturday. The bank's internal LCR overlay prices that velocity. The starting point is the 25% Basel runoff for operational wholesale deposits, but the operating-relationship character weakens with every layer of transferability the bank grants. A bank running a deposit token at institutional scale should expect to assign a runoff factor closer to the 40% non-operational wholesale rate. The live example is JPMD. J.P. Morgan launched its USD deposit token on Base, an Ethereum Layer 2 blockchain built within Coinbase, in November 2025\. JPMD is a permissioned deposit token, meaning only vetted institutional wallets can hold it, but those wallets transact on a public blockchain alongside other tokens issued by other institutions. The token is yield-bearing, a feature the bank can offer on a deposit token because the underlying instrument is a deposit, and deposits can carry interest. A stablecoin issued by a US bank cannot pay yield to holders under the GENIUS Act framework. JPMD is integrated with the Mastercard Token Network, which lets it settle alongside card-network flows in real time, and the bank's institutional clients can use it to fund collateral positions on partner venues without going through correspondent banking. A bank can choose 1B when three conditions hold together. The bank's institutional clients trade on venues that accept tokenized bank claims as margin or settlement collateral. The bank wants to preserve the deposit franchise rather than convert deposits into redemption contracts. The institutional flow is large enough to justify the engineering investment in protocol-level compliance, custody, and onchain-to-offchain reconciliation. The constraint on 1B is venue acceptance. Permissionless crypto derivatives venues that require non-restricted, fungible settlement assets do not accept bank-claim tokens with transfer restrictions or jurisdiction-specific KYC requirements. Where the institutional flow clears on those venues, the bank cannot use a deposit token to serve it, and Family 3 becomes the operative choice. ## **4\. Family 2: 1st Party Stablecoin** ![Figure 5](/reports/figures/tokenized-money-for-banks-figure-05.png) A bank in this family issues its own stablecoin. The bank stops being the holder of the customer's deposit and becomes the issuer of a redemption contract against a segregated pool of reserves. The customer keeps a dollar claim of the same face value, but the legal and prudential character of the claim has changed. The liability shift is the move that defines the family. Before issuance, the bank funds itself with the customer's deposit, which is a stable wholesale liability under Basel rules. An institutional operating deposit runs off at 25% in the LCR over a 30-day stress horizon and contributes at the 50% ASF rate in the NSFR. After issuance, the bank funds itself (or its subsidiary or consortium issuer funds itself) with a redemption liability that is treated under SCO60.108 as a 100% LCR outflow on the redeemable amount and a 0% ASF for any maturity less than thirty days. The funding base, measured in regulatory terms, has shifted from the most efficient category Basel recognizes into the least efficient. Reserves must be 1:1 in cash, central bank reserves, short-dated Treasuries, Treasury-backed reverse repos, and government money market funds. ### **2A. Own balance** A bank in 2A issues the stablecoin on its own consolidated balance sheet. There is no subsidiary to incorporate, no consortium to negotiate, no inter-group settlement to reconcile. The redemption liability sits directly on the parent bank's books, and the parent's regulatory ratios absorb the issuance in full. This is the simplest legal structure and the most expensive prudential structure. Two balance-sheet moves are possible when the bank issues on its own balance sheet. They differ in where the cash comes from to back the issuance, and the difference matters for what the issuance actually costs the bank. **The first move is an external mint.** A new customer brings cash from outside the bank, the bank mints a stablecoin against that cash, and the redemption liability is established alongside a new asset position in central bank reserves: **![Figure 6](/reports/figures/tokenized-money-for-banks-figure-06.png)** In an external mint, the bank's HQLA goes up by the amount of the issuance. So does the LCR outflow under the 100% rule. The net LCR impact depends on whether the new reserves are segregated for the stablecoin or merged into the bank's general HQLA stock. If the bank segregates the reserves and does not double-count them in eligible HQLA, SCO60.108(1)(b) allows the bank to offset the 100% outflow up to the segregated amount, net of LCR haircuts. If the reserves are merged into the general HQLA stock, they count toward the bank's existing LCR but cannot offset the new outflow. In practice, banks issuing on their own balance sheet structure the issuance to maximize the offset, which is the entire reason the reserve segregation requirement exists in the GENIUS Act and MiCAR. The ASF assigned to the redemption liability is based on the earliest date the stablecoin could be redeemed, which for a weekend-active settlement product is “now” and assigns 0% ASF, the most punitive NSFR category. **The second move is a conversion.** An existing customer with a deposit at the bank converts the deposit into a stablecoin. The bank's balance sheet sees a reclassification of liability lines without new cash entering: **![Figure 7](/reports/figures/tokenized-money-for-banks-figure-07.png)** The conversion move is the most expensive of the three from the bank's perspective, and the reason is mechanical. Before conversion, the bank was funded by an institutional operating deposit at a 25% LCR runoff and a 50% ASF. After conversion, the bank is funded by a redemption liability at a 100% LCR runoff and a 0% ASF. Because no new HQLA enters the balance sheet in a conversion, the SCO60.108(1)(b) offset is not available. The full 100% outflow hits the LCR without compensation from segregated backing reserves. The bank has paid the cost of the franchise migration without receiving any new cash for it. The customer's claim looks identical from the customer's seat. The bank's funding profile has weakened on both ratios. A bank can choose 2A when it has the capital headroom to absorb the LCR outflow on the redeemable amount without straining its existing ratio, when it wants the simplest legal and operational structure, and when it accepts that the franchise migration cost will be borne by the parent's funding base. The choice fits banks with deep wholesale deposit franchises and existing LCR buffers well above regulatory minimums. ### **2B. Subsidiary** A bank in 2B issues the stablecoin through a separately incorporated subsidiary that is a permitted issuer in its jurisdiction. The subsidiary is separately capitalized, separately licensed, with its own reserve pool and its own redemption obligations. The parent's standalone balance sheet does not carry the redemption liability. The parent's group balance sheet carries an equity investment in the subsidiary, and the consolidated regulatory ratios reflect both the parent's existing book and the subsidiary's issuance. What the journal entry shows for 2B depends on how the cash flows between the parent and the subsidiary. In a first case, the customer converts a deposit at the parent into a stablecoin issued by the subsidiary, and the subsidiary places the reserves back at the parent as a fiduciary reserve deposit. The parent's deposit line moves from a customer operating deposit to an interbank deposit, and the parent keeps the cash on its balance sheet: **![Figure 8](/reports/figures/tokenized-money-for-banks-figure-08.png)** The first case is worse for the parent than it appears. An interbank deposit from a financial institution carries a 100% LCR runoff under Basel rules, because financial-institution funding is the most volatile wholesale category. The parent has replaced a 25% runoff customer deposit with a 100% runoff interbank deposit. The cash is still on the balance sheet, but the funding stability has collapsed. In a second case, the customer converts the deposit into a stablecoin and the subsidiary places the reserves with a third-party custodian or with another bank entirely. The cash leaves the parent: **![Figure 9](/reports/figures/tokenized-money-for-banks-figure-09.png)** In the second case, the parent's standalone balance sheet shrinks. The customer's deposit goes out, the cash goes out, and no new liability comes in. From a standalone capital ratio perspective the parent looks cleaner. From a franchise perspective the parent has lost the customer's deposit to its own subsidiary, and the cash to a third-party custodian. A bank can choose 2B when it wants to protect the parent's standalone balance sheet from the LCR outflow on the issuance, when the regulatory regime requires a subsidiary structure (which the US framework does), and when it accepts that the consolidated group ratio will still reflect the issuance. The structural lesson of 2B is that a separately incorporated subsidiary isolates the parent's standalone capital but does not eliminate the support expectation. Under stress on the subsidiary's redemption queue, the market expects the parent to step in, and the ALCO should price the implicit support line into the consolidated risk view. ### **2C. Consortium** A bank in 2C participates in issuing a tokenized wholesale settlement asset through a joint venture or industry consortium with peer banks. The consortium structure spreads the issuance risk across multiple banks, dilutes the governance burden, and gives the resulting settlement asset a credibility no single-bank issuance can match. The cost is coordination: every consortium decision has to clear multiple banks' risk committees, multiple supervisors, and multiple jurisdictions. The bank's role in 2C is participation rather than direct issuance. The bank takes an equity stake in the consortium entity, and the consortium becomes the issuer of the settlement asset. The bank's balance sheet sees an equity investment line, and the cash used to purchase the stake leaves the balance sheet: **![Figure 10](/reports/figures/tokenized-money-for-banks-figure-10.png)** The standalone capital impact of the equity stake is small. The strategic value is access to a settlement rail operated by a consortium that includes the bank's peer institutions, with governance the bank can influence through its equity position. The cost beyond the equity is coordination overhead, which compounds with every additional jurisdiction and every additional participant the consortium adds. A bank can choose 2C when it wants the strategic benefits of a controlled settlement rail without the standalone balance-sheet impact of a single-bank issuance, when the consortium's settlement asset has a credit profile better than a private reserve pool, and when the bank can accept the governance overhead of consortium decision-making. The choice fits banks that participate in wholesale clearing infrastructure already and that see the consortium as an extension of that role. ## **5\. Family 3: 3rd party stablecoin** ![Figure 11](/reports/figures/tokenized-money-for-banks-figure-11.png) A bank in this family does not issue a token. The bank facilitates the customer's access to a third-party stablecoin and the claim leaves the bank's balance sheet. The stablecoin is issued by a regulated third-party issuer and backed by a reserve pool held in cash, short-dated government securities, reverse repos, bank deposits, money market funds, or other eligible reserve assets under the applicable stablecoin framework. The reserve composition is disclosed under the issuer's regulatory and reporting obligations. The issuance is structured to meet the applicable requirements for regulated payment stablecoins. The bank has four plausible roles when an institutional client wants to settle in a third-party stablecoin. The bank can act as agent, with no principal exposure to the stablecoin. The bank can prefund the customer, holding third-party stablecoin inventory on its own books. The bank can extend a fiat loan secured by a blocked customer deposit, with the stablecoin delivered to the venue directly from the issuer or from an approved liquidity provider. The bank can act as custodian, holding the customer's stablecoin keys. The two roles that move the bank's funded balance sheet are prefunded product and the secured loan. ### **3A. Prefunded** A bank in 3A holds a third-party stablecoin as an asset on its own balance sheet, available to deliver to a customer on demand. The bank has converted a portion of its central bank reserves into a stock of stablecoin assets, sized to serve expected institutional weekend draw. When a customer needs the stablecoin for a Saturday settlement, the bank delivers from its inventory and debits the customer's deposit account. The journal entry has two stages. In the first stage, the bank acquires the stablecoin inventory by purchasing it from the issuer or from a market maker, using cash from its reserves at the central bank: **![Figure 12](/reports/figures/tokenized-money-for-banks-figure-12.png)** In the second stage, the customer draws against the inventory, settling the draw against the customer's deposit balance at the bank: **![Figure 13](/reports/figures/tokenized-money-for-banks-figure-13.png)** The regulatory cost is concentrated in the first stage. The bank has converted a Level 1 HQLA position (central bank reserves, the highest quality money the bank can hold) into a Group 1b stablecoin asset (a regulated payment stablecoin with a separate prudential treatment). Under SCO60, the third-party stablecoin held on a bank's balance sheet does not qualify as HQLA in the LCR. The same stablecoin attracts an 85% required stable funding factor in the NSFR. The bank's regulatory liquidity position weakens twice: the HQLA stock falls by the amount of the conversion, and the funding requirement rises by 85 cents on the dollar of inventory held. If the stablecoin fails to meet the Group 1b classification conditions on an ongoing basis, the treatment is more punitive. A Group 2 cryptoasset attracts a 1250% risk weight under the cryptoasset capital framework and counts against the bank's 1% Tier 1 cap on aggregate Group 2 exposures. A bank that prefunds the stablecoin takes a position on the issuer's continuing compliance, on top of a position on the stablecoin itself. A bank can choose 3A when its institutional clients clear on venues that accept the third-party stablecoin but not bank-claim tokens (which describes most institutional crypto derivatives venues today), when the bank has the capital headroom to absorb the HQLA-to-stablecoin substitution and the 85% NSFR funding penalty without straining its existing ratios, and when the customer revenue from facilitating the stablecoin settlement exceeds the prudential cost of holding the inventory. For banks without that headroom, 3A absorbs balance-sheet capacity that could be deployed against loans or other higher-return assets, and the product rarely clears the standalone P\&L test. ### **3B. Deposit-secured fiat facility** A bank in 3B does not hold the stablecoin on its books. The customer keeps the deposit at the bank, blocked and pledged as collateral. The bank books a short-term secured loan against the blocked deposit. The loan funds the stablecoin purchase, which is delivered to the customer's whitelisted venue directly from the issuer or from an approved liquidity provider. The bank never holds the stablecoin, which means the prudential cost of the stablecoin sits with the customer, not with the bank. The journal entry shows reserves moving from the central bank into a secured loan asset, with the customer's deposit unchanged at the line level but encumbered through a security interest: **![Figure 14](/reports/figures/tokenized-money-for-banks-figure-14.png)** The ratio impact is calibrated to the secured loan, not to the stablecoin. A short-term loan fully secured by an unencumbered cash deposit at the same bank carries one of the lowest risk weights under the standardized approach to credit risk, with set-off against the deposit available as the default path on customer non-repayment. The LCR sees the reserve drop on the asset side and a contractual inflow from the loan's repayment, capped at the standard cap on inflows. The NSFR sees a short-term loan against stable secured collateral and a 25% LCR runoff operational liability (the blocked deposit) on the funding side. The bank has converted reserves into a loan, which is a category the bank's risk and capital framework already handles every day. There is no principal stablecoin on the bank's books, so the 85% RSF question does not arise. There is no bank-issued stablecoin liability, so SCO60.108’s 100% LCR outflow does not apply. The bank's regulatory liquidity position holds, save for the cash that left for the loan and the timing of the contractual inflow. A bank can choose 3B when it wants to serve customer stablecoin settlement without taking principal exposure, when it can price the weekend service as a financing spread (in basis points over the customer's blocked deposit rate) rather than as a stablecoin trading spread, and when its custody architecture and direct delivery relationship with the issuer is set up to handle weekend-active flows. The choice fits banks with strong secured lending capabilities and existing institutional credit lines that can be extended into a tokenized settlement context. |PRODUCT|CLAIM LOCATION|TRANSFERABILITY|RESERVES|LCR OUTFLOW|NSFR| |:-|:-|:-|:-|:-|:-| |**TOKENIZED DEPOSIT**|||||| |Tokenized deposit|Bank|Permissioned (Internal)|Fractional|25–100%|ASF 50%| |Deposit token|Bank|Permissioned|Fractional|25–100%|ASF 50%| |**1ST PARTY STABLECOIN**|||||| |Own balance|Bank|Permissioned|HQLA|100%|ASF 0%| |Subsidiary|Subsidiary|Permissioned|HQLA|100%|ASF 0%| |Consortium|Central bank|Consortium|HQLA|0%|RSF 0%| |**3RD PARTY STABLECOIN**|||||| |Prefunded|Issuer|Permissionless|HQLA (issuer)|100%|RSF 85%| |Secured loan|Issuer|Permissionless|\-|Per facility|Per facility| ## **6\. Considerations for banks evaluating these products** The framework above is the basis for product selection. The selection itself depends on the bank's specific franchise position, regulatory regime, capital headroom, and operational readiness. This section names the questions a bank should answer before committing to a product. ### **Strategic considerations** **Which family of products fits the bank's franchise position?** A retail-deposit-heavy bank with limited institutional capital markets activity has a different answer from a transaction banking bank serving hedge funds and corporate treasuries. A bank with captive institutional clients clearing on its own permissioned venues has a different answer from a bank whose clients clear on third-party public venues. The bank should map its existing institutional client base against the venues those clients use for digital-asset flow, then identify which family's products reach those venues. **Is the bank trying to defend an existing franchise or to capture a new revenue line?** A bank that already holds the institutional client's primary deposit relationship has reason to defend that relationship against stablecoin leakage by offering a bank-claim token or a deposit-secured fiat facility. A bank that wants to enter institutional settlement as a new business line should evaluate whether the consortium model gives it access to a credible settlement rail without the standalone capital cost of issuing alone. **Will the bank build product capability in-house or partner for it?** Building a deposit token program or a permitted issuer subsidiary is a multi-year investment in legal, regulatory, technology, and custody capabilities. Partnering with infrastructure providers can compress the timeline but introduces operational dependencies and revenue-sharing arrangements. The strategic answer constrains the regulatory and operational choices that follow. ### **Regulatory considerations** **Which prudential regime applies, and what is the implementation timeline in the bank's jurisdiction?** Basel SCO60 took effect 1 January 2026 in jurisdictions implementing on the international timeline. Several major jurisdictions, including the United States and the United Kingdom, have not committed to a fixed implementation date and may be operating under transitional frameworks through 2026 and 2027\. The European Union, Canada, the Hong Kong Monetary Authority, and the Monetary Authority of Singapore are implementing on schedule. **Does the bank's primary regulator accept the subsidiary path for stablecoin issuance, and on what conditions?** US banks issuing under the GENIUS Act must work through the OCC's permitted issuer framework for national banks, or the FDIC's framework for state-supervised insured depository institutions. The OCC issued its notice of proposed rulemaking in February 2026\. The FDIC issued its in December 2025\. The detailed conditions for approval, including capital, governance, and reporting requirements, are still being finalized through the rulemaking process. **For Family 1 products, how does the bank's regulator treat the tokenized deposit's deposit-guarantee coverage?** Tokenized deposits remain in scope of the deposit-guarantee framework when they meet the statutory deposit definition, both in Europe and in the United States. A bank issuing a deposit token should confirm that its specific product structure preserves the deposit-guarantee coverage that institutional clients will expect. **For Family 3 products, how does the bank's regulator treat the bank's principal holding of a third-party stablecoin?** The Group 1b classification under SCO60 depends on the issuer's continuing compliance with the prudential conditions, and a bank holding the stablecoin takes a view on that compliance. ### **Operational considerations** **Can the bank's incident response operate on chains that never close?** Settlement assets on public blockchains create incident windows that conventional payment systems do not. A token issuance contract bug, an oracle failure, a sanctions list update that affects an existing wallet, a custodian outage: each of these can require immediate response, including pausing transfers, freezing balances, or coordinating with the chain's validator set, regardless of whether the event happens at noon on a Tuesday or at four in the morning on a Saturday. **Is the bank's custody architecture ready for the products in scope?** Holding principal third-party stablecoin inventory requires qualified custody infrastructure. Issuing a stablecoin requires custody for the reserve pool. Issuing a deposit token requires custody for the institutional wallet-level holding addresses. The custody question is different for each family and should be answered before the product launches. **Are the bank's reconciliation systems set up to match onchain and offchain ledgers in real time?** The bank's existing ERP and treasury platforms were built for batch-based reconciliation against the bank's internal accounts and a fixed set of external counterparties. Real-time reconciliation against a public blockchain requires integration against the relevant blockchain events, the wallet-level state, and the bank's internal records of issuance and redemption. **What is the bank's wallet-level sanctions screening capability, and how does it scale to the transaction volumes the institutional flow will generate?** The bank's existing AML and sanctions infrastructure was built for SWIFT-message volumes. Onchain transfers generate event streams that require different screening architecture. > Interactive report gate is available on the HTML page. --- ## Reports and research – Tempo > Source: https://tempo.xyz/reports/ > Language: en # Research on payments & financial infrastructure ## [Stablecoins as cash on the balance sheet](/report/stablecoins-as-cash/) An analysis of FASB’s proposed cash-equivalent guidance and what it means for corporate finance teams. ## [Tokenized Deposits for Banks: A Primer](/report/tokenized-deposits-primer/) A practical primer on tokenized deposit models, accounting flows, and the options banks can use to settle with other institutions. ## [The Enterprise Guide to Stablecoin Earn Programs](/report/enterprise-guide-to-stablecoin-earn-programs/) A practical guide to choosing assets, designing the customer experience, and planning the launch of a stablecoin Earn program. ## [Off-Hours Cash](/report/off-hours-cash/) A commercial case for stablecoin settlement by banks, written for bank treasurers, ALM leads, and transaction banking heads. ## [Launching Stablecoin Payment Products](/report/launching-stablecoin-payment-products/) A practical guide for banks evaluating stablecoin payments, from outgoing transfers and prefunded liquidity to compliance, economics, and expansion into collections. ## [Tokenized Money for Banks](/report/tokenized-money-for-banks/) A primer for banks evaluating tokenized deposits, first-party stablecoins, and third-party stablecoin settlement products. ## [Creating More Liquidity in Markets](/report/creating-more-liquidity-mobility-in-markets/) A market-structure report on why liquidity mobility should be the primary lens for evaluating tokenized settlement infrastructure. --- ## Tempo Routes — Build stablecoin payment flows with one API > Source: https://tempo.xyz/routes/ > Language: en # Build stablecoin payment flows with one API Tempo Routes Tempo Routes let your business move money by connecting stablecoins, networks, and bank accounts in a single interface. [Talk with our team](/contact/) [Explore API](/developers/docs/api/routes/transfers/) ## Make stablecoins work for your business ### Reach more customers Support the currencies and payment methods your customers use. Accept and pay out in stablecoins. ### 1:1 stablecoin liquidity Convert between supported stablecoins and blockchains at a fixed 1:1 rate with instant settlement. ### One integration, many providers Connect once to Routes and tap into our growing set of liquidity providers, stablecoin issuers, and bank rails. ## From quote to completed transfer with Routes API How it works ### Choose your route Select the source and destination assets, network, and amounts. [Contact us](/contact/) for pricing. ### Review the quote Check the transfer route, quoted fees, and instructions before making the transfer. ### Initiate and track Execute the payment instructions and monitor throughout the payment lifecycle. ## One API to accept, convert, and make payments with stablecoins ### Accept stablecoin deposits Give customers a deposit address for any supported stablecoin and network. Funds land automatically in a Tempo account, private Tempo Zone, or Tempo Earn vault. ### Convert reliably between stablecoins Bridge and convert stablecoins on Tempo at a fixed rate. Subsidize to deliver a 1:1 experience. ### Bring your own stablecoin account Use your existing custodial or noncustodial wallet infrastructure with Tempo Routes. Orchestrate money movement directly from your wallets. ## FAQ ### Which stablecoins and networks can we support? Move supported stablecoins across Ethereum, Base, Polygon, BNB Smart Chain, Solana, Tron, and Tempo. Work with Tempo to confirm the routes your business needs. ### Can customers fund a Tempo account from an external wallet? Yes. For supported routes, your business can create a deposit address and route the funds to the Tempo account, Zone, or Earn destination you specify. ### Can I use my existing wallet provider? Yes. You can use the wallet infrastructure your business already supports to sign and broadcast transactions. ### How long do transfers take? Timing varies by network and route. Review expected transfer times for your required routes with Tempo. ## Build with Tempo Routes Work with Tempo to access custom pricing and design your payment flows. [Integrate Routes API](/developers/docs/api/routes/transfers/) [Talk with our team](/contact/) --- ## Meet Tempo at Sibos 2026 > Source: https://tempo.xyz/sibos/ > Language: en # Meet Tempo at Sibos Request a meeting with Tempo at Sibos. Our team will follow up by email to arrange a time. Provide your first name, last name, work email address, company name, company website, and interest. All fields are required. [Request a meeting](/sibos/) We’ll use these details to follow up on your meeting request. [Privacy Policy](/privacy-policy/) --- ## Agentic payments — Tempo Solutions > Source: https://tempo.xyz/solutions/agentic-payments/ > Language: en # The payment layer for AI agents Fund agent wallets, set permissions, and monetize your APIs — all with instant, low fee autonomous payments. [Contact us](/contact/) [Build on Tempo](/developers/) > Interactive agentic payment flow is available on the HTML page. ## Monetize your APIs Monetize Turn on another revenue source for your business by implementing the Machine Payments Protocol (MPP). MPP is the open protocol for machine-to-machine payments which allows businesses to charge agents for API requests, MCP servers, or access to content. All payments can be settled instantly into your Tempo wallet with no fees. - **Monetize agents:** Earn extra revenue by monetizing agents - **Instant settlement:** Accept payments from agents that settle instantly - **Flexible billing:** Charge per request without the need for subscriptions ## Give agents a wallet Agent Wallets Use Tempo Wallet or any other Tempo-compatible wallet to let your agents call APIs, buy services, and run tasks within budget. Fund it with a credit card, Apple Pay, ACH or with any fiat currency, and set limits and permissions. Or let your applications create user, agent, and team accounts on Tempo with Tempo Accounts SDK. - **Flexible wallets:** Let agents transact on their own without a human stepping in with a credit card - **Intuitive controls:** Set budgets per agent or workflow and control what agents can buy - **Low fees:** Agent transaction fees as low as a tenth of a cent ## Learn more ### [Machine Payments Protocol](https://mpp.dev/) The open protocol for machine-to-machine payments. Learn how MPP works. ### [Tempo Wallet](/developers/) Fund agent wallets, set permissions, and manage accounts with the Tempo Wallet SDK. ### [Tempo Mainnet Launch](/blog/mainnet/) Tempo is live. Read about the mainnet launch and what it means for payments. ## Take your stablecoin strategy into production Start using Tempo ### Design your stablecoin product Enterprises Build on Tempo with payments specialists, forward-deployed engineers, and global banking experts. [Talk to our team](/contact/) ### Start building Developers Build on the blockchain engineered for payments, with the tools and docs to bring your product to life. [Tempo API Platform](https://api.tempo.xyz) --- ## Cross-border payments — Tempo Solutions > Source: https://tempo.xyz/solutions/cross-border-payments/ > Language: en # Move money across borders in seconds Deliver faster, cheaper, and more predictable cross-border payments to individuals and businesses around the world with Tempo. [Contact us](/contact/) [Build on Tempo](/developers/) > Interactive payroll demo flow is available on the HTML page. ## Run cross-border payroll Payroll with privacy Give your customers same-day global payroll on stablecoin rails. Tempo Zones keep compensation data private while you unlock new revenue by embedding financial products alongside payouts. - **Same-day payroll:** Offer your customers instant global disbursements - **Built-in privacy:** Keep your customers' payroll data private with Tempo Zones - **Beyond payouts:** Embed cards, savings, and earned wage access into your platform ## Collect and settle payments worldwide Global payments Upgrade your payments platform to accept and send money on stablecoin rails, unlocking better money movement for your customers. - **Low fees:** Stablecoin transfers on Tempo cost \<$0.01, at any volume - **Instant settlement:** Pay-ins and payouts settle in less than a second, 24/7 - **Global by default:** No correspondent banks required ## Learn more ### [Stablecoins for Global Payouts](/blog/global-payouts/) How companies use stablecoins on Tempo for cross-border payouts with sub-second settlement and sub-cent fees. ### [Stablecoins for Remittances](/blog/remittances/) How stablecoins reduce the cost and time of cross-border remittances for consumers and businesses. ### [Tempo Documentation](/developers/) Technical documentation for integrating with Tempo's payment infrastructure. ## Take your stablecoin strategy into production Start using Tempo ### Design your stablecoin product Enterprises Build on Tempo with payments specialists, forward-deployed engineers, and global banking experts. [Talk to our team](/contact/) ### Start building Developers Build on the blockchain engineered for payments, with the tools and docs to bring your product to life. [Tempo API Platform](https://api.tempo.xyz) --- ## Embedded finance — Tempo Solutions > Source: https://tempo.xyz/solutions/embedded-finance/ > Language: en # Embedded finance powered by stablecoins Offer global stablecoin financial accounts to consumers and businesses. [Contact us](/contact/) [Build on Tempo](/developers/) > Interactive phone demo is available on the HTML page. ## Embed stablecoin payments into your product Offer stablecoin accounts Add stablecoin accounts alongside your existing products or build a fully native financial experience. Connect to your customers' preferred payment rails. - **Increase wallet share:** Retain customers with a full service financial account - **Global reach:** Unlock dollar access in 140+ countries - **Intuitive onboarding:** Onboard users in seconds with passwordless login ## Create new revenue streams Unlock new opportunities Expand margins with custom stablecoins, card payments, and savings products. Work with Tempo to design the right solutions for your business. - **Launch custom stablecoins:** Launch a stablecoin program and earn yield on reserves - **Collect interchange:** Offer stablecoin-backed cards and earn interchange - **Go beyond payments:** Enable DeFi, private credit, and money market yield ## Land and expand in high growth markets Global by default Expand into new geographies rapidly to capture emerging demand. Tempo enables secure, low-friction user onboarding, supports local onramps and offramps through trusted partners, and includes built-in compliance tools to help meet regional regulatory requirements. - **Frictionless onboarding:** Eliminate signup friction with passkey-based accounts - **Global fiat rails:** Tap into Tempo's partner ecosystem to enable onramps and offramps worldwide - **Compliance controls:** Meet local regulatory requirements with built-in compliance safeguards ## Learn more ### [Stablecoins for Global Payouts](/blog/global-payouts/) How companies use stablecoins on Tempo for cross-border payouts with sub-second settlement and sub-cent fees. ### [Stablecoins for Remittances](/blog/remittances/) How stablecoins reduce the cost and time of cross-border remittances for consumers and businesses. ### [Tempo Documentation](/developers/) Technical documentation for integrating with Tempo's infrastructure. ## Take your stablecoin strategy into production Start using Tempo ### Design your stablecoin product Enterprises Build on Tempo with payments specialists, forward-deployed engineers, and global banking experts. [Talk to our team](/contact/) ### Start building Developers Build on the blockchain engineered for payments, with the tools and docs to bring your product to life. [Tempo API Platform](https://api.tempo.xyz) --- ## Institutional settlement — Tempo Solutions > Source: https://tempo.xyz/solutions/institutional-money-movement/ > Language: en # Digital asset infrastructure for financial institutions Build digital asset solutions with institutional-grade privacy, compliance, and interoperability. [Contact us](/contact/) [Build on Tempo](/developers/) > Interactive settlement demo flow is available on the HTML page. ## Capture enterprise demand Issue digital assets Issue stablecoins, tokenized deposits and money market funds to capture growing enterprise and retail demand for digital assets. Issuing on Tempo puts your assets in front of corporate treasury, payments and savings use cases. - **Distribution:** Tap into enterprise and retail flows - **Compliance:** Ensure compliance with built-in issuer policies - **Issuer controls:** Launch KYC/KYB-restricted assets with native allowlists ## Unlock capital markets use cases Build with privacy Move funds across borders in real time and leverage tokenization to enable faster settlement for repo, margin management, and other capital markets workflows without sacrificing privacy. Tempo Zones let institutions launch private environments for their digital asset use cases without losing connectivity to public blockchains. - **Real-time:** Move funds across the globe in real time - **Privacy:** Keep customer transactions private - **Efficiency:** Unlock faster settlement and asset mobility with tokenization ## Settle with other institutions Transact with confidence Transact and settle with other institutions while meeting your regulatory requirements. Tempo enables this with built-in compliance controls and the ability to pay network fees in stablecoins or tokenized deposits. - **Interoperability:** Access liquidity and partner ecosystem on Tempo Mainnet - **Compliance:** Leverage built-in control to ensure compliance - **Predictable fees:** Pay fees in stablecoins or tokenized deposits > Interactive card settlement demo flow is available on the HTML page. ## Learn more ### [Tempo for Financial Institutions](/learn/) How financial institutions use Tempo to issue stablecoins, settle across institutions, and build digital asset solutions with built-in privacy and compliance. ### [Institutional Settlement Architecture](/developers/) Technical deep-dive into cross-institution settlement on Tempo, including Tempo Zones, tokenized deposits, and interoperability with mainnet liquidity. ### [Compliance Controls on Tempo](/blog/compliance-controls/) How Tempo's protocol-level compliance controls support KYC/AML requirements, allowlists, blocklists, and identity attestations for regulated institutions. ## Take your stablecoin strategy into production Start using Tempo ### Design your stablecoin product Enterprises Build on Tempo with payments specialists, forward-deployed engineers, and global banking experts. [Talk to our team](/contact/) ### Start building Developers Build on the blockchain engineered for payments, with the tools and docs to bring your product to life. [Tempo API Platform](https://api.tempo.xyz) --- ## Tokenized deposits | Tempo Solutions > Source: https://tempo.xyz/solutions/tokenized-deposits/ > Language: en # Issue private and interoperable tokenized deposits Tempo gives banks a private environment to issue tokenized deposits that settle 24/7. Deposits stay interoperable with stablecoins and deposits from other institutions. [Talk to our team](/solutions/tokenized-deposits/#contact) ### Keep deposit activity private Limit visibility to the bank, approved participants, and the trusted operator. ### Build compliance rules on chain Apply roles, allowlists, blocklists, pauses, freezes, and burns. ### Easily reconcile back to core systems Attribute flows by customer, account, desk, or transaction reference. ## Run a private deposit rail with open network reach ### Tempo Zones Issue and transfer deposits inside a private environment. ### Receive policies Define which assets and senders an account can accept. ### Structured memos Link each payment to ISO 20022 transaction data for easier reconciliation. ### Built-in compliance Configure roles, allowlists, blocklists, freezes, and burns. ### Virtual addresses Re-build bank deposit architecture on chain ### Stablecoin liquidity Connect approved flows to stablecoins and onchain liquidity. ## Tokenized money for regulated workflows ### Commercial deposits Represent approved customer balances in a private environment. ### Intragroup funding Move funds between entities with shared records and policy. ### Capital Markets settlement Use bank-issued money for approved counterparty flows. ### Programmable cash management Pair deposit balances with receiving and transfer controls. ## Tempo provides advisory and engineering support to get to market fast ### Prioritize the right use case Define the customer need and flow, model the economics, and map regulatory requirements. ### Design and build the product Shape the product and user experience, plan custody and liquidity, and build and integrate on Tempo. ### Launch with the right partners Connect issuers, ramps, custody, wallets, and payments, with Tempo engineers supporting launch. ## Explore tokenized deposits on Tempo > Interactive contact form is available on the HTML page. --- ## 联系 Tempo，获取支持或洽谈合作。 > Source: https://tempo.xyz/zh/contact/ > Language: zh-CN # 联系我们 欢迎介绍您正在构建的业务，我们将帮助您了解 Tempo 如何助力您打造更快、更可靠的支付基础设施。 技术问题或支持需求，请联系 [support@tempo.xyz](mailto:support@tempo.xyz)。 媒体咨询，请联系 [press@tempo.xyz](mailto:press@tempo.xyz)。 > Interactive contact form is available on the HTML page. --- ## Tempo Zones — Keep stablecoin balances and payments private > Source: https://tempo.xyz/zones/ > Language: en # Keep stablecoin balances and payments private Tempo Zones Tempo Zones let you offer private stablecoin products and retain the visibility your business needs. [Get early access](/contact/?interest=zones&cta_location=hero&message=I%27m%20interested%20in%20getting%20early%20access%20to%20Tempo%20Zones) [Explore API](/developers/docs/zones/) ## Build stablecoin products customers can trust ### Keep customer money private Offer your customers financial products with the privacy that they expect. ### Protect your competitive advantage Keep stablecoin activity inside your Zone, including revenue and treasury records. ### Built to meet your business needs Give your teams access to the records they need for support, reporting, and compliance. ## Tempo Zones add privacy to stablecoin products ### Built on your existing stack Tempo Zones work with stablecoin wallets and payments orchestration infrastructure to make payments fully private. ### Access liquidity across Tempo Connect to Tempo’s public stablecoin liquidity, Tempo Earn, and on/offramps. ### Configure your controls Built-in controls let you configure Zones for customers and account policies while automatically enforcing transaction screening. ## Zones are a private environment, connected to Tempo Visibility ### Your customers Access to their own balances and transactions. ### Your authorized teams Access to records for support, reporting, and compliance. ### The public No access to balances or activity inside the Zone. ## Deel keeps contractor balances and Earn positions private With Tempo Zones, contractors keep the familiar Deel experience, and authorized teams retain access to the records they need. [Customer story](/customer-stories/deel/) ## FAQ ### Can we make existing customer balances private? Yes. Customers can move funds from Tempo into a Zone using supported wallets. Their balances and activity inside the Zone stay private from the public. ### Who can see my transactions and balances? Balances and account activity inside a Zone stay private from the public. The business that operates the zone can see all balances and transactions within the Zone. Transfers at a Zone’s boundary are visible on Tempo. Deposits reveal the sender, token, and amount, but hide the recipient inside the Zone. Withdrawals reveal the recipient, token, and amount, but hide the sender inside the Zone. ### Can customers earn on private balances? Yes. Customers can access Tempo Earn from a Zone. Their accounts inside the Zone stay private, but actions on public Tempo remain visible. The identity of the account inside the Zone is hidden from the public. ### Do we need to operate our own Zone? You can run your own Zone or use one hosted by Tempo. In a hosted Zone, both your business and Tempo can see balances and activity. Your customers see their own accounts, and authorized teams can access records for support, reporting, and compliance. ## Build with Tempo Zones Tempo Zones are available for enterprises. Talk with our team about your setup. [Get early access](/contact/?interest=zones&cta_location=footer&message=I%27m%20interested%20in%20getting%20early%20access%20to%20Tempo%20Zones)