> ## 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.

# Partner Types

> Understanding Ratio's partner ecosystem

Ratio operates as B2B middleware — it does not serve retail end users directly. Instead, it provides FX execution and settlement infrastructure to regulated partners who integrate the SOL into their own products and services.

Six distinct partner types form the ecosystem. Each has different integration requirements, compliance obligations, and commercial structures. A single entity can also hold multiple roles.

## Partner types

<CardGroup cols={2}>
  <Card title="On-Ramp" icon="arrow-right-to-bracket">
    Converts fiat to stablecoin and deposits into the SOL. On-Ramp partners handle end-user KYC/KYB and provide the "money in" side of the cross-border flow.

    **Examples:** PSPs, banks, e-wallets, crypto exchanges with fiat gateways.

    **Integration:** SOL Communication Layer + FX Engine API + webhook receiver + KYC data relay + fiat rail mapping.
  </Card>

  <Card title="Off-Ramp" icon="arrow-right-from-bracket">
    Receives stablecoins from the FX Engine and converts them to local fiat for distribution via domestic rails (bank transfer, e-wallet, card). Off-Ramp partners handle "money out" in each destination market.

    **Examples:** Local PSPs, bank partners, payout providers.

    **Integration:** SOL Communication Layer + FX Engine API + webhook receiver + fiat rail mapping.
  </Card>

  <Card title="Stablecoin Issuer" icon="coins">
    Provides deep native-currency liquidity through mint and redeem capabilities. Stablecoin issuers are typically the anchor liquidity providers for their respective corridors and serve as Class A LPs.

    **Examples:** IDRX (Indonesian Rupiah stablecoin issuer), MYRC issuer, Tether (USDT).

    **Integration:** Mint/redeem API + LP deposit flow + proof of reserve integration (if applicable).
  </Card>

  <Card title="Liquidity Provider" icon="building-columns">
    Deposits stablecoins into Ratio's liquidity pools and earns a share of FX swap fees. Institutional LPs provide the capital depth that enables reliable execution at institutional scale.

    **Examples:** Institutional funds, DeFi yield funds, treasury desks, corporate treasury.

    **Integration:** Wallet whitelisting + LP class configuration + deposit routing verification.
  </Card>

  <Card title="RFQ Counterparty" icon="arrows-rotate">
    Provides external liquidity quotes when Ratio's internal pools need rebalancing. RFQ counterparties are professional market makers who respond to automated quote requests from the rebalancing engine.

    **Examples:** OTC desks, institutional market makers.

    **Integration:** RFQ API + quote-response SLA + execution settlement.
  </Card>

  <Card title="Distribution Partner" icon="network-wired">
    Sources end-user transaction volume by integrating the SOL API into their own product. Distribution partners may operate under their own brand (white-label) or refer users to Ratio-powered services.

    **Examples:** Remittance apps, neobanks, e-wallets, payroll platforms.

    **Integration:** Full FX Engine API + webhook receiver + optional white-label UI.
  </Card>
</CardGroup>

## Integration requirements by type

<Tabs>
  <Tab title="On-Ramp">
    | Requirement             | Details  |
    | ----------------------- | -------- |
    | SOL Communication Layer | Required |
    | FX Engine API           | Required |
    | Webhook receiver        | Required |
    | KYC data relay          | Required |
    | Fiat rail mapping       | Required |
  </Tab>

  <Tab title="Off-Ramp">
    | Requirement             | Details  |
    | ----------------------- | -------- |
    | SOL Communication Layer | Required |
    | FX Engine API           | Required |
    | Webhook receiver        | Required |
    | Fiat rail mapping       | Required |
  </Tab>

  <Tab title="Stablecoin Issuer">
    | Requirement                  | Details       |
    | ---------------------------- | ------------- |
    | Mint/redeem API              | Required      |
    | LP deposit flow              | Required      |
    | Proof of reserve integration | If applicable |
  </Tab>

  <Tab title="Liquidity Provider">
    | Requirement                  | Details                                    |
    | ---------------------------- | ------------------------------------------ |
    | Wallet whitelisting          | Required — Kaia address must be registered |
    | LP class configuration       | Required — Class A or Class B              |
    | Deposit routing verification | Required                                   |
  </Tab>

  <Tab title="RFQ Counterparty">
    | Requirement          | Details                                        |
    | -------------------- | ---------------------------------------------- |
    | RFQ API              | Required                                       |
    | Quote-response SLA   | Required — demonstrated during sandbox testing |
    | Execution settlement | Required                                       |
  </Tab>

  <Tab title="Distribution Partner">
    | Requirement        | Details  |
    | ------------------ | -------- |
    | Full FX Engine API | Required |
    | Webhook receiver   | Required |
    | White-label UI     | Optional |
  </Tab>
</Tabs>

## Multi-role partners

A single entity can serve multiple roles. For example, IDRX is both a stablecoin issuer and a Class A LP, while a crypto exchange might be an On-Ramp partner and an LP simultaneously.

<Info>
  Multi-role partners go through a single compliance review with parallel technical and commercial tracks. They receive a unified Partner ID with role-specific sub-configurations — eliminating redundant KYB checks while maintaining clean audit separation per role.
</Info>