Transaction Optimisation

  • Overview

    Ravelin's transaction optimisation API recommend merchants 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 More
  • Requesting and handling recommendations

    Alongside your payment fraud integration, there are two extra things to consider for transaction optimisation:

    1. 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.

    2. Update us with authentication and authorisation attempts
      Make sure you update us at the end of the transaction about these attempts.

    Requesting recommendations

    A transaction optimisation recommendation can be requested by sending a request to the Checkout Endpoint and adding the transactionOptimisation=true query parameter to the end of the request’s URL. This must be used in addition to the score query parameter for specifying a Checkpoint.

    Read More
  • 3DS Data Enrichment

    A guide on how to use the 3DS AReq returned alongside transaction optimisation recommendation.

    Read More
  • Testing Your Integration

    Testing with your PSP / 3DS Provider

    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.

    Testing with Ravelin

    You can test your transaction optimisation integration with Ravelin by sending a request with the customer.email field set to a special test value.

    Read More
  • Error Handling

    Our platform has been designed to be resilient to failure. However, in the unlikely event of an error we will attempt to continue to process your request as completely as possible.

    When requesting a transaction optimisation recommendation you also have to request a fraud recommendation, which means errors could occur in the 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. A message will be returned describing the error which occurred during transaction optimisation.

    Read More

Feedback