<!-- tempo-docs-context -->
> Source: [/docs/resources/guides/cross-border-payments-latin-america](https://tempo.com/developers/docs/resources/guides/cross-border-payments-latin-america.md)
> Section: [Get Started](https://tempo.com/developers/get-started.md). Choose a starting point, send a test payment, get testnet funds, connect a coding agent, find the SDKs and CLI, and use the resource guides to plan payment workflows, liquidity, provider selection, and partner integrations.
> [Documentation index](https://tempo.com/developers/llms.txt) · [Docs skill](https://tempo.com/developers/SKILL.md)

> Tempo MCP: Use `search`, `find_pages`, `read_page`, and `code` at `https://mcp.tempo.xyz` for Tempo and related documentation.
> If an indexed page is missing or reflects an older site, read this site’s [documentation index](https://tempo.com/developers/llms.txt) and Markdown pages directly.

[Guides](https://tempo.com/developers/docs/resources/guides) / [Payment workflows](https://tempo.com/developers/docs/resources/guides#payment-workflows) / Plan Latin America payment routes

# Plan Latin America payment routes

Cross-border stablecoin payments in Latin America connect an onchain settlement leg with country-specific funding, conversion, and delivery services. Evaluate one country and delivery method at a time using the [cross-border payment checklist](https://tempo.com/developers/docs/resources/guides/cross-border-payments). Use [Routes](https://tempo.com/developers/docs/routes) for its supported cross-network stablecoin operations.

Companies paying suppliers, contractors, sellers, or subsidiaries across Latin America work across different currencies, banks, and domestic payment systems. A useful route makes the recipient amount and delivery status clear while preserving evidence from every leg.

## Map country-specific payment requirements

A flow that works in Brazil can require a different provider, currency workflow, beneficiary record, and reconciliation process in Mexico, Colombia, Argentina, or Peru.

| Requirement | Operating implication |
| --- | --- |
| Funding and settlement timing | Bank funding, onchain delivery, conversion, and local payout have separate clocks. |
| Local currency | A USD-denominated stablecoin keeps that leg in dollars; a recipient spending in another currency still carries FX exposure. |
| Domestic rail | The payout provider must support both the stablecoin and the domestic rail. |
| Payment visibility | Link the invoice or payroll obligation to each network and provider identifier. |
| Recipient access | Verify the wallet, bank, account type, limits, and required beneficiary details. |

Stablecoin settlement can connect approved wallets and providers between these endpoints. Local banks, conversion providers, and payout services retain their own availability and operating requirements.

## Match the route to the business use case

**Payroll and contractor payouts** start with approved compensation and a worker's payment preference. Determine whether the worker wants a stablecoin balance or a local payout. A fast onchain leg is useful only if the worker can access the promised funds. See [stablecoin payroll](https://tempo.com/developers/docs/resources/guides/stablecoin-payroll-for-global-teams).

**Marketplace settlements** need seller eligibility, release rules, accurate beneficiary details, and an order or payout reference. The platform can share onchain infrastructure across markets while maintaining country-specific provider configurations.

**Treasury transfers** need clear entity ownership, custody controls, funding limits, and reconciliation. Model the balances each provider needs; faster settlement doesn't eliminate prefunding.

**Remittance and supplier payments** require an agreed delivery currency and endpoint. Preserve the recipient's requested local amount, conversion quote, and final delivery evidence. Settlement between providers is a separate step from delivery to the recipient.

## Verify local delivery country by country

Before funding a payment, verify one complete route: the sender's country and funding currency, the stablecoin and network, the recipient's eligibility, any conversion, and the final delivery method.

| Route detail   | Evidence to request                                                                                       |
| -------------- | --------------------------------------------------------------------------------------------------------- |
| Sender access  | The provider accepts this individual or business, origin country, funding method, and payment purpose.    |
| Asset support  | Deposit instructions name the network and token contract; withdrawal support is checked separately. |
| Local delivery | The required bank account, wallet, or other endpoint is supported for this recipient and amount.          |
| Conversion     | A current quote states the local-currency amount, applicable fees, expiry, and conversion timing.         |
| Completion     | A payment reference and delivery status can be matched to the beneficiary, invoice, and amount.           |
| Exceptions     | The provider explains delayed delivery, rejected beneficiary details, returns, and refunds.               |

Use the same worksheet for Brazil, Mexico, Colombia, Argentina, Peru, and other markets. Check that the provider accepts the asset on Tempo specifically. For Tempo Routes, use the [network and asset directory](https://tempo.com/developers/docs/routes/networks) and quote the actual payment inputs.

### Brazil: separate Pix delivery from the cross-border route

Use [Banco Central do Brasil's Pix information](https://www.bcb.gov.br/en/financialstability/pix_en) to understand the domestic system. A Pix payout also needs a provider that accepts your stablecoin, converts it to BRL, and delivers the payment.

For a proposed Brazil payout, request the provider's current asset and network instructions, eligible recipient details, BRL quote, payout limits, and evidence of the final Pix delivery. Keep the onchain transaction and the provider's local payout reference together.

### Mexico: distinguish a SPEI payment from beneficiary credit

[SPEI is operated by Banco de México](https://www.banxico.org.mx/services/interbanking-electronic-payme.html) and moves payments between accounts through financial institutions. A proposed stablecoin-to-MXN payout still needs a provider that supports the complete route.

Banco de México's [payment-status guidance](https://www.banxico.org.mx/servicios/mi-spei_-transferencias-ban.html) distinguishes settlement in SPEI from credit to the beneficiary. Its electronic payment receipt, the CEP, is generated from the receiving institution's confirmation of that credit. Ask which payout identifiers and delivery evidence your provider supplies, then connect those records to the original payment.

### Compare the amount recipients can use

For a contractor expecting local currency, compare quotes for the same local-currency delivery. For a contractor choosing to retain a dollar-denominated balance, explain the supported asset, custody model, and withdrawal options. A dollar-pegged token isn't a dollar bank deposit, and converting it later still costs FX.

A treasury team should also model where liquidity must be available before the payout. [Prefunding](https://tempo.com/developers/docs/resources/guides/prefunding) can move between providers or accounts when the settlement architecture changes; a stablecoin leg doesn't remove it.

## Implement the settlement and reporting path

Use [Send payments](https://tempo.com/developers/docs/guide/payments/send-a-payment) for direct supported stablecoin transfers. Choose [atomic batches or independent transactions](https://tempo.com/developers/docs/resources/guides/batch-payments) according to the required failure boundary. Your application schedules and submits recurring runs.

Attach an opaque [payment reference](https://tempo.com/developers/docs/guide/payments/transfer-memos) and keep sensitive payroll, supplier, and bank data offchain. Save the network, transaction hash, and transfer log index, then connect them to the local payout reference. Recover missed events and process each transfer once.

Use the [fee documentation](https://tempo.com/developers/docs/protocol/fees) to choose eligible fee tokens and estimate actual execution. Include funding, FX, provider charges, and local delivery in the complete cost comparison.

For private balances, see [Zones](https://tempo.com/developers/docs/zones) and its [privacy model](https://tempo.com/developers/docs/zones/privacy). A Zone's operator can read its ledger, deposit and withdrawal amounts are public, and the current runtime disables general TIP-20 transfers.

## Latin America payment questions

<details>
  <summary>How do businesses send money across Latin America?</summary>

  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.
</details>

<details>
  <summary>What should companies evaluate before using stablecoin payment rails?</summary>

  Companies should evaluate compliance, custody, privacy, reconciliation, local payout coverage, FX conversion, off-ramp availability, and issuer risk.
</details>

<details>
  <summary>What are the main challenges of cross-border payments in Latin America?</summary>

  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.
</details>

<details>
  <summary>Does Pix or SPEI availability prove a Tempo payout route is supported?</summary>

  No. Before funding a payment, confirm the provider, sender and recipient eligibility, asset and network, conversion quote, and final delivery method.
</details>

<details>
  <summary>Does a confirmed onchain transfer prove the recipient received local currency?</summary>

  No. Verify local delivery with the payout provider or receiving institution. Link the onchain transaction to the payout identifier, beneficiary, currency, amount, and delivery evidence in your payment records.
</details>
