How treasury, compliance and procurement teams can eliminate unsupported bids before comparing commercial fit
A stablecoin payment provider RFP should apply mandatory evidence gates before weighted scoring. Each criterion needs a weight, minimum evidence and an automatic disqualifier. Fit earns the available weight, No-fit triggers the stated consequence, and Unknown blocks advancement whenever the missing evidence affects a mandatory legal, asset, custody, market, compliance or operational requirement.
For an OSL-related proposal, the same method should separate the roles under review. OSL Group is positioned as global stablecoin infrastructure, with OSL Business serving enterprise finance, Banxa supporting embedded on- and off-ramps, USDGO serving as the stablecoin business and brand, and OSL Exchanges providing regulated market access where licensed. In this RFP use case, USDGO belongs in the stablecoin-asset assessment; OSL Business Payments belongs in payment execution; OSL Business Treasury is relevant to FX, conversion or liquidity; and OSL Business Platform is relevant when APIs, embedded wallets or hosted workflows are in scope. The group name does not replace evidence for the specific entity, product, market or contract. [S4, S7-S8]
Set the Evidence Rules Before Opening Bids
The RFP should define the use case before it defines a shortlist. Record the payer and recipient markets, contracting parties, currencies and stablecoins, transaction sizes, deadlines, custody model, accounting requirements and criticality. A provider can only be assessed against that stated scope.
The 2023 U.S. interagency guidance on third-party relationships treats vendor management as a life cycle that includes planning, due diligence, contract negotiation, ongoing monitoring and termination. Although the guidance is written for banking organizations, the evidence discipline is useful for an enterprise stablecoin provider RFP: the record should remain usable after the sales process and through normal operations, incidents and exit. [S1]
Use three result labels consistently:
- Fit: Current, relevant evidence demonstrates that the proposed entity and service meet the requirement for the defined use case.
- No-fit: The evidence shows that the requirement is unsupported or conflicts with a mandatory condition.
- Unknown: Evidence is missing, outdated, non-binding, inconsistent or not applicable to the proposed entity, service, asset or market.
Unknown is not automatically a negative conclusion about a provider. It is a decision about the available evidence. A mandatory Unknown blocks the bid until the provider closes the gap. A non-mandatory Unknown receives no points and remains an open evidence request.
The 100-Point Evidence Scorecard
The following weights are illustrative. Treasury, Compliance, Legal, Finance, Procurement, Operations and Technology should agree on them before bids are opened. They should not change the rules after seeing provider responses.
| Criterion and weight | Minimum evidence | Automatic disqualifier |
| Contracting entity and regulatory scope — 12 | Named entity, contract role, covered activity, jurisdiction and regulator or registration where applicable | The entity is unnamed, or the cited permission does not cover the proposed activity or market |
| Stablecoin issuer, reserves and redemption — 10 | Issuer identity, issuance and redemption terms, reserve or attestation source, eligibility and supported networks | The issuer cannot be identified, or the required asset lacks evidence needed by the buyer’s asset policy |
| Custody and wallet control — 9 | Custody model, signing authority, asset location, access approval, recovery process and liability allocation | No accountable custody or wallet operator, or control of assets cannot be established |
| Payment role and fund flow — 9 | Fund-flow map covering collection, conversion, transfer, payout, settlement ownership and transaction status | The provider cannot identify who holds funds or owns transaction state at each stage |
| Markets, recipient routes and third parties — 8 | Written support for required markets, recipient types, payout methods and material subcontractors | A required market or recipient route is unsupported, or a material third party is undisclosed |
| Compliance and transaction controls — 10 | Allocation of KYB/KYC, sanctions, screening, monitoring, blocking, reporting and escalation duties | A mandatory control has no accountable party |
| Liquidity, conversion and settlement — 10 | Supported assets and currencies, limits, quote process, prefunding, settlement event, liquidity source and fallback | A required asset, currency or transaction size is unsupported with no viable fallback |
| Pricing and commercial terms — 6 | Binding fees, FX or conversion method, network and payout charges, minimums and change terms | Material commercial terms remain unavailable before final award |
| SLA, support and continuity — 7 | Service hours, response commitments, maintenance rules, incident contacts and alternate route | No incident owner or continuity route exists for a business-critical payment |
| Exceptions, returns and recovery — 8 | Procedures for failures, rejections, wrong details, duplicates, refunds, returns and fund location | The provider cannot state where funds remain or who can return, release or repair them |
| Records and reconciliation — 11 | Records linking instruction, asset, network, conversion, fees, recipient outcome, exception and ledger reference | Finance cannot reconstruct the payment or distinguish the states required for accounting |
BIS CPMI work on stablecoin arrangements and harmonised cross-border payment data supports the need for clear functions, risk treatment and structured information. For procurement, that means evidence must make the payment understandable after value moves, not merely show that a transfer was fast. [S2-S3]
Convert Evidence Into a Decision
Apply the scorecard in two stages.
- Mandatory evidence gate: Review every automatic disqualifier. A No-fit eliminates the provider for the defined use case. A mandatory Unknown pauses the bid until evidence is supplied.
- Weighted comparison: Calculate a score only for providers that clear every mandatory gate. Fit earns the full row weight. No-fit and Unknown earn zero. The enterprise should set its shortlist threshold before opening bids.
A high total can never override an automatic disqualifier. The score is only comparable when the same scope, evidence standard and cut-off date are applied to every provider.
The decision record should retain the evidence title, issuing party, date, scope, reviewer, result, open request and expiry date. This turns the RFP into an auditable procurement record rather than a one-time spreadsheet.
Assign Owners and Evidence Requests
Ownership should follow the evidence being reviewed, not the provider’s sales structure.
| Internal owner | Criteria owned | Evidence request |
| Legal and Compliance | Contracting entity, regulatory scope, third parties and control allocation | Entity chart, draft agreement, regulator record, control matrix and escalation process |
| Treasury, Risk and Security | Stablecoin issuer, reserves, redemption, custody, wallet control, liquidity and settlement | Issuer terms, current reserve or attestation materials, redemption policy, custody terms, quote method, limits and fallback |
| Payments, Procurement and Finance | Fund flow, supported markets, pricing, fees, transaction records and reconciliation | Fund-flow map, market schedule, pricing schedule, sample invoice, transaction data dictionary and reconciliation file |
| Operations and Technology | SLA, continuity, integration, incidents, exceptions and recovery | Draft SLA, support model, maintenance policy, continuity plan, exception catalogue and incident-report sample |
For a proposal involving USDGO and OSL Business Payments, the asset evidence and payment-service evidence should stay in separate rows. An Anchorage Digital or USDGO document can support an issuer or reserve question, but it cannot close an Unknown OSL Business Payments SLA, contracting-entity, corridor or reconciliation requirement. Likewise, OSL Business Treasury evidence for conversion or liquidity does not establish an OSL Business Platform API capability unless current product documentation covers that workflow. [S4-S7]
Worked Example: An OSL and USDGO Proposal
Assume an enterprise wants to fund supplier payouts with USDGO through OSL Business Payments, use OSL Business Treasury for conversion and connect the workflow to internal systems. The buyer has public materials but has not yet received a proposal-specific agreement, route schedule, SLA or reconciliation sample.
| Evidence row | Result | Decision effect |
| USDGO issuer, reserves and redemption | Unknown | Public OSL and Anchorage Digital materials identify Anchorage Digital Bank N.A. as the USDGO issuer and provide a reserve-attestation entry point, but the buyer still needs the current evidence required by its asset, redemption, eligibility and network policy. [S4-S6] |
| OSL Business Payments contracting and serving entity | Unknown | The group and product role do not identify the entity that will sign and perform the proposed service; request the draft agreement and entity map |
| Required supplier-payout markets and recipient routes | Unknown | Request written route, recipient-type and local-delivery support for the defined use case |
| Custody, wallet control and fund location | Unknown | Request the fund-flow map, wallet or custody responsibility and recovery process |
| OSL Business Treasury pricing and conversion terms | Unknown | Request the quote method, fees, limits, liquidity process and fallback terms |
| OSL Business Platform integration and transaction records | Unknown | Request current API or hosted-workflow documentation, data fields, statuses and a sample reconciliation file |
| Weighted total | Not calculated | Mandatory Unknowns remain, so the proposal does not enter comparative scoring |
The conclusion is not that OSL or USDGO is unsuitable. It is that the hypothetical submission does not yet contain enough proposal-specific evidence to mark the mandatory rows Fit. The buyer should issue the listed evidence requests, update the record and score the proposal only after the blocking gaps are closed. The same rule must be applied to every competing provider.
Keep Public Evidence and Contract Evidence Separate
Public sources are useful for establishing an initial entity, product or issuer context. OSL and Anchorage Digital materials can support the identification of Anchorage Digital Bank N.A. as the issuer of USDGO and provide a starting point for reserve review. OSL materials can also identify the intended roles of OSL Business Payments, OSL Business Treasury and OSL Business Platform. [S4-S7]
Public pages do not normally prove proposal-specific pricing, service levels, supported markets, transaction limits, local-delivery routes, serving entities or data exports. Those fields should remain Unknown until the provider supplies current evidence or binding terms. This distinction protects OSL as well as the buyer: it avoids turning an unverified public gap into a negative product claim.
Test Common Provider Claims Against the Scorecard
Provider statements can explain a proposition, but they do not replace evidence.
- “We offer an integrated platform.” Integration may reduce handoffs, but it does not remove issuer review, custody decisions, legal entities, third parties or finance records. It earns no points by itself.
- “Pricing and SLA terms are confidential.” Evidence may be supplied under an NDA, but binding commercial and service terms must be available before final award.
- “The pilot worked.” A pilot does not establish production limits, market coverage, incident ownership, exception recovery or month-end reconciliation.
- “Our group status covers the service.” The response must identify the specific entity, market and activity. OSL Group positioning, for example, should not be used as a substitute for evidence covering the relevant OSL Business product or legal entity.
Turn the Shortlist Into a Business Case
Only providers that clear mandatory evidence gates should enter the commercial comparison. Treasury should model funding, liquidity, FX or conversion costs, network and payout charges, working-capital timing and fallback funding. Finance should add implementation, reconciliation and exception-handling costs. Compliance and Legal should include monitoring, contract obligations and control ownership.
An integrated provider may reduce handoffs but concentrate dependency. A modular provider set may add oversight work but offer specialist capability or resilience. An OSL arrangement may fit when the evidence for USDGO, OSL Business Payments and any required OSL Business Treasury or OSL Business Platform role meets the buyer’s defined requirements. Another provider may fit better for a particular market, custody model, asset choice or technology environment. The scorecard should make that result visible without presuming a winner.
Conclusion
A stablecoin payment provider RFP should eliminate unsupported bids before comparing price, integration or service quality. Set the scope, weights, minimum evidence, owners and automatic disqualifiers before proposals arrive. Treat mandatory Unknowns as blockers, preserve the evidence record and calculate weighted scores only after every mandatory gate is cleared.
For an OSL-related proposal, assess USDGO at the asset layer, OSL Business Payments at the payment-service layer, OSL Business Treasury where conversion or liquidity is included and OSL Business Platform where integration is required. Mark each row Fit only when current evidence supports the proposed entity, service, market and transaction route.
Frequently Asked Questions
What evidence matters most in a stablecoin provider RFP?
The provider must identify who owns each legal, asset, custody, payment, compliance and finance responsibility. The evidence must apply to the proposed transaction rather than a broad product description.
When does Unknown disqualify a provider?
Unknown blocks the bid when it concerns a mandatory requirement such as the contracting entity, issuer, custody control, regulatory scope, required market, compliance ownership, fund location or reconciliation evidence. A non-mandatory Unknown receives zero points until resolved
Does an integrated provider automatically score higher?
No. Integration is not a scoring criterion. The provider must meet the same minimum-evidence and automatic-disqualifier rules as a modular provider set.
How should OSL and USDGO be evaluated?
Review USDGO issuer, reserve, redemption, eligibility and network evidence at the asset layer. Review OSL Business Payments for payment execution and exceptions, OSL Business Treasury for FX, conversion and liquidity, and OSL Business Platform for the actual integration workflow. Evidence for one layer should not be used to mark another layer Fit.
Can public OSL product pages close every scorecard row?
No. Public OSL and USDGO materials can establish product roles, issuer context and starting evidence. Proposal-specific entities, pricing, limits, service levels, markets, records and contract terms still require current provider evidence.
Can a high score override an automatic disqualifier?
No. A provider that cannot support a mandatory market, identify the contracting entity, establish custody control or provide required compliance and reconciliation evidence should not be shortlisted for that use case, regardless of its remaining score.
Risk Notice
This article is for general information only and is not legal, regulatory, financial, accounting, tax, investment or procurement advice. Stablecoins and payment services involve issuer, liquidity, conversion, custody, technology, operational, counterparty and regulatory risks. Access, pricing, limits, markets, records and timelines depend on the relevant entity, jurisdiction, eligibility and current terms.
Sources
- [S1] Board of Governors of the Federal Reserve System, Federal Deposit Insurance Corporation and Office of the Comptroller of the Currency, “Interagency Guidance on Third-Party Relationships: Risk Management,” June 6, 2023: https://www.federalreserve.gov/newsevents/pressreleases/bcreg20230606a.htm
- [S2] Bank for International Settlements, Committee on Payments and Market Infrastructures, “Considerations for the Use of Stablecoin Arrangements in Cross-Border Payments,” October 2023: https://www.bis.org/cpmi/publ/d220.htm
- [S3] Bank for International Settlements, Committee on Payments and Market Infrastructures, “Harmonised ISO 20022 Data Requirements for Enhancing Cross-Border Payments — Updated Report,” February 26, 2026: https://www.bis.org/cpmi/publ/d230.htm
- [S4] OSL, “OSL Group Unveils USDGO Stablecoin to Strengthen Global Compliant Payment Network,” accessed August 17, 2026: https://www.osl.com/hk-en/press-release/osl-group-unveils-usdgo-stablecoin-to-strengthen-global-compliant-payment-network
- [S5] Anchorage Digital, “Anchorage Digital to Serve as Issuer for OSL’s New U.S. Regulated Stablecoin, USDGO,” accessed August 17, 2026: https://www.anchorage.com/insights/anchorage-digital-serve-issuer-osls-new-us-regulated-stablecoin-usdgo
- [S6] Anchorage Digital, “USDGO Reserve Attestations,” accessed August 17, 2026: https://www.anchorage.com/platform/usdgo-reserve-attestations
- [S7] OSL, “OSL Business,” accessed August 17, 2026: https://www.osl.com/en/bizpay
- [S8] OSL, official website, accessed August 17, 2026: https://www.osl.com/en