Every fee layer in card processing versus stablecoin rails, the chargeback math no one publishes honestly, and the defensible ROI model your CFO can actually approve.
Scope Note · Educational and operational content — not legal, tax, accounting, financial, investment, or compliance advice · Verify current terms directly with each provider · Full disclaimers at module end
Numbers are where enthusiasm goes to get tested, and that is a good thing. This module exists so a payment decision never has to be defended with a vibe. Everything here is built to survive a skeptical CFO, a careful accountant and a second look at eleven at night. The savings are real but narrower than the marketing suggests, and the model below includes the downside. Bring real statements — the math gets interesting fast.
Modules 01 and 02 established the architecture. This module turns the architecture into a number — one a CFO can defend, a board can approve, and a finance team can monitor against. The work below is a structured accounting of where modern payment rails capture value, where they don't, and how to model both honestly inside the framework an institutional reviewer expects.
A CFO reviewing a proposed payment-rail addition will press on four questions:
Are the cost inputs verifiable? Every fee, rate, and assumption traceable to a public source or signed contract — not a marketing page.
Are the savings net of operational cost? Implementation effort, accounting reconciliation, training, ongoing vendor management — subtracted before the savings line.
Is the model conservative? Adoption rates, conversion assumptions, and timing all assume slower uptake than the optimistic case.
What does the downside look like? If adoption is half of plan, fees come in higher than modeled, and integration takes twice as long — is it still net-positive within the budget cycle?
A business case that survives those four questions earns approval. One that doesn't, won't. The module is structured around them.
Three principles thread through every lesson. First: the savings story is real but narrower than crypto-native marketing implies. It concentrates in specific transaction types — international, B2B large-ticket, contractor payroll, chargeback-exposed sales — and is materially smaller for everything else. Second: chargeback elimination is structurally the largest single benefit for many operators, and almost no one prices it correctly in their initial analysis. Third: working-capital effects from settlement compression frequently exceed the headline fee savings, and almost no one models them at all.
The honest pitch: meaningful savings on a narrow slice of transactions — usually international, large B2B, contractor payouts, and chargeback-exposed sales. For everything else, the delta is small.
The invisible costs are often the big ones. Chargebacks and slow settlement frequently cost more than the fees you can see on a statement. This module prices both.
Every figure here is illustrative. Your statements, your negotiated terms, and your customers’ actual adoption set the real number — nothing in this module is a projection or a promise.
The conservative case is the decision case. If the model only works in the optimistic scenario, it doesn’t work.
Payment economics resist easy analysis because the headline rate is one layer of many. Card processing in particular hides fee structure inside interchange categories, network assessments, and pricing models designed to optimize for processor margin rather than merchant transparency. The same is true at lighter scale for ACH and wire. The first step in defensible ROI is naming every layer.
Fee and ROI examples are illustrative frameworks, not guaranteed savings, projections, or financial advice. Actual outcomes depend on processor terms, customer behavior, settlement path, chargeback profile, and operating context.
A "2.9% + $0.30" headline rate is a composite. Under the hood, the card transaction passes through three distinct fee surfaces:
| Layer | Who Receives It | Typical Range | What It Covers |
|---|---|---|---|
| Interchange | Issuing bank | 1.15% – 2.95% + flat | Set by the card network. Varies by card type (debit, credit, rewards, corporate), transaction type (card-present, card-not-present, recurring), and merchant category. |
| Network assessment | Card network (Visa, Mastercard, etc.) | 0.13% – 0.15% | Fixed network fee for routing and authorization. Smaller than interchange but consistent across every transaction. |
| Processor markup | Your payment processor | 0.30% – 1.50% + flat | The processor's margin. Wide range driven by pricing model (interchange-plus, tiered, blended), merchant size, and negotiation. |
The composite rate excludes a meaningful list of additional fees that materially affect actual cost-to-process:
| Fee | Typical Range | When It Applies |
|---|---|---|
| International surcharge | 0.80% – 1.50% | Card issued outside the merchant's country |
| Cross-border surcharge | 0.40% – 1.00% | Cross-currency settlement |
| FX markup | 1.00% – 4.00% | Currency conversion · often hidden in the FX rate, not itemized |
| PCI compliance fee | $5 – $30 / month | Card data handling compliance · monthly |
| Statement / gateway fee | $10 – $50 / month | Account access, reporting, gateway service · monthly |
| Chargeback fee | $15 – $100 per incident | Per chargeback, regardless of outcome · separate from disputed amount |
| Retrieval / representment fee | $10 – $50 | Documentation submission for disputed transactions |
| Reserve hold | 5% – 10% of volume | For higher-risk merchant categories · funds held for rolling periods (often 90–180 days) |
| High-risk surcharge | +1% – 4% on base rate | For specific industries (gaming, adult, subscription, travel) |
| Termination / early cancellation | $295 – $2,000+ | Multi-year contract early exit |
Your true card processing cost is the effective rate: total fees divided by total processed volume across a representative period. Most operators discover that their effective rate runs 50–150 basis points above the headline rate once all layers are included. For ROI analysis, use effective rate from your last four quarters of processor statements — not the nominal rate from your contract.
For many B2B operators the relevant baseline isn't card processing — it's ACH and wire. Both have their own fee surfaces:
| Rail | Per-Transaction Cost | Settlement | Operational Limits |
|---|---|---|---|
| Standard ACH | $0.25 – $1.50 | 1–3 business days | US-only. Return risk. Daily cutoff windows. |
| Same-day ACH | $1.00 – $5.00 | Same business day | US-only. $1M per-transaction cap. Multiple windows per day. |
| Wire (domestic) | $15 – $35 | Same business day | Reversible only by recipient consent. No customer-side dispute mechanism. |
| Wire (international) | $25 – $50 sender + $10 – $30 recipient | 1–5 business days | FX markup 1–4%. Intermediary bank fees often unbilled to sender, deducted from recipient. |
| FedNow / RTP | $0.25 – $1.00 | Real-time | US-only. Adoption still expanding across receiving institutions. |
| SEPA Instant (EU) | €0.20 – €0.50 | ~10 seconds | EU-only. €100,000 transaction cap typical. |
The dominant cost of international wires for most operators isn't the wire fee — it's the failure rate and the support cost of resolution. Bounced wires due to incorrect SWIFT codes, missing intermediary instructions, or sanctioned-corridor blocks generate finance-team time, customer friction, and frequently unrecoverable intermediary fees. Track this line. It compounds quietly as headcount expense rather than per-transaction cost.
Three rails, three distinct fee structures. The right baseline for your ROI analysis is the rail your specific transaction would otherwise have used — not the most expensive rail available. Domestic small-ticket: card is the baseline. International B2B invoicing: wire is the baseline. Contractor payroll: a mix of ACH, wire, and third-party (Wise, PayPal) depending on geography. Compare modern rails against the right counterfactual.
Stablecoin payment rails have a fee structure too. It's materially different from card processing, materially smaller in aggregate for most workloads, and worth naming explicitly so the comparison is apples-to-apples rather than headline-to-headline.
| Layer | Who Receives It | Typical Cost | Notes |
|---|---|---|---|
| Network fee (gas) | The underlying chain | $0.001 – $0.05 on modern L2s | Paid in chain-native gas. Volatile under congestion; predictable under normal conditions. |
| Processor fee | Your stablecoin processor | 0% – 1.5% | Coinbase Business (fee-free under published threshold*) to Stripe Crypto (~1.5%) to BitPay / Triple-A (~1%). |
| Conversion spread | Off-ramp provider | 0% – 1.0% | USDC→USD on Coinbase typically carries no spread within the published conversion threshold*; cross-currency (USDC→EUR) carries a small spread. |
| Operational overhead | Your finance / operations team | Variable | Accounting reconciliation, wallet management, treasury operations. Quantified below. |
*Coinbase offers fee-free USD ↔ USDC conversion up to $5 million in net conversion volume within a rolling 30-day period. Above that threshold, Coinbase applies a USDC processing fee only to net conversion volume above the limit. Operators should verify the current threshold, fee schedule, account type, and Coinbase product terms directly with Coinbase before relying on this for high-volume treasury planning.
High-volume operators should model Coinbase's USD ↔ USDC conversion threshold separately from processor, network, and off-ramp fees.
Operational overhead is where most informal ROI analyses break down. It's real cost, it scales with volume non-linearly, and it deserves explicit estimation rather than handwaving. The dominant components:
| Overhead Component | Typical Time / Cost | Scales With |
|---|---|---|
| Initial integration | 8–80 hours (one-time) | Complexity of payment stack and existing systems |
| Wallet architecture setup | 4–16 hours (one-time) | Volume tier (hot/cold sufficient vs. multi-sig required) |
| Accounting integration | 4–24 hours (one-time) | Whether processor offers native QuickBooks/Xero sync |
| Monthly reconciliation | 1–8 hours / month | Volume and number of chains/processors |
| Treasury management | 2–10 hours / month | Reserve size and rebalancing frequency |
| Team training | 2–4 hours / employee with access (one-time + annual refresh) | Number of employees touching the system |
| Ongoing vendor management | 1–4 hours / month | Number of processors, exchanges, custodians used |
For ROI modeling, convert overhead to dollar cost using your loaded internal hourly rate — typically $50–$200/hour depending on role and geography. One-time integration cost is amortized over the first 12–24 months of operation. Recurring overhead is subtracted from monthly savings. Most operators find that recurring overhead runs $200–$2,000/month depending on volume tier — material at low volume, immaterial at scale.
| Rail | Per-Transaction Cost (Effective) | Settlement | Operational Overhead Floor |
|---|---|---|---|
| Card processing (domestic) | 2.5% – 3.5% effective | T+1 to T+3 | Existing — captured in operations baseline |
| Card processing (international) | 4.0% – 6.5% effective | T+1 to T+3 | Existing — plus dispute resolution overhead |
| International wire | $40–$80 + 1–4% FX | 1–5 business days | ~30 min per wire including failure resolution |
| Stablecoin · processor route | ~1% all-in | Seconds to minutes | Material at low volume · immaterial at scale |
| Stablecoin · wallet route | ~$0.01 + manual ops | Seconds | High per-transaction · low aggregate (small volume only) |
Marketing materials on both sides — traditional processor and crypto-native — quote gross fee rates against each other. The honest comparison is effective net cost-to-serve including operational overhead. At low volume, stablecoin rails' overhead floor can erase the headline savings entirely. At meaningful volume, the math inverts decisively. Know which side of that curve your operation sits on before building the business case.
Chargebacks are the single most under-modeled line in card-processing economics. The disputed amount is only the visible cost. The full cost — fees, recovery effort, dispute-team headcount, reserve drag, threshold-monitoring overhead, and the second-order reputational and revenue effects — runs materially higher and accrues across the operating year as a structural drag on margin.
| Cost Component | Typical Amount | What It Covers |
|---|---|---|
| Direct loss of disputed amount | 100% of transaction | If the chargeback is upheld (most are), the merchant loses the disputed amount in full. |
| Chargeback fee | $15 – $100 per incident | Charged by the processor regardless of dispute outcome. Non-refundable even on successful representment. |
| Representment cost | 30 min – 4 hours per case | Finance / customer-support team time to gather documentation and submit dispute response. |
| Indirect cost | 3–5× direct cost | Goods or services already delivered. Fulfillment cost. Shipping cost. Customer support cost. Refund processing if a partial settlement is reached. |
A subscription SaaS company processes a $200 monthly subscription. The customer disputes the charge six weeks later, claiming non-recognition of the transaction. The representment is denied. The composite cost looks like this:
The disputed amount alone — $200 — undercounts the true cost by roughly 2×. At chargeback rates of 0.5% to 3% of volume, structural cost runs into meaningful percentages of revenue across the year.
For merchants in higher-risk categories (subscription, travel, digital goods, gaming, certain B2B verticals), processors impose a rolling reserve — typically 5%–10% of processed volume held for 90 to 180 days. The funds are not lost; they're held against future chargeback risk. During the hold, they're working capital the business doesn't have. The cost is the opportunity cost of capital tied up in the reserve.
| Reserve Scenario | Tied-Up Capital | Annual Opportunity Cost @ 8% |
|---|---|---|
| $50K/month volume · 5% / 180-day reserve | ~$15,000 | ~$1,200 / year |
| $500K/month volume · 7% / 180-day reserve | ~$210,000 | ~$16,800 / year |
| $5M/month volume · 10% / 180-day reserve | ~$3,000,000 | ~$240,000 / year |
Stablecoin payments, once confirmed on-chain, are final. There is no chargeback mechanism. For merchants in chargeback-exposed categories, this is not a minor convenience — it is direct margin recovery at the structural level. Composite annual savings, including direct chargeback cost, reserve drag, and dispute-team overhead, often exceed the headline fee savings by a wide margin. The single largest under-modeled benefit in most initial ROI analyses.
The absence of a chargeback mechanism shifts dispute resolution entirely to your refund policy. Customer-experience consequences of refund denial are real. Operationally, refund policy becomes a customer-trust instrument rather than a back-office process. Operators capturing chargeback recovery savings should invest part of those savings into generous, fast, clearly-documented refund handling. Doing otherwise trades chargeback risk for customer-retention risk — frequently at unfavorable exchange.
Aggregate ROI numbers obscure what's actually happening underneath. The real economics live at the workload level. Six recurring transaction patterns, each modeled honestly across card, wire, and stablecoin rails. The numbers are illustrative; the structure is what matters. Apply your own effective rates from Lessons 01 and 02 to the same framework.
Vendor features, fees, supported assets, settlement options, and jurisdictional availability can change. Verify current terms directly before relying on any provider.
| Rail | Per-Transaction Cost | Effective Rate | Net to Merchant |
|---|---|---|---|
| Card (domestic credit) | $2.48 | 3.3% | $72.52 |
| Card (debit) | $1.18 | 1.6% | $73.82 |
| Stablecoin (processor route) | ~$0.75 | ~1.0% | ~$74.25 |
Verdict: Small-ticket domestic retail is the workload where the stablecoin advantage is real but modest. Per-transaction savings of $1–$2. Multiplied across volume the savings are meaningful, but rarely the strongest case for adoption in isolation. Card rails remain a perfectly defensible choice here.
| Rail | Per-Transaction Cost | Effective Rate | Net to Merchant |
|---|---|---|---|
| Card (intl. + FX markup) | ~$8.85 | 5.9% | ~$141.15 |
| Stablecoin (processor route) | ~$1.50 | ~1.0% | ~$148.50 |
Verdict: The international consumer checkout is where stablecoin rails demonstrate clear advantage. Per-transaction savings of ~$7 — before accounting for the failed-authorization rate, which on international cards routinely runs 10–25% depending on issuer geography. For operators with meaningful international volume, this pattern alone often justifies adoption.
| Rail | Per-Transaction Cost | Effective Rate | Net to Merchant |
|---|---|---|---|
| Card (B2B credit) | ~$750 | 3.0% | $24,250 |
| International wire | $70 + ~2% FX | ~2.3% | ~$24,430 |
| Stablecoin (processor route) | ~$250 | ~1.0% | ~$24,750 |
| Stablecoin (Request Finance route) | ~$25–$125 | ~0.1%–0.5% | ~$24,875–$24,975 |
Verdict: Large B2B invoicing is where the economics tilt most decisively. Card rails are rarely competitive at this ticket size. Wire is the realistic baseline; stablecoin rails on accounting-first processors like Request Finance deliver per-invoice savings of $50–$500 with same-day settlement and no FX markup. Across an invoicing book this compounds into materially larger annual numbers than retail workloads.
| Rail | Sender Cost | Recipient Receives (after fees + FX) |
|---|---|---|
| International wire | $35 | ~$3,800 |
| PayPal | Up to 5% | ~$3,720 |
| Wise | $25 + ~0.7% | ~$3,940 |
| Stablecoin on L2 | ~$0.01 | ~$3,999.99 |
Verdict: The largest single per-transaction advantage of any pattern in this lesson — and the workload most operators leave on the table. Across a 10-person international contractor team, the annual delta versus wire runs $20,000–$24,000. The quietest win in the stablecoin economics, and almost always the fastest payback inside an organization once enabled. Figures are illustrative of the structure; actual outcomes depend on your contract terms, adoption rate, operating context, and current processor fees, and should be modeled against your own data.
| Cost Layer | Card (typical) | Stablecoin |
|---|---|---|
| Processing fees (~3%) | $15,000 / month | $5,000 / month (~1%) |
| Chargebacks (1% rate, $385 full cost each) | $38,500 / month | $0 (refund policy instead) |
| Reserve drag (7% / 180-day, opportunity cost) | ~$2,940 / month | $0 |
| Composite monthly cost | $56,440 | $5,000 + refund-handling buffer |
Verdict: The single most under-modeled ROI scenario in the category. A subscription business operating at chargeback rates above 1% sees its true cost of card rails dominated by chargeback economics rather than headline processing fees. Annual structural savings for this profile commonly exceed $400K — substantially before accounting for refund-policy overhead. Figures are illustrative of the structure, not a projection for any specific business; actual outcomes depend on your chargeback profile, adoption, contract terms, and operating context, and should be modeled against your own data with professional review.
| Treasury Approach | Yield (per published terms) | Annual on $1M |
|---|---|---|
| Standard business checking | 0% – 0.5% | $0 – $5,000 |
| Money-market account | 3% – 4.5% | $30,000 – $45,000 |
| Treasury bills (T-bill ladder) | 4% – 5% | $40,000 – $50,000 |
| Stablecoin treasury (Coinbase Business / Slash) | ~4% – 5% | ~$40,000 – $50,000 |
Verdict: Stablecoin treasury programs may be competitive with T-bill ladders on headline rate per current published terms — but they are not equivalent in risk. Stablecoin-balance yield carries issuer, custody, platform, and regulatory-characterization risk that a Treasury instrument does not, is generally uninsured, and its regulatory treatment varies by provider and jurisdiction and is subject to change. The differentiation is operational: same-day liquidity, programmable splits, no maturity ladder management, native integration with stablecoin payment flows. For operators already running stablecoin payments, the integrated treasury layer captures yield without adding architectural surface area. For operators not running stablecoin payments at all, a T-bill ladder is the operationally simpler choice. Treat the comparison as operational, not as a statement of equivalent safety, and confirm the structure and current terms of any yield program with qualified professionals before relying on it.
A defensible ROI model is not a spreadsheet that produces a favorable number. It's a structured accounting of inputs, assumptions, and ranges that survives institutional scrutiny because every line is traceable, every assumption is named, and the downside case is modeled as carefully as the base case.
| Input | What to Measure | Source |
|---|---|---|
| 01 · Volume by transaction type | Total monthly volume in each of the six patterns from Lesson 04 | Last 12 months of processor statements · invoicing reports · payroll reports |
| 02 · Current effective rate | True all-in fee rate, by pattern | Total fees / total volume from processor statements |
| 03 · Chargeback rate & full cost | Chargebacks / total transactions · cost per chargeback including indirect | Dispute records · finance-team time tracking |
| 04 · Reserve exposure | Current reserve hold as % of volume · hold duration | Processor agreement |
| 05 · Stablecoin rail cost | Expected effective rate on target processor | Published terms · signed contract |
| 06 · Operational overhead | Integration cost · ongoing monthly cost (in loaded hours converted to dollars) | Lesson 02 framework · internal hourly rates |
| 07 · Adoption ramp | Realistic adoption curve by customer segment over 12 months | Customer geography mix · pilot conversation data |
Three scenarios — conservative, base, optimistic. The same input variables across all three, with adoption rate and per-transaction cost as the swing variables. The conservative case is the one that earns approval.
| Variable | Conservative | Base | Optimistic |
|---|---|---|---|
| Adoption rate by month 12 | 30% of addressable volume | 50% | 70% |
| Effective stablecoin rate | 1.5% all-in | 1.0% | 0.7% |
| Integration cost (one-time) | 120 hours | 60 hours | 30 hours |
| Monthly operational overhead | $2,500 | $1,200 | $600 |
| Time to first transaction | 90 days | 45 days | 14 days |
Institutional reviewers approve business cases on the strength of the conservative scenario, not the base case. If the model is net-positive in the conservative case, the project gets funded. If it requires the optimistic case to clear hurdle rates, it doesn't. Build the conservative case rigorously. If the conservative case still produces meaningful ROI, the base and optimistic cases become upside — not justification.
Three numbers, derived from the structure above, give a CFO everything needed to decide:
The single most common error in stablecoin business cases is overestimating adoption. Customers don't switch payment methods because you enabled a new one. They switch when the new method is genuinely better for them — typically international customers facing high decline rates, B2B customers tired of wire failures, or contractors weary of FX markup. Model adoption against the segments where the new option is meaningfully better, not the total addressable customer base. Over-modeled adoption produces approval-stage credibility damage that takes quarters to recover from.
The seven operator profiles introduced in Module 02 Lesson 07 each have characteristic ROI shapes. The worked examples below apply the model framework from Lesson 05 to each profile using conservative assumptions. The numbers are illustrative; the structure is reusable for any operation with the underlying data.
| Line | Annual Impact (Conservative) |
|---|---|
| Current effective rate (PayPal/wire mix at ~4.5%) | ~$8,100 fees |
| Stablecoin route (~0.3% on Request Finance + minimal overhead) | ~$540 fees |
| Gross savings | ~$7,560 |
| Integration cost (one-time, ~8 hours @ $75 loaded) | ~$600 |
| Ongoing overhead (~30 min/month) | ~$450 |
| Year-one net savings | ~$6,500 |
| Payback period | ~5 weeks |
Verdict: The smallest absolute number on the list — but the largest percentage of revenue recovered. For a solo operator, this is meaningful take-home income returned. Adoption is trivially fast because the operator controls every variable.
| Line | Annual Impact (Conservative) |
|---|---|
| Card processing on domestic ($45K/mo @ 3%) | ~$16,200 fees |
| International invoicing ($60K/mo @ wire + FX) | ~$15,000 fees |
| Contractor payroll ($15K/mo, 6 contractors) | ~$3,200 fees + FX |
| Current baseline | ~$34,400 |
| Stablecoin route (30% adoption on intl, 100% on payroll) | ~$22,000 saved |
| Integration + overhead (year 1) | ~$8,400 |
| Year-one net savings | ~$13,600 |
| Payback period | ~5 months |
Verdict: A defensible mid-five-figure annual savings driven primarily by contractor payroll and international invoicing — not by replacing domestic card processing. Start where the math is clearest; expand once adoption data justifies it.
| Line | Annual Impact (Conservative) |
|---|---|
| Card processing fees (~3% effective) | ~$144,000 |
| Chargebacks (1.5% × $4.8M ARR × $385 full cost / $50 avg) | ~$554,400 composite |
| Reserve drag (7% × 180-day on $1.68M @ 8%) | ~$94,080 |
| Current composite cost | ~$792,000 |
| Stablecoin route at 30% conservative adoption | ~$237,000 saved |
| Implementation + overhead (year 1) | ~$45,000 |
| Year-one net savings | ~$192,000 |
| Payback period | ~3 months |
Verdict: Chargeback economics dominate. The fee savings line is the smallest of the three benefit categories. The largest under-modeled benefit in the entire category, and the strongest fit for SaaS companies with measurable chargeback exposure.
| Line | Annual Impact (Conservative) |
|---|---|
| Card processing on domestic ($1.875M @ 3%) | ~$56,250 |
| Card processing on intl ($625K @ 5.5% + 20% decline impact) | ~$76,500 composite |
| Chargeback & refund handling (0.6% rate, full cost) | ~$57,800 |
| Current baseline | ~$190,550 |
| Stablecoin route (40% intl adoption · partial domestic) | ~$68,000 saved |
| Implementation + overhead | ~$22,000 |
| Year-one net savings | ~$46,000 |
| Payback period | ~5 months |
Verdict: International conversion lift (from reduced decline rates) is the under-modeled component. A 20% decline rate on international card transactions effectively means 20% of attempted international revenue evaporates at checkout. Stablecoin checkout typically clears at 95%+. The fee savings line undersells the actual revenue impact.
| Line | Annual Impact (Conservative) |
|---|---|
| Wire fees (~$1.26M @ avg $60 + 2% FX) | ~$28,000 |
| Wire failures & resolution overhead (8% failure rate) | ~$15,000 |
| DSO carrying cost on slow settlement (avg 12-day delay @ 8% cost of capital) | ~$33,000 |
| Current baseline | ~$76,000 |
| Stablecoin route (50% conservative adoption among intl clients) | ~$38,000 saved |
| Implementation + overhead | ~$12,000 |
| Year-one net savings | ~$26,000 |
| Payback period | ~3.5 months |
Verdict: The DSO line (carrying cost of delayed settlement) frequently exceeds the fee line in services businesses. Working-capital effects matter as much as headline fees. Covered in depth in Lesson 07.
| Line | Annual Impact (Conservative) |
|---|---|
| Payment processing on GMV (~2.9% blended) | ~$580,000 |
| Seller-payout costs (200 sellers × monthly intl payouts) | ~$120,000 |
| Chargeback exposure (marketplace risk surcharge tier) | ~$280,000 composite |
| Reserve drag (10% × 180-day) | ~$160,000 |
| Current baseline | ~$1,140,000 |
| Stablecoin route — 30% adoption + programmable splits eliminate payout overhead | ~$340,000 saved |
| Implementation + overhead (multi-quarter) | ~$95,000 |
| Year-one net savings | ~$245,000 |
| Payback period | ~4 months |
Verdict: Marketplaces capture the broadest range of structural benefits — fees, chargebacks, payout automation via programmable splits, reserve recovery. The strongest composite case in the category, though the implementation effort is also the highest.
| Line | Annual Impact (Conservative) |
|---|---|
| Cross-border treasury movements (intercompany, supplier, payroll) | ~$420,000 fees + FX |
| Working capital tied in float (avg 3-day settlement on $50M) | ~$330,000 opportunity cost @ 8% |
| FX hedging cost on non-USD operating exposure | ~$180,000 — partially substitutable with stablecoin hedging |
| Addressable baseline | ~$930,000 |
| Conservative stablecoin route (custodial multi-sig, regulated processors, 25% migration) | ~$280,000 saved |
| Implementation + governance + audit + custody (year 1) | ~$150,000 |
| Year-one net savings | ~$130,000 |
| Payback period | ~8 months |
Verdict: Enterprise economics differ from SMB economics in two ways: implementation cost is materially higher (governance, audit, custody, internal-control redesign) and adoption pace is slower. The business case is still strong, but the timeline assumes 18–36 month deployment rather than 90 days. Year-three NPV typically dominates the conversation, not year-one savings.
Across all seven profiles, three patterns repeat. First: chargeback economics dominate where they exist; fees dominate where they don't. Second: implementation cost scales with organizational complexity, not with revenue. Third: the working-capital line — slow settlement carrying cost, reserve drag, DSO — frequently rivals or exceeds the headline fee savings, and is under-modeled in almost every initial business case.
Headline fee savings are visible. Working-capital effects are not — yet for many operators they dominate the actual financial impact of payment-rail modernization. The accounting is straightforward. It just isn't typically part of a payments conversation.
| Effect | What Changes | How to Quantify |
|---|---|---|
| Settlement velocity | Funds move from "earned" to "available for use" in seconds rather than days | (avg settlement delay reduction in days × annual processed volume × cost of capital ÷ 365) |
| Reserve release | Rolling reserves at card processors disappear with stablecoin rails | (reserve % × volume held × hold duration × cost of capital ÷ 365) |
| DSO compression | Days Sales Outstanding shortens — customers pay faster because the rail itself is faster | (historical avg DSO − new avg DSO) × daily revenue × cost of capital ÷ 365 |
The firm bills 70% of revenue internationally on net-30 terms via wire. Historical average DSO: 38 days (8-day wire-and-resolution delay layered on net-30). The firm migrates 50% of international invoicing to stablecoin on Request Finance. New average DSO on stablecoin invoices: 27 days. Cost of capital: 8%.
The recurring $4,200/year is the visible part. The $52,700 of one-time working capital released — which can fund inventory, hires, or debt reduction — is the buried benefit. For capital-constrained operators this is often the most consequential single number in the analysis.
Working-capital effects are most material for businesses where cash conversion velocity is a binding constraint on growth — services firms with consultant payroll obligations before client payment, e-commerce businesses funding inventory ahead of fulfillment, agencies fronting media spend before client billing, marketplaces holding seller payouts. For businesses with substantial cash reserves and no working-capital constraints, the dollar value of the effect is real but operationally invisible. Calibrate the case accordingly.
Beyond velocity, stablecoin rails introduce capabilities that don't exist on traditional rails: conditional release, automated splits, escrow with cryptographic conditions, programmable royalty routing. These don't fit neatly into a fee-comparison spreadsheet, but they materially change cost-to-serve for specific workloads:
| Capability | Traditional Cost | Programmable Settlement |
|---|---|---|
| Marketplace seller payouts | Custom escrow + manual disbursement OR third-party service @ 1–3% | On-chain split on receipt · near-zero marginal cost |
| Royalty distribution | Quarterly batch processing + bookkeeping headcount | Automatic per-transaction split to N recipients |
| Milestone-based contractor payment | Manual approval + wire + reconciliation | Smart-contract escrow with cryptographic release conditions |
| Multi-party affiliate revenue share | Spreadsheet + monthly wire batch + chargeback exposure | Automatic on-transaction routing |
| Cross-entity intercompany settlement | FX-laden wires + treasury reconciliation | Stablecoin transfer + automatic ledger entry |
Working-capital effects and programmable-settlement capabilities are the two ROI categories that turn defensible stablecoin business cases into compelling ones. They don't replace headline fee math; they layer on top. For operators in the right pattern — services, marketplaces, multi-party flows, capital-constrained growth — they frequently double or triple the total ROI a fee-only analysis would surface.
The model from Lessons 05 and 06 produces numbers. Leadership review requires a document. The format below is the institutional standard for finance-led business cases — concise enough to read in a meeting, complete enough to defend, structured enough to compare against alternative capital allocations.
| Section | What It Contains |
|---|---|
| 01 · Executive summary | Three sentences: the proposal, the headline financial impact, the recommendation. |
| 02 · Problem & opportunity | The transactional friction or cost being addressed. Specific. Sourced from internal data. |
| 03 · Proposed solution | The architecture: processor(s), stablecoin(s), chain(s), wallet stack. One paragraph. References Module 02 stack pattern. |
| 04 · Financial model | Conservative / base / optimistic scenarios from Lesson 05. Payback period, year-one net savings, three-year NPV. Conservative case in bold. |
| 05 · Implementation plan | 30 / 60 / 90 day milestones. Resource requirements. First-quarter operational metrics. |
| 06 · Risk & mitigation | Top five risks named explicitly. Mitigations referenced to Module 02 controls (multi-sig, processor redundancy, off-ramp redundancy, internal authorization, address verification). |
| 07 · Compliance posture | Regulatory jurisdiction(s), processor compliance status (MiCA / FCA / MAS / federal-state), tax/accounting treatment. References Module 02 Lesson 09 risk taxonomy. |
| 08 · Decision & ask | The decision being requested. Budget approval. Authority delegations. Success criteria. Review cadence. |
A well-constructed business case anticipates the questions leadership will ask. The list below recurs in virtually every institutional review of payment-infrastructure changes. Prepare answers in advance.
The most consequential property of a successful business case isn't analytical rigor — it's operational confidence without overclaim. Reviewers approve cases authored in the voice of someone who has thought through the failure modes and is comfortable defending the conservative scenario. They decline cases authored in the voice of someone selling the proposal. Write the case the way Modules 01 and 02 read: calm, structured, honest about tradeoffs, grounded in what works rather than what's possible.
Mistake 1. Quoting headline rates rather than effective rates. Effective rate is always 50–150 bps higher than nominal. Use effective rate from your own statements.
Mistake 2. Under-pricing chargebacks at the disputed amount. Full cost runs 2–3× the disputed amount. Include reserve drag and representment overhead.
Mistake 3. Ignoring operational overhead. Implementation, reconciliation, treasury management, and training all cost real hours. Quantify them or your conservative case isn't actually conservative.
Mistake 4. Modeling adoption against total customer base. Model against the segments where the new rail is genuinely better. Optimistic adoption assumptions destroy reviewer credibility.
Mistake 5. Omitting working-capital effects. DSO compression, reserve release, and settlement velocity frequently rival or exceed fee savings. Lesson 07 must appear in the model.
Mistake 6. Presenting only the optimistic case. Institutional reviewers approve on the conservative case. Lead with it.
The economics of stablecoin payment rails resist easy summary because the headline rate is one layer of many. The honest analysis requires naming every fee layer on both sides, pricing chargebacks at full cost rather than disputed amount, and including working-capital effects most analyses ignore entirely. Done honestly, the analysis produces defensible numbers — and for the right operator profiles, those numbers are decisive.
Three patterns repeat across the seven operator profiles. Chargeback economics dominate where chargebacks exist. Working-capital effects rival or exceed fee savings for capital-constrained operators. Implementation cost scales with organizational complexity, not revenue. The business case format from Lesson 08, anchored on the conservative scenario from Lesson 05, is the artifact that earns approval — structured, sourced, honest about tradeoffs, grounded in the same operational discipline that runs through Modules 01 and 02.
Module 04 turns to the accounting, reconciliation, and tax discipline that converts the architecture into audit-ready operations.
Before any ROI model built from this module travels to a board, a lender, or an investor, have your accountant or CPA review the assumptions — and have counsel look at any forward-looking statements. Illustrative frameworks become representations the moment someone relies on them. An hour of professional review is cheap insurance on a document that travels.