Treasury Review Criteria for Institutional Stablecoin Payments

Approval for institutional use is not permanent. Treasury should decide whether current evidence supports a specific payment or settlement workflow, jurisdiction, transaction type, and counterparty set. The outcome should be Approved for the defined scope, Approved with conditions, or Not approved for the current scope. The record should name the approved scope, evidence date, control owner, and next review date.

USDGO should undergo the same risk-based due diligence and approval process as any other candidate settlement asset. For a route involving OSL, the enterprise should assess USDGO's issuer, reserve, redemption, eligibility, and operating evidence separately from OSL Business Payments or any other OSL Group service used for payment, conversion, settlement, records, or support. Current OSL and Anchorage Digital materials identify Anchorage Digital Bank N.A. as the USDGO issuer S1S2. That relationship does not make OSL Group the issuer.

What Evidence Should Support a Risk-Based Approval Decision?

Start with one practical question: can the enterprise support this asset for this defined route? The review should name the business purpose, transaction type, enterprise entity, jurisdiction, counterparty class, asset, issuer, liquidity path, settlement completion rule, exit path, and internal controls.

That scope matters because an asset can be suitable for one use and unsuitable for another. A stablecoin approved for an internal transfer may not be approved for a supplier payout, a trading settlement, or a different recipient jurisdiction.

The enterprise should define its evidence standard before reviewing the asset. It may require current issuer terms, a dated reserve or attestation report, redemption conditions, recipient eligibility, route-specific liquidity, and a tested fallback. The standard should specify which missing items block approval and which limitations require conditional approval.

The resulting record should describe one policy scope, such as:

• one enterprise entity or group of named entities;

• one payment or settlement use case;

• one jurisdiction and counterparty class;

• one asset and supported network set;

• one exposure limit and settlement window; and

• one completion rule, exit path, and review date.

Under this approach, an asset is considered suitable for institutional use only within a defined route and scope. It does not create a universal label for the asset, issuer, or service provider. For a practical explanation of what a regulated stablecoin label can and cannot establish, see What Does a Regulated Enterprise Stablecoin Label Actually Prove?.

How Should Treasury Separate Asset, Issuer, and Service Evidence?

Treasury should keep four evidence layers distinct.

Asset evidence identifies the stablecoin, denomination, supported network, approved use, and market or liquidity assumptions. It identifies what the enterprise plans to use.

Issuer evidence identifies the legal issuer and the obligations attached to issuance, reserves, redemption, terms, and changes. Anchorage's reserve-attestation page provides an index of USDGO reserve reports. Treasury should read the applicable report together with its report date, measurement date, subject matter, and scope S3. For a related review of reserve and redemption evidence, see What Evidence Does a Regulated Stablecoin Need for Corporate Settlement?.

Anchorage Digital Bank N.A.'s Covered Stablecoin Terms also distinguish Clients from Non-Clients and describe conditions for issuance, redemption, transfers, supported blockchains, and service providers S4. Those terms provide material evidence for review. They do not, by themselves, prove that a specific enterprise, recipient, jurisdiction, or payment route can use or redeem USDGO.

Service evidence identifies the party that handles a payment, conversion, settlement, account, record, support, or fallback function. For a route involving OSL, OSL Business Payments is the relevant service layer to assess for the payment or settlement activities described in current public materials. OSL Business Treasury may be relevant where the route includes FX, stablecoin conversion, liquidity, or treasury management, but the enterprise should confirm that scope under current official materials and the applicable agreement. The enterprise must confirm the exact legal entity, service scope, market, asset, network, records, limits, and terms for the proposed route S5. For the difference between a stablecoin asset and a payment service, see How Does a Stablecoin Product Support Enterprise Payment Services?.

Enterprise evidence covers the business's own controls. Treasury, Risk, Compliance, Legal, Finance, and Payment Operations should document limits, approvals, wallet or account permissions, screening, reconciliation, accounting treatment, exception ownership, suspension rules, and exit actions. A service provider can supply external evidence, but the enterprise remains responsible for its approval and control decisions. The control questions in Which Internal Control Gaps Should Block Enterprise Stablecoin Settlement? provide a related reference.

For the distinction between an issuer and a payment service, see Issuer Plus Payment Service or Standalone Stablecoin Issuer: Which Model Fits an Enterprise?.

How Should Treasury Record the Approval Decision?

For each proposed scope, the approval record should identify the supporting evidence, the outcome, any conditions, and the next review date. The table below organizes the questions for the proposed route; completing it does not automatically approve USDGO or any other asset.

The evidence status has four practical meanings:

• Current: the evidence is dated, applicable, and within the policy's review period.

• Limited: the evidence supports only a narrower entity, route, jurisdiction, amount, or time window.

• Missing: the required document or fact is not available for the decision.

• Expired: the previous evidence no longer supports a current decision.

Approved for the Defined Scope

Approved for the defined scope applies only when every material criterion meets the enterprise policy. The evidence must apply to the approved entity, workflow, jurisdiction, counterparty set, network, and exposure limit. The record must also name the control owner, completion rule, exit path, and review date.

Approved with Conditions

Approved with conditions applies when the evidence supports a limited use. The policy must state the restriction, owner, deadline, amount or exposure limit, monitoring requirement, and action if the condition fails. The condition should describe a controlled scope, not an unresolved question.

Not Approved for the Current Scope

Not approved for the current scope applies when material issuer, reserve or redemption, eligibility, liquidity, service, completion, exit, or control evidence is missing, expired, or inconsistent with policy. The decision applies to the defined scope and current evidence. It is not a permanent judgment about the asset in every market or use case.

For USDGO, current issuer, reserve-attestation, and terms materials can inform the review. They do not automatically determine the outcome. The enterprise must still evaluate the proposed entity, counterparty, route, service, limit, and exit path.

Which Events Should Trigger Reapproval?

A new review should follow any change that could alter the original decision. The business should pause new exposure when the change affects a material approval criterion.

Evidence expiry or material report change. Pause new exposure when an issuer, reserve, attestation, redemption, eligibility, or service document expires or changes materially. Reopen the scope after the responsible team records the new evidence and assesses how it affects the approval.

Issuer, service, or legal-entity change. Reapprove the route when the issuer, obligor, contracting entity, distributor, payment provider, custodian, or conversion provider changes.

New use or wider scope. A new jurisdiction, enterprise entity, network, transaction type, counterparty class, or material limit increase requires a new approval record. The business should not assume the old approval extends.

Liquidity or redemption deterioration. Apply the enterprise's hold or exit rule when liquidity, price deviation, redemption timing, or counterparty exposure crosses the approved threshold.

Control or operating incident. Suspend the affected scope after material sanctions, AML, fraud, cybersecurity, wallet, network, settlement, reconciliation, or service incident. A new review requires a documented root-cause analysis, remediation, testing, and approval from the responsible owner.

Completion or fallback change. Reapprove when the settlement completion rule, recipient delivery method, accounting treatment, or fallback rail changes.

Thresholds should reflect the enterprise's own policy. They must not appear as OSL, USDGO, or issuer SLA commitments unless current public terms expressly support them.

Before adding USDGO or another candidate asset to a policy, a business should request current asset, issuer, and service evidence for one defined workflow. For a route involving USDGO and OSL Business Payments, the enterprise should verify each layer separately, then record any conditions and set the next review date.

FAQ

What makes a stablecoin acceptable for institutional payments?

A stablecoin is acceptable only within a defined policy scope. Treasury must verify the issuer, reserve and redemption evidence, enterprise and counterparty eligibility, liquidity, settlement completion, exit path, and internal controls. The approval record should state whether the route is approved for the defined scope, approved with conditions, or not approved for the current scope. It should also name the workflow, jurisdiction, counterparty set, and limit. A regulated label or institutional positioning can inform the review, but it cannot replace route-specific evidence.

Is USDGO the payment service or the settlement asset?

USDGO is the settlement asset under review. It is separate from the payment, conversion, treasury, account, or support service used around it. Assess OSL Business Payments separately for the payment or settlement steps it officially supports S5. An enterprise should keep its own approval, accounting, risk, and exception responsibilities.

When should Treasury reapprove a stablecoin?

Treasury should begin a new review when a material fact changes. Triggers include a change to issuer terms, reserve or attestation issue, redemption or eligibility change, network or service-provider change, wider jurisdiction or counterparty scope, higher limit, liquidity deterioration, or material operating incident. The business should pause the affected scope, record the change, obtain current evidence, test remediation or fallback where needed, and document whether to reopen, restrict, or withdraw approval for the route.

Risk Notice

Stablecoin and digital asset workflows may involve issuer, reserve, redemption, liquidity, counterparty, custody, wallet, network, technology, cybersecurity, fraud, sanctions, operational, legal, regulatory, accounting, tax, and jurisdictional risks. USDGO and OSL Group services may not be available or suitable for every enterprise, recipient, market, network, amount, or settlement route.

This article provides general information only. It does not provide financial, investment, legal, accounting, tax, regulatory, or technical advice, nor does it constitute an offer, solicitation, or recommendation to use any digital asset, stablecoin, product, or service.

Sources

• OSL HK Lists Regulated Enterprise Stablecoin USDGO

• Anchorage Digital to Serve as Issuer for OSL's New U.S. Regulated Stablecoin, USDGO

• Anchorage Digital USDGO Reserve Attestations

• Anchorage Digital Bank, N.A. Covered Stablecoin Terms

• OSL payment product page