diff --git a/src/pages/learn/tempo/modern-transactions.mdx b/src/pages/learn/tempo/modern-transactions.mdx
index 30ff3e8..7a83db4 100644
--- a/src/pages/learn/tempo/modern-transactions.mdx
+++ b/src/pages/learn/tempo/modern-transactions.mdx
@@ -10,6 +10,8 @@ Tempo has built-in support for gas sponsorship, batch transactions, scheduled pa
On other chains, even when available, these are generally add-on functionalities that require third-party providers to unlock. By natively enabling these features at the protocol level, developers on Tempo can deploy payment logic without managing additional middleware or custom contracts, and can build to enshrined standards.
+Tempo Transactions are built into the protocol so developers don't need custom smart contracts or third-party middleware to get batching, sponsorship, scheduling, and modern auth. This reduces integration risk and operational overhead for payment applications.
+
## Batched Payments
Payment processors and platforms often need to send thousands of payments at once (e.g., payroll runs, merchant settlements, customer refunds). Tempo supports batch transactions where multiple operations execute atomically in a single transaction.
@@ -22,6 +24,10 @@ Applications often want to pay transaction fees on behalf of their users. For in
Tempo's protocol-level fee sponsorship allows an account to sign a transaction while a separate sponsor (typically the application) pays the gas fee. This means end users can interact with your application without holding any tokens for fees, dramatically lowering the barrier to entry.
+## Configurable Fee Tokens
+
+Tempo supports paying transaction fees in USD-denominated stablecoins. This removes the need for users to acquire a volatile gas token and simplifies accounting for payment applications operating in dollars. Users can pay fees in any supported USD stablecoin, and the protocol handles conversion automatically.
+
## Scheduled Payments
The Tempo transaction type includes scheduling as a protocol feature. Users can specify a time window for transaction execution, and validators will include the transaction when it becomes valid.
@@ -35,3 +41,56 @@ Tempo supports passkey authentication through WebAuthn/P256 signature validation
Their keys are stored in their device's secure enclave, and passkeys sync across devices via services they already use such as iCloud Keychain or Google Password Manager. This way, users don't need to secure a 12 or 24-word seed phrase for traditional wallets. For payment applications, this means onboarding flows can be as simple as existing consumer apps, without sacrificing security.
Tempo uses an [EIP-2718](https://eips.ethereum.org/EIPS/eip-2718) transaction type with native support for these features.
+
+## Use Cases
+
+Tempo Transactions provide the features necessary to bring a wide range of payment use cases onchain:
+
+### 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.
+
+See: [Global payouts with stablecoins](/learn/use-cases/global-payouts)
+
+### 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.
+
+### 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.
+
+See: [TIP-20 Tokens](/learn/tempo/native-stablecoins) for stable fees and payment memos.
+
+### Subscriptions
+
+Scheduled transactions automate recurring payments and enable true subscription services onchain. No need for external automation services or custom smart contracts.
+
+## Partner Ecosystem
+
+Infrastructure partners including [Crossmint](https://www.crossmint.com/), [Fireblocks](https://www.fireblocks.com/), [Privy](https://www.privy.io/), and [Turnkey](https://www.turnkey.com/) support Tempo Transactions and can help accelerate your development. Visit the [Ecosystem](https://tempo.xyz/ecosystem) to explore Tempo's growing network of partners.
+
+For partner testimonials and rollout context, see [Introducing Tempo Transactions](https://tempo.xyz/blog/tempo-transactions).
+
+## Next steps
+
+
+
+
+
+
diff --git a/src/pages/learn/tempo/native-stablecoins.mdx b/src/pages/learn/tempo/native-stablecoins.mdx
index d609d15..7c25929 100644
--- a/src/pages/learn/tempo/native-stablecoins.mdx
+++ b/src/pages/learn/tempo/native-stablecoins.mdx
@@ -24,12 +24,16 @@ For wallets and custodians, this removes the need to hold a balance of new crypt
Costs are predictable and low: TIP-20 transfers target one-tenth of a cent per transaction. This removes a major barrier for mainstream adoption. Users can interact with Tempo using only the stablecoins they're already familiar with, without needing to understand or manage volatile crypto assets.
+For how applications sponsor fees and batch payments, see [Tempo Transactions](/learn/tempo/modern-transactions).
+
## Native Reconciliation
Tempo's TIP-20 tokens can natively attach a short memo directly to each transfer. This mirrors traditional payment systems, where every transaction carries context (e.g., an invoice number, a customer ID, a cost center, or a simple reference note) for backend systems to automatically match payments to internal records.
For larger memos, Tempo supports flexible approaches where only a commitment (like a hash or locator) travels onchain while the full data (including PII) lives off-chain. This means finance teams can automatically match payments to invoices and payment processors can embed the structured data their systems need without custom solutions or integration with third-party reconciliation infrastructure.
+See stablecoin reconciliation in practice: [Global payouts](/learn/use-cases/global-payouts) and [Tokenized deposits](/learn/use-cases/tokenized-deposits).
+
## Built-in Compliance
Stablecoin (and other regulated asset) issuers operate under regulatory requirements. They need to enforce whitelists (only approved addresses can transact) or blacklists (sanctioned addresses cannot transact).
@@ -39,3 +43,83 @@ Tempo provides a shared compliance infrastructure through the TIP-403 Policy Reg
## 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.
+
+## When TIP-20 matters
+
+Use TIP-20 when you need:
+
+- **Predictable throughput** for large payment runs without congestion-driven fee spikes.
+- **Stable-denominated fees** for simpler unit economics.
+- **Reconciliation metadata** to tie onchain transfers to invoices and ERP records.
+- **Shared compliance enforcement** across multiple regulated assets.
+
+For basic token functionality without these requirements, standard ERC-20 contracts work on Tempo as they do on any EVM chain.
+
+## Use Cases for Custom Stablecoins
+
+Beyond peer-to-peer payments, custom stablecoins built on TIP-20 can be designed for specific treasury, settlement, and foreign exchange 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.
+
+### 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.
+
+### 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.
+
+### 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.
+
+### 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.
+
+## FAQs
+
+### Is TIP-20 compatible with ERC-20 tooling?
+
+TIP-20 extends ERC-20 semantics for payment-scale features while remaining familiar to EVM developers. Most indexers and wallet patterns still apply, but advanced features (memos, policy registry) require TIP-20-aware integrations.
+
+### How big can a reconciliation memo be?
+
+TIP-20 supports short onchain memos for common references (invoice ID, customer ID). For larger data, store details offchain and put only a commitment or locator onchain to avoid leaking PII.
+
+### How should issuers handle compliance updates?
+
+Use the TIP-403 Policy Registry so multiple tokens can share a policy and inherit updates automatically, rather than updating each token contract individually.
+
+## Infrastructure Partners
+
+Work with infrastructure partners who are rolling out TIP-20 support to accelerate your development:
+
+- [AllUnity](https://allunity.com/) - Regulated euro stablecoins for European corporates
+- [Bridge](https://www.bridge.xyz/) - Custom regulated stablecoin issuance with off-the-shelf templates
+- [LayerZero](https://layerzero.network/) - Cross-chain token extensions for Tempo's payment ecosystem
+
+## Related reading
+
+
+
+
+
+
diff --git a/src/pages/learn/use-cases/global-payouts.mdx b/src/pages/learn/use-cases/global-payouts.mdx
index 2717d24..9c94bc0 100644
--- a/src/pages/learn/use-cases/global-payouts.mdx
+++ b/src/pages/learn/use-cases/global-payouts.mdx
@@ -3,7 +3,6 @@ description: Deliver instant, low-cost payouts to employees and contractors worl
---
import { Cards, Card } from 'vocs'
-import { ZoomableImage } from "../../../components/ZoomableImage.tsx"
# Pay your global workforce instantly [Deliver faster, cheaper, and more predictable cross-border payouts to employees and contractors around the world with stablecoins.]
@@ -14,12 +13,63 @@ Managing global payroll is both complex and expensive. Businesses must either re
This complexity results in a patchwork of manual workflows that is burdensome for finance teams and often frustrating for employees waiting on delayed transfers. Stablecoins offer a way to simplify this process by reducing cost, improving predictability, and removing much of the operational overhead associated with traditional cross-border payments.
+## The real cost of traditional 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.
+
+## Common pain points this removes
+
+Traditional cross-border payouts fail in predictable ways:
+
+- **High all-in cost:** Fees plus FX spread leakage compounds at scale.
+- **Slow settlement:** 3-5 business days plus holidays and cutoffs.
+- **Failures and reconciliation overhead:** Incorrect recipient details or intermediary issues create manual rework.
+- **Currency volatility exposure:** Recipients can lose value between send and receive.
+
## How stablecoins solve this
Blockchains are global by design, allowing companies to send stablecoin payouts directly to employees' wallets anywhere in the world without relying on local banks or intermediaries. These transfers typically cost less than a cent and arrive within seconds, offering far more consistency than traditional international payment rails.
+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** 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.
+
+Cost reduction note: Traditional wire fees on a $1,000 payout typically range $10-$40 (1-4%) excluding FX spreads. Stablecoin onramp fees range from 0.1-0.4%. Comparing 0.4% vs 1.0% yields approximately 60% reduction; higher savings occur vs higher wire fees and FX spreads.
+
Companies can also choose to distribute funds through their subsidiaries. In this model, a business can convert funds into stablecoins at the headquarters level, such as in the United States, and distribute those funds to subsidiary wallets around the world. Liquidity moves to subsidiaries in seconds rather than days, removing the need to pre-fund subsidiary accounts in advance. Subsidiaries can then handle payouts to local employees.
+## Key benefits
+
+
+
+
+
+
+
+For structured payment references (invoice IDs, customer IDs), see [TIP-20 Tokens](/learn/tempo/native-stablecoins).
+
+
+
+
+
## Benefits beyond speed and cost
@@ -31,6 +81,40 @@ Finally, reconciliation becomes significantly simpler. Because stablecoin payout
Global payouts with stablecoins already deliver meaningful benefits for both employers and employees. As familiarity grows and merchant acceptance expands, stablecoins are likely to become a preferred payment method not only for international payouts, but for domestic payroll as well. With lower costs, real-time settlement, and programmability, stablecoins bring payroll systems closer to the always-on, digital nature of today's workforce.
+For native batching and scheduled payout execution, see [Tempo Transactions](/learn/tempo/modern-transactions).
+
+## Evaluating stablecoins for global payouts
+
+Stablecoin adoption starts with a clear business use case. Before evaluating vendors or integration paths, consider this framework:
+
+- **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
+
+Payouts are one of the cleanest entry points for stablecoins because you can pilot quickly and measure impact.
+
+### Step 1: Clarify the business case
+
+Pick your highest-friction corridor (e.g., U.S. to Brazil, Philippines, or Nigeria). Identify where fees, failed payments, or delays create real pain.
+
+### Step 2: Choose an integration approach
+
+Decide whether to **buy** (provider abstracts custody, liquidity, compliance) or **build** (you assemble wallets, custody, bank rails, and potentially licensing).
+
+### Step 3: Run a pilot
+
+Run stablecoin payouts alongside your existing system for approximately 60 days. Track delivery time, net recipient received, support tickets, and reconciliation effort.
+
+### Step 4: Operationalize
+
+Define SLAs, exception handling, reconciliation processes, and support playbooks, then expand corridors and automate what was manual.
+
## Building with Tempo
Designed for high-volume, global disbursement, Tempo allows organizations to bypass the fragmentation of local banking rails and reach employees and contractors directly. We work closely with payroll providers and platforms to design stablecoin payout flows that are compliant, efficient, and user-friendly.
@@ -51,3 +135,48 @@ If you are interested in seeing how a unified onchain ledger can simplify your g
title="Build on Tempo"
/>
+
+## FAQs
+
+### 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.
+
+## Related reading
+
+
+
+
+
+
diff --git a/src/pages/learn/use-cases/tokenized-deposits.mdx b/src/pages/learn/use-cases/tokenized-deposits.mdx
index e1d615c..1ccad31 100644
--- a/src/pages/learn/use-cases/tokenized-deposits.mdx
+++ b/src/pages/learn/use-cases/tokenized-deposits.mdx
@@ -3,7 +3,6 @@ description: Move treasury liquidity instantly across borders with real-time vis
---
import { Cards, Card } from 'vocs'
-import { ZoomableImage } from "../../../components/ZoomableImage.tsx"
# Move treasury liquidity instantly across borders [Enable corporate treasury teams to improve liquidity management across banks, currencies, and regions with tokenized deposits.]
@@ -14,6 +13,12 @@ Operating across multiple geographies requires companies to maintain relationshi
Moving liquidity between a company's own accounts can take days and require subsidiaries to hold excess cash "just in case." Visibility into cash positions is incomplete, workflows vary by region, and reconciling activity across dozens of accounts becomes an ongoing operational burden. The result is inefficient use of capital and a patchwork of manual processes for controls and compliance.
+For companies operating across multiple jurisdictions, correspondent banking creates three specific problems:
+
+- **Higher borrowing costs** from trapped cash that cannot be deployed efficiently
+- **Suboptimal hedging** based on incomplete or delayed data from disconnected systems
+- **Excess bank fees** for accounts holding idle liquidity across regions
+
## How tokenized deposits and stablecoins solve this
Tokenized deposits and stablecoins offer a path toward simplifying this complexity. Instead of managing dozens of accounts across multiple banks, companies can operate a single wallet per subsidiary. Sitting alongside traditional bank accounts, these digital wallets become a natural extension of corporate treasury operations and provide a more efficient way to manage global liquidity.
@@ -26,6 +31,36 @@ Each wallet can hold stablecoins, tokenized deposits, and even tokenized money m
- **Idle balances can be deployed more efficiently**, improving working-capital usage and enabling immediate access to interest-bearing tokenized assets;
- **Treasury workflows such as approvals, sweeps, and controls can be automated** with smart contracts, reducing manual processes and operational overhead.
+See also: [Global payouts with stablecoins](/learn/use-cases/global-payouts) for the outbound payments use case. For payment references and structured metadata, see [TIP-20 Tokens](/learn/tempo/native-stablecoins). For batching and scheduled treasury movements, see [Tempo Transactions](/learn/tempo/modern-transactions).
+
+## How stablecoins fit into treasury workflows
+
+Stablecoins are most useful when they remove timing and intermediary constraints (cutoff times, weekends, correspondent banks). Common first deployments:
+
+- **Intercompany settlements:** Move USD liquidity between parent and subsidiary entities instantly and settle back to bank accounts on your own schedule.
+- **Cash positioning and forecasting:** Use onchain balances as a real-time view of global liquidity rather than end-of-day bank reports.
+- **International payouts:** Use stablecoins as the settlement leg for high-volume payouts; recipients can receive stablecoins or be paid in local currency via offramps.
+
+## Current limitations
+
+Stablecoins complement bank accounts rather than replace them. Key constraints to plan for:
+
+- **Limited non-USD liquidity:** Most stablecoin liquidity is USD-denominated; EUR and GBP liquidity is improving but thinner.
+- **Off-ramping coverage varies:** Not all markets have reliable bank offramps yet.
+- **Custody and controls:** Decide between self-custody vs institutional custody (multi-sig, insurance, governance).
+- **Systems integration:** Treasury systems may need adapters for onchain settlement data.
+- **Operational risk differs by asset and network:** Prefer regulated, 1:1 reserve-backed assets; evaluate chain uptime and fee variability.
+
+## Reconciliation and operational risk
+
+### Automated GL reconciliation
+
+Fast settlement only matters if transactions reconcile cleanly. Use transfer metadata (e.g., invoice ID, cost center, GL code) so treasury movements can auto-post back into ERP/TMS. Tempo TIP-20 supports native transfer memos designed for reconciliation: see [TIP-20 Tokens](/learn/tempo/native-stablecoins).
+
+### Controls and auditability
+
+24/7 rails require strong approval policy. Enforce role-based permissions and programmable approvals so each movement is attributable and auditable end-to-end.
+
## Understanding tokenized deposits vs. stablecoins
As digital wallets become integrated into corporate treasury operations, it is important to understand how stablecoins and tokenized deposits differ. They are distinct instruments with different issuers, obligations, and regulatory treatment:
@@ -44,6 +79,66 @@ The main challenge for banks today is interoperability. Most tokenized deposit p
Public blockchains provide this missing bridge. They allow tokenized deposits from different banks to coexist on shared infrastructure, enabling frictionless swaps between tokenized deposits and stablecoins, and supporting cross-bank liquidity movement with the same speed as stablecoin rails. Banks that issue tokenized deposits on public chains gain the interoperability corporates require, while strengthening their role at the center of onchain financial flows.
+## Key questions to answer
+
+Before engaging providers, answer these questions:
+
+1. **What problem are you solving?** Identify your highest-value use case: reducing FX costs, accelerating intercompany transfers, or improving cash visibility in specific regions.
+2. **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.
+3. **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
+
+- **Assess pain points:** Where is cash trapped (weekends, slow corridors, expensive FX)?
+- **Build a business case:** Compare current fees, spreads, and delays vs stablecoin rails using your own data.
+- **Choose build vs buy:** Many teams start with infrastructure providers that handle custody, on/offramps, and compliance.
+- **Pilot a contained flow:** Start with one region or corridor and run in parallel before expanding.
+
+## FAQs
+
+### 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.
+
+### 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:
+
+1. Payment instruction originates in ERP/TMS
+2. Instruction routes to a stablecoin infrastructure provider
+3. Settlement occurs onchain
+4. Confirmation and settlement data flows back to TMS
+5. Accounting entries are generated automatically
+
+Tempo offers ISO 20022-compatible messaging, simplifying integration for teams already working with SWIFT MT messages.
+
## Building with Tempo
Tempo provides the neutral, high-performance infrastructure required for tokenized deposits and stablecoins to operate side-by-side. For treasury teams looking to modernize their liquidity stack, the challenge is often interoperability between these assets and existing banking systems. We collaborate with financial institutions and enterprises to model how these assets can coexist within your current treasury operations. Let's examine how onchain rails can fit into your broader liquidity management strategy.
@@ -62,3 +157,26 @@ Tempo provides the neutral, high-performance infrastructure required for tokeniz
title="Build on Tempo"
/>
+
+## Related reading
+
+
+
+
+
+
diff --git a/vite.config.ts b/vite.config.ts
index 2eafcb3..96bbb99 100644
--- a/vite.config.ts
+++ b/vite.config.ts
@@ -38,9 +38,7 @@ function syncTips(): Plugin {
console.log('→ syncing TIPs from GitHub...')
- const res = await fetch(
- `https://api.github.com/repos/${repo}/contents/tips`,
- )
+ const res = await fetch(`https://api.github.com/repos/${repo}/contents/tips`)
if (!res.ok) {
console.error('✗ failed to fetch TIPs directory:', res.statusText)
return