Digital Dollars and Cross-Border Business Payments

A cross-border invoice is paid when the supplier receives the agreed value in a form it can use. That makes digital dollars an operational choice involving currencies, counterparties, timing, and records. Start with the supplier’s required outcome: how much should arrive, in which account or wallet, and by when? Then assess whether a digital-dollar route improves that outcome for both businesses.

Understand which kind of money you are moving

A commercial bank deposit is a claim on a commercial bank. Businesses already hold and transfer money electronically through such accounts. A central bank digital currency, or CBDC, is a liability of a central bank. A dollar denomination alone does not make a private instrument central bank money.¹

A tokenized deposit represents a bank deposit claim on a programmable platform. Its transfer arrangements matter: the Bank of England describes designs that settle between banks and designs in which a recipient becomes a customer of the issuing bank. Tokenization changes the platform without automatically changing the underlying claim into a stablecoin.²

A dollar stablecoin is a privately issued token designed to track a dollar value. Reserve-backed stablecoins use assets to support that objective. Their issuer, reserve arrangements, and redemption conditions need separate evaluation from those of bank deposits.²

For a payment decision, ask who owes the holder value, what the holder must do to convert it, and which intermediary actually serves the recipient. Grouping everything under digital dollars leaves those operational questions unanswered.

Map the invoice through every currency

Keep four things distinct: the invoice currency, the payer’s funding currency, the transferred asset, and the recipient’s payout currency. A euro-funded company can owe pesos while using a dollar token for one step. That arrangement still needs EUR-to-USD and USD-to-MXN conversion.

If the supplier instead agrees to receive and retain dollar tokens, define that as a different endpoint. Record the accepted asset, quantity, and conditions for acknowledging receipt. Ask whether the supplier expects to spend those tokens or convert them later; that choice determines whose workflow must accommodate the eventual conversion. Share those acceptance criteria with both providers before authorizing funding.

Specify when each rate becomes binding and who carries currency movements between those moments. A reference FX rate can help evaluate a quotation; it does not establish the executable price, token availability, or payout commitment. If one conversion remains open while the other is fixed, record that exposure explicitly.

Agree on the payment destination before funding the transaction. Circle’s integration documentation, for example, distinguishes supported tokens and blockchains and cautions against sending unsupported or bridged assets to Circle Mint addresses.³ Your workflow should verify the exact asset and network accepted by the receiving service, alongside the beneficiary details. Matching a familiar token name is insufficient.

Work through a hypothetical invoice

Consider a wholly hypothetical business paying a Mexican supplier’s MXN 198,000 invoice from euros through an unnamed dollar stablecoin. Assume the selected providers support the complete route and the supplier requires pesos in its bank account. Every price and fee below is an invented assumption.

The payer commits EUR 10,000 at USD 1.10 per euro, producing USD 11,000 before charges. Assume the token is acquired and converted back at dollar parity. Acquisition costs 0.30% of the gross dollar amount, or USD 33. Redemption costs another 0.20% of that same gross amount, or USD 22. Network and local payout charges add USD 1 and USD 25 respectively.

For this example, all USD 81 of costs are deducted from the proceeds. That leaves USD 10,919. At an assumed payout rate of MXN 18 per dollar, the supplier receives MXN 196,542, leaving an unpaid balance of MXN 1,458.

The operations team should therefore request a quotation for a recipient amount of MXN 198,000 and the total euros needed to deliver it. It should also establish whether both conversion rates remain fixed until completion. A successful token transfer would not, by itself, satisfy this invoice: the agreed peso amount must reach the supplier.

Price the entire route

Build the comparison around total payer cost and net recipient value. Request separate figures for acquisition, currency conversion, transfer, redemption, custody where relevant, and local payout. Identify who pays each charge and whether it is deducted from principal or billed separately.

Circle’s USDC terms for holders outside the European Economic Area illustrate why dollar parity needs qualification. They describe redemption through eligible Circle Mint accounts at one dollar per USDC, less applicable fees, while third-party prices can move above or below a dollar. The same terms describe outbound transfer charges, bank fees, and possible currency-conversion costs.⁴

Ask whether a quoted FX price already includes a spread. Adding that spread again as a separate expense would overstate cost. Conversely, evaluating only an explicit transfer charge would omit conversion costs embedded in the price.

Compare competing routes for the same invoice size, recipient amount, quotation time, and delivery requirement. Include the cost of money held in advance and the staff time needed to resolve exceptions. A modest transfer saving can be outweighed by a difficult reconciliation process.

Measure availability at both ends

The BIS describes stablecoin wallet transfers that can occur outside banking hours, while emphasizing that cost and speed improvements are not assured.⁵ That capability concerns a part of the journey. A supplier waiting for local currency needs a delivery promise that covers the banking step too.

For a concrete operational example, Circle’s USD withdrawal FAQ describes weekday availability excluding Federal Reserve holidays and says resulting wires can take one to three business days. It also explains that a receiving bank’s network may apply FX conversion and associated charges for a non-USD account.⁶ Those are conditions of that described service, rather than a timetable for every stablecoin payment.

Check the selected payout provider’s cutoff, time zone, holiday calendar, available liquidity, and destination-bank processing. Request separate estimates for token receipt and usable bank funds. If the last conversion or payout pauses over a weekend, reflect that in the date shown to the customer.

Reconcile the commercial payment

Design the record around the invoice. Link its identifier to the approved quotation, funding debit, conversion rates, token amount, network, transaction reference, payout instruction, fees, and final bank credit. Keep the relevant timestamps and original currencies so finance can explain differences between the approved amount and the amount received.

Maintain separate statuses for funding received, token transfer confirmed, payout submitted, and beneficiary credited. A blockchain transaction reference can help locate one transfer; it does not establish that a particular invoice was paid in full in local currency.

The customer should see the amount expected, the amount delivered, and the next meaningful milestone. If a payout stalls, give a specific update and an owner for resolution. Establish how underpayments, duplicate instructions, rejected bank credits, and refunds will be handled. For a refund involving another conversion, agree on its currency, applicable rate, and fee treatment before an exception occurs.

Pilot with clear operating limits

Begin with one currency route and a small set of willing counterparties. Verify provider onboarding requirements and eligibility for the actual businesses and countries involved. Confirm redemption access, custody responsibilities, transaction limits, and the procedures for a delayed conversion or payout.

Use ordinary treasury controls: independently verify beneficiary changes, require appropriate approvals, and limit the balance held with each provider. Establish who can change wallet destinations and who investigates an unmatched transfer. Decide in advance what happens if a quotation expires or the recipient cannot use the agreed payout method.

Include a delayed payout in the pilot exercise. Have the team locate the funds, identify the responsible provider, and explain the next step to the supplier. Set a clear escalation deadline. This reveals whether support and records remain useful when the normal sequence stops, before larger invoices depend on it.

Measure results against your existing route using final recipient amounts, delivery times, exception rates, and reconciliation effort. Review customer questions as carefully as transfer fees. Expand only when the pilot demonstrates that both businesses can understand the transaction, receive the expected value, and close their records reliably.

Sources