Evina Developer Portal

Welcome to the Evina developer portal. You'll find comprehensive guides and documentation to help you start working with Evina as quickly as possible, as well as support if you get stuck. Let's jump right in!

Redirect

The redirect integration is made for merchants and for payment aggregators when mobile network operators (or payment gateways) are hosting payment pages (players do not host any landing pages).

Integration steps to manage fraud on the flow

1- Partner requests GetScript API from Evina’s platform.

2- Events and metrics (load, click…) are sent to Evina’s platform for deep analysis.

3- Partner asks for the transaction’s authenticity by calling GetCheck API from Evina’s platform and responds to MNOs/payment gateways.

4- Partner calls Transaction API to notify Evina’s system that a transaction has been confirmed.

Set up

It is a code to be deployed on the purchase confirmation pages:

  • Javascript code
  • Non-blocking 
  • Dynamically generated via web service
  • Low latency under 100ms RTT included

This probe will gather the information necessary for our real-time analysis.

This kit is generated at the code level that produces the page to monitor.

All API calls use a signature mechanism to guarantee the user's identity and access confidentiality.
Please contact your Customer Success Manager for more details.

Data request

This API allows you to extract the following data:

  • Fraud type
  • Transaction ID
  • Arguments
  • Time

Specifications:

  • Raw data is exportable over a 31-day period
  • Searches can go up to a year back
  • One call per second

Parameters to send with the data request:

  • Start Date
  • End Date
  • Signature

The API data is available anytime.

Additional APIs

Evina provides API to receive additional information

  • Data API: Partner can check request records asynchronously
  • User Report API: Partner can notify Evina that a transaction is a false positive

Updated 2 months ago


Redirect


The redirect integration is made for merchants and for payment aggregators when mobile network operators (or payment gateways) are hosting payment pages (players do not host any landing pages).

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.