Freight forwarders pay carriers, customs brokers and partner agents with stablecoins by holding the dollar stablecoin USDC and settling each invoice in the payee's local currency over that country's own bank rail. The payee receives an ordinary domestic transfer and never handles a stablecoin, and the forwarder avoids sending an international wire for every invoice.
Best for: forwarders, 3PLs and customs brokers paying many small invoices to payees in Brazil, Mexico and Colombia.
Skip it if: you need to move a shipper's money through your own account to pay the shipper's duties.
A trucker's invoice lands on a Saturday, the container cannot leave the terminal until it is paid, and the wire desk opens on Monday.
Why a freight invoice strains an international wire
Freight runs on many small payments that cannot wait; a wire suits fewer, larger ones. The Federal Reserve's FEDS Note of March 30, 2026 describes the friction for individuals and small banks: they reach foreign markets through correspondent banks, so each payment takes longer, its status is harder to see and the cost of the chain lands on the sender. The note says stablecoins could reduce that intermediation, not remove it.
The freight reading is ours, not the note's. Time in transit is time a container sits without a release, and a payment nobody can see cannot be matched to a bill of lading. Small tickets also pay the most in proportion: BIS Working Paper 1385 (October 2026) puts the median cost of money transfer operators at roughly 200 to 300 bps on US$200, falling to about 40 to 130 bps on US$10,000. The trucking leg is the small ticket.
Who does a forwarder pay, and over which rail?
The payees are trucking carriers paid per load, customs brokers paid per entry, local agents paid per bill of lading and partner forwarders paid on a net statement. The rail follows the payee's country, not its type.
Rails a forwarder can use to pay each payee on Lumx, from the Lumx documentation read on November 1, 2026, as confirmed by Lumx for Colombia.
Payee location | Rail | Cut-off | Settlement |
Brazil | Pix | None | Instant, 24/7/365 |
Mexico | SPEI | None | Instant, 24/7/365 |
Colombia, invoice up to COP 12,110,000 | Bre-B | None | Instant |
Colombia, larger invoice | ACH Colombia | Pay ahead of release | Pay ahead of release |
United States | ACH or FEDWIRE | 2:00 PM ET or 3:00 PM ET | ACH 1 to 2 business days; FEDWIRE same business day |
Euro area | SEPA | None | Instant; payments of EUR 100k or more sent between 4:30 PM and 2:30 AM UK time go by SEPA Credit Transfer, same or next business day |
United Kingdom | Faster Payments | None | Instant, up to £1M per payment |
Anywhere else | SWIFT in USD | 3:00 PM ET | 1 to 5 business days, with UETR and MT103 |
Pix (Brazil's instant payment system) takes a Pix key: CPF (individual tax ID), CNPJ (company tax ID), email, phone or random key. It runs on weekends, so the Saturday invoice does not wait for Monday. SPEI (Mexico's interbank transfer system) takes a CLABE (the 18-digit bank account number). Rates: USDC to BRL, USDC to MXN.
Bre-B (Colombia's instant payment system) uses the key the carrier holds. The central bank caps it at 1,000 UVB per operation, which is COP 12,110,000 in 2026, about US$2,870 (Circular Reglamentaria Externa DSP-465, Asunto 18, numeral 3.2, March 31, 2026). The cap binds every provider. On Lumx a Bre-B payout above it is refused, never split or diverted. A trucker billed per load fits Bre-B.
A terminal or broker billing in bulk belongs on ACH Colombia, which takes bank details and has no per-payment limit.
PSE (Colombia's online bank-transfer network) collects and never pays.
On Lumx the forwarder registers each payee once as a destination, and the destination carries the rail. On Pix the carrier's statement shows the forwarder's legal name as the payer, so nobody on the payee side has to recognise an intermediary.
How a stablecoin carrier payment works
Register the payee once, with its legal name, tax ID and the identifier its rail needs.
Quote the invoice. On every rail in the table, including Bre-B and ACH Colombia, the request can name the invoice amount as the target, so the carrier receives the amount on the invoice and the source amount follows. The rate holds for the lock window, at most five minutes, and an approval that runs longer needs a new quote.
Approve and send from the forwarder's wallet.
The carrier is paid over its local rail. The payment is complete when the funds leave the banking partner.
Store the payment reference with the invoice and the bill of lading number.
The lock lasts 30 seconds, one minute or five minutes: the 30-second lock itself carries no fee, and the longer ones carry a fee for the volatility they cover. The quote shows the base rate and the final rate, so the FX is visible before approval. For weekly runs, see batch payouts with live quotes.
Three things should be settled when the payment is created.
Purpose code. Every payment on Lumx carries one, and the docs say to pick the most specific code that describes the commercial activity. The docs describe TRADE_TRANSACTIONS as supplier invoices and import/export settlement, which fits carrier and terminal invoices. A broker's filing fee could also read as PROFESSIONAL_SERVICES, so agree the choice for broker fees with Lumx compliance before the first run. A misclassified purpose can hold the payment or raise an RFI (request for information, a compliance hold that asks for a document before a transaction clears).
Relationship. The destination's holder relationship for a carrier or broker is SUPPLIER.
Memo and metadata. The request also takes an optional memo as the reference on the transfer and a metadata object, so the invoice number, the bill of lading and the shipment reference stay attached to the payment record.
Lumx runs the final leg as a stablecoin off-ramp from the forwarder's wallet to the payee's destination and sends a webhook at each status, ending in success or failed. The offramp.success event marks the moment the money leaves the banking partner.
What does a carrier payment cost compared with a wire?
Two numbers matter: what the sender pays in total and what the payee receives. The table shows where cost sits on each side.
Cost components of paying one carrier invoice. The Lumx column is from Lumx's pricing model and the Lumx documentation read on November 1, 2026.
Component | International wire | Lumx stablecoin payout | What to ask each provider to quote |
Sender fee | A per-wire fee set in the sending bank's published fee schedule | Monthly platform fee plus usage-based per-transaction fees, set in the customer's agreement | The fee for this payment, in writing |
FX margin | Built into the bank's rate and often not shown | Transparent FX on locked quotes: the quote shows the base rate and the final rate | Mid-market rate against the rate you receive |
Intermediary deductions | Correspondent banks may take a cut before the payee is credited | Nothing deducted from the amount on Pix, SPEI or Bre-B | The exact amount the payee will receive |
What the payee receives | The invoice amount minus any deduction, known after the fact | The target amount on the rails that support it, with the 30-second lock carrying no fee | The received amount as a fixed figure, not an estimate |
The 30-second lock itself carries no fee, which does not make FX free: the rate carries its own spread, which is why the quote shows both rates. The right comparison is the all-in cost of the same invoice, and the total depends on the customer's agreement. For a run of forty invoices, ask each provider for the same four lines and add them up. The float on a funded wallet is covered in pre-funding cross-border payouts.
Onboarding a forwarder and the Brazilian authorisation
The payee receives local currency over a domestic rail. On the Brazilian side, Lumx applied for SPSAV authorization and operates in the transition regime of Resolução BCB 520/2025, Art. 88. The peso leg in Colombia runs under a banking partner's sponsored program, not a licence of Lumx's own. A forwarder is onboardable through standard KYB (know your business, the verification of a company and its owners): the industry list includes LOGISTICS_CUSTOMS_TRANSPORT, and it is not on the high-risk list. What Brazil, Mexico or Colombia require of the carrier, and how the forwarder treats the payment for tax and customs, sits with the forwarder's own advisers. On Lumx, KYB covers the forwarder and each destination is verified before a payment goes out.
Where nesting starts: shipper disbursements and partner statements
A forwarder often advances duties and port fees for a shipper and bills them back. When the forwarder contracts with the carrier as principal, paying that carrier is the forwarder's own obligation. Moving a shipper's money through its account to pay the shipper's duties is a different flow.
Lumx's nested payments rule reduces it to one test: whose money is it, and whose business does it pay for? If both answers are the onboarded customer, the payment fits the rule. If either names an entity Lumx has not onboarded, it is nesting, and a customs entry in the shipper's name paid from the shipper's money matches both signals. Nesting needs written approval from compliance, and the same goes for agent-style or netted flows where the forwarder acts for others: ask compliance@lumx.io first. A parent can pay a subsidiary's supplier from its own wallet once compliance has approved that flow of funds in writing. Marketplaces face the same rule, as the marketplace payouts guide explains.
I would settle this before building anything else, and I would keep the default simple. A forwarder that advances duties and port fees should pay them from its own funds and invoice the shipper afterwards, because the payment then settles the forwarder's own obligation and every party in the chain is one we can see. If the shipper's money genuinely has to move through the forwarder, I would onboard the shipper as its own customer instead of asking for an exception. An exception needs written approval, and a design that depends on one is fragile.
Partner agents settle differently. Agents in a forwarding network exchange statements, net what each owes and pay the residual. A stablecoin changes only the last step: the paying agent sends the residual in the partner's currency over the partner's rail. On Lumx each partner agent is a destination under the paying forwarder, and the residual is one off-ramp from the forwarder's wallet. A partner with no local rail receives US dollars over SWIFT, with a UETR and an MT103 confirmation.
Payment limits and a weekly run
The ceiling that matters is the customer's limit, not the rail, and limits are set per transaction type. At KYB Standard on Lumx, one payment can be up to US$50,000 and a day or a month up to US$100,000, global limits that apply to every customer. Forty US$2,500 invoices use the full US$100,000, which at this level is also the month. A limit-increase request, with a supporting document, has a one-business-day review target; it is a target, not a promise.
A weekly run is one off-ramp call per payee, each with its own idempotency key, so a retry cannot pay a carrier twice. A payment over a limit is rejected with TRANSACTION_LIMIT_EXCEEDED, which can leave a run half paid. The cut-offs are in the rails table, and payout limits and cut-offs by rail goes deeper. On Lumx, read includeTransactionLimits on the customer before a run to see the remaining daily and monthly amounts.
When a stablecoin payment is the wrong tool for freight
When the money is not the forwarder's. A shipper's duties paid from the shipper's funds through the forwarder's account is nesting.
When the invoice may be reversed. An off-ramp is complete once the funds leave the banking partner, so settle a disputed accessorial charge before paying it.
What a carrier payment looks like on Lumx
Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.
The forwarder goes through KYB, which Lumx targets at one business day, and then receives a custodial wallet on each supported blockchain. A payout runs from USDC on Ethereum, Polygon or Base, or from USDT on Ethereum, Polygon or Tron. The wallet keeps its balance between operations, so the forwarder can fund it once and pay many carriers from it. That is a choice, not a requirement: no pre-funding on Lumx means no capital parked in settlement (nostro) accounts before a payment, because conversion and settlement happen when the payment is initiated.
A forwarder that bills shippers in Brazil or Mexico can collect into named virtual accounts in BRL and MXN in its own name, without a local entity in either country (setup guide). See the named virtual accounts page.
Pricing is a monthly platform fee plus usage-based per-transaction fees, with transparent FX on locked quotes and no pre-funding. The global payments page shows how collections and payouts fit together, the coverage page lists current rails and pairs, and the USDC to COP page shows the Colombian rate.
Methodology and sources
What Lumx does was read on November 1, 2026 in the Lumx documentation. The Colombian rails, the SPSAV transition statement, named accounts, Pix sender name, KYB target and pricing model are as confirmed by Lumx. The BIS figures come from BIS Working Paper 1385, October 2026, cited by name and not linked. The US$2,500 invoice and the run of forty are illustrative, not measurements.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Feodor Chistyakov on Unsplash.
How do freight forwarder payments work with stablecoins?
The forwarder holds USDC, registers each payee and pays each invoice in local currency over the local rail: Pix in Brazil, SPEI in Mexico, Bre-B or ACH Colombia in Colombia. The payee gets a normal bank transfer. On Lumx, the forwarder is a verified business customer with its own wallet, each payee is a destination, and each payment is an off-ramp from that wallet.
Is a stablecoin payment fast enough to release cargo?
On Pix, SPEI and Bre-B, usually: they are instant, at any hour. ACH Colombia and a dollar payout over SWIFT (one to five business days) are slower, so those payees need paying ahead of release. On Lumx, the offramp.success webhook marks the point at which funds have left the banking partner. The beneficiary bank can still hold funds for its own review, so releasing cargo against that event is the forwarder's own risk call.
Can a forwarder pay a client's duties and port fees with stablecoins?
Only with care. Paying its own broker or carrier settles the forwarder's own obligation, but moving a shipper's money through the forwarder's account is nesting. On Lumx, that flow is allowed only if the shipper is onboarded as its own customer or the structure has written approval from compliance, requested at compliance@lumx.io.
Which documents should a freight payment carry?
The invoice, the bill of lading or customs entry, and for a partner agent the net statement, kept with the payment reference. On Lumx, each payment takes a purpose code (TRADE_TRANSACTIONS for freight invoices), a memo and metadata, so the invoice number and bill of lading travel with it.
How large can one carrier payment be?
At KYB Standard on Lumx, one payment can be up to US$50,000 and a day or a month up to US$100,000, so forty US$2,500 invoices use the whole month. Bre-B has its own ceiling of COP 12,110,000 per payment and Lumx refuses a Bre-B payout above it, so larger Colombian invoices go over ACH Colombia, which has no per-payment limit.
