Skip to main content

Technical Integration

Purpose: Connect the partner's systems to Ratio's SOL infrastructure, configure partner-specific parameters, and establish secure communication channels.

1. Credential Issuance

Upon compliance clearance, the Ratio admin provisions the partner in the system:

CredentialFormatScopeRotation Policy
Partner ID (X-Partner-ID)UUIDAll API requests; fee routing and audit trailPermanent (revoke on offboarding)
API Key (Bearer Token)256-bit randomAuthentication for all API endpoints90-day rotation; emergency revoke capability
Sandbox API Key256-bit randomTestnet access only; no real fundsNo rotation required
Webhook SecretHMAC-SHA256 keyPartner verifies callback authenticity90-day rotation aligned with API key
Wallet WhitelistKaia address(es)LP deposits and withdrawal destinationsAdd/remove via admin; requires 24h cooling

2. Partner Configuration (Admin-Set)

All partner-specific parameters are stored off-chain in the Admin Config Store and are readable by the routing engine and FX engine. These are configured by Ratio admin during onboarding, not by the partner directly.

ParameterApplies ToExampleSet By
Corridors EnabledAll[USD-IDR, USD-SGD]Admin (per licence map)
Volume Limit (Daily)All$500K per corridorAdmin (compliance-derived)
Volume Limit (Monthly)All$10M aggregateAdmin (commercial terms)
Fee Tier MultiplierLP0.3× (issuer), 1.0× (retail)Admin (per Liquidity Onboarding config)
Liquidity Intent ClassLPClass A (FX-Only)Admin (per partner choice)
Deposit AcceptanceLPEnabled / DisabledAdmin
Webhook URLOn/Off-Ramphttps://partner.com/ratio/callbackPartner (verified by Ratio)
Settlement CurrencyOff-RampIDRX, MYRCAdmin (per corridor)
Fee Tier OverrideLP, On/Off-RampCustom variable bips and spread bps per corridor per size tier. NULL values use standard tier defaults.Admin (per Fee Tiers)
RFQ Access TierRFQTier 1 (auto-eligible)Admin

3. Integration Tracks by Partner Type

On-Ramp / Off-Ramp Partners

  1. SOL Communication Layer integration — implement standardised messaging templates (SWIFT-style) for deposit confirmations, beneficiary validation, transaction status, and rollback signals.
  2. FX Engine API integration — implement GET /v1/quote (indicative pricing), POST /v1/quote (firm quote), and POST /v1/execute (trade execution) endpoints.
  3. Webhook receiver setup — implement callback endpoint for trade confirmations, settlement status, and error notifications.
  4. KYC/KYB data relay — if the partner handles end-user KYC, configure data-sharing templates for Travel Rule compliance.
  5. Fiat rail mapping — map local fiat rails (bank transfer, e-wallet, card) to standardised Ratio data templates (bank info, SWIFT/IBAN, beneficiary details).

Stablecoin Issuer Partners

  1. Mint/Redeem API integration — configure mint and redeem endpoints for on-demand liquidity provisioning (used by Smart Rebalancing escalation for issuer-heavy pools).
  2. Reserve Pool deposit flow — as Class A LP, verify deposit routing is 100% Reserve Pool with kXXX-fx token issuance.
  3. Proof of Reserve (POR) integration — if issuer publishes POR data, configure feed for Ratio's internal validation checks.
  4. Emergency minting protocol — establish on-demand minting path for deficit recovery scenarios (Smart Rebalancing escalation).

LP Partners (Institutional / Retail Aggregators)

  1. Wallet whitelisting — register Kaia wallet address(es) for deposits and withdrawals.
  2. LP class and fee tier configuration — admin sets Class A or B, fee multiplier, per Liquidity Onboarding architecture.
  3. Deposit routing verification — test deposit flow through routing engine to confirm correct pool allocation.
  4. kToken receipt verification — confirm correct kXXX-fx or kXXX-full tokens are received in partner wallet.

RFQ Counterparties

  1. RFQ API integration — implement quote request/response endpoints for Liquidity Hub's rebalancing flow.
  2. Settlement flow — configure on-chain settlement paths for successful RFQ executions.
  3. Latency & reliability SLA — agree on maximum quote response time and uptime requirements.
  4. Credit/netting terms configuration — if bilateral netting applies, configure netting window and settlement schedule.

Distribution Partners

  1. SOL API / SDK integration — full API access for quote, execute, and status endpoints; or SDK wrapper for simplified integration.
  2. White-label configuration (if applicable) — custom branding, fee passthrough rules, and end-user facing components.
  3. Webhook and notification setup — real-time transaction status callbacks for their end-user experience.

4. Communication Layer Setup

  • Message format alignment: partner's data mapped to Ratio's ISO 20022-inspired templates for bank info, SWIFT details, beneficiary data, and transaction confirmations.
  • Event subscription: partner subscribes to relevant event streams (transaction status, settlement confirmations, balance notifications).
  • Encryption: all API communications over TLS 1.3; webhook payloads signed with partner-specific HMAC keys.

Estimated Duration: 2–6 weeks (depending on partner technical maturity)