A treasury-focused framework for separating the settlement asset, route, service provider, evidence record and fallback plan.
Summary
An on-chain transfer can be complete while the underlying invoice is still open. Asset movement, recipient delivery and financial close are different events. Corporate treasury should therefore evaluate the USD settlement asset and the payment service separately.
Within OSL Group’s current product structure, USDGO belongs on the asset side, and Anchorage Digital identifies Anchorage Digital Bank N.A. as its issuer. OSL Business Payments belongs on the service side for payment and settlement workflows, while OSL Business Treasury may be relevant to FX, conversion and liquidity. Each component requires its own approval for the proposed company, jurisdiction and route. [S2, S3]
Key Points
- Define what the recipient must receive and what record will close the obligation before selecting an asset.
- Review the stablecoin and the payment service separately, even when they are offered through related businesses.
- A regulatory label does not replace review of reserves, redemption, eligibility, liquidity and operating controls.
- A payment service adds value when the company needs conversion, delivery, reporting or exception management that it cannot operate itself.
- Every approval should state where the proposed arrangement fits, where it does not fit and what remains unconfirmed.
Define the Settlement Outcome First
Corporate settlement is complete when the agreed obligation has been discharged in the required form and Finance can match the result to the underlying business record. A blockchain transaction may prove that tokens moved between wallet addresses, but it does not by itself show that the correct invoice, intercompany balance or supplier obligation has been closed.
Treasury should document four points before reviewing any stablecoin:
- Recipient outcome: Must the recipient hold a stablecoin, receive USD in a bank account or receive local currency?
- Completion event: Is settlement complete at on-chain confirmation, provider confirmation, conversion or bank credit?
- Evidence requirement: Which invoice reference, transaction ID, conversion record, approval and ledger entry must be retained?
- Fallback requirement: What route will be used if the stablecoin, service provider, conversion counterparty or banking endpoint is unavailable?
This definition determines whether the company needs only an approved settlement asset or also needs a payment service. An asset-only arrangement may be workable when both parties already operate approved wallets, accept the same stablecoin and can handle controls and reconciliation internally. A payment service becomes more relevant when the workflow requires fiat funding, currency conversion, recipient delivery, status reporting or managed exceptions.
Review the USD Settlement Asset on Its Own Terms
The asset review should begin with legal responsibility. Treasury needs to identify the issuer and understand which entity is responsible for issuance and redemption. The regulatory status of an exchange, group affiliate or payment provider should not be treated as evidence about the issuer unless the official record expressly covers that entity and activity.
Reserve and attestation materials should then be reviewed for scope, reporting date, frequency and the party that prepared the report. These materials can help a company understand what was examined at a particular point in time. They do not automatically establish direct redemption access, market liquidity or suitability for every payment route.
Redemption requires a separate check. The company should confirm who is eligible to redeem, through which entity, in which currency, under what limits and operating conditions, and whether redemption is available directly or through an intermediary. A stablecoin may have public reserve materials while still being impractical for a company that cannot obtain or exit the asset through its approved counterparties.
Liquidity and network fit complete the asset review. Treasury should verify where the stablecoin can be acquired, transferred and converted under the company’s actual operating arrangement. Exchange liquidity, provider liquidity and direct issuer redemption are different access paths. The asset must also be available on a network supported by the company’s wallets, service providers and intended recipients.
The Financial Stability Board’s recommendations for global stablecoin arrangements emphasize governance, risk management, disclosures and redemption rights. Those categories provide a useful starting point, but an enterprise still needs route-specific evidence before approving an asset for settlement. [S1]
Decide What the Payment Service Must Do
A stablecoin can carry value without solving the operational work around the payment. The service review should start with the functions the company actually needs rather than a provider’s full product list.
The required scope may include:
- accepting a payment instruction and validating the required data;
- funding or converting fiat and stablecoin balances;
- transferring value through an approved wallet and network;
- delivering stablecoin, USD or local currency to the recipient;
- returning transaction status, fees and conversion records;
- supporting reconciliation, failed-payment handling and escalation;
- maintaining a fallback route when the primary path is unavailable.
Each capability should be verified against current product documentation and contract terms. The company should confirm the contracting entity, supported jurisdictions, eligible customers, payment routes, operating limits, pricing, service availability, reporting fields and exception ownership. Capabilities that are not publicly documented should remain unconfirmed until the provider supplies evidence.
Evidence Matrix for Asset and Service Selection
The same matrix can be used for every candidate. This keeps a recognizable brand, a regulatory label or an integrated product story from carrying more weight than the underlying evidence.
| Review area | Minimum evidence | May fit when | Poor fit when | Confirm before approval |
| Settlement outcome | Contract, invoice or treasury instruction defining the required recipient value | The route produces the agreed asset or bank credit and a record Finance can close | Completion is defined only as token transfer while the recipient needs another form of value | Finality, destination evidence and accounting treatment |
| Issuer and legal responsibility | Issuer documentation and relevant regulatory or legal records | The responsible issuer and issuance activity are clearly identified | Responsibility is inferred from an exchange, affiliate or provider brand | Issuing entity, governing terms and eligible users |
| Reserve information | Current reserve disclosures or attestation materials with dates and scope | Treasury can review what was examined and when | Claims are undated, incomplete or unsupported by accessible materials | Reporting cadence, exceptions and source documents |
| Redemption and exit | Current redemption terms and available access path | The company has an approved route to redeem or convert under workable conditions | Direct or intermediary exit is unavailable, unclear or incompatible with policy | Eligibility, limits, timing, fees and fiat destination |
| Liquidity and network | Evidence from the actual provider, venue or counterparty used in the route | The required amount can be sourced, transferred and converted on supported networks | Liquidity exists elsewhere but not in the approved operating route | Depth, limits, spreads, networks and counterparty acceptance |
| Payment-service role | Product documentation and contract scope | The service covers the conversion, delivery, reporting or exception work the company needs | The service does not support the required recipient, route or completion state | Contracting entity, jurisdictions, service hours and third parties |
| Finance records | Sample statement, status record or reporting specification | Finance can connect the instruction, transfer, conversion, fees and destination to the ledger | Wallet activity cannot be matched to the business obligation | Identifiers, status definitions, data retention and exception records |
| Fallback | Approved alternative route and named owner | A bank, provider or alternative asset route can complete the obligation within policy | Failure leaves funds without an approved exit or operating owner | Trigger, escalation path, liquidity source and reconciliation treatment |
Where USDGO and OSL Business May Fit
USDGO can be reviewed as one USD settlement-asset candidate. Anchorage Digital’s USDGO transparency page identifies Anchorage Digital Bank as the issuer and provides monthly reserve-attestation materials prepared by an independent Big Four accounting firm under AICPA attestation standards. This establishes a named issuer and a public source for reviewing reserve information. It does not establish that every enterprise can redeem USDGO directly, that every network or jurisdiction is supported, or that sufficient liquidity exists for a particular route. Those points require current confirmation. [S2]
The service decision remains separate. OSL Business Payments is the relevant OSL Business category when the required workflow includes collections, cross-border payments, stablecoin settlement or business payouts. OSL Business Treasury is the category to examine when the company needs FX, stablecoin conversion, liquidity or treasury management. OSL’s public materials provide the starting point for this review, while the contracting entity, route coverage, eligibility, limits, pricing, operating conditions, reporting and fallback responsibilities must be confirmed for the proposed arrangement. [S3]
This combination may be worth evaluating when the company wants to assess USDGO as the settlement asset and an OSL Business service for part of the operating route. It may be a poor fit when the recipient, jurisdiction, network, redemption path or required service is unsupported or remains unverified. The asset and service should therefore receive separate approval decisions, even if they are ultimately used together.
A Five-Step Selection Process
- Define completion. Record what the recipient must receive and what evidence closes the obligation.
- Approve the asset standard. Review the issuer, reserves, redemption, eligibility, liquidity and network.
- Identify service gaps. Determine which conversion, delivery, control, reporting or exception functions cannot be handled internally.
- Test the full route. Confirm every counterparty, endpoint, operating condition and fallback under current terms.
- Record the decision. State where the arrangement fits, where it does not fit and which items remain unresolved.
A company can then choose an asset-only arrangement, an asset-plus-service arrangement or a route that retains bank infrastructure for part of the settlement. The choice should follow the required business outcome rather than the provider’s preferred product structure.
FAQ
How should a treasury team choose a USD stablecoin for settlement?
Review the issuer, reserve disclosures, redemption access, eligibility, operating liquidity, supported networks and counterparty acceptance. The asset should also produce the records and exit options required by the company’s treasury policy.
Is USDGO a payment service?
No. USDGO is the stablecoin asset and brand. Anchorage Digital identifies Anchorage Digital Bank N.A. as the issuer. OSL Business Payments is a separate service category for enterprise payment and settlement workflows. [S2, S3]
When does a company need a payment service as well as a stablecoin?
A payment service may be needed when the company requires fiat funding, conversion, recipient delivery, transaction reporting, reconciliation support or managed exceptions. Companies that already operate these functions under approved controls may need less service involvement.
Does a regulated label make a stablecoin suitable for corporate settlement?
No single label completes the review. Treasury still needs evidence covering the issuer, reserves, redemption, eligibility, liquidity, network, operating controls and intended settlement route. [S1]
Risk Notice
Stablecoin settlement can involve issuer, reserve, redemption, liquidity, network, wallet, custody, cybersecurity, legal, regulatory, operational and counterparty risks. Product access and suitability depend on jurisdiction, eligibility, supported routes and current terms. This article is for general information and does not constitute legal, investment, accounting, tax, procurement or financial advice.
Sources
- [S1] Financial Stability Board, “High-level Recommendations for the Regulation, Supervision and Oversight of Global Stablecoin Arrangements: Final report,” July 17, 2023: https://www.fsb.org/2023/07/high-level-recommendations-for-the-regulation-supervision-and-oversight-of-global-stablecoin-arrangements-final-report/
- [S2] Anchorage Digital, “USDGO Reserve Attestations,” accessed August 6, 2026: https://www.anchorage.com/platform/usdgo-reserve-attestations
- [S3] OSL, official website and OSL Business materials, accessed August 6, 2026: https://www.osl.com/en and https://www.osl.com/en/bizpay