Luminate Online/Digital Resolve Integration

Overview - What is Digital Resolve?

Digital Resolve provides a comprehensive rule-based application for identifying potentially fraudulent transactions and for analyzing transaction patterns to progressively refine the rules. For organizations that are frequent targets of carding attacks, large volumes of charge backs can result in higher processing costs, fines and even suspension of their ability to accept credit cards. The organizations most susceptible to these types of attacks are large well-known charities particularly those involved in international relief.

The Digital Resolve system incorporates geo-location based upon IP address as a key part of their rules. Some of the rules frequently associated with fraudulent transactions are that the request is coming from a private IP address or anonymous proxy server, that it is coming from a high risk country or that the location of the IP address does not match the location specified with the credit card billing information.

The Luminate Online integration requires that the client separately purchase the fraud management service from Digital Resolve in a hosted environment. Luminate Online will then call out to the Digital Resolve system via HTTPS as each transaction is processed.
This callout takes place after internal velocity based fraud rules are checked and before the transaction is passed to the payment gateway (where AVS and CVV are checked). The callout includes the city/state/zip/country entered for the customer's billing information, email address, first name and last name entered by the donor, the amount of the transaction and the IP address that the donor is coming from. For constituents who are logged in, the callout also includes the first donation date and last transaction date.

The Digital Resolve system will run the transaction against the client's rule base and return an appropriate status value. The values returned from Digital Resolve are:
  • Declined - Indicates that this transaction should be declined based on the client's rule set.
  • Approved - Indicates that this transaction should be passed to the payment gateway for approval.
  • A numeric value (2-5) indicating the severity of a rule that fired on the transaction but was not considered severe enough for a blanket decline.
The Luminate Online system can be configured such that the different values of the intermediate return codes can be processed in one of 3 ways:
  • Decline the transaction (i.e. treat the same as a Decline response)
  • Continue the transaction (i.e. treat the same as an Approve response)
  • Turn on strict AVS for this transaction