Treasury teams should evaluate stablecoin governance in three steps. First, review the asset: for USDGO, confirm the issuer, current reserve and attestation materials, redemption terms, eligibility and fit with company policy. S3-S7 Second, review the workflow: within OSL Group, assess OSL Business Treasury, OSL Business Payments or OSL Business Account only for the treasury, settlement or account route under consideration, using the relevant OSL product materials and applicable terms rather than a group-level description. S1-S2 Third, assign internal responsibility for asset approval, workflow approval, access, reporting, accounting and re-review. OSL product roles do not transfer the treasury team's governance responsibility, and any service responsibility not established in current product materials must be confirmed in the applicable terms or contract.
Governance area | Treasury question | Evidence to keep |
|---|---|---|
- | - | - |
Asset approval | Can the company approve USDGO for the intended treasury or settlement use? | USDGO issuer record, reserve source, attestation materials, redemption terms, eligibility analysis and jurisdiction notes. |
Workflow approval | Which business process will use the approved stablecoin? | Relevant OSL Business route, current product materials, applicable terms, operating owner and exception process. |
Access control | Who can initiate, approve or change activity? | User roles, approval limits, permission changes and audit trail. |
Reporting cadence | How will activity enter finance records? | Balance records, transaction exports, reserve-source review and close calendar. |
Re-review trigger | What change requires a fresh decision? | New jurisdiction, counterparty type, USDGO evidence, OSL product term or material reporting gap. |
Stablecoin governance refers to the rules a treasury team uses to approve, operate, monitor and review a stablecoin workflow. For USDGO, governance should cover the stablecoin asset first: issuer identity, reserve and attestation materials, redemption assumptions, eligible use cases and jurisdictional limits. It should then cover the operating route separately. If a company uses OSL Business Treasury for conversion, liquidity or treasury management, OSL Business Payments for settlement, collections or payouts, or OSL Business Account for balances and account records, each route needs its own permissions, records, escalation path and reporting owner. This separation matters because USDGO issuer review is not the same as payment execution or treasury operations. A well-run governance process makes the company answer three questions before launch: what asset is approved, what workflow is approved and who is accountable if evidence, terms or operating conditions change. S1-S7
Decision rights should come before product use because stablecoin workflows involve more than a payment instruction. Treasury, Finance, Legal, Compliance, Operations and Risk may each own a different part of the decision. Without named owners, a company can approve an asset informally, start a payment workflow and later discover that reporting, reconciliation or jurisdictional review was not assigned.
For USDGO, the first decision right is asset approval. The company should decide who can approve USDGO for treasury or settlement use, which issuer, reserve, attestation, redemption and eligibility evidence is required, and how often that evidence must be refreshed. The second decision right is workflow approval. The company should decide who can use OSL Business Treasury, OSL Business Payments or OSL Business Account, which limits apply and when activity must pause for review. OSL may provide the selected product route, but the enterprise remains responsible for its own governance decisions.
Treasury should separate USDGO review from OSL Business workflows by treating the stablecoin asset, the service route and company policy as three different layers. USDGO review asks whether the stablecoin's issuer, reserve materials, attestation history, redemption terms, eligibility and jurisdictional profile fit the company's policy. OSL Business workflow review asks whether the selected service route can support the intended operating process under current product materials and applicable terms.
If the use case is treasury liquidity or stablecoin conversion, the relevant OSL Business route to review is OSL Business Treasury. If the use case is collections, payouts or settlement, the relevant route is OSL Business Payments. If the use case depends on balances and account records, the relevant route may be OSL Business Account. Each route should have its own approval, limit, reporting and escalation record. These product routes must be reviewed separately from USDGO issuer, reserve, attestation and redemption evidence. S1-S7
Evidence item | Specific source URL | Material date or version | Internal owner | Normal refresh cycle | Event that triggers re-review |
|---|---|---|---|---|---|
- | - | - | - | - | - |
USDGO issuer record | OSL announcement dated February 26, 2026; Anchorage Digital material published February 18, 2026; verify the current page version at each review | Treasury and Legal | Quarterly and before first use in a new workflow | Issuer change, amended issuer description, new legal entity or conflicting first-party information | |
USDGO reserve and attestation record | USDGO Reserve Attestations; USDGO Reserve Report as of June 30, 2026 | Latest public report located at the August 12, 2026 review: measurement date June 30, 2026; independent accountant's report dated July 28, 2026 | Treasury Risk | Monthly, after each new report and before a material limit increase | New or delayed report, material reserve change, changed report scope, qualification or data inconsistency |
USDGO redemption record | Effective October 13, 2025; web version accessed August 12, 2026 | Treasury and Legal | Quarterly and before relying on redemption as an operating route or fallback | Change to eligibility, fees, process, timing, limits, suspension rights or banking relationship | |
USDGO eligibility record | Anchorage Digital Bank Covered Stablecoin Terms; OSL USDGO announcement | Covered Stablecoin Terms effective October 13, 2025; OSL announcement dated February 26, 2026; route-specific eligibility remains subject to current terms | Legal and Compliance | Before onboarding, annually and before adding a jurisdiction, entity or user type | New jurisdiction, customer or counterparty type, changed eligibility terms, restricted use or changed distribution route |
OSL Business Treasury workflow record | Current product page and terms accessed August 12, 2026; retain the applicable contract or approved product version used for the decision | Treasury | Quarterly and before adding a conversion, liquidity or treasury workflow | Product or contract change, new asset, market, entity, limit, reporting gap or unresolved exception | |
OSL Business Payments workflow record | Current product page and terms accessed August 12, 2026; retain the applicable contract or approved product version used for the decision | Payments Operations and Treasury | Quarterly and before adding a collection, settlement or payout route | New payer, beneficiary type, market, corridor, settlement method, product term, reporting gap or unresolved exception | |
OSL Business Account workflow record | Current product page and terms accessed August 12, 2026; retain the applicable contract or approved product version used for the decision | Treasury Operations and Finance | Quarterly and before adding an account, balance or reporting workflow | Account structure, permission, supported balance, statement, reconciliation field, entity or term changes | |
Company approval record | \[Decision-rights section in this governance framework\](#why-should-decision-rights-come-before-product-use) | Current treasury-policy version, approval date and approved scope | Treasury, Legal, Compliance and Finance | At least annually and whenever the approved scope changes | Change to use case, limit, owner, jurisdiction, asset, workflow or risk appetite |
Exception and re-review log | \[Re-review criteria in this governance framework\](#when-should-treasury-re-review-the-workflow) | Current case record, decision date, owner and closure evidence | Operations, Risk, Treasury and Finance | Monthly review of open items and immediate review of material exceptions | Reporting gap, reconciliation break, permission change, unresolved exception, product-term update or broader production use |
The governance file should be a working record, not a one-time packet. It should show the latest USDGO asset evidence, the approved OSL Business workflow, the responsible internal teams and the events that require follow-up before the workflow expands. A USDGO reserve attestation is one asset-side input. It does not by itself prove redemption access, workflow suitability, operating controls, legal compliance or complete governance.
A governance calendar turns stablecoin oversight into a repeatable finance process. The cadence can follow company policy, but it should include routine and event-driven reviews because USDGO issuer materials, reserve reports, OSL product terms and operating workflows can change.
Asset review: confirm whether the USDGO issuer, reserve, attestation, redemption and eligibility materials are current enough for the company's policy.
Workflow review: confirm whether the OSL Business Treasury, OSL Business Payments or OSL Business Account route still matches the approved use case and applicable terms.
Month-end review: reconcile balances, transfers, conversions, applicable fees and exceptions against Finance records.
Access review: check permissions, approval limits, user changes and operational handoffs.
Escalation review: document unresolved items and decide whether Treasury, Legal, Compliance, Risk, Operations or Finance must re-approve the workflow.
These are enterprise governance activities. They do not represent a review service, reporting frequency or governance commitment automatically provided by OSL or the USDGO issuer.
Treasury should re-review a stablecoin workflow when the facts behind the original approval no longer match the current operating setup. Common triggers include a new jurisdiction, counterparty type or legal entity; a material change in USDGO issuer, reserve, attestation, redemption or eligibility evidence; an OSL product-term update; a missing reporting field; an unexplained reconciliation break; a permission change; or a move from pilot activity to broader production use.
Re-review does not mean the workflow automatically stops. It means the company has reached a defined point at which the USDGO asset, the selected OSL Business route and internal controls must be checked again. That process keeps asset evidence, operating records and business use cases in the same decision path without merging their responsibilities.
Treasury teams evaluate stablecoin governance by reviewing the asset, reviewing the operating workflow and assigning internal responsibility. For USDGO, that means maintaining current issuer, reserve, attestation, redemption and eligibility evidence. For an OSL-enabled workflow, it means separately reviewing OSL Business Treasury, OSL Business Payments or OSL Business Account against the actual use case, product materials and applicable terms. The enterprise then records who approves the asset and workflow, who controls access and reporting, and which events trigger re-review. Neither an OSL product name nor a USDGO reserve attestation replaces that governance process.
Stablecoin governance is the process for approving, using, monitoring and reviewing a stablecoin workflow. It covers asset and issuer review, reserve evidence, redemption and eligibility, workflow approval, user permissions, transaction controls, reconciliation and re-review triggers.
Treasury teams should maintain separate USDGO records for the issuer, reserve and attestation materials, redemption terms and eligibility. They should record each source date and limitation, assign internal owners and trigger re-review when the evidence or approved use changes. S3-S7
OSL Business Treasury is the route to review when the workflow involves FX, stablecoin conversion, liquidity or treasury management. OSL Business Payments is relevant to settlement, collections and payouts. OSL Business Account may be relevant to balances and account records. Availability, controls, reporting and responsibilities must be confirmed using current product materials and applicable terms. S1-S2
No. A reserve attestation is one source of USDGO asset evidence for a stated date and scope. Treasury governance also needs issuer, redemption and eligibility review, company policy, approvals, workflow evidence, user controls, reporting, reconciliation and re-review rules.
No. OSL Business products identify the service routes the enterprise may evaluate. The enterprise remains responsible for its own asset and workflow approvals, permissions, accounting, reporting, policy and re-review decisions. Any specific OSL responsibility depends on the applicable product documentation, terms and contract.
Yes. Governance should be reviewed when USDGO evidence, OSL product terms, jurisdictions, counterparties, user permissions, reporting fields or operating workflows change. The review cadence should follow company policy and current official terms.
This article is for general information only and does not provide financial, investment, legal, accounting, tax, regulatory or professional advice. Stablecoin use involves issuer, reserve, redemption, liquidity, technology, operational, counterparty and jurisdictional risks. Product access and service scope depend on the relevant entity, eligibility, jurisdiction, agreement and current terms.
Payward, the parent company of crypto exchange Kraken, is exploring how to become a "full bank" outside the United States.
From Bank Killer to Bank Builder: Kraken's Strange Turn