Stablecoin Due Diligence Checklist for Corporate Treasury Teams

Stablecoin due diligence is not simply a review of whether a token usually trades near its reference currency. A corporate treasury must assess the complete operating path: acquiring the stablecoin, holding it securely, transferring it on an approved network and converting it back into usable bank money.

That path may depend on an issuer, reserve custodians, wallet technology, exchanges, liquidity providers, banks, blockchain networks and fiat payment rails. A weakness in any one dependency can prevent treasury from meeting a payroll, supplier or liquidity deadline. The review should therefore produce an evidence-backed approval with exposure limits, authorised networks, permitted providers and a defined exit plan.

1. Define the intended treasury use

Start with the transaction rather than the token. A stablecoin suitable for occasional supplier payments may not be appropriate for customer funds, payroll or a large operating reserve.

• Use case: Document whether the asset supports collections, cross-border payouts, payroll, working capital or short-term holdings.
• Currency path: Identify the source fiat currency, stablecoin, blockchain network and destination currency.
• Exposure: Set expected and maximum balances, individual transaction limits and maximum holding periods.
• Timing: Record settlement deadlines, bank cut-offs and weekend or public-holiday requirements.
• Exit requirement: Define how quickly the full position must become cleared funds in the required bank account.

This scope creates measurable approval criteria. For example, a treasury could require two operationally independent conversion routes for its maximum balance. Those routes are not genuinely independent if they ultimately rely on the same exchange, bank or liquidity provider.

2. Review the issuer, reserves and holder rights

Identify the legal entity responsible for issuing and redeeming the stablecoin. Review its contracting jurisdiction, ownership, operating history, eligibility rules and the terms that govern token holders. Determine whether your company has a direct contractual redemption right or merely expects to sell the token to another market participant.

Obtain the latest reserve disclosures and record:

• The proportions held in cash, bank deposits, government bills, money market instruments or other assets.
• The maturity and liquidity profile of reserve investments.
• Whether reserves are described as segregated from operating assets.
• The concentration of banks, custodians and investment managers where disclosed.
• The reporting date, publication frequency and comparison of reserve assets with tokens outstanding.
• Whether the document is an attestation, financial statement audit or management report, including its scope and exclusions.

An attestation reports on specified information under a defined engagement. It should not be treated automatically as a full financial statement audit, a legal opinion on asset ownership or a guarantee of immediate redemption. Treasury should retain the actual report reviewed, not only a webpage stating that reserves are backed.

3. Test redemption and secondary-market liquidity

Direct redemption and exchange liquidity are different exit routes. Direct redemption depends on issuer eligibility, onboarding, minimums, fees, processing procedures and access to the relevant bank rail. A market sale depends on available bids, trading limits, venue access and the ability to withdraw the fiat proceeds.

Blockchains can process transfers outside banking hours, but that does not mean fiat proceeds can reach a bank account continuously. ACH, Fedwire, SEPA, SEPA Instant, SWIFT, Faster Payments, CHAPS and BACS differ in availability, cut-offs and participant coverage. Verify the actual rail and receiving bank used for each corridor.

Model the all-in cost under normal and stressed spreads. Use quotes at representative transaction sizes rather than relying only on an advertised fee or aggregate daily volume. Conduct a small end-to-end test and document the time from initiating the stablecoin transfer to receiving cleared fiat.

4. Examine depeg events and hidden concentration

Review historical periods when the stablecoin traded away from its reference value. Record the size and duration of the movement, available depth at your expected transaction size, whether minting or redemption continued and whether relevant networks or providers suspended transfers.

Investigate the cause rather than treating every depeg alike. Possible drivers include concerns about reserve assets, disruption at a banking partner, exchange-specific liquidity, network congestion or broader market stress. Review how quickly the issuer communicated and what evidence supported its statements.

Map concentration across the complete arrangement. Holding two stablecoins does not necessarily diversify risk if both depend on the same reserve bank, custodian, exchange, blockchain or off-ramp. Likewise, two providers may rely on the same underlying banking partner.

5. Approve the token and blockchain together

A ticker is not enough to identify an asset. Record the issuer-confirmed contract address, blockchain and whether the token is issued natively or represented through a bridge. A bridged version introduces dependencies on bridge smart contracts, operators and the assets locked on another network.

Approve supported networks explicitly and configure address books or allowlists accordingly. For each network, review transaction finality, fee variability, operational history and provider support for both deposits and withdrawals. Confirm whether the receiving counterparty supports the exact token and network combination.

Before increasing limits, send a small test transaction in each required direction. Document what happens if funds are sent to the correct address over an unsupported network, including whether recovery is possible, which provider must act and whether recovery is discretionary.

6. Evaluate custody and provider counterparty risk

Map legal ownership and operational control at every stage. In a custodial arrangement, a provider generally controls the private keys while recording the customer’s entitlement. Review contractual segregation, withdrawal rights, administrator powers and the stated treatment of customer assets in insolvency. Obtain legal advice where the ownership analysis is material.

With self-custody, the company controls transaction authorisation but still depends on wallet software, key-management processes and infrastructure. Multiparty computation can distribute signing activity so that a complete private key need not exist in one place. A signing quorum can require several authorised parties before a transfer is broadcast. Treasury must still test recovery, staff departures, lost devices, credential compromise and provider unavailability.

For every custodian, exchange, wallet or off-ramp, collect the legal entity name, contracting jurisdiction, supported assets and networks, transaction limits, fee schedule, banking arrangements where disclosed, incident contacts and complaint escalation route. Complete KYB early enough to identify beneficial ownership, source-of-funds and expected-volume requirements.

7. Verify treasury controls and audit evidence

Controls should reflect transaction size, frequency and irreversibility. At minimum, separate payment creation from approval, require quorum for material transfers, restrict destination wallets and review changes to users or approval settings independently.

Sanctions and address screening should occur before funds are sent, with documented procedures for alerts, false positives and escalation. Screening is a control input, not a substitute for deciding whether the counterparty and transaction are legitimate.

The evidence pack for each payment should connect the business request, invoice, beneficiary, approved wallet address, screening result, approvers, transaction hash, exchange rate, fees and final bank or counterparty confirmation. Stablerail supports USDC and USDT treasury workflows with approvals and signing quorum, pre-send sanctions and address screening, global payouts, fiat off-ramp and exportable audit evidence.

8. Resolve accounting, tax and jurisdiction questions

Ask accounting advisers how the stablecoin should be classified under the company’s applicable reporting framework. Set a consistent valuation source and time, and define the treatment of spreads, provider charges, blockchain fees and realised or unrealised movements.

Reconcile on-chain balances with wallet or provider records and the general ledger. Monthly reconciliation may be insufficient for a high-volume payment account, so frequency should match activity and financial reporting risk. Investigate pending, failed and replaced transactions rather than treating a broadcast transaction as completed automatically.

Tax and reporting consequences vary by jurisdiction and activity. Fiat conversion, stablecoin swaps, yield arrangements, compensation and supplier payments may require different analysis. Confirm that the issuer, provider, asset and intended activity are available to the company’s legal entity, jurisdiction and industry before funding the account.

Final approval checklist

1. Document the use case, maximum exposure, holding period and exit deadline.
2. Retain issuer terms, reserve reports and evidence of redemption eligibility.
3. Test primary and backup conversion routes at a representative scale.
4. Approve exact contract addresses, networks, providers and transaction limits.
5. Confirm custody, recovery, segregation and insolvency terms.
6. Test approvals, signing quorum, address controls, screening and evidence exports.
7. Approve accounting, reconciliation, tax and jurisdictional treatment.
8. Assign an owner and review date, with earlier reassessment after material incidents or changes.

The decision should be more precise than “approved” or “rejected.” State the permitted use cases, maximum balance, networks, providers and required controls. Repeat due diligence periodically and when reserve composition, redemption terms, banking partners, supported networks, legal terms or the treasury’s exposure materially changes.