As well as testing your integration with Ravelin, it is important that you test any requests with your PSP and/or 3DS providers. This is to ensure that they are prepared to receive any new fields relating to our recommendations, as well as a smooth go-live process.
You can test your transaction optimisation integration with Ravelin by sending a request with the customer.email field set to a special test value.
The following emails will allow you to test the responses that Ravelin may return for traffic which we determine to be non-optimisable. The responses will contain a recommendation as well as a reason why we could not optimise the transaction in the data.transactionOptimisation.compliance.description field.
| Recommendation | Description | |
|---|---|---|
"qa-force-txopt-olo@ravelin.com" | AUTHORISE | issuer or acquirer country is outside of the EEA |
"qa-force-txopt-amex@ravelin.com" | AUTHENTICATE with challenge preference NO_PREFERENCE | cannot optimise American Express transactions |
"qa-force-txopt-rfr@ravelin.com" | AUTHENTICATE with challenge preference CHALLENGE_AS_MANDATE | reference fraud rate breached for acquirer |
"qa-force-txopt-highvalue@ravelin.com" | AUTHENTICATE with challenge preference CHALLENGE_AS_MANDATE | must authenticate transactions with value 500 EUR or greater |
These requests will always produce the same corresponding recommendation so you can ensure your system handles the response accordingly.
As well as testing the compliance-driven recommendations, Ravelin can set up rules in your sandbox account to facilitate testing all possible recommendations:
| Recommendation | |
|---|---|
"qa-force-txopt-authorise@ravelin.com" | AUTHORISE |
"qa-force-txopt-authorise-tra@ravelin.com" | AUTHORISE with TRANSACTION_RISK_ANALYSIS exemption |
"qa-force-txopt-authorise-lowvalue@ravelin.com" | AUTHORISE with LOW_VALUE exemption |
"qa-force-txopt-authenticate-nopreference@ravelin.com" | AUTHENTICATE with challenge preference NO_PREFERENCE |
"qa-force-txopt-authenticate-nochallenge@ravelin.com" | AUTHENTICATE with challenge preference NO_CHALLENGE_REQUESTED |
"qa-force-txopt-authenticate-challenge@ravelin.com" | AUTHENTICATE with challenge preference CHALLENGE_REQUESTED |
"qa-force-txopt-authenticate-challengeasmandate@ravelin.com" | AUTHENTICATE with challenge preference CHALLENGE_REQUESTED_AS_MANDATE |
"qa-force-txopt-authenticate-tra@ravelin.com" | AUTHENTICATE with TRANSACTION_RISK_ANALYSIS exemption
and challenge preference NO_CHALLENGE_REQUESTED |
"qa-force-txopt-authenticate-lowvalue@ravelin.com" | AUTHENTICATE with LOW_VALUE exemption
and challenge preference NO_CHALLENGE_REQUESTED |
To enable you to test using different cards, we will not consider the card scheme or issuing country when determining if the transaction
is optimisable in cases where these test emails are used. This includes American Express cards. If you want to test the recommendation
which is returned for an American Express card, please use the qa-force-txopt-amex@ravelin.com email in your request.
Other fields, such as the acquirer ID and transaction value, may affect whether we are able to optimise the transaction.
Learn how to correctly handle transaction optimisation errors
Was this page helpful?