iovation's Integration Services

iovation’s integration services are designed to expedite and facilitate integration of our Software as a Service (SaaS) solutions into our subscribers’ online environments. To meet our subscribers’ diverse requirements, we offer two integration options— Gateway Integration & Server Integration. Additionally, we provide tailored professional services to our customers, during integration to optimize the use of the solution and return on investment.

Our integration services provide support for widely deployed end user platforms and web browsers. Our solution has been easily integrated into customer environments utilizing C, C++, Java, PHP, .NET and Perl and we have a wide range of sample code for developers to utilize in their integration.


Gateway Integration

The Gateway Integration accelerates the integration process with minimal development resources. This integration option is ideal for subscribers who submit real-time device reputation requests but do not require a real-time response from the system. This integration enables subscribers to get delayed-time alerts about suspicious/abusive transactions. Additionally, subscribers can use the system’s Administrative Console to perform forensic analysis, generate reports, and to submit evidence of fraud/abuse against devices and accounts/transactions.

This diagram provides a high level view of the iovation ReputationManager™ Gateway implementation process:

  1. A small amount of “client code” is inserted in the subscriber Web site that enables it to collect device identification information and to communicate directly with iovation ReputationManager service.
  2. The “client code” sends the user’s device information and the associated account or transaction ID, as supplied by the subscriber’s Web site, to iovation’s gateway server.
  3. The gateway server passes the device information to iovation DRA server where it is stored for evidence entry, fraud analysis and notification.
  4. The system emails alerts to the subscriber when suspicious/abusive activity is detected. Subscribers can also use the system’s Administrative Console for forensic analysis, generating reports, and to submit evidence against any fraudulent account/transaction, or device.

Server Integration

The Server Integration is ideal for subscribers who submit real-time device reputation requests and require real-time response from the iovation system in their fraud assessment to decide whether to process or deny transactions. This bi-directional integration of ReputationManager™ solution enables subscribers to take real-time fraud prevention action in addition to using the system’s Administrative Console to perform Fact-Based forensic analysis and placement of evidence on devices or accounts.

This diagram provides a high level view of the iovation ReputationManager Server implementation process:

  1. A small amount of “client code” is inserted in the subscriber Web site that enables it to collect device information.
  2. The subscriber’s Web server receives the user’s device identification information.
  3. The server associates the device information to an account or transaction and sends the information to the iovation DRA server.
  4. The iovation DRA server determines the device’s identity (DeviceID) and whether it is associated with known fraud or abuse and returns the result to the subscriber’s web server.
  5. The subscriber decides whether to proceed and process or deny the transaction.

    6. Additionally, subscribers can use the system’s Administrative Console to perform forensic analysis, generate reports, and to submit evidence of fraud/abuse against devices and accounts/transactions.

     

Solutions

Technology