Deactivate Customer
Customers
Deactivate Customer
Deactivates a customer account and all associated fiat accounts. This action sets the customer and their deposit accounts to inactive. External fiat accounts are transitioned to deactivated as well.
POST
Deactivate Customer
Before you deactivate: no pending operations
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 becomesREFUNDED). An order still inPENDING(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.
What happens when a customer is deactivated
Deactivating a customer setsisActive to false on the customer record. This has the following cascading effects:
- Customer detail (
PUT /customers/{customerId}/): still works and returnsisActive: falsein the response. - KYC, fiat account creation, accept terms, and OTP (
/kyc/,/kyb/,/fiatAccount/,/acceptTerms/,/otp/): return404. - On-ramp and off-ramp orders and sessions: stop appearing in list endpoints; detail endpoints (
GET /onramp/{orderId}/,GET /onrampSession/{sessionId}/, etc.) return404. - Fiat accounts: stop appearing in list endpoints; detail and confirm endpoints return
404. - KYC submissions list: the customer’s submissions are excluded from results.
Webhook notification
When a customer is deactivated, Ripio automatically sends anACCOUNT.CLOSED webhook event to your configured webhook URL. See Account Webhook Events for the payload structure.Authorizations
Access token obtained via /oauth2/token/. Use as Authorization: Bearer <access_token>.
Path Parameters
Unique identifier for the customer.
Response
Customer deactivated successfully.
The response is of type object.