Evina Fraud Check overview
Last updated: 2026-10-21
The Evina Fraud Check service is Mobixone's gateway to Evina's anti-fraud platform. Partners use it in two steps: a script call fetches the protection script that runs on a subscription page and watches the customer's interaction, and a check call, made when the customer acts, returns Evina's verdict on whether that action was genuine. Mobixone holds the Evina credentials, signs every request, and passes Evina's answer back unchanged.
The service has moved to a new address and now authenticates partners with OAuth 2.0 access tokens. The operations, paths, request bodies and responses are the same as before.
Endpoints
| Environment | Base URL | audience value | Evina environment |
|---|---|---|---|
| Staging | https://stage-evina.mobixone.co | https://stage-evina.mobixone.co | Evina test |
| Production | https://evina.mobixone.co | https://evina.mobixone.co | Evina live |
Every fraud-check call is a POST with a JSON body. GET /actuator/health answers
{"status":"UP"} without a token.
Authentication
Requests carry an OAuth 2.0 Bearer access token obtained with the client credentials grant, as described under Authentication. Two details are specific to this service:
- The token must carry the scope
content:fraud-check. - The token's
audiencemust be the fraud-check base URL from the table above, not the XCIS API audience. A token requested for the XCIS API is rejected by this service.
In this section
- Switching to the new Evina Fraud Check service: what changes, what you will receive from Mobixone, the steps to make on your side, and how to test in staging before moving production.