Skip to main content

Partner Offboarding & Suspension

1. Suspension Triggers​

  • Licence revocation or expiry in any active corridor jurisdiction.
  • Failed sanctions screening re-check (entity or UBO).
  • Repeated API abuse (rate limit violations, malformed requests exceeding threshold).
  • Suspicious transaction patterns flagged by monitoring system.
  • Material breach of MOU/MSA commercial terms.

2. Suspension Process​

  • Immediate: API key suspended (returns 403); new quote requests rejected; in-flight transactions allowed to settle.
  • Within 24 hours: Partner notified with reason and remediation path.
  • Within 7 days: If unresolved, escalate to full offboarding review.

3. Voluntary Offboarding​

  1. Partner provides 30-day written notice.
  2. Ratio freezes new transaction routing to the partner.
  3. Outstanding settlements completed within the standard settlement window.
  4. LP positions: withdrawal initiated per LP Withdrawal queue rules; cooldown periods still apply.
  5. API keys permanently revoked upon final settlement.
  6. Corridor routing updated to redirect volume to alternate partners.

4. Involuntary Offboarding (Compliance-Triggered)​

  • Immediate suspension of all transaction routing upon compliance flag.
  • Partner's funds secured in escrow pending investigation.
  • Regulatory notification as required by jurisdiction.
  • Orderly liquidation of LP positions once investigation concludes.

5. Data Retention​

Partner transaction records retained per regulatory requirements (minimum 5 years post-offboarding). API access logs retained for audit trail. KYB documentation archived per jurisdiction-specific retention rules.