Transparent Gateway

The transparent gateway integration is made either for mobile network operators authorizing payment gateways and merchants, or payment gateways authorizing merchants to host payment pages.

Here, partners can be mobile network operators authorizing payment gateways and merchants, or payment gateways authorizing merchants to host payment pages.

2425

Integration steps to manage fraud on the flow

1- Your partner requests GetScript API from Evina’s platform.

2- Your partner installs this script on the relevant pages to protect.

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

4- Your partner asks its other partners (mobile network operator/payment gateways) if content access can be granted.

5- The mobile network operators or payment gateways ask for the transaction’s authenticity by calling GetCheck API from Evina’s platform and by responding to your partner.

Transaction check

Before finalizing the user's subscription initiated by your partner, the mobile network operator or payment gateway calls upon DCBprotect to validate the authentication of the transaction. 

If the transaction is not authentic, you can either:

  • Block fraudulent sources in real-time (blocking mode).
  • Investigate suspicious traffic sources without any impact on your conversion rate (audit mode).

Usually, it is recommended to start in audit mode to progressively move to block mode.

How to check the authenticity of a transaction that belongs to your partner?
By using the transaction identifier shared between your partners to call upon DCBprotect to validate the authentication of the transaction.

Sub-accounts system

This integration works on a sub-accounts system for which:

Partner owns and manages all your partner's accounts on a master account: doing all the checks on its side.
Each of your partner has its own and unique credentials in order to sign their calls to Evina's API.

📘

In this type of integration

Only mobile network operators/payment gateways have access to the dashboard to monitor and analyse traffic of their partners.

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

995

This API allows you to extract the following data:

  • Fraud type
  • Transaction ID
  • Arguments
  • Time

Specifications:

  • Raw data exportable over 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