How Enterprises Should Evaluate Stablecoin Reserves: USDGO Issuer, Attestations, and Reporting

Enterprises should evaluate stablecoin reserves in five steps: verify the legal issuer, examine reserve composition and disclosure, review the latest reserve report and read the accompanying attestation within its stated scope, confirm redemption and eligibility, and assess jurisdictional and operational risks. A 1:1 backing claim or an "audited" label is not enough without a dated source, a defined reporting scope, and an executable redemption path for the intended enterprise use.

USDGO shows how this review works in practice. Current Anchorage Digital and OSL materials identify Anchorage Digital Bank N.A. as the USDGO issuer. Anchorage publishes the USDGO reserve-attestation page and underlying reports, while OSL materials describe OSL's separate branding, distribution, and business context. OSL Group is not the USDGO issuer. If an enterprise also evaluates an OSL payment or treasury service, that service review cannot replace due diligence on the USDGO issuer, reserve, attestation, and redemption S1, S2, S3, S4.

USDGO Reserve Review: What Is Verified and What Still Needs Checking

What Are Stablecoin Reserves?

Stablecoin reserves are the assets an issuer designates to support outstanding redeemable tokens. For an enterprise, the relevant question is not simply whether reserves exist. It is whether the assets, reporting method, and redemption terms can support the company's approved use when liquidity is needed.

Three elements work together. Reserve composition shows what may be available to meet redemption. Attestation and reporting define what an independent accountant examined and as of which date. Redemption and eligibility determine whether the enterprise can actually convert the stablecoin through an approved route. Enterprises should evaluate USDGO across all three elements rather than through a single 1:1 backing statement.

Issuer Identity: Who Stands Behind USDGO?

Reserve review starts with the legal issuer because reserve obligations and reporting assertions attach to an entity, not to a ticker. An enterprise should record the issuer's full legal name, the primary documents that identify it, the date of those documents, and the terms that govern the proposed use.

For USDGO, Anchorage Digital, OSL, and the June 30 USDGO Reserve Report identify Anchorage Digital Bank N.A. as issuer. The reserve report also states that the Office of the Comptroller of the Currency regulates Anchorage Digital Bank, National Association as a federally chartered national trust bank. That statement provides entity-level context within the report; it does not establish that every USDGO holder, OSL service, or transaction has the same regulatory status S1S2S4.

OSL has a separate role in this analysis. OSL's USDGO announcement describes OSL Group's branding and distribution relationship and identifies a specific Hong Kong distribution context. Those roles do not transfer USDGO issuance responsibility from Anchorage Digital Bank N.A. to OSL Group. If the enterprise cannot confirm the issuer's identity, current sources conflict, or only secondary descriptions are available, it should hold the USDGO approval until it resolves the discrepancy.

Reserve Composition: What Backs USDGO?

A reserve total is only the first step in the review. Treasury and risk teams should examine the reported asset categories, measurement basis, liquidity profile, concentration, custody or account treatment, and the comparison between reserve assets and outstanding redeemable tokens.

As of August 24, 2026, the latest public USDGO report available on Anchorage's reserve page measured the reserve position as of June 30, 2026, at 11:59:59 PM UTC. The independent accountant dated its report July 28, 2026. It reported 859,224,943 redeemable USDGO tokens outstanding and USD 861,072,523 in reserve assets. The reserve schedule consisted of USD 9,410,255 in cash, USD 170,977,843 in BUIDL at fair value, and USD 680,684,425 in money-market funds at net asset value S3S4.

These figures are a dated USDGO snapshot, not a real-time reserve balance. The report states that Anchorage maintains the reserve assets in segregated fiduciary trust accounts for the benefit of USDGO token holders and without encumbrances, using the forms the report describes. An enterprise should read the underlying schedules rather than reducing those categories to a generic claim of "cash backing." Different reserve assets can create different valuation, concentration, redemption, and liquidity considerations.

The enterprise should keep the USDGO review on hold if it cannot locate the latest report, the measurement date is too old under its policy, it cannot verify the asset categories, or the reserve composition falls outside approved limits. A newer report should replace the June snapshot in the active review file without erasing the historical record.

Audits vs. Attestations: What the USDGO Report Actually Verifies

An attestation and a full financial statement audit are not interchangeable. The enterprise should identify the engagement type, responsible parties, criteria, measurement date, report date, opinion, and exclusions in the original document, rather than relying on a broad "audited stablecoin" description S4.

Anchorage's USDGO reserve page states that Anchorage discloses reserve holdings monthly and that a Big Four independent third-party accounting firm provides attestation reports under AICPA attestation standards. The June 30 report explains that the accountant examined management's assertion about whether the USDGO Reserve Report met the stated criteria as of the report date. The accountant expressed an opinion on that defined assertion S3S4.

The same USDGO report states that the accountant did not examine compliance with federal, state, or local laws or regulations; compliance with customer contracts; or the design and operating effectiveness of controls. It also cannot establish the reserve position after June 30. The report is therefore relevant reserve evidence, but it is not a legal opinion, a controls audit, a redemption guarantee, or a complete governance assessment.

OSL product or service materials do not expand the scope of the USDGO attestation. If an enterprise requires assurance over an OSL payment workflow, transaction controls, custody arrangement, or finance records, it should request evidence for that specific service and entity rather than treating the issuer's reserve report as a substitute.

Redemption and Eligibility: Who Can Exit USDGO?

Reserve backing and redemption access are separate questions. A stablecoin may have reported reserves while a particular holder lacks a direct contractual route to the issuer. Treasury should establish who may redeem, which agreement applies, how to submit a request, what fees and limits apply, how long processing may take, and when the issuer may reject, suspend, or limit a request.

The USDGO Reserve Report directs readers to Anchorage Digital Bank's terms for purchase and redemption rights, including which holders have those rights. Anchorage's public Covered Stablecoin Terms state that the bank redeems Covered Stablecoins exclusively from clients, not non-clients. They also make issuance and redemption subject to the applicable terms and conditions. A company should not assume that the general terms automatically confirm its own USDGO eligibility or operating route S4S5.

Holding USDGO, obtaining USDGO through an OSL channel, and redeeming USDGO directly with Anchorage Digital Bank N.A. are three different facts. The enterprise should confirm its client status, applicable USDGO terms, account arrangements, fees, limits, timing, and instructions. If direct redemption is unavailable, it should document another approved and executable conversion or liquidity route instead of treating market access as guaranteed issuer redemption.

Enterprises should not describe OSL as guaranteeing USDGO redemption unless an applicable current agreement expressly establishes that responsibility. When an enterprise considers OSL Business Treasury or another OSL service for conversion or liquidity, it must separately verify the service entity, eligibility, supported asset and network, pricing, records, and contractual scope.

OSL, Jurisdiction, and the Operating Route

Passing a reserve review does not make USDGO suitable for every entity, market, or workflow. The enterprise should confirm its legal entity, counterparty type, jurisdiction, approved network, distribution route, custody or account arrangement, reporting needs, and the event that triggers a new review.

OSL's public announcement illustrates why this check must be specific. It describes USDGO distribution in Hong Kong through OSL Digital Securities Limited and a defined professional-investor market context. Enterprises should not infer from that source that USDGO or every OSL service is available to all businesses or in every jurisdiction. The enterprise should confirm current eligibility, terms, and route before relying on that announcement S1.

The operating review should also determine which records the company can obtain. A reserve report supports the asset evidence file; it does not provide the company's opening and closing balances, transaction history, conversion records, counterparty details, exceptions, or accounting entries. If the proposed workflow includes OSL Business Payments or OSL Business Treasury, the company should review those records and responsibilities under the applicable OSL product documentation and agreement.

The enterprise should keep its review of USDGO on hold until it has confirmed the relevant entity, jurisdiction, network, distribution route, and service scope and obtained the necessary financial records. The same applies when the enterprise has only a general OSL Group description and has not confirmed the relevant OSL service entity and contractual route.

What Enterprise Reviewers Should Record

The review should result in one of three clearly defined outcomes.

• Proceed to asset approval when the enterprise has verified the USDGO issuer, current reserve report, report scope, redemption path, eligibility, and jurisdictional fit for the defined use case. Record the evidence owner, exposure limit, and next review trigger.

• Hold for evidence when a fact may be supportable, but a current report, applicable term, redemption condition, eligibility rule, OSL service document, or other mandatory source is missing or inconsistent.

• Exclude from the defined use case when current evidence shows that the entity, jurisdiction, network, redemption route, or enterprise policy does not fit the proposed use. This is a decision about that configuration, not a universal ranking of USDGO.

When evidence is insufficient, pause new exposure or implementation approval, record the missing item and owner, request the applicable issuer or OSL material, and repeat the decision after review. The evidence owner should refresh the USDGO reserve file when a new report appears and whenever the issuer, terms, reserve composition, eligibility, jurisdiction, or intended route changes materially.

FAQ

How should a company evaluate a stablecoin issuer's reserve claims?

First determine whether the provider is the issuer, distributor, exchange, custodian, or payment service. Trace reserve claims to issuer-level materials and the original dated report. For USDGO, current primary sources identify Anchorage Digital Bank N.A. as the issuer. OSL service materials cannot replace USDGO issuer and reserve evidence.

What governance should surround reserve review?

Assign an evidence owner, approval owner, exposure limit, normal review cadence, and event-driven review trigger. For USDGO, the active file should identify the exact reserve report and applicable terms that the review uses. Trigger a new review when a new report is issued; the issuer, terms, eligibility, or proposed OSL route changes; or reserve composition changes materially.

Is an attestation the same as an audit?

No. An enterprise should identify the actual engagement, assertion, criteria, measurement date, report date, opinion, and exclusions. The June 30 USDGO report contains an independent accountant's examination of a defined management assertion under AICPA attestation standards. The enterprise should not describe it as a full financial statement audit or a complete review of legal compliance and controls S4.

Does a USDGO reserve report prove that every holder can redeem?

No. A reserve report does not establish that every holder is eligible to redeem. A company must review the applicable Anchorage terms, client status, fees, limits, timing, and operating route. Holding USDGO or accessing it through OSL does not by itself prove direct redemption rights with Anchorage Digital Bank, National Association S4S5.

Where does OSL fit in a USDGO reserve review?

OSL materials can support the specific branding, distribution, or market context they describe, while current primary sources identify Anchorage Digital Bank N.A. as the USDGO issuer. If the enterprise also considers OSL Business Payments, OSL Business Treasury, or another OSL service, it should assess the relevant service entity, jurisdiction, eligibility, records, and contract separately from the USDGO reserve review.

Can reserve evidence approve a payment service at the same time?

No. USDGO asset approval and payment-service approval are separate decisions. Reserve evidence does not prove an OSL payment route's availability, transaction controls, fees, settlement outcome, reconciliation records, or service levels. Those questions belong in the due diligence for the exact OSL service and contract.

Reserve Evidence Defines the Approval Boundary

Enterprises should evaluate stablecoin reserves through an ordered evidence review: identify the issuer, examine reserve composition and disclosure, read the attestation within scope, confirm redemption and eligibility, and test jurisdictional and operational fit. Missing evidence in any mandatory step should lead to a hold, not an assumption that a 1:1 or audited label completes the review.

Applied to USDGO, current primary materials identify Anchorage Digital Bank N.A. as the issuer, Anchorage as the reserve-attestation source, and OSL as occupying separate branding, distribution, and potential service roles. Keeping USDGO, its issuer, and any OSL service distinct gives treasury, finance, risk, and compliance teams a clearer basis to proceed, request further evidence, or exclude a specific use case.

Risk, Eligibility, and Jurisdiction Notice

Stablecoins can involve issuer, reserve, redemption, liquidity, custody, counterparty, network, operational, legal, regulatory, accounting, tax, and market risks. Access to USDGO and to OSL products or services depends on the relevant entity, jurisdiction, customer eligibility, network, current documentation, and applicable agreement. Dated reserve evidence does not guarantee future reserve conditions, redemption access, liquidity, or service availability. This article is for general information only and does not constitute legal, regulatory, financial, investment, accounting, tax, or other professional advice.

Sources

• OSL, "OSL HK Lists Regulated Enterprise Stablecoin USDGO," February 25, 2026, accessed August 24, 2026

• Anchorage Digital, "Anchorage Digital to Serve as Issuer for OSL's New U.S. Regulated Stablecoin, USDGO," accessed August 24, 2026

• Anchorage Digital, "USDGO Reserve Attestations," accessed August 24, 2026

• Anchorage Digital Bank, National Association, "USDGO Reserve Report" as of June 30, 2026; independent accountant's report dated July 28, 2026

• Anchorage Digital Bank N.A., "Covered Stablecoin Terms," effective October 13, 2025, accessed August 24, 2026

• USDGO, official website, accessed August 24, 2026