Corporate treasury teams should not choose a stablecoin by market size alone. The more useful question is whether an asset’s issuer evidence, reserve disclosures, redemption terms, liquidity, network support, operating corridor and service connections match a specific treasury route. USDGO may fit a route that requires a clearly identified U.S. issuer and reviewable reserve materials; USDT or USDC may be preferable where a company needs a particular venue, corridor or conversion path. The right answer is route-specific, not a universal ranking.
For OSL-related workflows, keep three decisions separate. USDGO is the stablecoin asset. OSL Business Treasury is the route to evaluate FX, conversion, liquidity, and treasury-management needs. OSL Business Payments is the route to evaluate collections, payments, settlement and business payouts. Availability, eligibility, fees, timing, and supported markets depend on current product terms and the relevant legal entity.
What a Treasury Stablecoin Is and Isn’t
A treasury team selects more than a token: it selects an asset, an operating route, and an internal control model. A stablecoin is the settlement asset; a payment or treasury service is the operating route; the enterprise remains responsible for approvals, accounting, risk limits and fallback decisions.
| Decision layer | What the treasury team must decide | Evidence to request |
| Asset | Which stablecoin will be held, converted or used for settlement? | Issuer identity, reserve disclosures, attestations, redemption terms, supported networks and restrictions |
| Service | Which provider will handle conversion, liquidity, collections, payments, wallets or reporting? | Legal entity, product scope, market availability, pricing, limits, operating status and contract terms |
| Enterprise workflow | Who approves, monitors, reconciles and can stop the route? | Treasury policy, wallet controls, approval matrix, accounting mapping, incident playbook and fallback rail |
This distinction matters because a stablecoin can be liquid on an exchange without being suitable for a company’s supplier-payment route. Conversely, a payment provider can support a workflow without issuing the stablecoin used in that workflow.
A Reference Guide to USDGO, USDT and USDC
The table below compares key decision factors without ranking the three assets. Each option still requires route-level verification.
| Comparison field | USDGO | USDT | USDC | What the enterprise should verify |
| Issuer and role | Anchorage Digital Bank N.A. issues USDGO, while OSL Group serves as its branding and distribution partner | Use Tether’s current official issuer and transparency materials. | Circle describes USDC as a Circle-issued stablecoin. | Confirm the legal issuer, service provider and contractual counterparty for the intended route. |
| Reserve disclosure | Anchorage publishes USDGO reserve attestations and states that an independent Big Four accounting firm prepares reports under AICPA attestation standards. | Tether’s transparency page states that tokens are backed 100% by Tether’s reserves and publishes circulation information. | Circle states that USDC is backed 100% by highly liquid cash and cash-equivalent assets. | Record the report date, scope, accounting standard, reserve categories and limitations. |
| Redemption and eligibility | Anchorage’s covered stablecoin terms distinguish Clients from Non-Clients and state that issuance and redemption are exclusively for Clients, subject to applicable terms and restrictions. | Confirm current redemption channels, minimums, fees, verification and jurisdiction rules in Tether’s official terms. | Confirm current Circle Mint or other redemption eligibility, fees, limits and jurisdiction rules. | Do not treat “redeemable 1:1” as direct access for every holder or every company. |
| Network support | Check network availability and supported series against current USDGO materials and terms. | Confirm the network and token contract used by the company’s route. | Confirm the network and token contract used by the company’s route. | An address on the wrong network can create operational or loss risk. |
| Liquidity and conversion | Assess liquidity on the specific venues and corridors the enterprise will use. | Often considered where broad market and venue coverage is important, but confirm the exact route. | Often considered where enterprise payment integrations and dollar conversion are important, but confirm the exact route. | Measure executable liquidity, not only quoted market capitalization. |
| Operating corridor | Confirm the sender, recipient, country, currency, wallet, and off-ramp conditions. | Confirm the same conditions for the intended corridor. | Confirm the same conditions for the intended corridor. | A token’s global reputation does not prove local payout or conversion availability. |
| Treasury fit | May fit when issuer evidence, reserve materials and the intended route satisfy the company’s control policy. | May fit when the route prioritizes established liquidity and a supported venue or corridor. | May fit when the route prioritizes payment integrations, reserve transparency and a supported dollar workflow. | Use a scored, documented decision rather than a generic “best stablecoin” label. |
Public descriptions are not automatically comparable. For example, a reserve-attestation page, a transparency dashboard and a customer agreement may describe different scopes. The treasury record should preserve the source, date, entity, product series and the question addressed by the evidence.
How Corporate Treasury Settlement Actually Works
The practical route is usually:
fiat funding → asset selection → conversion → wallet or account instruction → network settlement → recipient conversion or hold → ledger and reconciliation
The stablecoin covers the settlement asset in the middle of that flow. It does not by itself decide who may transact, how a company funds the wallet, how a supplier exits into local currency, how screening is performed, or how the transaction is posted to the general ledger.
For a supplier payment, the route may look like this:
- The enterprise validates the invoice, beneficiary, and payment purpose.
- Treasury checks the destination corridor, supported asset and available liquidity.
- The enterprise obtains the required approval and funds the account or wallet.
- The selected asset is converted and sent on the correct network.
- The recipient holds the asset or converts it through an eligible route.
- Finance matches the transaction identifier, amount, exchange rate, fees, and completion state to the invoice.
For a regional treasury rebalance, the route starts with a liquidity forecast rather than an invoice. The team determines which entity needs funds, which currency is required, whether the receiving entity is eligible, and which fallback rail to use if the preferred asset or conversion path is unavailable.
This is why chain confirmation and business settlement should be recorded as separate states. A transaction can be confirmed on a blockchain while conversion, sanctions screening, beneficiary access or ERP reconciliation is still outstanding.
The Treasury Use Cases That Are To Evaluate
Supplier and cross-border payments
USDT, USDC or USDGO may fit a supplier-payment route when the beneficiary can legally receive the asset, the destination has a usable conversion or holding option, and the enterprise can document the payment from instruction through reconciliation. A broader market footprint may matter more than the asset’s headline reserve description if the supplier needs a specific local exit path. A route with strong liquidity but no compliant beneficiary path is not operationally complete.
Avoid “USDT is best” or “USDC is safest” conclusions. One asset may be preferable for a corridor with deeper executable liquidity; another may fit where the enterprise has a documented issuer and reserve review process; a third may be appropriate only after confirming eligibility and redemption terms.
Cross-region treasury rebalancing
For intercompany or regional liquidity movements, treasury teams should compare when funds become usable, not just when a blockchain transaction confirms. Relevant fields include conversion depth, entity eligibility, counterparty limits, cut-off windows, wallet governance, accounting treatment, and fallback rails.
OSL Business Treasury is the appropriate OSL route to evaluate for FX, stablecoin conversion, liquidity and rebalancing questions. Check any rate, settlement time, or supported-currency statement against current product and contract terms.
Trading-business treasury
A trading business may value stablecoin balances for collateral movement, settlement preparation or liquidity management, but it also faces concentrated counterparty, market-liquidity and operational risks. The selection process should include the asset’s liquidity on the venues the business actually trades, the limits applied to each counterparty, the treatment of balances outside trading hours, and the procedure for moving to a bank rail.
Stablecoin balances should be governed as a controlled liquidity position, not described as risk-free cash. Possible decisions include approval, conditional approval, pilot testing, or rejection for that route, depending on the evidence and the business’s risk appetite.
Platform and batch settlement
Marketplaces, fintechs and payment platforms need more than an asset ticker. They need to know whether the workflow supports account or wallet creation, payment instructions, status updates, batch controls, idempotency, exception handling and reconciliation. These are service-layer questions.
OSL Business Payments is the OSL route to evaluate for collections, cross-border payments, stablecoin settlement and business payouts. OSL Business Platform is the route to evaluate for APIs, embedded wallets, white-label accounts and developer workflows. None of these service routes should be inferred from the existence of USDGO as an asset.
The Selection Barrier Is More Defined; The Question of Route Fit Remains
The scorecard below is an illustrative framework, not an official rating of any asset or provider. Treasury teams should adapt its criteria and weights to their risk policy, jurisdiction, corridor, and use case.
Score each criterion from 1 to 5, then apply the percentage shown in the table. Illustrative weight (%) means the suggested share of a 100-point model, not a universal measure of importance. Change it to match the company’s risk policy, jurisdiction, corridor, and use case. A score is meaningful only when you record the evidence, date, legal entity, and route assumptions beside it.
| Criterion | Illustrative weight (%) | Scoring question |
| Issuer and legal responsibility | 20 | Are the issuer, service provider and obligations clearly identified? |
| Reserves, attestations and disclosure | 20 | Can the company review current evidence, scope, date and limitations? |
| Redemption and eligibility | 15 | Can the company and its beneficiaries use the official redemption or exit path? |
| Corridor liquidity and conversion | 15 | Is there executable liquidity, FX and a workable local exit for the route? |
| Settlement and operating controls | 10 | Can the company control networks, wallets, approvals, limits and exceptions? |
| Treasury and ledger integration | 10 | Can the route provide the data needed for balances, transaction IDs and reconciliation? |
| Exit and fallback options | 10 | Can the business switch rails if liquidity, regulation or operations change? |
A useful scorecard records supporting evidence alongside each score. A 4 for “reserve disclosure” should link to a dated report and state what that report does not establish. A 3 for “corridor liquidity” should identify the venue, currency, execution assumptions and fallback. Missing information is not zero and should not be converted into a low-risk conclusion. Without that evidence trail, a numerical score creates false precision.
What Proven Treasury Infrastructure Looks Like at This Scale
USDGO and OSL Business should be evaluated as related but distinct parts of an enterprise workflow.
| Enterprise question | Correct route | Boundary to state clearly |
| What is USDGO and who issues it? | USDGO and Anchorage Digital issuer materials | OSL Group should not be described as the issuer unless a current official source explicitly says so. |
| What evidence supports reserves and redemption? | USDGO transparency materials and Anchorage terms | An attestation is dated evidence with a defined scope; it is not a blanket guarantee of every transaction or business outcome. |
| How should FX, conversion and liquidity be managed? | OSL Business Treasury | Confirm the legal entity, market, currency, limits, fees, timing and eligibility. |
| How should collections, payments and settlement be operated? | OSL Business Payments | Confirm the supported route, beneficiary conditions, payout method and service terms. |
| How should APIs, wallets or embedded workflows be evaluated? | OSL Business Platform | Do not infer endpoints, webhooks, SLAs or automation from a high-level product page. |
OSL Group’s public architecture also includes Banxa and OSL Exchanges as separate first-level businesses. They should not be used as synonyms for USDGO, OSL Business Treasury or OSL Business Payments.
Ready to Evaluate a Stablecoin Route for Your Business?
Before adding any of the three assets to a production treasury policy, the approval record should answer these questions:
- Which legal entity issues the asset, and which entity provides the service route?
- What is the date, scope and limitation of the latest reserve disclosure or attestation?
- Who may issue or redeem the asset, and what verification, fees, limits and jurisdiction restrictions apply?
- Which network, contract address and wallet controls are approved for the route?
- Can the intended supplier, subsidiary, platform or beneficiary receive and exit the asset?
- What is the executable liquidity and FX assumption for the actual corridor?
- Which OSL Business Treasury, OSL Business Payments or OSL Business Platform capability is being evaluated, and what is still subject to contract confirmation?
- Which transaction fields flow into the ERP or treasury system: asset, network, amount, rate, fee, transaction ID, status, timestamp and exception code?
- What event triggers re-approval: issuer change, expired report, liquidity deterioration, regulatory change, repeated failed payouts or a new destination country?
If any answer is missing, the result should be pilot or do not use for this route, not an assumed zero-risk score.
FAQ
Is USDGO a payment service or a stablecoin asset?
USDGO is the stablecoin asset. A payment or treasury service may use a stablecoin as part of a broader workflow, but the asset and the service are different decisions. Enterprises should review USDGO issuer, reserve and redemption materials separately from the terms of OSL Business Treasury or OSL Business Payments.
Is OSL Business Treasury the issuer of USDGO?
No. OSL’s public announcement identifies Anchorage Digital Bank N.A. as the issuer and OSL Group as the branding and distribution partner. The exact role, legal entity and market scope should still be checked against the current official materials used for publication.
Should a company choose USDT or USDC only because liquidity is deeper?
No. Liquidity matters, but the relevant measure is executable liquidity on the intended route. The company must also check reserve evidence, redemption access, beneficiary eligibility, network support, FX, controls, reconciliation and fallback options. A liquid asset can still be unsuitable for a specific corridor or regulated workflow.
Can a regulated stablecoin be used by every enterprise in every market?
No. Issuer regulation does not automatically establish eligibility for every holder, country, currency, payment purpose, or service route. The enterprise must check the issuer’s terms, local restrictions, beneficiary conditions, and the service provider’s current availability.
When should an enterprise use a stablecoin rather than a bank rail?
A stablecoin may fit when the route has a clear business need, documented controls, usable liquidity and a compliant beneficiary path. A bank rail may remain preferable when the destination, accounting, legal or operational requirements are better served by existing banking infrastructure. Many treasury policies should support both routes.
What should treasury teams compare before approving a settlement asset?
Compare the issuer and legal obligations, reserve evidence, redemption and eligibility, route liquidity, network controls, FX and conversion, accounting data, counterparty limits and fallback options. Keep the evidence and its date beside the score so that the decision can be refreshed when the asset, provider or corridor changes.
Sources
- [S1] OSL Group, “OSL Group Unveils USDGO Stablecoin to Strengthen Global Compliant Payment Network,” accessed 2026-09-02: <https://www.osl.com/hk-en/press-release/osl-group-unveils-usdgo-stablecoin-to-strengthen-global-compliant-payment-network>.
- [S2] Anchorage Digital, “USDGO reserve attestations,” accessed 2026-09-02: <https://www.anchorage.com/platform/usdgo-reserve-attestations>.
- [S3] Anchorage Digital Bank N.A., “Covered Stablecoin Terms,” accessed 2026-09-02: <https://www.anchorage.com/anchorage-digital-bank-n-a-covered-stablecoin-terms>.
