Skip to main content
POST
/
api
/
v1
/
customers
/
{customerId}
/
deactivate
/
Deactivate Customer
curl --request POST \
  --url https://skala-sandbox.ripio.com/api/v1/customers/{customerId}/deactivate/ \
  --header 'Authorization: Bearer <token>'
{}

​
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.