Stablecoin Due Diligence Checklist for Corporate Treasury Teams

Stablecoin due diligence should cover more than whether a token usually trades at one dollar. A corporate treasury team needs to understand who issues it, what supports its value, how it can be redeemed, where company funds are held and what happens when a bank, blockchain or service provider is unavailable.

The review should examine both the stablecoin and every provider used to hold, convert or transfer it. Start by collecting primary documents: issuer terms, reserve reports, redemption rules, provider agreements, custody documentation, fee schedules, supported-network lists and transaction records from a small operational test.

1. Identify the issuer and legal claim

Confirm the legal entity that issues the stablecoin and the entity with which your company contracts. Similar token names can appear on several networks, and bridged or wrapped versions may introduce additional counterparties.

• Issuer: Record its legal name, incorporation jurisdiction and relevant regulated status.
• Token contract: Verify the official contract address for every supported chain using issuer documentation.
• Holder rights: Read whether token holders have a direct redemption claim, contractual claim or no direct relationship with the issuer.
• Eligibility: Check whether your company’s jurisdiction, industry and entity type can open a direct issuer account.
• Insolvency treatment: Ask how reserve assets and customer claims would be treated if the issuer failed.

Do not assume that buying USDC or USDT through an exchange gives the company the same rights as being an approved direct redemption customer. Treasury should document the actual route available to the business.

2. Review reserve quality

Reserve quality determines how readily an issuer may be able to meet redemptions. Obtain the latest reserve report and several earlier reports rather than relying on a homepage summary.

An attestation is a point-in-time examination of specified information; it is not necessarily a full financial statement audit. Record the reporting scope, date and accounting basis when comparing issuers.

3. Test redemption and market liquidity

Liquidity has two distinct forms. Primary liquidity is redemption with the issuer. Secondary liquidity is selling or converting through an exchange, market maker or treasury platform. A token may trade actively while direct redemption remains unavailable to your company.

• Document minimum redemption sizes, supported currencies, cut-off times and expected settlement windows.
• Identify which bank account receives fiat and whether it must be in the same legal name as the issuer account.
• Record issuer, network, conversion, banking and intermediary bank fees separately.
• Compare quoted conversion prices with the amount ultimately credited, including spread and gas costs.
• Run a small on-ramp and off-ramp test before moving a material balance.
• Maintain at least one tested alternative conversion route where practical.

Published corridor pricing is useful because it lets treasury compare the full cost of converting stablecoins to EUR, USD or GBP rather than looking only at a headline fee. The review should cover the actual rails required, such as SEPA or SEPA Instant, ACH or Fedwire, SWIFT, Faster Payments, CHAPS or BACS.

4. Examine depeg history and concentration

Review occasions when the stablecoin traded away from its target value. For each event, record the lowest observed price, duration, trading venue, cause and time taken to recover. Distinguish a broad issuer event from a temporary price discrepancy on one exchange or blockchain.

Set a treasury response in advance. This could include pausing new receipts, stopping conversions, reducing exposure or requiring CFO approval above a defined deviation. Avoid relying on an automatic sale alone: during stressed markets, spreads can widen and available liquidity can fall.

Also measure concentration by stablecoin, issuer, banking route, provider and blockchain. Holding two tokens does not provide meaningful diversification if both depend on the same conversion provider or bank.

5. Assess blockchain and token-contract risk

The same stablecoin can have different operational characteristics across Ethereum, Base, Arbitrum, Polygon, Tron, BNB Chain, Optimism and Solana. Confirm that the sender, recipient and treasury provider all support the exact token and network combination.

• Native versus bridged: Determine whether the token is issued natively or represented through a bridge. Bridges add smart-contract and operator risk.
• Network fees: Identify which asset pays transaction fees and how the business will maintain enough of it.
• Finality: Document when your provider treats a transfer as complete and how chain outages or reorganisations are handled.
• Contract powers: Review whether the issuer can freeze addresses, block transfers or upgrade the token contract.
• Address controls: Test address validation and use a small first payment for new destinations.

Wallet screening can identify sanctions exposure and other risk indicators before a payment. Screening does not eliminate chain risk, but it supports documented transfer decisions. Stablerail’s wallet checker can be used as part of that review.

6. Review custody and counterparty risk

Map who can technically and legally move the assets. In a custodial arrangement, the provider generally controls the keys and records a claim for the customer. In self-custody, the company controls transaction approval and key material, although technology vendors may still be operational dependencies.

For example, Stablerail uses self-custodial MPC vaults with quorum signing. Multiparty computation, or MPC, divides signing authority so that no single complete private key is used. Treasury should still document signers, approval thresholds, recovery procedures and what happens if a signer or vendor becomes unavailable.

For every provider, request:

• Contracting entity, service jurisdictions and subcontractors performing material functions.
• Customer-asset ownership and segregation terms.
• Named banking partners where disclosure is available, plus the flow of funds for each fiat rail.
• Withdrawal limits, cut-off times, manual-review triggers and service dependencies.
• Incident, insolvency, account suspension and termination procedures.
• Insurance scope, exclusions and limits, without treating insurance as a substitute for sound custody.

7. Verify fees and operational controls

Build a sample transaction from end to end: incoming fiat, stablecoin purchase, blockchain transfer, conversion back to fiat and bank payout. Include fixed charges, percentage fees, spreads, network fees, correspondent bank deductions and card or payout costs where applicable.

Then test the operating controls used in normal treasury work:

• Role-based access and separation between payment creation and approval.
• Approval limits and quorum rules for high-value transfers.
• Wallet and bank-account allowlists.
• Sanctions and wallet screening.
• Batch-payment review for vendors, contractors or payroll.
• Complete audit logs and downloadable evidence packs.
• Procedures for rejected, duplicated, delayed or misdirected payments.

If stablecoins will be used for vendor or contractor payments, test the complete workflow rather than only a wallet withdrawal. This includes beneficiary import, approval, network selection, transaction references and reconciliation. See the practical options for stablecoin payouts.

8. Confirm accounting, tax and jurisdictional treatment

Agree the accounting policy before balances become material. Determine how the stablecoin will be classified, valued and presented, and how transaction fees, realised gains or losses and yield will be recorded. Retain wallet addresses, transaction hashes, exchange rates, timestamps, invoices and approval evidence.

Tax treatment varies by jurisdiction. A transfer, conversion, payment or receipt may create reporting or taxable events even when the token targets the company’s functional currency. Obtain local advice on corporate tax, VAT or sales tax, withholding, payroll and information-reporting obligations.

Finally, confirm that the issuer, treasury provider, banking route and intended recipients support every relevant jurisdiction and industry. Onboarding usually requires KYB documents such as incorporation records, ownership information, director identification, business activity, source of funds and expected transaction volumes.

Final approval checklist

• Issuer, token contracts and legal holder rights verified.
• Current and historical reserve evidence reviewed.
• Direct and secondary redemption routes tested.
• Depeg events and concentration limits documented.
• Each blockchain and token version approved.
• Custody, recovery and counterparty risk assessed.
• Banking partners and fiat flow of funds mapped.
• End-to-end fees and settlement timings tested.
• Approvals, allowlists, screening and audit evidence verified.
• Accounting, tax and jurisdictional treatment signed off.

Stablecoin due diligence is not a one-time onboarding task. Corporate treasury should refresh the review when reserve composition changes, a banking partner is replaced, a new chain is added, redemption terms change or the company enters a new jurisdiction. Assign an owner and a review date so that operating assumptions do not quietly become outdated.