---
title: "How freight forwarders pay carriers, customs brokers, and agents in Latin America with stablecoins"
seoTitle: "Freight forwarder payments with stablecoins in LatAm"
description: "How freight forwarders and 3PLs pay carriers, customs brokers, and partner agents in Brazil, Mexico, and beyond with USDC: rails, documents, and timing."
date: "2026-10-10"
updated: "2026-10-10"
category: "payments"
author: "BlindPay Team"
faq:
  - q: "How can a freight forwarder pay a Mexican carrier with stablecoins?"
    a: "The forwarder holds USDC, adds the carrier's CLABE as a bank account, and requests a quote in pesos for the invoice amount. After it executes the quote, the carrier receives pesos over SPEI, which settles in minutes. The carrier gets an ordinary bank transfer. Nobody on the Mexican side needs a crypto wallet or an exchange account."
  - q: "Which documents should a freight payment carry?"
    a: "The document that proves why the money moves: the carrier's invoice, the bill of lading, a delivery slip, or the customs declaration. SWIFT payouts to a third party need one before the payment is released. On Pix, SPEI, and other local rails, a document is optional, but attaching the invoice to large or unusual payments speeds up any compliance review."
  - q: "Can a forwarder pay customs duties on behalf of its clients?"
    a: "Check the structure first. Paying your own carrier or broker invoices is paying your own obligations. Moving a shipper's money through your account to settle the shipper's duties means the funds belong economically to someone the payment provider hasn't onboarded, which matches BlindPay's definition of nesting. Talk to the provider before you design that flow."
  - q: "How do partner agents settle balances with stablecoins?"
    a: "Forwarders in an agent network usually exchange monthly statements, net what each side owes, and pay the difference. With USDC, the net balance can be paid in the partner's local currency over Pix or SPEI the day the statement is agreed, or by SWIFT where no local rail is available, with the statement attached as the document."
  - q: "Is a stablecoin payment fast enough to release cargo?"
    a: "On instant rails, usually yes. Pix in Brazil, SPEI in Mexico, and Transfers 3.0 in Argentina settle in minutes, and the payout reference is available as soon as the payout completes. ACH Colombia and TED take about 1 to 2 business days, and SWIFT up to 5. A compliance review can add time on any rail."
  - q: "Do Incoterms change who pays with stablecoins?"
    a: "No. Incoterms decide which party pays for freight, insurance, and duties at each point of the journey. The stablecoin rail only changes how that party pays. Under CIF, the seller pays main carriage; under FOB, the buyer does. Map each charge to the party that owes it, then pay from that party's own account."
---

Freight forwarders pay carriers, customs brokers, and partner agents in Latin America with stablecoins by holding USDC and paying each invoice in local currency over the country's own rail: Pix in Brazil, SPEI in Mexico, Transfers 3.0 in Argentina, ACH Colombia in Colombia, and SWIFT elsewhere. The payee gets a normal bank transfer. The forwarder skips the international wire.

The model behind it is the [stablecoin sandwich](/resources/more/what-is-a-stablecoin-sandwich): dollars become USDC, USDC crosses the border, and USDC becomes local currency at the other end. Freight just has more invoices, more countries, and less patience than most industries.

**Key takeaways**

- Forwarders pay many small, urgent invoices across many countries, the worst case for international wires.
- Local rails settle in minutes in Brazil, Mexico, and Argentina, which helps when cargo release waits on payment.
- Freight documents already exist: invoices, bills of lading, customs declarations. Use them as the payment's proof.
- Netting with partner agents still works. Pay the net balance in the partner's currency.
- Paying a client's charges with the client's money through your account is a nesting question. Settle it before you build.

## Why are freight payments hard to send by wire?

Because freight runs on many small payments with deadlines. A single shipment from Shanghai to Guadalajara can create invoices from an ocean carrier's local agent, a terminal, a customs broker, and a trucking company, each in its own country. Containers that sit past their free time pick up demurrage and detention charges, so a payment stuck in transit costs real money.

International wires were built for the opposite pattern: fewer, larger payments. The Federal Reserve's [FEDS Note of March 30, 2026](https://www.federalreserve.gov/econres/notes/feds-notes/payment-stablecoins-and-cross-border-payments-benefits-and-implications-for-monetary-policy-20260330.html) explains why. Each correspondent bank in the chain adds processing time, the payment's status is hard to see while it sits at an intermediary, and compliance checks repeat along the way. For a US$1,800 trucking invoice, the wire fee and the delay are a large share of the payment.

## Who does a freight forwarder pay?

Four groups, each with a different payment habit.

| Payee | Typical invoice | Where | Usual rail with a stablecoin payout |
| --- | --- | --- | --- |
| Trucking carriers | Per load, often weekly | Mexico, Brazil, Colombia | SPEI, Pix, ACH Colombia |
| Customs brokers | Per entry: fees plus disbursements | Mexico (agentes aduanales), Brazil (despachantes) | SPEI, Pix, TED |
| Ocean and air carriers' local agents | Local charges per bill of lading | Most ports | Local rail or SWIFT (POBO/COBO) |
| Partner forwarders (agent network) | Monthly net statement | Anywhere | Local rail or SWIFT |

Forwarders that operate as ocean transportation intermediaries in the US are licensed by the [Federal Maritime Commission](https://www.fmc.gov/resources-services/ocean-transportation-intermediaries/), and the industry's international federation is [FIATA](https://fiata.org/). Neither changes how a payment settles, but both shape the paperwork a forwarder already keeps.

## How does a stablecoin carrier payment work?

Five steps, the same for every country.

1. **Add the payee once.** Collect the carrier's legal name, tax ID, and rail identifier: a CLABE in Mexico, a Pix key or bank details in Brazil, a CBU or CVU in Argentina. The [Latin America payout cheat sheet](/resources/more/latin-america-payout-cheat-sheet) lists them by country.
2. **Quote the invoice amount.** Ask for a quote in the carrier's currency, for the exact amount billed. The rate and fees lock for 5 minutes.
3. **Approve and execute.** Send the USDC from the forwarder's wallet. Large or first-time payments should pass a second approver ([approval controls](/resources/more/stablecoin-payout-approval-controls)).
4. **Carrier gets paid.** Pesos or reais land in the carrier's account over the local rail.
5. **Close the loop.** Store the payout reference with the invoice and the shipment's bill of lading number.

For many carriers a week, run one quote per payout and execute them in a batch, the pattern in [batch payouts with live quotes](/resources/more/batch-stablecoin-payouts-live-quotes).

## Which documents should a freight payment carry?

The ones you already have. Freight is document-heavy, which helps.

On SWIFT, BlindPay creates every payout `on_hold`, and a third-party payout waits for a transaction document before release. Accepted document types include invoices, purchase orders, delivery slips, contracts, customs declarations, and bills of lading ([SWIFT deliverability](/docs/kb/swift-deliverability)). Documents are due within 30 days of payout creation and reviewed within 8 days ([SWIFT statuses](/docs/kb/swift-statuses)). [How to send a SWIFT payout from USDC](/resources/more/how-to-send-swift-payout-from-usdc) walks through the address and document rules.

On Pix, SPEI, ACH Colombia, and Transfers 3.0, no document blocks the payout. Attaching the carrier's invoice is still cheap insurance for large amounts. Set the relationship to supplier, since the carrier is a third party ([first-party vs third-party payouts](/resources/more/first-party-vs-third-party-payouts)).

## Where does a forwarder's payment become nesting?

At disbursements. Customs brokers and forwarders often advance duties, taxes, and port fees for their clients, then bill them back. Paying your own carrier for a service you bought is your obligation. Routing a shipper's money through your account to pay the shipper's duties is different.

BlindPay's [nested payments guide](/docs/kb/nested-payments) defines nesting as moving money for a party the provider hasn't onboarded or can't see. Its warning signs include funds that belong economically to someone else and documentation that names a different entity than the account holder. A customs entry in the shipper's name, paid with the shipper's money from the forwarder's account, matches both.

Two clean setups:

- **Pay from your own funds, bill later.** The forwarder pays its own broker invoice and invoices the shipper. The payment settles the forwarder's obligation.
- **Onboard the payer.** Where the shipper's money has to move, the shipper is onboarded in its own right, so every party is visible.

## How do partner agents settle with stablecoins?

The same way they net today, with a faster last step. Agents in a network exchange statements, net what each owes, and pay the residual. That's a natural hedge: flows in both directions cancel before any currency moves ([natural FX hedge](/resources/more/natural-fx-hedge-stablecoin-rails)).

Once the net is agreed, the paying agent quotes the balance in the partner's currency and pays it over the local rail. For a partner in a country without a local rail, the statement goes as the SWIFT document. Incoterms decide which side owed each charge in the first place. The [ICC Incoterms rules](https://iccwbo.org/business-solutions/incoterms-rules/) assign freight, insurance, and duties to buyer or seller at each point of delivery, and the statement should follow them line by line.

## How fast does each payee get paid?

| Country | Rail | Typical settlement |
| --- | --- | --- |
| Brazil | Pix, PIX Safe | Minutes |
| Brazil | TED | About 1 to 2 business days |
| Mexico | SPEI | Minutes |
| Argentina | Transfers 3.0 | Minutes |
| Colombia | ACH Colombia | About 1 to 2 business days |
| Other countries | SWIFT (POBO/COBO) | Up to 5 business days |

Timing per the [payment methods reference](/docs/kb/payment-methods). A compliance review can add time on any rail, and slower rails follow bank calendars ([cut-offs, weekends, and holidays](/resources/more/stablecoin-payout-cut-off-times-weekends-holidays)). Some Brazilian carriers bill by boleto; those can be paid from stablecoins too ([paying invoices and boletos with stablecoins](/resources/more/how-to-pay-invoices-with-stablecoins-api)).

## How does BlindPay handle this?

BlindPay pays out from USDC or USDT over Pix, PIX Safe, TED, SPEI, ACH Colombia, Transfers 3.0, and SWIFT (POBO/COBO) with UETR tracking and MT103 confirmations, so a terminal agent can match the payment to the bill of lading. Each quote locks the rate and fees for 5 minutes, in the forwarder's currency or the carrier's. KYB on the forwarder and KYC or KYB on payees run inside the same API. BlindPay combines a monthly plan with per-transaction fees that vary by rail and network, disclosed in the live quote before execute.

## What to do next

Pull last month's carrier and broker invoices and sort them by country and amount. The pile of small invoices to Mexico and Brazil is where wire fees hurt most, so price three of them on a BlindPay development instance with the [payout quotes docs](/docs/payout-quotes) and compare against what the wires cost.