Stablecoin Due Diligence Checklist for Corporate Treasury Teams

Stablecoin due diligence should determine whether corporate treasury can hold, convert and transfer an asset safely under both normal and stressed conditions. The review must extend beyond the issuer to every dependency in the operating chain: reserves, redemption routes, market liquidity, custody, blockchain networks, banks, exchanges, on-ramps, off-ramps and internal approval controls.

Start with the treasury use case

Define the intended use before comparing USDC, USDT or service providers. A stablecoin suitable for occasional supplier payments may not be appropriate for holding several months of operating liquidity.

• Purpose: payments, collections, working capital, payroll, trading collateral or treasury holdings.
• Exposure: average and maximum balance in stablecoin units and the company’s reporting currency.
• Transaction profile: typical payment size, monthly volume, peak-day volume and beneficiary count.
• Required coverage: operating jurisdictions, fiat currencies, blockchain networks and payment rails.
• Timing: acceptable blockchain confirmation time, fiat settlement window, provider cutoff and manual-review delay.
• Concentration limits: maximum exposure to one issuer, network, custodian, bank or conversion provider.

Document non-negotiable requirements and risk limits before requesting quotes. This prevents a low headline fee from outweighing weak redemption access, poor network compatibility or an unsuitable custody structure.

Stablecoin due diligence decision table

Assess the issuer and reserve structure

Identify the legal entity issuing the token and obtain current terms directly from the issuer. Confirm what gives a holder a claim, whether direct redemption is available to the company, and how token holders may rank if the issuer, a reserve bank or a custodian fails. Legal counsel should evaluate insolvency and contractual questions where exposure is material.

Review more than the total reported reserve value. Consider asset type, credit quality, duration, liquidity and concentration. Cash and short-dated government obligations have different stress behavior from corporate debt, loans or digital assets. Examine where reserves are held, how frequently reports are published and whether the methodology has changed.

Distinguish an attestation or assurance report from a financial statement audit. A point-in-time reserve report may support a stated balance, but it does not by itself guarantee redemption, continuous solvency or a particular outcome in insolvency.

Verify redemption and secondary-market liquidity

Direct issuer redemption and selling through an exchange or over-the-counter provider are separate exit routes. Direct redemption may require an approved issuer account, supported bank details, minimum amounts and banking-day processing. A secondary-market sale may be more accessible, but the executable price depends on buyers, market depth and provider limits.

Record eligibility, minimum and maximum sizes, quoted fees, spreads, fiat cutoffs and expected settlement windows for each route. Run a low-value end-to-end test, followed by a transaction closer to the expected business size. Small test trades may not reveal tiered spreads, liquidity constraints or manual reviews that affect larger transfers.

Review previous deviations from the reference price. USDC traded below one US dollar in March 2023 after concerns about reserve cash held at Silicon Valley Bank, then recovered after the related uncertainty eased. USDT has also traded above and below its target price. Treasury should assess the duration of a deviation, redemption availability, issuer communications and whether its own providers remained operational.

Set a written depeg threshold and response process. Possible actions include pausing new receipts, obtaining additional approval, reducing exposure through an available redemption route or switching the asset used for payments. Avoid making an automatic market sale the only response, because it can crystallize a temporary discount.

Review blockchain and token-specific risks

The same stablecoin can have different liquidity and operational characteristics across networks. Verify the contract address against official issuer documentation and confirm whether the asset is natively issued, officially supported or represented through a bridge. A token with a familiar symbol is not necessarily the issuer-supported asset.

Confirm that the sender, recipient, custodian and conversion provider all support the exact network. Assess transaction finality, fee mechanics, operational history and whether native network tokens are needed for fees. Understand the issuer’s ability to freeze addresses or upgrade contracts, and document who bears losses if a bridge is used.

Use beneficiary allowlists and test transfers for new addresses. Screen addresses for sanctions and other risk indicators before sending, while recognizing that screening is a control rather than a guarantee. Transfers to an incorrect address or incompatible network are generally difficult or impossible to reverse.

Map custody and counterparty dependencies

List every party involved in holding, converting or transferring funds: issuer, wallet provider, custodian, exchange, liquidity provider, on-ramp, off-ramp, bank and blockchain infrastructure provider. A single user interface can conceal several legal and operational dependencies.

For each provider, identify the contracting entity, jurisdiction, service scope, client-asset treatment, transaction limits, fees, supported countries and account-recovery process. Ask when transactions can be delayed for compliance review and what evidence the provider requires to release them. Review disclosed banking dependencies and available contingency routes.

For custody, determine who controls the private keys and administrator permissions. In self-custody or multiparty computation arrangements, review signing quorum, recovery shares, device loss, approver departure and administrator replacement. In hosted custody, review contractual asset treatment, withdrawal controls and the consequences of provider insolvency or account restriction.

A consolidated account can reduce operational handoffs but does not remove issuer, banking or blockchain risk. For example, Stablerail combines USDC and USDT treasury operations with approvals and signing quorum, pre-send sanctions and address screening, global payouts, fiat off-ramp, corporate cards and exportable audit evidence. Finance teams should still review the underlying structure and set exposure limits.

Test total cost and execution

Compare the delivered cost rather than the advertised conversion fee. Include the stablecoin spread, provider charge, blockchain fee, fiat payment fee, intermediary bank deduction and any cost caused by settlement delay.

For each important corridor, retain the quote, amount sent, amount received, timestamps, transaction hash, bank confirmation and all fees. Test normal and larger transaction sizes, inbound and outbound flows, and at least one contingency route. Reperform tests when a provider, bank, network or transaction profile changes.

Implement treasury controls and audit evidence

1. Approve maximum balances by stablecoin, issuer, blockchain and provider.
2. Separate beneficiary creation, payment preparation and final approval.
3. Require multiple approvals or a signing quorum above defined thresholds.
4. Allowlist verified wallet addresses and bank accounts.
5. Screen counterparties and destination addresses before funds move.
6. Set per-transaction, daily and monthly transfer limits.
7. Reconcile stablecoin balances, fiat balances and network fees daily.
8. Retain invoices, quotes, approvals, transaction hashes and bank records.
9. Test recovery and alternate conversion routes before an emergency.

The control design should cover predictable failures: an approver leaves, a signing device is lost, a provider restricts the account, a bank rejects a transfer or a blockchain becomes unavailable. Assign an owner, escalation path and manual fallback for each scenario.

Resolve accounting, tax and reporting treatment

Agree the accounting policy with the company’s auditor before balances become material. Depending on the applicable framework and facts, a stablecoin may not qualify as cash or a cash equivalent. Document classification, valuation source, period-end cutoff, transaction-fee treatment, impairment or fair-value approach and foreign-exchange presentation.

Tax consequences vary by jurisdiction and transaction. Fiat conversion, stablecoin swaps, invoice payments and yield can create different reporting outcomes. Retain acquisition cost, disposal proceeds, timestamps, fees, wallet addresses and the business purpose of every movement so finance can reconstruct the ledger without relying solely on a provider dashboard.

Make approval conditional and repeatable

Conclude the review with approved use cases, balance limits, permitted networks, authorized providers and depeg or disruption triggers. Record unresolved risks and the executive who accepted them. Repeat due diligence at least annually and after material events such as reserve changes, a banking-partner change, redemption disruption, network incident, provider restriction or significant change in transaction volume.