Skip to main content
POST
Deactivate Customer

Before you deactivate: no pending operations

A customer cannot be deactivated while they have operations still in progress. The request returns 409 Conflict with the error code 20063 (CustomerHasPendingOperationsException), and nothing is changed.
An operation is considered pending when:
  • An on-ramp or off-ramp order is being processed (PROCESSING) or awaiting a refund (CANCELLED — not final until it becomes REFUNDED). An order still in PENDING (created but no deposit received yet) does not block.
  • A fiat payout or refund is still being processed — for example, an off-ramp withdrawal or a refund that has not settled yet.
Wait until those in-progress operations finish before retrying. This guard exists because a deactivated customer’s operations can no longer be processed, so deactivating with work still in flight would leave those orders or refunds permanently unresolved.

What happens when a customer is deactivated

Deactivating a customer sets isActive to false on the customer record. This has the following cascading effects:
  • Customer detail (PUT /customers/{customerId}/): still works and returns isActive: false in the response.
  • KYC, fiat account creation, accept terms, and OTP (/kyc/, /kyb/, /fiatAccount/, /acceptTerms/, /otp/): return 404.
  • On-ramp and off-ramp orders and sessions: stop appearing in list endpoints; detail endpoints (GET /onramp/{orderId}/, GET /onrampSession/{sessionId}/, etc.) return 404.
  • Fiat accounts: stop appearing in list endpoints; detail and confirm endpoints return 404.
  • KYC submissions list: the customer’s submissions are excluded from results.
Deactivation is irreversible — there is no reactivation endpoint.

Webhook notification

When a customer is deactivated, Ripio automatically sends an ACCOUNT.CLOSED webhook event to your configured webhook URL. See Account Webhook Events for the payload structure.

Authorizations

Authorization
string
header
required

Access token obtained via /oauth2/token/. Use as Authorization: Bearer <access_token>.

Path Parameters

customerId
string<uuid>
required

Unique identifier for the customer.

Response

Customer deactivated successfully.

The response is of type object.