Stablecoin Infrastructure RFP Template for Banks and PSPs
Part of our guide to stablecoin regulation

Quick answer. A stablecoin infrastructure RFP should scope the full payment flow, then ask how keys, contracts, sanctions, Travel Rule data, settlement states and outages are handled. Require dated evidence for every answer: audit and pentest reports, key ceremony records, test results and exit terms.
Video transcript
A stablecoin infrastructure RFP should scope the whole payment flow, ask hard questions, and require dated evidence for every answer.
The OCC's GENIUS Act final rule, for stablecoin issuers under its jurisdiction, takes effect January 18, 2027.
Start with scope: the lifecycle, entities, chains, volumes, customer types and exclusions, plus a versioned architecture diagram.
One question sorts most vendors. Can a single person, credential or compromised system mint, move or freeze funds? The strong answer is a reasoned no, with evidence.
On compliance, ask about licenses, KYC ownership, sanctions screening and Travel Rule data. Counsel should map the answers per corridor.
Define every settlement state, from submitted to reconciled, with a finality signal per chain. Then test fees, duplicate webhooks and rollbacks.
Guardian's Orderly Solana Vault review shows why. The ledger booked the full CCTP V2 burn, but the fee came out of the destination mint, so recorded holdings exceeded real ones. The Medium finding was resolved.
A logo or certificate is only a claim. Ask for the underlying reports under NDA, with period, scope and exceptions, and check the red flags.
Then run procurement in gates: evidence review, architecture workshop, sandbox tests, references and legal review, then an exit plan.
Read the full template. Or ask Guardian about a Digital Asset Assurance Pilot to pressure-test your custody model, issuance path and operator roles before you sign.
Why the RFP Matters Now
The OCC's GENIUS Act final rule, for stablecoin issuers under its jurisdiction, takes effect January 18, 2027. DORA has applied to in-scope EU financial entities since January 17, 2025.[1, 2]
For security questions on any crypto vendor, use our vendor due diligence questionnaire; to run the program after contract, use our stablecoin settlement risk framework.
Scope the Payment Flow
Ask each vendor for a versioned architecture diagram: APIs, signers, contracts, bridges, RPC, screening, ledgers, banks and offramps. Mark who operates each.
To vet each coin before it enters scope, run our stablecoin due diligence checklist. The RFP then covers the infrastructure that moves it.
- Lifecycle: collection, conversion, treasury holding, settlement, refunds, redemptions and fiat payout.
- Entities: each legal entity, license holder and jurisdiction in the flow.
- Assets: fiat currencies, tokens and chains in scope.
- Volumes: expected monthly value, peak throughput and transaction-size ranges.
- Customers: retail, business or institutional, and their locations.
- Exclusions: products, corridors and tokens the vendor will not support.
Security and Custody Questions
One question sorts most vendors: can a single person, credential or compromised system mint, move or freeze funds? The strong answer is a reasoned no, with evidence.
Write in change control: no new token address, chain or contract version reaches production without notice and your approval.
- S1. Describe your HSM, MPC or multisig design, thresholds and signer separation.
- S2. Who witnessed the last key-generation ceremony, and can we see the record?
- S3. How are quorum changes, joiners, leavers, rotation and revocation approved?
- S4. Which transaction policies, dual controls and allowlists does the signing service itself enforce?
- S5. Who holds break-glass access, and when did you last restore from backup?
- S6. List every token contract address, deployment version and native or bridged status, per chain.
- S7. Who holds mint, burn, pause, freeze and upgrade authority, behind what threshold and timelock?
- S8. How do you verify deployed bytecode against the audited source?
- S9. Per bridge or messaging layer: verifier set, rate limits, oracles and finality assumption.
- S10. How are emergency pauses, unpauses and upgrades authorized, monitored and rehearsed?
Compliance Questions
Ask which GENIUS Act controls run today and which wait for the OCC rule to take effect.
In the EU, Regulation (EU) 2023/1113 requires covered PSPs and CASPs to ensure payer and payee, or originator and beneficiary, information is not missing or incomplete.[3]
OFAC recommends a risk-based sanctions program with management commitment, risk assessment, internal controls, testing and training. Screening may use wallet, transaction and IP data.[4]
These duties depend on your entity, customers and token design, so have counsel map the answers per launch corridor.
- C1. Which licenses or registrations do you rely on, held by which entity, for which jurisdictions?
- C2. Who owns KYC and AML for each customer type: you, us or a partner?
- C3. What do you screen: customers, counterparties, wallet addresses, transactions and IP data?
- C4. How are matches escalated, blocked or licensed, and is every decision logged?
- C5. How do you collect, validate and transmit Travel Rule data, and reject or queue transfers missing it?
- C6. Which monitoring scenarios and regulator reports do you run, and who works the cases?
- C7. Where is data stored, for how long, and under which transfer controls?
Operations and SLAs
None of the sources cited here sets an uptime target, confirmation count or SLA credit for stablecoin payments. Set thresholds from your exposure, customer promises and legal cutoffs.
Make settlement states explicit. CPMI-IOSCO guidance for systemically important stablecoin arrangements treats settlement finality and money settlement as principles of their own.[5]
Reject a generic finality label; ask for the signal per chain, as in our blockchain finality comparison. Legal decides which state discharges the customer's obligation.
Acceptance tests should try to break reconciliation: fee-on-transfer tokens, bridge fees, partial delivery, duplicate webhooks, delayed attestations and rollbacks.
Guardian's Orderly Solana Vault review shows the fee case. The ledger booked the full CCTP V2 burn, but the fee came out of the destination mint, so recorded holdings exceeded real ones (Medium, resolved). Reconcile on what arrived.[6]
- Availability per service: API, signing, screening and payout, measured separately.
- Support hours and response times by severity, weekends included.
- Incident notice deadline in hours, and its required content.
- RTO and RPO per service, with the last tested result.
- Handling of reorgs, chain outages, stalled finality and issuer pauses.
- Replay and duplicate protection for instructions and webhooks.
- Reconciliation cadence, fee treatment, failed payments, refunds and disputes.
- Who approves a restart after a pause or incident.
| State | Ask the vendor to define |
|---|---|
| Submitted | Instruction ID, timestamp and accepting system |
| Confirmed | Which chain event counts, and confirmations per chain |
| Finalized | The chain's finality signal, and the action if it stalls |
| Attested | Required issuer or bridge attestation, and its timeout |
| Credited | When the customer balance moves, and if it can reverse |
| Paid out | The payout event, with bank or offramp proof |
| Reconciled | Instruction, fees, bank movement and customer liability match |
Evidence to Require
A logo, certificate or summary is a claim. Ask for the underlying report under NDA, with its period, scope, exceptions and remediation status.
PCI DSS applies only if cardholder data is in scope. Version 4.0.1 added no requirements, so ask for the ROC or AOC, the responsibility matrix and exceptions, not a version number.[7]
| Area | Evidence to require | Red flag |
|---|---|---|
| Independent assurance | Current report, period, scope and exceptions | A bridge letter only, or an expired period |
| Pentests | Scope, findings and retest status for APIs, consoles and signing | Signing services or admin consoles out of scope |
| Smart contracts | Audit and fix-review reports with commit hashes | Audited commit does not match deployed bytecode |
| Threat model | A dated model of every path funds can take | None, or older than the current architecture |
| Keys | Signer inventory, ceremony records and sample approval logs | One person can approve a transfer alone |
| Recovery | Incident, backup-restore and continuity exercise results | Never tested, or tested without key recovery |
| Dependencies | Subcontractor list and service-dependency map | Unnamed subprocessors, or no change notice |
| Remediation | A dated register of open findings and owners | Open High findings with no fix date |
The RFP Template
Copy these sections, keeping the question IDs so answers line up across vendors.
DORA sets key contractual provisions for in-scope EU entities. Its technical standard on the policy for contractual arrangements covering ICT services that support critical or important functions addresses due diligence, audit and information access, subcontracting, exit and termination.[2, 8, 9]
The financial entity still maps those terms into its own contract. Our DORA Article 30 checklist lists each clause.
Score security, custody, compliance, operations, resilience, integration, evidence quality and total cost. Set and approve your weights before responses arrive.
- 1. Scope: objective, entities, corridors and the scope list above.
- 2. Architecture: versioned diagram and component ownership.
- 3. Security and custody: S1 to S10, plus change control.
- 4. Compliance: C1 to C7.
- 5. Operations: settlement states, SLA schedule and acceptance tests.
- 6. Evidence: the schedule above, dated and under NDA.
- 7. Contract: audit and regulator access, notice duties, subcontractors, data return, transition and termination.
- 8. Response: the matrix below, with pricing in a separate file.
- 9. Process: deadlines, a written question window, then gates: evidence review, architecture workshop, sandbox tests, references, legal review and exit plan.
| Matrix column | What goes in it |
|---|---|
| Requirement ID | The question ID, such as S4 or C5 |
| Answer | A direct answer, not a product description |
| Evidence ID and date | The document reference and the period it covers |
| Scope and exclusions | What the answer and evidence do not cover |
| Customer responsibility | What you must operate or configure yourself |
| Commitment | Whether the answer becomes a contract term |
| Residual risk and effort | Buyer's score after review |
Pressure-Test the Design Before You Sign
In a Digital Asset Assurance Pilot, Guardian assesses your custody model, issuance path and operator roles. Add a smart contract audit and offchain pentests of the signing services your program relies on.
Frequently Asked Questions
Does the OCC's GENIUS Act rule cover AML and sanctions?
No. The OCC left AML and sanctions rules to separate rulemaking. FinCEN and OFAC proposed theirs in April 2026, the OCC in June. FinCEN sent its final rule for White House review on November 18; none was final by November 21. Ask vendors which proposed sanctions program controls they run.[1, 10, 11, 12, 13, 14, 15]
What if a counterparty keeps sending incomplete Travel Rule data?
In Ireland, providers must notify the Central Bank of a repeatedly failing provider without undue delay, and within three months of identifying it. Ask vendors how they detect repeat failures and draft that notice.[3]
Related reading
- smart contract audit rfp template
- third party risk management digital assets
- stablecoin cross border payments security
- accept stablecoin payments
Sources
- Office of the Comptroller of the Currency: GENIUS Act Regulations: Final Rule
- European Securities and Markets Authority: Digital Operational Resilience Act (DORA)
- Central Bank of Ireland: Recast Funds Transfer Regulation notification requirements
- U.S. Department of the Treasury, OFAC: Sanctions Compliance Guidance for the Virtual Currency Industry
- BIS, CPMI and IOSCO: Application of the Principles for Financial Market Infrastructures to stablecoin arrangements
- Guardian Security public audit portfolio: Orderly Solana Vault: M-01, CCTPv2 Rebalance Credits Ignore Bridge Fees
- PCI Security Standards Council: Just Published: PCI DSS v4.0.1
- European Commission: Commission Delegated Regulation on DORA ICT third-party contractual policies
- EUR-Lex, Publications Office of the European Union: Commission Delegated Regulation (EU) 2024/1773
- Office of the Comptroller of the Currency: OCC Bulletin 2026-28: GENIUS Act AML/CFT and Sanctions Compliance NPRM
- Office of the Comptroller of the Currency: OCC Proposed Issuances - 2026
- U.S. Department of the Treasury, FinCEN and OFAC: 91 FR 18582: Permitted Payment Stablecoin Issuer AML/CFT and Sanctions Compliance Requirements
- Office of Foreign Assets Control: OFAC Federal Register Notices index
- Reginfo.gov, Office of Information and Regulatory Affairs: Pending EO 12866 Regulatory Review, RIN 1506-AB73
- Reginfo.gov, Office of Information and Regulatory Affairs: Executive Order Submissions Under Review
- Federal Reserve Board, FDIC and OCC: Agencies issue joint statement on risk-management considerations for crypto-asset safekeeping
- National Institute of Standards and Technology: SP 800-57 Part 1 Rev. 5, Recommendation for Key Management
- Guardian Security: Digital Asset Assurance Pilot
- Office of the Comptroller of the Currency: Permitted Payment Stablecoin Issuer AML/CFT and Sanctions Compliance Risk Management
- Office of the Comptroller of the Currency: OCC Final Issuances - 2026
- Circle: CCTP fees