A stablecoin payments business case is a short internal document that asks a finance team to approve moving cross-border supplier or payout flows onto stablecoin rails. It compares the all-in cost of today's bank wires with a priced alternative, names each risk with an owner, and requests a capped pilot with metrics and a stop rule.
It is written for the head of payments or treasury, and follows one worked example: a Brazilian company paying suppliers in Mexico and Colombia, with every input illustrative. For the asset itself, start with what a stablecoin is.
What does a stablecoin payments business case need to contain?
Seven sections, each carrying a number or a named owner, in two pages plus an appendix.
The seven sections of the business case
# | Section | What goes in it | Who supplies it |
1 | Problem | Corridors, monthly volume, what goes wrong, what doing nothing costs | Payments or operations lead |
2 | Cost baseline | All-in cost of the last 3 to 6 months, per corridor | Finance, from statements and the payout ledger |
3 | Proposed flow | The new route in four plain steps, with who does what | Payments lead |
4 | Cost model | A formula, live quotes for your top corridors, the break-even | Payments lead with finance |
5 | Risks and controls | Each risk with a control and one owner | Compliance, treasury, engineering |
6 | Pilot plan | Corridor, cap, duration, three metrics, stop rule | Payments lead |
7 | Decision | The exact approval, with a date | The sponsor |
Write the problem as one paragraph:
> We pay [number] suppliers a month in [countries], about [amount] a month, by [bank wire]. Suppliers wait [X] business days on average, and [Y]% of payments need manual follow-up. Over the last [N] months the all-in cost was [Z]% of the amount delivered.
As a yardstick, the Financial Stability Board's G20 targets for cross-border payments set an average cost of no more than 1% for retail payments, with no corridor above 3%, by end-2027. That target is for retail payments, so use it only as a rough yardstick for small B2B payments. The rule that a baseline under 1% makes the case thin is this post's heuristic, not the FSB's.
Build the cost baseline from every line of the wire
The baseline is total cost divided by what the recipient actually received, per corridor. Wire fees alone understate it, so add each line from your own records.
The lines are bank fees (yours and the recipient's), intermediary deductions, FX spread against mid-market, cash held abroad times your cost of capital, and operations hours times a loaded rate.
Keep the average payment size beside the percentage: a $45 wire fee is 0.9% of $5,000 and 4.5% of $1,000. Lumx's docs include a migration prompt that builds a corridor table from your beneficiary list.
A worked example: a Brazilian company paying MXN and COP suppliers
These inputs are illustrative, not Lumx figures or market averages. Replace every one before the document leaves your team.
Illustrative inputs
Input | Value |
Monthly delivered volume | $400,000: $250,000 to Mexico in 50 payments, $150,000 to Colombia in 30 |
Average payment | $5,000 |
Today's route | USD wire from a Brazilian bank; the supplier's bank converts on arrival |
Cost of capital / loaded rate | 12% a year / $40 an hour |
The proposed route funds each payout by Pix (Brazil's instant payment system, run by the Central Bank), converts to USDC, and pays in local currency: MXN over SPEI (Mexico's interbank transfer system, run by Banxico), and COP over Bre-B (Colombia's instant payment system) or ACH Colombia. The Bre-B cap is 1,000 UVB per transaction, COP 12,110,000 in 2026, so a $5,000 invoice goes by ACH Colombia.
Baseline, today's USD wires (monthly)
Cost line | Calculation | Cost |
Wire fees and deductions | $45 x 80 wires | $3,600 |
FX spread, including the BRL-to-USD leg before the wire | 2.0% of $400,000 | $8,000 |
Cash held abroad | $100,000 at 12% a year | $1,000 |
Operations time | 30 hours x $40 | $1,200 |
Total | $13,800 (3.45%) |
Proposed, stablecoin to local rails (monthly, before the platform fee)
Cost line | Calculation | Cost |
Locked quote: spread plus per-transaction fees, every conversion leg | 0.8% of $400,000, an illustrative figure to replace with your live quote | $3,200 |
Cash held abroad | Each payout is funded when approved | $0 |
Operations time | 8 hours x $40 | $320 |
Total | $3,520 (0.88%) |
The gap is $13,800 minus $3,520, or $10,280 a month before the platform fee. That gap is the ceiling on what the monthly fee can be. To reuse it, paste the three tables into a spreadsheet and turn the inputs into formulas.
At what cost does the case stop paying for itself?
When the platform fee eats the gap, or when the live quote comes back worse than assumed. Put both in the document as formulas, so finance can change an input.
> Monthly gap = baseline monthly cost - proposed monthly cost before the platform fee > Net monthly saving = monthly gap - platform fee (or the monthly minimum, if higher) > Payback in months = one-off integration cost / net monthly saving
Integration in the example costs 120 engineering hours at $80, or $9,600. The proposed cost is the number you cannot read off your statements, so stress it: the example at three quote levels, with the platform fee taking none and then half of the gap.
Sensitivity of the example to the live quote
All-in quote | Proposed monthly cost | Monthly gap | Payback, fee takes 0% of gap | Payback, fee takes 50% of gap |
0.8% | $3,520 | $10,280 | 0.9 months | 1.9 months |
1.4% | $5,920 | $7,880 | 1.2 months | 2.4 months |
2.0% | $8,320 | $5,480 | 1.8 months | 3.5 months |
Before the platform fee and integration cost, the case breaks even at a quote of 3.37% ($13,480 plus $320 of operations time against $13,800 of baseline).
For what sits in a quote, see how stablecoin payout costs work and stablecoin API fees compared.
On Lumx, a floating rate is a real-time reference with no lock and no fee, and a locked rate returns an exchangeRateId that holds the rate for 30 seconds, 1 minute or 5 minutes, with only the 30-second lock free. Lumx prices as a monthly platform fee plus usage-based per-transaction fees, with transparent FX on locked quotes and no pre-funding. The standard agreement has a monthly minimum, waived during a ramp-up period, so line up the pilot window with the ramp-up before quoting a payback.
Risks a CFO will raise, each with a control and an owner
Name six, each with one owner.
Risk register for the business case
Risk | Control | Owner |
The stablecoin trades below one dollar | Hold the coin for minutes between legs and execute against a locked quote. Use an issuer that publishes reserves: Circle states USDC is redeemable 1:1 for US dollars and reports reserves weekly, as of October 29, 2026, on its transparency page | Treasury |
The provider holds funds and fails | Confirm in writing who holds the money at each step and the refund rule; see what a custodial wallet is | Finance |
A payout fails after funds move | A documented refund path, with status events written into your ledger | Operations |
Receiving-country rules change | Dated legal sign-off per corridor, reviewed every quarter; see stablecoin rules in Mexico for the CNBV (Mexico's banking and securities regulator) side | Compliance |
Tax and accounting: how each conversion leg (BRL to USDC, USDC to MXN or COP) is taxed and booked, including a coin held for minutes | A written opinion from tax counsel on every leg, and one ledger entry per leg | Finance and Tax |
Wrong recipient details | Validate the destination before the first payout and re-approve any change | Operations |
A Brazilian payer has one more question: how the flow is classified. Lumx applied for SPSAV authorization and operates in the transition regime of BCB Resolution 520 of 2025, Article 88. Converting BRL to USDC falls under BCB Resolution 521 of 2025: an operation in the exchange market that is not itself foreign exchange. Lumx's position is that no IOF applies, because a stablecoin is not foreign currency. Our guide to stablecoin regulation in Brazil covers Law 14.478/2022 and BCB Resolution 561 of April 30, 2026, which keeps virtual assets out of the eFX cycle. A business case does not settle your position, so add a dated opinion from counsel.
On Lumx, a customer's wallet is custodial: the balance sits in a wallet provisioned with the customer and holds USDC or USDT between an on-ramp and an off-ramp. A transaction that Lumx's monitoring flags goes on hold as an RFI (request for information, a compliance hold that asks for a document before a transaction clears), and every status change arrives as a webhook event, so the failure row has an owner and an event to point at.
A pilot plan that fits on one page
Ask for one corridor, a hard cap, a fixed window and three metrics agreed up front. A pilot measures cost per delivered dollar, not savings: at 10% of volume the monthly gap in the 0.8% case is about $1,028 before the platform fee.
> Corridor: [Brazil to Mexico over SPEI]. Cap: [amount] a month, [amount] a payment. Duration: [60 to 90] days. Success metrics: (1) all-in cost per delivered dollar below [X]%; (2) median time from approval to supplier credit below [Y]; (3) payments needing manual handling below [Z]%. Stop rule: pause if any payout is unaccounted for after [N] hours, or if metric 3 doubles in any week. Review: 30 minutes a week, readout on day [90].
I recommend that the business case ask for a pilot and never for a migration, and that it put the losing corridor on page one. A CFO approves a loss they can see and cap, and a document that admits one corridor does not beat the baseline reads as more credible than one that wins everywhere. I would also write the stop rule before the success metrics, because a team that has agreed when to stop argues less about the numbers.
On Lumx, business verification targets one business day, BRL and MXN accounts are active as soon as the customer is approved, and an API integration takes 2 to 3 weeks to go-live. Sandbox moves no real money. Standard business verification allows $50,000 per transaction and $100,000 a month, limits that can change, which cover the pilot but not the $400,000 of the full example. Higher limits need Enhanced verification or a limit increase request. To pick the provider first, use the 30-day evaluation plan.
The decision to ask for
Ask for one specific approval with a date.
> Approve a [90]-day pilot of stablecoin payouts in [corridor], capped at [amount] a month, with [provider] as payout provider, an integration budget of [hours or amount], and a go or no-go review on [date] against the three success metrics above.
The risk register template goes deeper on the risk table above.
When a stablecoin payout case is the wrong case
Do not write it when the destination has no local rail a provider can reach, because then the saving does not exist and a wire is the answer. Lumx runs SWIFT in USD only; POBO and COBO are in USD, EUR, and GBP. A wire in another currency belongs to your bank. Skip it when your baseline is already under 1% (the heuristic above), or when the payment needs a bank instrument such as a letter of credit.
If a live quote does not beat the baseline in a corridor, drop it and say why. Stablecoins vs SWIFT for B2B payments covers where correspondent banking still wins.
What the case 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.
For the example, section 3 maps to three steps. The Brazilian company is onboarded as a business customer with a BRL account and funds its wallet by Pix, a locked quote fixes the rate and fees, and an off-ramp pays the supplier's registered destination: SPEI for MXN, Bre-B or ACH Colombia for COP, chosen when the destination is registered. SPEI has no cut-off and runs 24/7/365. A payout above the Bre-B cap is refused, not split or rerouted, and ACH Colombia has no per-payment limit. Lumx deducts no fee from the amount that reaches the supplier on a Pix, SPEI or Bre-B payout.
The off-ramp status events give finance the timestamps behind metric 2. The corridor pages for USDC to MXN and USDC to COP show the live rate, and the coverage page lists every rail by country. See global payments for the rails.
Methodology and sources
Lumx product facts come from the docs pages on exchange rates, transactions, wallets, accounts, coverage, environments, rail cut-off times, transaction limits, limit increase requests and webhooks. The FSB targets are from the FSB page, and Circle's USDC statements from its transparency page. All were read on November 1, 2026.
Every dollar figure in the worked example is illustrative. The Brazilian rules are cited by number and year, with links to the official texts.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Sohan Rayguru on Unsplash.
What should a stablecoin payments business case include?
Seven sections: the problem in one paragraph, a cost baseline, the proposed flow in plain words, a cost model with a break-even, risks with a control and an owner each, a capped pilot plan, and the exact decision requested. On Lumx, the cost model is filled from a locked quote, which fixes the rate and fees for 30 seconds, 1 minute or 5 minutes, and the pilot runs first in sandbox, where no real money moves.
How do I estimate what today's cross-border payments really cost?
Pull three to six months of payouts and add every line: bank fees, intermediary deductions, the FX spread against mid-market, the cost of cash held abroad and staff hours. Divide by the amount delivered, per corridor, with the average payment size beside it. Lumx's docs include a migration prompt that builds a corridor table from your beneficiary list and the coverage page.
How big should the pilot be and when can it start?
One corridor, a monthly cap set by treasury, 60 to 90 days and three metrics agreed in advance. The start date depends on verification and integration. Lumx targets one business day for business verification, activates BRL and MXN accounts once the customer is approved, and takes 2 to 3 weeks to go-live by API. Standard verification allows $50,000 per transaction and $100,000 a month, and higher limits need Enhanced verification or a limit increase request.
What will the CFO ask about risk first?
Five things: what happens if the stablecoin loses its dollar price, who holds the money at each step, what happens when a payout fails, whether the flow is lawful in each country, and how each conversion leg is taxed and booked. Answer each with a control and an owner. On Lumx, the wallet is custodial and holds USDC or USDT between legs, flagged transactions are held as an RFI, and every status change arrives as a webhook event. Lumx applied for SPSAV authorization and operates in the transition regime of BCB Resolution 520 of 2025, Article 88.
