Partner Onboarding Process
1. Executive Summary
This section defines the end-to-end Partner Onboarding Process for Ratio FX's Stablecoin Orchestration Layer (SOL). It establishes a standardised, repeatable framework for evaluating, integrating, and activating the diverse partner types that form the backbone of the protocol's multi-sided ecosystem.
Ratio FX operates as regulated middleware connecting stablecoins, banks, and e-wallets across fragmented Asian markets. Unlike permissionless DeFi protocols where participants interact directly with smart contracts, Ratio's institutional positioning requires a structured onboarding process that balances speed-to-market with compliance rigour, technical integration quality, and commercial alignment.
Key Design Principles
- Partner-type-aware: Different partner types (On-Ramp, Off-Ramp, Stablecoin Issuer, Liquidity Provider, RFQ Counterparty, Distribution Partner) follow tailored onboarding tracks with shared compliance gates.
- Compliance-first: KYB, AML/CFT screening, licensing verification, and sanctions checks are mandatory gates before any technical integration begins.
- Phased activation: Partners move through Commercial → Compliance → Technical → Testing → Production stages with clear gate criteria at each transition.
- Admin-configurable: Partner-specific parameters (fee tiers, corridor access, volume limits, LP class) are set by Ratio admin during onboarding and can be updated post-activation without on-chain transactions.
- Aligned with MOU milestones: The API/SDK integration track (Phase 2 onward) and Communication Channel integration (Phase 3 onward) align with the DODO development roadmap.
Dependencies
| Priority | Component | Dependency |
|---|---|---|
| FX Engine | FX Engine & API | Partner API keys, Bearer token auth, X-Partner-ID headers issued during onboarding |
| LP Withdrawals | LP Withdrawal | LP partner onboarding sets cooldown schedule and withdrawal tier thresholds |
| Liquidity Onboarding | Liquidity Onboarding | LP class selection (A/B), fee tier configuration, deposit routing rules set during onboarding |
| MOU | API/SDK (Phase 2) | Partner sandbox and production API access requires completed onboarding |
2. Partner Taxonomy
Ratio's ecosystem involves six distinct partner types, each with different integration requirements, compliance obligations, and commercial structures. A single entity may hold multiple partner roles.
| Partner Type | Role in SOL | Examples | Onboarding Track |
|---|---|---|---|
| On-Ramp Partner | Converts fiat to stablecoin; provides KYC/KYB for end-users; deposits stablecoins into FX Engine | EP, Pavio, Bitazza, BitoPro, APAC Bank | Full (Compliance + Technical + Commercial) |
| Off-Ramp Partner | Receives stablecoins from FX Engine; converts to local fiat; distributes via local rails | DurianPay, local PSPs, bank partners | Full (Compliance + Technical + Commercial) |
| Stablecoin Issuer | Provides deep native-currency liquidity; mint/redeem capability; typically Class A LP | IDRX, MYRC issuer, Tether (USDT) | Strategic (Enhanced DD + LP Config) |
| Liquidity Provider (Institutional) | Deposits stablecoins into Reserve/Yield pools; earns FX fees and/or yield | Institutional funds, DeFi yield funds, treasury desks | LP Track (Compliance + LP Class Config) |
| RFQ Counterparty | Provides external liquidity quotes for Phase 2 rebalancing; OTC execution partner | Binance OTC, Wintermute, institutional MMs | Counterparty Track (Enhanced DD + API) |
| Distribution Partner | Sources end-user transaction volume; integrates SOL API into own product; white-label or referral | Remittance apps, neobanks, e-wallets, payroll platforms | Full (Compliance + Technical + Commercial) |
Multi-Role Partners
When a single entity serves multiple roles (e.g., IDRX as both Stablecoin Issuer and Class A LP, or BitoPro as CEX On-Ramp and potential LP), onboarding proceeds through a single compliance review with parallel technical and commercial tracks. The partner receives a unified Partner ID (X-Partner-ID) with role-specific sub-configurations. This eliminates redundant KYB checks while maintaining clean audit separation per role.
Minimum Volume Thresholds (Phase 1 Launch)
| Partner Type | Minimum Threshold | Rationale |
|---|---|---|
| On-Ramp / Off-Ramp | $100K monthly volume | Sufficient transaction density for meaningful SLA measurement and operational efficiency |
| Stablecoin Issuer | $500K TVL commitment | Strategic liquidity floor for corridor viability |
| Liquidity Provider | $50K minimum deposit | Operational efficiency threshold for pool management |
| RFQ Counterparty | RFQ response within 60s | Rebalancing cycle timing requirement for Phase 2 execution |
| Distribution Partner | $100K monthly volume | Ensures integration investment is commercially justified |