When does a stablecoin payment route earn its place?

Decision and provisional conclusion

A fictional treasury team makes twenty $100,000 cross-border payments each month. It is considering an additional route that converts fiat into a stablecoin, transfers it and converts back into the recipient’s local money. The decision is whether to fund a limited operating pilot.

Provisional conclusion: the assumed economics support a pilot, with a modeled saving of approximately $133 per payment after allocating incremental monthly operating costs. They do not yet support moving the full flow. The conversion quote, availability of recipient funds and exception-handling arrangements remain unverified.

The baseline keeps the existing route available. The pilot would have a defined payment limit, an accountable operator and stop conditions agreed with the treasury team.

1 / Define the endpoint before comparing routes

The measured outcome is usable money in the recipient’s account. The comparison starts when the payer commits funds and ends when the recipient can use the intended currency. Token transfer confirmation is an intermediate event.

Circle’s documentation distinguishes fiat deposits, stablecoin availability, onchain transfers and redemption. It also describes different settlement timing for different bank rails. This supports analyzing each leg separately; it does not establish the performance or eligibility of this hypothetical route. Source: Circle’s minting and redemption documentation, reviewed 5 November 2026.

For a real mandate, the operating diagram should identify the legal entity, account, asset, currency and responsible party at every leg. Written provider terms and observed transaction timestamps would replace assumptions.

2 / Compare the whole cost

Both routes are modeled at the same $100,000 payment size and a hypothetical 6% annual capital opportunity cost. The token route adds $2,000 per month of incremental integration and operations cost, allocated across twenty payments. These figures are invented for the example.

Calculations use unrounded inputs; displayed dollar amounts are rounded to the nearest cent.

Method: conversion cost = payment size × basis points ÷ 10,000. Capital cost = payment size × annual rate × days ÷ 365. Expected exception cost = assumed frequency × handling cost. These handling costs exclude loss of principal; exposure to such losses requires separate limits and diligence.

Only incremental operating costs enter this comparison. Shared staff and systems costs are excluded from both sides. Any dedicated prefunding reserve, hedging cost, tax effect or additional provider fee would need its own line before a real decision.

3 / Find the assumptions that can reverse the result

• Conversion spread: holding all other assumptions fixed, the token route reaches cost parity at approximately 31.33 basis points of combined conversion cost, compared with the assumed 18. An apparently small change in execution terms can absorb the advantage.
• Payment volume: the $2,000 monthly overhead is material. At the assumed payment size and other inputs, the token route needs at least nine payments per month to cover that incremental overhead. Eight would not be enough.
• Funding delay: each extra day tying up the $100,000 adds approximately $16.44 at the assumed annual rate. Additional prefunding outside the payment itself is not included.
• Exceptions: a low average handling cost can conceal an unacceptable tail event. Failure to redeem, a frozen account or an unresolved beneficiary mismatch is an operating and counterparty question as well as a cost question.

Explore the interactive cost model → The model tests per-payment fees, conversion, capital and exceptions; the monthly overhead adjustment above is an additional step in this memo.

4 / Evidence required before a pilot

5 / Pilot, measure, then decide

The illustrative pilot uses a limited number of low-value payments after eligibility and counterparty checks. The team records quoted and realized costs, timestamps for every leg, exception frequency, handling time and recipient confirmation. No assumed saving is reported as realized until these observations exist.

The team would agree success thresholds in advance for all-in cost, usable-funds timing, reconciliation and operational workload. An unresolved eligibility issue, inability to verify receipt or exposure above the approved limit stops the pilot. Expanding the route requires a written review of the observed results and the remaining limitations.

What would change the conclusion: a conversion quote above the break-even level, lower sustainable volume, materially higher prefunding needs or failure of an operating prerequisite would remove the case for rollout. A successful technical transfer alone would not resolve those questions.