Key takeaways
- A platform that holds stablecoins and fiat for customers must prove each day, per asset and per currency, that what it holds covers what it owes, with no stablecoin surplus offsetting a dollar shortfall.
- Blockchains settle around the clock, while the Fedwire Funds Service runs on weekdays only, from 9:00 p.m. ET on the previous day to a 7:00 p.m. ET cut-off for bank transfers, so one fixed snapshot time is needed for both sides.
- Network fees on Ethereum must be paid in ether, not in the stablecoin, so a USDC payment flow creates a separate ether cost that belongs to the platform, never to customers.
- Under Texas law a licensee may count stablecoin towards permissible investments only up to its outstanding obligations in the same kind of stablecoin (Tex. Fin. Code 152.356(a)(6)).
- In the UK, CASS 17 will require a client cryptoasset reconciliation at least once each business day per trust and per asset class, with no allowance for shortfalls caused by timing, from 25 October 2027.
What are the key facts on stablecoin and fiat reconciliation?
A platform holding both stablecoins and fiat for customers runs one daily reconciliation that covers both, kept separate by asset and by currency.
| Item | Position |
|---|---|
| Who it applies to | Platforms, marketplaces and payment firms that accept, hold or pay out stablecoins (for example USDC) alongside fiat for customers or merchants |
| Records matched | Internal ledger, blockchain wallet balances and transactions, custodian statements, bank statements and conversion partner reports |
| Unit of comparison | Each asset and each currency separately, per legal entity; USDC owed is covered by USDC held, dollars owed by dollars held |
| Main timing issue | Blockchains settle 24 hours a day; Fedwire operates on weekdays only, closing to bank transfers at 7:00 p.m. ET |
| Main cost issue | Network fees (gas) are paid in the network's own token, such as ether, and conversion spreads fall on the platform when merchants are paid at par |
| US rules | GENIUS Act custody rules (Section 10); state money transmitter permissible investment rules, for example Texas |
| EU rules | MiCA Articles 70 and 75 for crypto-asset service providers; e-money tokens are deemed e-money under Article 48 |
| UK rules | CASS 17 for client cryptoassets from 25 October 2027 (FCA PS26/11) |
| Last checked | 26 October 2026, against primary legislation and regulator publications |
What is stablecoin and fiat reconciliation?
It is the daily check that a payment firm's records of what it owes customers, in stablecoins and in fiat, agree with what it actually holds on the blockchain, at custodians and in the bank.
A stablecoin is a digital token designed to keep a fixed value against a currency, usually the US dollar, and redeemable with its issuer. USDC, issued by Circle, is the most common example in commerce. When a platform accepts USDC from buyers and pays merchants either in their local currency or in USDC, it ends up holding two kinds of customer money at once: tokens in blockchain wallets and fiat in bank accounts. Its internal ledger, the platform's own record of every balance it owes, has to agree with both.
Existing guides cover the narrower parts. Stablecoin reserve reconciliation is the issuer's check that tokens in circulation are backed by reserves. On-chain reconciliation matches blockchain data to internal records, and crypto custody reconciliation covers exchanges and custodians matching customer ledgers to wallets. This guide covers the combined operating view: a platform or payment firm that is not the issuer, holds both fiat and stablecoins for customers, and converts between them every day.
Which records must agree each day?
Five record sets, each proving something different, must be brought to the same cut-off time and compared asset by asset.
| Record | Where it comes from | What it proves | Typical difference |
|---|---|---|---|
| Internal ledger | The platform's own system of merchant and customer balances | What is owed, per customer, asset and currency | Payments or withdrawals not yet posted |
| Wallet balances and transactions | Read directly from each blockchain, per wallet address and network | What tokens are actually held | Payments received but not yet final; withdrawals sent but not posted |
| Custodian statements | Third-party custodian holding tokens or keys | Tokens held for the platform away from its own wallets | Statement timing; assets moved between custodian and own wallets |
| Bank statements | Banks holding customer fiat | Cash actually held, per account and currency | Wires or ACH not yet received; bank cut-offs |
| Conversion partner reports | Exchange or liquidity provider converting stablecoins to fiat and back | Rate, fees and amount actually received | Proceeds in transit; spread against the rate credited to merchants |
The ledger is the only record of each customer's share when tokens sit in pooled wallets. The blockchain, in contrast, is an external record that anyone can read and nobody can edit, which makes it a stronger source than many bank feeds, provided every wallet is read at the same moment as the ledger.
How does a stablecoin payment reach a merchant?
In four legs: the buyer pays on-chain, the platform records a debt to the merchant, the stablecoin is either converted to fiat or kept, and the merchant is paid out from the bank or to a wallet.
Shopify's announcement of USDC on Shopify Payments, dated 12 June 2025, is a public example of this model. Built with Coinbase and Stripe, it lets merchants "accept USDC from customers globally on the Base network", a blockchain network built by Coinbase. Shopify states that "merchants will receive their local currency by default, with no foreign transaction or exchange fees", or can instead "claim USDC directly into their own wallet". Customers can pay "from hundreds of supported crypto wallets, on guest checkout and with Shop Pay".
For the reconciliation team this creates two populations of merchant balances. Merchants paid in local currency are owed fiat, even though the money arrived as USDC, so the platform must convert and carry the conversion risk until the fiat reaches its bank. Merchants who claim USDC are owed tokens, and the platform must hold the same tokens until it sends them out. Each leg leaves a trail that must be matched: the buyer's on-chain transaction, the ledger entry crediting the merchant, the conversion trade, the bank receipt and the payout file or outgoing on-chain transfer.
How do block confirmations and bank cut-offs create timing differences?
The blockchain side never closes and the bank side closes every evening and at weekends, so balances read at different moments will disagree even when nothing is wrong.
A blockchain transaction is not final the moment it appears. On Ethereum, according to ethereum.org, "it takes about 15 minutes for an Ethereum block to finalize", meaning to reach the point where it can no longer be reversed. Each platform sets its own confirmation policy per network and should credit customers only once a payment meets it. Payments seen on-chain but not yet final at the cut-off are a timing item: held in the wallet, not yet owed in the ledger.
The fiat side runs on banking hours. The Fedwire Funds Service, the Federal Reserve's large-value payment system in the US, opens its business day at 9:00 p.m. ET on the preceding calendar day and closes at 6:45 p.m. ET for customer transfers and 7:00 p.m. ET for bank transfers. It does not operate on Saturdays, Sundays or Federal Reserve holidays. In October 2025 the Federal Reserve announced its intention to add Sundays and weekday holidays, for six operating days a week, to be implemented in 2028 or 2029.
The practical answer is one snapshot time, applied to every wallet, every custodian, every bank account and the ledger, with two holding accounts in the ledger: payments received on-chain but not final, and conversion proceeds sent by the partner but not yet received by the bank. A stablecoin sold on Saturday morning for dollars that arrive on Monday sits in the second account for two days. These items must clear by rule on the expected date; anything that does not clear becomes a break to investigate.
How should gas, fees and exchange rates be recorded?
Every cost and every conversion rate is recorded as a separate line at the moment it occurs, so that no fee ever reduces a customer balance by mistake.
Gas is the fee paid to a blockchain network to process a transaction. On Ethereum, ethereum.org states that "gas fees have to be paid in Ethereum's native currency, ether (ETH)". A USDC transfer therefore costs ether, not USDC. Platforms that hold ether for fees should keep it in their own wallets, separate from customer token wallets, and record it as the platform's expense. If a customer wallet is used to pay fees, customer holdings fall below the ledger and a shortfall appears.
| Cost or rate | When it arises | How to record it |
|---|---|---|
| Network fee (gas) | Every on-chain transfer, sweep or payout | Platform expense in the network token, from the platform's own wallet |
| Conversion spread | Stablecoin sold for fiat at a rate below 1.0000 | Executed rate and amount from the partner report; the gap to the amount credited to merchants is the platform's cost |
| Partner or bank fees | Conversion, wire or payout | Separate fee line; never netted silently against customer funds |
| Local currency rate | Merchant paid in a currency other than US dollars | Rate and time of the trade, kept with the payout record |
A stablecoin's value against the dollar is a market price, not a guarantee, so the platform should record the rate it actually achieved, with its time, rather than assume one to one. Where merchants are credited at par, as in the Shopify model, any spread is the platform's own cost and must be funded from its own money.
What does a daily stablecoin and fiat reconciliation look like?
It produces one position per asset, each tested on its own, with every difference given a cause.
Worked example. Nexus Payments, a fictional US platform, takes its snapshot at 23:00 UTC. Merchants who chose local currency are owed USD 12,400,000. Merchants who chose to claim USDC are owed 3,150,000 USDC. Earlier that day the platform sold 480,000 USDC received from buyers to its conversion partner at 0.9995 dollars per USDC, having already credited the merchants USD 480,000; the dollars, USD 479,760, are due at the bank on the next business day.
| Line | US dollars | USDC |
|---|---|---|
| Owed to merchants (ledger) | 12,400,000 | 3,150,000 |
| Bank balance or on-chain wallet balance | 11,920,000 | 3,152,650 |
| Less: buyer payments on-chain, not yet final | n/a | (3,500) |
| Add: conversion proceeds in transit | 479,760 | n/a |
| Holdings counted | 12,399,760 | 3,149,150 |
| Difference | (240) | (850) |
| Cause | Spread: 480,000 x 0.9995 = 479,760 | Merchant withdrawal sent on-chain at 22:58, not yet posted |
| Action | Fund USD 240 from own money today | Post the withdrawal; USDC owed falls to 3,149,150 |
The two differences have different meanings. The USD 240 is a real shortfall: the platform promised merchants USD 480,000 and received USD 479,760, so it must top up from its own funds. The 850 USDC is a posting delay: once the withdrawal is recorded, the amount owed falls to 3,149,150 USDC and matches holdings exactly. The ether used to pay for the withdrawal sits in the platform's own fee wallet and plays no part in either column. Netting the two columns into one dollar total would hide both findings, which is why each asset is tested separately. Whether in-transit conversion proceeds may count towards a regulatory coverage test depends on the applicable rules, so they should always be shown as a separate line.
How do regulators treat stablecoin balances held for customers?
In the US, the EU and the UK, stablecoins held for customers must be kept apart from the firm's own assets, recorded per customer and, in several regimes, covered in the same kind of asset.
| Jurisdiction | Rule | What it means for reconciliation |
|---|---|---|
| US federal | GENIUS Act, Section 10 (12 U.S.C. 5909) | Custodians of payment stablecoin reserves, stablecoins used as collateral or issuing keys must treat customer stablecoins and cash as the customer's, account for them separately and not commingle them, with an omnibus account exception; customer claims to stablecoins held for them have priority |
| Texas | Tex. Fin. Code 152.003(19) and 152.356(a)(6); Supervisory Memorandum 1037 | A fully backed, redeemable stablecoin pegged to a currency is money or monetary value; it counts towards permissible investments only up to obligations in the same kind of stablecoin |
| EU | MiCA Articles 70, 75 and 48(2) | Client crypto-assets protected and never used for the firm's own account; a register of positions per client; holdings segregated on the ledger; e-money tokens are deemed e-money |
| UK | CASS 17 (FCA PS26/11), from 25 October 2027 | Client cryptoasset reconciliation at least once each business day per trust and asset class; shortfalls topped up in the same class and reported to the FCA if not resolved by the next reconciliation |
United States. The GENIUS Act, Public Law 119-27, was signed on 18 July 2025 and takes effect on the earlier of 18 months after enactment or 120 days after the regulators issue final implementing regulations. Section 10 sets the custody rules above, and Section 3(b) makes it unlawful, from three years after enactment, for a digital asset service provider to offer or sell a payment stablecoin in the US unless it is issued by a permitted issuer. State money transmitter rules apply alongside. The Texas Department of Banking states that a licensee "may only include virtual currency assets in calculations for its permissible investments under Finance Code §152.356 if it is stablecoin, and only to the extent of outstanding transmission obligations received by the licensee in the same kind of stablecoin". A platform that converts most stablecoin receipts to dollars must therefore cover its dollar obligations with dollar-type assets. Our guide to like-kind holding requirements covers other states.
European Union. Under MiCA Article 70, a crypto-asset service provider holding clients' crypto-assets must protect their ownership rights and prevent their use for its own account, and must place client funds other than e-money tokens with a credit institution or central bank by the end of the business day after receipt; the funds rules do not apply to providers that are themselves e-money, payment or credit institutions. Article 75 requires a register of each client's positions, an electronic statement at least every three months, and segregation of client holdings, including on the distributed ledger. Because Article 48(2) deems e-money tokens to be electronic money, a euro or dollar e-money token sits close to the fiat side of the reconciliation.
United Kingdom. The FCA's cryptoasset regime applies in full from 25 October 2027. In PS26/11, CASS 17.5.10R requires a client cryptoasset reconciliation for each trust at least once each business day, comparing what clients are owed with what is held, per asset class, at the same point in time, with a record of each one kept for five years. The FCA declined to treat timing differences as an excuse for crypto shortfalls, noting that bank cut-offs do not apply to a market that runs around the clock. Client money arising from safeguarding client cryptoassets falls under CASS 7.
What should a platform check every day?
These checks cover both sides of a combined stablecoin and fiat book.
- One snapshot time applied to every wallet, custodian, bank account and the ledger.
- A separate position for each asset and each currency, per legal entity, with no netting across them.
- Every wallet address in the register, tagged as customer or platform, with no unlisted wallets holding customer tokens.
- Buyer payments credited only after the platform's confirmation policy for that network is met.
- Network fees paid only from platform wallets and booked as platform expense.
- Executed conversion rate, time and fees taken from the partner report, with any spread funded the same day.
- Conversion proceeds in transit tracked to the expected bank receipt date, and escalated if late.
- Custodian statements agreed to internal records for every custodied asset.
- Coverage tested against the applicable rules, for example same-kind stablecoin coverage in Texas.
- Every difference recorded with its amount, cause, owner and resolution.
How does Safeheld help?
Safeheld matches bank statements, processor and partner reports, ledgers, custody and blockchain wallet records every day, with one position per legal entity in its own currency, never offset against another entity and agreeing back to a group total.
Differences are raised the day they appear: routine timing items clear by rule, and others are worked to a cause with the evidence recorded. Regulatory returns, including prepared packs for the US state and NMLS call report, are built from the same reconciled figures. See Safeheld for stablecoins and daily reconciliation.
Frequently asked questions
What is stablecoin reconciliation?
It is the daily check that a firm's records of stablecoins owed to customers agree with the tokens it holds in blockchain wallets and at custodians. For a payment platform it also covers the fiat side: bank accounts and conversion proceeds.
How do you reconcile stablecoin payments with fiat payouts?
Take one snapshot time, read every wallet, custodian, bank account and the ledger at that moment, and compare each asset and currency separately. Track payments not yet final and conversion proceeds in transit in their own accounts, and give every remaining difference a cause.
Can a USDC surplus cover a US dollar shortfall?
No. Each asset is tested on its own. In Texas, for example, stablecoin counts towards permissible investments only up to obligations in the same kind of stablecoin, so dollar obligations need dollar-type assets.
Why do block confirmations cause reconciliation differences?
A payment visible on-chain may not yet be final. On Ethereum a block takes about 15 minutes to finalise, so payments seen but not final at the cut-off are held in the wallet but not yet owed in the ledger, and must be shown as a timing item.
Who pays the gas on stablecoin transfers?
On Ethereum gas must be paid in ether, not in the stablecoin. Platforms should pay it from their own wallets and book it as their own expense, so customer token balances are never reduced by fees.
Does the GENIUS Act apply to platforms holding stablecoins for customers?
Section 10 sets custody rules for persons holding payment stablecoin reserves, stablecoins used as collateral or issuing keys: customer property treated as the customer's, separately accounted for and not commingled. Section 3(b) restricts digital asset service providers to permitted issuers' stablecoins from three years after enactment.
How does MiCA treat stablecoins held for clients?
Article 70 requires client crypto-assets to be protected and never used for the provider's own account, and Article 75 requires a per-client register of positions and segregation on the ledger. E-money tokens are deemed electronic money under Article 48.
When do UK rules on client cryptoasset reconciliation start?
The FCA's cryptoasset regime applies in full from 25 October 2027. CASS 17 then requires a client cryptoasset reconciliation at least once each business day for each trust and asset class.
References
- Shopify, Stablecoins on Shopify: USDC on Shopify Payments (12 June 2025)
- Public Law 119-27, Guiding and Establishing National Innovation for U.S. Stablecoins Act (GENIUS Act), 18 July 2025
- Texas Department of Banking, Supervisory Memorandum 1037, Regulatory Treatment of Virtual Currencies Under the Money Services Modernization Act (rev. 28 January 2025, PDF)
- ESMA interactive single rulebook, MiCA Article 70: safekeeping of clients' crypto-assets and funds
- ESMA interactive single rulebook, MiCA Article 75: custody and administration of crypto-assets on behalf of clients
- FCA, PS26/11 Regulated cryptoasset activities, including CASS 17 (June 2026, PDF)
- Federal Reserve Financial Services, Fedwire Funds Service and National Settlement Service operating hours
- ethereum.org, Single slot finality (current finality time)
About Safeheld
Safeheld is reconciliation and regulatory reporting software for regulated firms that hold client money, across countries, currencies and regulators, in fiat and stablecoin. For platforms and payment firms holding both, it matches bank, partner, ledger, custody and blockchain wallet records every day, per entity and currency, and records the cause of every difference. To discuss your stablecoin and fiat reconciliation, contact us at safeheld.com/contact.
This article is general information on stablecoin and fiat reconciliation for payment firms and is not legal or regulatory advice.