Skip to main content
When you integrate via the API, every request reaches Ripio from your servers. Ripio does not see the end user’s own network or device, so it cannot tell two customers on the same phone apart, or notice that an operation comes from somewhere unusual for that customer. Three optional headers fill that gap. You send them with the requests your customers trigger, and Ripio records them against the customer for traceability and fraud prevention.
The headers are optional. A request without them works exactly the same: nothing is rejected, and nothing about the customer’s experience changes. Sending them is recommended, because it gives Ripio’s risk checks the information they would otherwise not have.

Send the end user’s values, never your server’s

This is the one thing to get right. The values describe the person operating, so they have to come from their device:
  1. Capture them on your frontend — the browser or app the customer is using.
  2. Forward them to your backend with the customer’s request.
  3. Send them to Ripio in these headers when your backend calls the API.
Do not fill them from your own server: its IP address, the user agent of your HTTP client, or a fixed identifier would make every customer look like the same machine — a datacenter — and turn the signal into noise. If you cannot get a value from the customer’s device, leave that header out. Each header is independent, so sending only the ones you have is fine.
Ripio never uses the address your request comes from as the customer’s IP: for an API integration, that address is your infrastructure. X-Ripio-User-Ip is the only way the customer’s IP reaches Ripio.
The values are declared by you: Ripio records them as you send them, as the context of your customer’s request. Send a valid IPv4 or IPv6 address in X-Ripio-User-Ip; an invalid one does not fail the request, but none of the three values of that request is recorded.

Example

Where they are recorded

The headers can be sent on any request, but they are recorded on the actions a customer takes — the ones where knowing who is behind the request matters: They are recorded only when the request succeeds: a rejected request leaves no record. On any other endpoint the headers are accepted and ignored, so it is safe to attach them to every call your backend makes on a customer’s behalf.

Widget integrations

Partners on the Ramps widget do not need any of this: the widget captures the end user’s context itself and sends it with every operation.