How freight forwarders and 3PLs pay carriers, customs brokers, and partner agents in Brazil, Mexico, and beyond with USDC: rails, documents, and timing.
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: 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
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 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.
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, and the industry's international federation is FIATA. Neither changes how a payment settles, but both shape the paperwork a forwarder already keeps.
Five steps, the same for every country.
For many carriers a week, run one quote per payout and execute them in a batch, the pattern in batch payouts with live quotes.
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). Documents are due within 30 days of payout creation and reviewed within 8 days (SWIFT statuses). How to send a 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).
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 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:
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).
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 assign freight, insurance, and duties to buyer or seller at each point of delivery, and the statement should follow them line by line.
| 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. A compliance review can add time on any rail, and slower rails follow bank calendars (cut-offs, weekends, and holidays). Some Brazilian carriers bill by boleto; those can be paid from stablecoins too (paying invoices and boletos with stablecoins).
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.
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 and compare against what the wires cost.
Always cheaper? No intermediaries? Recipient needs a wallet? 10 common claims about cross-border stablecoin payments, checked against the Fed and the BIS.
Seven places blockchain payments beat bank rails: contractor payroll, remittances, B2B suppliers, marketplaces, 24/7 treasury, bill pay, and PSP payouts.
The dates that turned stablecoins from a trading tool into cross-border payment rails: USDC, Pix, MiCA, the GENIUS Act, ISO 20022, and Visa settlement.