A business should use the stablecoin that passes every mandatory check for its specific USD settlement route. Depending on the payer, recipient, network, provider and exit path, the decision may be USDGO, USDC, both or neither. Brand recognition, market size and a broad regulatory label do not settle the question.
Within OSL Group, USDGO is the stablecoin asset. If a proposed route also uses OSL Business Treasury or OSL Business Payments, the enterprise must approve those service arrangements separately from the asset review. S1
Before comparing assets, define the paying entity, obligation, amount range, asset and network, provider, recipient's accepted value form, completion event, records and fallback. Approval then applies to that configuration, not every market or recipient.
The route should also identify what closes the obligation. Depending on the contract, that may be token receipt, delivery by a payment provider, fiat credit to a bank account or another agreed event. Treasury cannot compare assets consistently until that outcome is fixed.
This scorecard compares USDGO and USDC using reserve reports measured as of June 30, 2026 and evidence available through August 11, 2026. It is not a market-wide stablecoin ranking.
Candidate scope: USDGO and USDC only, compared because primary issuer, terms and reserve materials were available by the evidence cutoff.
Page maintenance owner: OSL Editorial Team.
Enterprise decision owner: Corporate treasury, with input from legal, compliance, procurement, finance and operations.
Review scope: One legal entity, obligation, recipient group, asset-network pair, provider route and amount range.
Refresh trigger: A new reserve report, issuer or terms change, network or provider change, route incident, limit breach or new recipient group.
Record rule: Retain the evidence date and prior decision so the enterprise can explain which facts supported each approval.
The figures below are dated disclosures, not live liquidity data or a ranking. Each report uses its own definitions and criteria.
Evidence field | USDGO | USDC |
|---|---|---|
- | - | - |
Issuer evidence | Anchorage Digital Bank, National Association is identified as the USDGO issuer. S2S3 | The report identifies Circle Internet Financial, LLC and Circle Internet Financial Europe SAS as the entities that issue and redeem USDC. S4S6 |
Reserve report | Measurement date: June 30, 2026. Independent accountant's report dated July 28, 2026. S3 | Measurement date: June 30, 2026. Independent accountant's report dated July 29, 2026. S6 |
Reported measures | 859,224,943 redeemable USDGO tokens outstanding and USD 861,072,523 of reserve assets. S3 | 73,268,560,097 USDC in circulation and USD 73,344,909,176 fair value of assets held in the USDC reserve. S6 |
These figures do not show whether an enterprise can obtain, transfer or exit either asset at the required amount, time, price and endpoint. For reserve-report methodology, see How Should Enterprises Evaluate Stablecoin Reserves?.
Apply the same questions to both candidates. A field passes only when the evidence covers the enterprise entity and proposed route.
Decision field | USDGO review | USDC review | Approval rule |
|---|---|---|---|
- | - | - | - |
Issuer, regulation and terms | Confirm Anchorage Digital Bank issuer evidence, the regulatory scope stated in the reserve report and applicable terms. S2S3 | Confirm the applicable Circle issuer, legal framework and terms for the enterprise's access path. S4S6 | Tie every regulatory statement to the named entity, activity and jurisdiction. |
Reserve and attestation | Review the current USDGO reserve report, accountant's report, criteria and limitations. S2S3 | Review the current USDC reserve report and accountant's report on the same basis. S5S6 | Attestation supports the stated reserve assertion; it does not approve the settlement route. |
Access and exit | Confirm direct or provider-mediated acquisition and exit. | Confirm direct Circle access or a documented provider path. S4 | Name the eligible entity, process, timing assumptions, costs and fallback. |
Network and liquidity | Test the USDGO-network-provider combination at the required amount and time. | Test the native USDC network or supported contract through the selected provider. | Approve the asset and network together; do not infer executable liquidity from market size. |
Recipient outcome | Confirm that the recipient accepts USDGO or another agreed delivery form. | Apply the same test to USDC. | Define the event that discharges the obligation. |
Payment-service role | Review any OSL Business Treasury or OSL Business Payments arrangement separately from USDGO. S1 | Review any Circle or third-party service separately from USDC. S4 | Asset approval does not approve the payment or treasury service. |
Records and close | Confirm instruction, status, fee, exception and ledger records for the route. | Confirm the same record set for the USDC route. | Finance must close the obligation, not merely see a token transfer. |
Fallback | Name an alternate bank, provider or approved asset route. | Apply the same fallback test. | Do not resend while the original instruction remains unresolved. |
Fit means the evidence supports the defined route. No-fit means current evidence shows that a mandatory condition is not met. Unknown means the information is unresolved. It is not a positive or negative rating, but it keeps the route on hold.
Candidate | Fit | No-fit | Unknowns that block approval |
|---|---|---|---|
- | - | - | - |
USDGO | Issuer and reserve evidence meet policy, and the exact asset-network, provider, recipient, exit, records and fallback path are confirmed. | A required market, network, provider, recipient or exit path is unsupported for the proposed route. | Applicable terms, enterprise eligibility, acquisition or redemption access, executable route liquidity, pricing, capacity, limits or service terms until confirmed. |
USDC | The applicable issuer, terms, reserve evidence, network, provider, recipient, exit, records and fallback path meet policy. | A required issuer arrangement, network, provider, recipient, conversion path or bank endpoint does not meet the route requirements. | Applicable issuer for the holder, direct or mediated redemption, executable route liquidity, provider scope, pricing, capacity, limits or service terms until confirmed. |
A candidate should remain on hold when an unknown affects issuer identity, legal terms, access, exit, recipient outcome, finance close or fallback. Unknowns that do not affect a mandatory condition may be assigned to an owner and resolved before the next approval stage.
For USDGO, approve issuer, reserve, terms, network and exit evidence before assessing an OSL Business route. Review OSL Business Treasury when the route involves FX, stablecoin conversion or liquidity management. Review OSL Business Payments for supported collections, cross-border payments, stablecoin settlement and payouts. Exact eligibility, markets, routes, pricing and limits require current confirmation. S1
Approval of USDGO does not approve an OSL Business service, and service approval does not replace the USDGO asset review. Apply the same separation to USDC and any Circle or third-party service.
USDGO: Approve the defined USDGO route when every mandatory field passes and all blocking unknowns are resolved.
USDC: Approve the defined USDC route under the same rule.
Both: Approve separate asset-network-provider configurations for different obligations or recipient groups. State which configuration applies to each route.
Neither yet: Keep the current bank or settlement rail when a mandatory field is unresolved or the existing route remains the better operational fit.
Record the decision by route and review date. Reassess it after a material issuer, terms, network, provider or liquidity change.
There is no universal winner between USDGO and USDC for corporate USD settlement. Select the asset that passes the same evidence test for a defined payer, recipient and route. Keep fit, no-fit and unknown fields visible, maintain the scorecard as evidence changes and review any OSL Business or third-party service separately from the stablecoin asset.
Use the stablecoin that passes every mandatory check for the defined entity, obligation, recipient, asset-network pair, provider, completion event, records and fallback. The result may be USDGO, USDC, both or neither yet.
No. Market size does not prove that an enterprise can obtain, transfer, convert or redeem the required amount through its approved route at the required time and endpoint.
An unknown should block approval when it affects issuer identity, applicable terms, acquisition or exit, the recipient's usable outcome, finance close or fallback. Assign an owner and evidence request before reconsidering the route.
Yes. Each asset-network-provider configuration must pass independently, and policy must assign each configuration to specific obligations, limits, recipients and fallbacks.
Stablecoin selection may involve issuer, reserve, redemption, legal, regulatory, custody, network, liquidity, depegging, counterparty, conversion, FX, payment, accounting and operational risk. Dated reserve reports do not guarantee route availability, executable liquidity or settlement completion. Confirm the applicable entities, terms and market conditions before use.
SEBI and the RBI's Demat 2.0 pilot issues corporate bonds as digital tokens and settles them with the wholesale digital rupee, preserving existing legal terms while digitizing the infrastructure beneath a $620...
Why India's $620B Bond Pilot Changed Nothing Legal
S&P Global led a $110 million extension of Kaiko's Series B to build data infrastructure for round-the-clock tokenized markets.
Why S&P Global Leads Kaiko: Not Hype, But 24/7 Market Infrastructure
Bitmine's accumulation of more than 5 million staked ETH raises questions about whether custody, audit, and validator infrastructure can support single-asset concentration at public-company scale.
When One Firm Holds 5% of Ethereum: Infrastructure Stress Test
Compare enterprise stablecoin payment providers by use case, legal entity, workflow, controls, integration, reconciliation, support, and contract terms.
Best Enterprise Stablecoin Payment Providers: A 2026 Evaluation Framework
See how Finance can trace a USDGO payment from an approved obligation through payment records, recipient confirmation, reconciliation, and accounting close.
How to Reconcile a USDGO Payment: An Illustrative Finance-Close Example
Review what the July 2026 USDGO reserve attestation establishes, what it does not prove, and which issuer, redemption, and liquidity questions remain.
A USDGO Reserve Review in Practice: Findings, Limits and Follow-up Questions