Ravelin's transaction optimisation API recommends PSPs to either send a customer to authentication or proceed directly to authorisation and which SCA exemption to use, with the aim of maximising the transaction's chance of acceptance with the least friction.
Read MoreAlongside your payment fraud integration, there are two extra things to consider for transaction optimisation:
Requesting recommendations
Make sure you send us important transaction and payment method details. We will return a recommendation to
authenticate or authorise with or without an exemption or 3DS challenge preference where applicable.
Update us with authentication and authorisation attempts
Make sure you update us at the end of the transaction about these attempts.
A transaction optimisation recommendation can be requested by sending a request to the transaction endpoint.
Read MoreYou can test your transaction optimisation integration 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.
Read MoreOur platform has been designed for resilience. However, in the unlikely event that an error is returned, we will attempt to continue processing your request as best as possible.
When requesting a transaction optimisation recommendation, you also have to request a payment fraud recommendation. This means that an error could occur on different parts of our platform.
If an error occurs when generating a transaction optimisation recommendation, but not during fraud scoring, we will still return a payment fraud recommendation. An error will be returned for transaction optimisation.
Read MoreWas this page helpful?