Skip to main content

Overview

Onramps transition through different statuses based on their lifecycle stage. Understanding these statuses helps you handle different scenarios correctly.

Status Values

StatusDescriptionCan Receive Deposits?Terminal?
ACTIVEOnramp is operational✅ Yes (if within TTL)❌ No
EXPIREDTTL elapsed (throwaway only)❌ No (deposits flagged)✅ Yes
DISABLEDManually disabled by operations❌ No✅ Yes
FLAGGEDRisk or compliance review triggered❌ No✅ Yes

Status Lifecycle

ACTIVE

Initial state for all onramps
  • Onramp can receive deposits (within TTL for throwaway)
  • FX and settlement proceed normally
  • Most common state
When set:
  • Immediately upon creation
  • After resolving FLAGGED state

EXPIRED

Throwaway onramps only
  • 25-minute TTL has elapsed
  • New deposits are FLAGGED (require manual review)
  • Onramp cannot be reactivated
When set:
  • Automatically when expires_at timestamp is reached
Permanent onramps never transition to EXPIRED state because they have no TTL.

DISABLED

Manually disabled by merchant or operations
  • All deposits are rejected or flagged
  • Can be set at any time by authorized personnel
  • Typically permanent (not reactivated)
Common reasons:
  • Merchant requested to disable
  • Suspicious activity detected
  • User account closed
  • Compliance requirement

FLAGGED

Held for risk or compliance review
  • Deposits may be held or rejected
  • Requires manual operations review
  • Can be resolved (→ ACTIVE) or permanently disabled (→ DISABLED)
Common triggers:
  • Unusual usage patterns
  • Risk engine flagged the onramp
  • Multiple failed deposits
  • Compliance red flags

Handling Different Statuses

Action: Normal operation
  • Accept deposits
  • Monitor for status changes via webhooks
  • Show countdown timer (throwaway onramps)

Next Steps