Overview
Onramps transition through different statuses based on their lifecycle stage. Understanding these statuses helps you handle different scenarios correctly.Status Values
| Status | Description | Can Receive Deposits? | Terminal? |
|---|---|---|---|
ACTIVE | Onramp is operational | ✅ Yes (if within TTL) | ❌ No |
EXPIRED | TTL elapsed (throwaway only) | ❌ No (deposits flagged) | ✅ Yes |
DISABLED | Manually disabled by operations | ❌ No | ✅ Yes |
FLAGGED | Risk 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
- Immediately upon creation
- After resolving
FLAGGEDstate
EXPIRED
Throwaway onramps only- 25-minute TTL has elapsed
- New deposits are
FLAGGED(require manual review) - Onramp cannot be reactivated
- Automatically when
expires_attimestamp 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)
- 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)
- Unusual usage patterns
- Risk engine flagged the onramp
- Multiple failed deposits
- Compliance red flags
Handling Different Statuses
- ACTIVE
- EXPIRED
- DISABLED
- FLAGGED
Action: Normal operation
- Accept deposits
- Monitor for status changes via webhooks
- Show countdown timer (throwaway onramps)