> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ratiofx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Onboarding

> From application to production activation

Every partner follows a structured onboarding process that balances speed-to-market with compliance rigour, technical integration quality, and commercial alignment. The process has five stages with clear gate criteria at each transition.

<Steps>
  <Step title="Commercial evaluation">
    The initial stage establishes commercial alignment and partnership fit.

    **Activities:**

    * Partnership application and initial screening
    * Commercial terms discussion (corridor access, volume expectations, fee structure)
    * MOU or MSA negotiation and execution
    * Partner type classification and onboarding track assignment

    **Gate criteria:** Signed commercial agreement and confirmed partner type.
  </Step>

  <Step title="Compliance and KYB">
    All partners undergo Know Your Business (KYB) verification before any technical integration begins. The depth of due diligence scales with the partner's risk profile.

    **Activities:**

    * Documentation submission (incorporation, UBO disclosure, director verification)
    * AML/CFT policy review
    * Sanctions screening (OFAC, UN, EU, and local lists)
    * Licensing verification per jurisdiction and corridor
    * Risk tier assignment (Standard, Enhanced, or Strategic)

    <Note>
      Enhanced and Strategic partners undergo additional checks including financial statement review, source of funds verification, blockchain address screening, and (for issuers) reserve audits.
    </Note>

    **Gate criteria:** All mandatory compliance checks passed for the assigned risk tier.
  </Step>

  <Step title="Technical integration">
    Once compliance is cleared, you receive API credentials and begin technical integration against the sandbox environment.

    **Credentials issued:**

    | Credential               | Description                                 |
    | ------------------------ | ------------------------------------------- |
    | Partner ID               | UUID used in all API requests               |
    | API key                  | Bearer token for authentication             |
    | Sandbox API key          | Separate key for testnet access             |
    | Webhook secret           | Used to verify callback signatures          |
    | Wallet whitelist entries | For LP partners — Kaia address registration |

    **Activities:**

    * API integration against the sandbox environment
    * Webhook receiver setup and signature verification
    * Partner-specific configuration by Ratio admin (corridors, fee tiers, volume limits)
    * Integration track varies by partner type — On-Ramp, LP, Issuer, and RFQ each have a tailored checklist

    **Gate criteria:** API integration functional in sandbox; all partner-specific configuration applied.
  </Step>

  <Step title="Sandbox testing and certification">
    You must pass a set of certification test cases before production activation. Tests are partner-type-specific.

    | Test category      | Description                                                                     |
    | ------------------ | ------------------------------------------------------------------------------- |
    | Happy path         | End-to-end: quote → execute → settle → confirm for each enabled corridor        |
    | Quote expiry       | Attempt execution on expired quote; verify rejection and re-quote flow          |
    | State scenarios    | Test behaviour under different system states                                    |
    | Volume limits      | Exceed daily/monthly limits; verify graceful rejection                          |
    | Webhook delivery   | Verify callbacks received, HMAC signature validated, idempotent handling        |
    | Auth failure       | Invalid API key, expired token, wrong Partner ID — verify clean error responses |
    | Error and rollback | Simulate settlement failure; verify error handling                              |
    | Reconciliation     | Daily reconciliation of stablecoin-in vs. fiat-out; zero discrepancy target     |

    LP and issuer partners have additional tests for deposit routing, kToken issuance, and withdrawal cooldown verification. RFQ counterparties have quote-response SLA tests.

    **Estimated duration:** 1–3 weeks.

    **Gate criteria:** All mandatory test cases passed; SLA targets demonstrated.
  </Step>

  <Step title="Production activation">
    You go live with a controlled ramp-up and enhanced monitoring period.

    **Go-live checklist:**

    * All compliance gates cleared and documented
    * All certification test cases passed
    * Production API key issued; sandbox key deactivated
    * Commercial agreement fully executed
    * Escalation contacts exchanged for incident response
    * Volume limits set at initial conservative levels

    **Ramp-up schedule:**

    | Period   | Volume cap           | Review cadence   |
    | -------- | -------------------- | ---------------- |
    | Week 1–2 | 25% of agreed limit  | Daily monitoring |
    | Week 3–4 | 50% of agreed limit  | Weekly review    |
    | Month 2  | 75% of agreed limit  | Bi-weekly review |
    | Month 3+ | 100% of agreed limit | Monthly review   |

    <Note>
      The first 30 days post-go-live include a hypercare period with daily reconciliation review, weekly performance calls, real-time alerting on SLA breaches, and a dedicated account manager.
    </Note>
  </Step>
</Steps>