Transaction Optimisation

  • Overview

    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 More
  • Requesting and handling recommendations

    There are two steps to integrate with transaction optimisation: Request a recommendation Send us transaction details, and we will return a recommendation to authenticate or authorise, with or without an exemption and 3DS challenge preference. Update us with authentication and authorisation attempts You can update us at the end of transaction about these attempts. Requesting recommendations A transaction optimisation recommendation can be requested by sending a request to the transaction endpoint.

    Read More
  • Testing your integration

    You can test your transaction optimisation integration either by: Sending a request with the paymentMethod.iin field set to a special test value. Sending a request with the field set to a special test value. These requests will always produce the same corresponding recommendation. You can then ensure your system handles the response accordingly. The test card BINs and email addresses are shown in the table below: Field Name Field Value Recommendation Example Response Card BIN "

    Read More
  • Error handling

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

    Read More