Overview
The Partner integrating with Ripio via API shall be responsible for ensuring that their customers explicitly accept Ripio’s Terms and Conditions (T&C) prior to performing any on-ramp or off-ramp operations.How it works
When T&C acceptance is required, attempting to create an on-ramp or off-ramp session without a prior acceptance will return an error:Checking acceptance status
Before showing the T&C screen to a customer, check whether they have already accepted the currently active Terms and Conditions. This avoids presenting the acceptance screen unnecessarily to returning customers.accepted is true, proceed directly with on-ramp or off-ramp operations. When accepted is false, display the T&C document (via url) and record the customer’s acceptance before continuing.
When no active Terms and Conditions exist for the account’s country,
accepted is always true and
the term fields (termsId, version, url) are null. The customer is not blocked and no
acceptance is required.Acceptance Flow
1. Get the active Terms and Conditions
Retrieve the current active T&C for your account’s country. This returns atermsId that you’ll need in the next step.
url) to the customer and collect their acceptance.
2. Record the customer’s acceptance
Once the customer has accepted, send the acceptance record to the API including thetermsId, the customer’s IP address, and optionally their user agent.
201 Created):