Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.ripio.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Introduction to Account Webhooks

Ripio uses webhooks to notify your application when a customer account changes state. By subscribing to these events, you can react in real time to account lifecycle transitions — for example, updating your own records or notifying the end user when their account is closed. Account events are triggered when a customer is deactivated, either from the Ripio partner dashboard or via the Deactivate Customer endpoint. They are sent as POST requests to your configured webhook endpoint. Remember to validate the signature of each incoming webhook as described in the Webhooks Introduction.

​
Event Payload Structure

Each Account event notification contains a JSON-formatted payload with the following structure: 
{
  "eventType": "ACCOUNT.CLOSED",
  "issueDatetime": "2026-05-19T14:30:00.000Z",
  "account": {
    "customerId": "7142b065-79c4-4f48-9e33-11b23bg689e2",
    "isActive": false
  }
}
  • eventType (String): The specific type of Account event that occurred, following the format ACCOUNT.<STATUS>.
  • issueDatetime (String): UTC timestamp indicating when the event was triggered.
  • account (Object): An object containing details of the customer account associated with the event.

​
Payload Fields

The account object contains the following fields:
  • customerId (String, UUID): Your partner-facing customer ID for the affected customer.
  • isActive (Boolean): The new active state of the customer. Always false for ACCOUNT.CLOSED events.

​
Account Event Types

The following event types are available for account lifecycle changes:

​
ACCOUNT.CLOSED

  • Description: Sent when a customer account has been deactivated. After this event, all operations on the customer’s resources (KYC submissions, fiat accounts, on-ramp and off-ramp sessions and orders) will return 404. The account deactivation is irreversible — there is no reactivation endpoint.