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

# Going Live

> Production activation checklist and go-live process

After sandbox certification, you transition to production with a controlled ramp-up and an enhanced monitoring period. This page covers the checklist, ramp-up schedule, and what to expect in your first 30 days.

<Info>
  For context on the full onboarding journey that leads up to this stage, see [Onboarding](/partners/onboarding-process).
</Info>

## Go-live checklist

All of the following must be complete before your production API key is issued:

| Item                                                                                       | Owner            |
| ------------------------------------------------------------------------------------------ | ---------------- |
| All compliance gates cleared and documented in Partner File                                | Ratio compliance |
| All certification test cases passed in sandbox                                             | Partner + Ratio  |
| Production API key and Partner ID issued; sandbox keys deactivated                         | Ratio            |
| Commercial agreement (MOU or MSA) fully executed                                           | Both parties     |
| Escalation contacts exchanged — partner ops and Ratio ops                                  | Both parties     |
| Volume limits set at initial conservative levels (ramp-up schedule agreed)                 | Ratio            |
| Admin configuration reviewed and locked (corridors, fee tiers, LP class, wallet whitelist) | Ratio            |

<Warning>
  Your sandbox API key is deactivated when your production key is issued. Ensure your integration is switched to the production base URL and production credentials before going live.
</Warning>

## Ramp-up schedule

All new partners start with conservative volume limits that increase based on successful operation. Volume cap increases are not automatic — each step requires review and approval by the Ratio operations team.

| Period   | Volume cap           | Review cadence   | Auto-pause trigger        |
| -------- | -------------------- | ---------------- | ------------------------- |
| Week 1–2 | 25% of agreed limit  | Daily monitoring | Error rate > 5%           |
| Week 3–4 | 50% of agreed limit  | Weekly review    | Anomaly detected          |
| Month 2  | 75% of agreed limit  | Bi-weekly review | Standard ops process      |
| Month 3+ | 100% of agreed limit | Monthly review   | Quarterly business review |

## Hypercare period (first 30 days)

The first 30 days post-go-live include enhanced monitoring and support:

* **Daily reconciliation review** by the Ratio operations team
* **Weekly performance call** with your technical and operations teams
* **Real-time alerting** on SLA breaches, settlement delays, or anomalous transaction patterns
* **Dedicated account manager** as your single point of contact for all issues

## Ongoing monitoring

After the hypercare period, you move to standard ongoing monitoring.

<AccordionGroup>
  <Accordion title="Transaction monitoring">
    Real-time alerts for unusual patterns including volume spikes, repeated failures, and spread anomalies.
  </Accordion>

  <Accordion title="KYB refresh">
    Annual re-verification for Standard-tier partners; semi-annual for Enhanced and Strategic partners.
  </Accordion>

  <Accordion title="Licence monitoring">
    Automated alerts for licence expiry or regulatory action that affects your partner status.
  </Accordion>

  <Accordion title="Quarterly business review (QBR)">
    Covers volume trends, error rates, commercial performance, corridor expansion discussion, and annual fee tier review.
  </Accordion>
</AccordionGroup>

## Suspension and offboarding

Partners can be suspended if compliance standards are not maintained, SLA targets are consistently missed, or regulatory requirements change. Suspended partners retain their configuration but cannot execute new transactions.

Offboarding follows a structured process: open positions are settled, API keys are revoked, LP deposits are withdrawn (subject to cooldown), and the partner's configuration is archived.