Stablecoin card vs local payout: how to pay people abroad

A stablecoin card is a Visa or Mastercard that spends a stablecoin balance at merchants. A local payout converts the balance to local currency and sends it over a domestic rail, such as Pix (Brazil's instant payment system, run by the Central Bank), to a bank account. Use the card for merchants and the payout for bank accounts.

How does a stablecoin card compare with a local payout?

A card ends at a merchant terminal, where the issuer converts and settles with the card network. A payout ends at a bank account, where a domestic rail settles in local currency.

Stablecoin card and local payout, side by side.

In a card program built on Lumx, a separate issuer provides the card. Lumx provides the local-currency top-up that fills the wallet and the cash-out to a bank account that empties it.

Match the payment to the recipient

Start from who receives the money: a merchant with a terminal gets the card, and a bank account gets the rail.

Which tool fits which payment.

The pattern is the recipient, not the amount, and the reason is reconciliation: a landlord, a payroll file or a supplier ledger matches an incoming transfer against a bank reference. The contractor case in full is the guide to pay LATAM contractors in stablecoins.

On Lumx, the payout column is a destination plus an off-ramp. You register each payee's bank account as a destination under your customer, with a holder relationship that says whether the payee is an employee, a supplier or yourself. Each off-ramp carries a purpose code: PROFESSIONAL_SERVICES for contractor payments and, as the closest available code, for salary (the payroll guide notes there is no dedicated payroll code), TRADE_TRANSACTIONS for supplier invoices, REAL_ESTATE for rent, TAX for tax authorities, BILLS for utilities and EXPENSES_REIMBURSEMENT for reimbursements. A purpose that does not match the activity can trigger an RFI (request for information, a compliance hold that asks for a document before a transaction clears).

What each path costs per dollar delivered

Compare the two paths on one number: the stablecoin that leaves the wallet, against the amount that would have left at the mid-market rate. Two inputs drive it. The first is the card markup. NGIBANK's guide to crypto debit cards, a third-party figure from a card issuer's marketing blog published March 3, 2026, puts the FX markup on a crypto card at 1.5% to 3% when you pay in a currency other than the card's base currency. It puts ATM withdrawals at 1.5% to 2%. For scale, BlindPay's article on small versus large cross-border payments (read November 2, 2026) cites BIS Working Paper 1385, October 2026: median money transfer operator costs of about 200 to 300 bps on USD 200, falling to about 40 to 130 bps on USD 10,000. The second input is your payout quote: the final rate against the base rate in the exchange-rate response, which you read before the money moves.

The stablecoin leaving the wallet is the local amount delivered, divided by the mid-market rate, divided by one minus the spread. The example sends R$5,000 at R$5.00 per dollar, so 1,000 USD at zero spread.

Cost of delivering R$5,000 at a mid-market rate of R$5.00. A payout quoted at the same spread costs the same.

The break-even is the card's own markup. A payout costs the same as the card when your quoted spread equals it, so the quote can rise to 1.5% against the low end of the range, or to 3.0% against the high end, before the card wins. How stablecoin payout pricing works explains why the spread is usually the largest of the three cost layers.

Lumx charges a monthly platform fee plus usage-based per-transaction fees, and the standard agreement carries a monthly minimum, so add that layer to your per-dollar number when you compare.

On Lumx, every exchange rate response returns the base rate and the final rate together, so the all-in spread on a payout is one subtraction. The gap is the Lumx fee plus any partner fee you add, with no FX margin built into the rate. A locked rate holds for 30 seconds at no fee, or for one or five minutes with a fee that covers the volatility. On a payout by Pix, SPEI (Mexico's interbank transfer system, run by Banxico) or Bre-B (Colombia's instant payment system, run by the Banco de la República), Lumx does not deduct a fee from the amount that reaches the recipient.

How fast is each path, and where does it stop?

On the rails that matter here, speed rarely separates the two, because Pix and SPEI settle instantly around the clock. What separates them is where each one stops. A card stops at the issuer's spending limit, and a payout stops at the customer's transaction limits and at the rail's cut-off.

Payout rails by currency, from the Lumx docs and Lumx product confirmation as of November 1, 2026.

A request after a cut-off, on a weekend or on a bank holiday is processed on the next business day. The full picture is in payout limits and cut-offs by rail.

On the card side, limits belong to the issuer's program and the cardholder's tier, so ask the issuer before you promise a recipient a figure. On Lumx, transaction limits are per transaction type and per customer, and the same defaults apply to every customer from any country. At the Standard level, an individual verified with KYC (know your customer) can send USD 7,500 per transaction, USD 15,000 a day and USD 15,000 a month. A company verified with KYB (know your business, the verification of a company and its owners) can send USD 50,000 per transaction, USD 100,000 a day and USD 100,000 a month. Enhanced KYC or KYB raises them, and a customer can ask for more. A payout that would pass a limit is rejected with TRANSACTION_LIMIT_EXCEEDED. Each payout moves from stablecoin transfer to trade to fiat transfer to success, as the transactions docs describe, and the offramp.success and offramp.failed webhooks report the result.

Brazil, Mexico and Colombia: where each tool wins

In Brazil the payout has the stronger case, because Pix takes a key and arrives in seconds, and the recipient already pays rent and bills from that account. Visa's first launch list with Bridge, announced April 30, 2025, named Argentina, Colombia, Ecuador, Mexico, Peru and Chile and did not include Brazil, so ask your issuer about card availability there. See USDC to BRL.

Mexico is where both tools are available, and a SPEI payout takes a CLABE (the 18-digit Mexican bank account number) and arrives instantly. See USDC to MXN.

Colombia adds a cap. Bre-B is limited to 1,000 UVB per transaction (COP 12,110,000 in 2026) by the Banco de la República's Circular Reglamentaria Externa DSP-465, Asunto 18, numeral 3.2, sheet of March 31, 2026, for every provider. On Lumx a Bre-B payout above the cap is refused and never split, and ACH Colombia has no per-payment limit, so the larger invoice goes there. PSE (Colombia's online bank-transfer network) only collects, so it can fill a wallet but cannot pay a person. The right tool follows the stablecoin corridor, meaning the currency pair and the rail at each end.

Running both: a card for spend, a payout for the rest

Most teams that pay people abroad end up with two lanes, a card for discretionary spend and a payout for obligations, both drawing on one stablecoin balance. Rain's real-time funding, in beta at the time of writing (read November 1, 2026) and limited to a short list of assets and networks, lets a card spend straight from a wallet the user connects, so there is no separate card balance to drain. The cash-out is then an off-ramp from that wallet to a bank account the cardholder registered as their own. One risk belongs to your app: an off-ramp does not see open card authorizations, so cap each cash-out at the wallet balance minus what open authorizations have committed.

I recommend paying people by payout and offering the card as an optional second balance. I would put the contractor invoice, the salary and the rent on the rail, because those are bank-account obligations, and I would let the recipient decide how much to move to a card. A card that is the only way to receive money pushes people to an ATM or an exchange the moment they need to pay a landlord, and that detour is the cost no quote shows.

A card program with both lanes is a stack of separate companies with separate terms. See Lumx vs Rain for the role split and Mastercard settling in stablecoins for the network side.

The decision rule: send obligations by payout and discretionary spend by card, and set a dollar threshold above which the markup is real money. At 1.5% to 3%, a USD 1,000 payment costs 15 to 30 USD more than at mid-market, and a USD 10,000 payment costs 150 to 300 USD.

On Lumx, the card lane is a local-currency top-up by Pix, SPEI or PSE that converts to stablecoin in the wallet, and the cash-out is an off-ramp started by your platform through the API.

When a card or a payout is the wrong tool

A card is the wrong tool when the payee is a bank, a tax authority or a landlord, when the amount is large enough that a markup of a few percent is real money, or when the issuer's program is not offered where the recipient lives.

A payout is the wrong tool for a terminal purchase, a subscription billed in dollars and a recipient with no reachable bank account.

What this looks like with 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.

Lumx covers the payout lane and the two legs around a card. The paying company is a business customer that completes KYB, and its wallet holds the stablecoin. Each payee is a destination with a rail, a holder and a relationship, and each payment is an off-ramp from the wallet, so a contractor in Brazil receives reais by Pix and a supplier in Mexico receives pesos by SPEI, both showing the paying company's name as sender (effective November 2026 for Pix).

For the card lane, the same wallet is the top-up target: the cardholder deposits local currency over Pix, SPEI or PSE, the deposit converts to USDC or USDT, and the card spends from the balance. The global payments page covers the rails, the coverage page lists what runs where, and the off-ramp explainer covers conversion.

Methodology and sources

We read the Lumx documentation and the pages below on November 1, 2026. The card markup range is a third-party figure from a card issuer's guide, and the cost table is arithmetic on that range, not a Lumx rate.

• Lumx docs: Coverage, Payment rail cut-off times, Destinations, Purpose codes, Transaction limits, Exchange rates, Transactions, Payroll

• Cards: Visa and Bridge announcement (April 30, 2025), NGIBANK crypto debit card guide (March 3, 2026), Rain's "Introducing real-time funding" page (read November 1, 2026)

• Colombia: Banco de la República, Circular Reglamentaria Externa DSP-465, Asunto 18, numeral 3.2 (sheet of March 31, 2026), and the "Conozca Bre-B" page for COP 12,110,000

Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.

Cover photo: Wolfgang Rottmann on Unsplash.