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

• Transaction Routing Diagram

  The flow diagram below shows all the possible routes a transaction could take during the payment flow, and the messages sent between you, Ravelin and your PSP.

  

  Next steps

  Learn how to request a transaction optimisation recommendation

  Read More

• Requesting Recommendations

  There are two steps to integrate with transaction optimisation:

  1. Request a recommendation
     Send us details of a transaction. We will return a recommendation to either perform authentication or authorisation.

  2. Update us with authentication and authorisation attempts
     This could be after each attempt or at the end of the transaction.

  Request Recommendations

  A transaction optimisation recommendation can be requested by sending a request to the Checkout Endpoint.

  Add the transactionOptimisation=true query parameter to the end of the request’s URL.

  Read More

• 3DS Data Enrichment

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

  Read More

• Testing Your Integration

  You can test your transaction optimisation integration either by:

  • Sending a request with the paymentMethod.cardBin field set to a special test value.
  • Sending a request with the customer.email 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	"000001"	Authenticate with no SCA exemption	"action": "AUTHENTICATE"
  Email	"qa-force-txopt-authenticate@ravelin.com"
  Card BIN	"000002"	Authorise with no SCA exemption	"action": "AUTHORISE"
  Email	"qa-force-txopt-authorise@ravelin.com"
  Card BIN	"000005"	Authenticate with Transaction Risk Analysis exemption	"action": "AUTHENTICATE" "exemption": "TRANSACTION_RISK_ANALYSIS"
  Email	"qa-force-txopt-authenticate-tra@ravelin.com"
  Card BIN	"000006"	Authorise with Transaction Risk Analysis exemption	"action": "AUTHORISE" "exemption": "TRANSACTION_RISK_ANALYSIS"
  Email	"qa-force-txopt-authorise-tra@ravelin.com"
  Card BIN	"000007"	Authorise with Low Value exemption	"action": "AUTHORISE" "exemption": "LOW_VALUE"
  Email	"qa-force-txopt-authorise-lowvalue@ravelin.com"

  Next steps

  Learn how to correctly handle transaction optimisation errors

  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 the fraud score along with the message: “Could not generate transaction optimisation recommendation”.

  Read More

Feedback

Was this page helpful?

Yes No

Thanks for the feedback. If you'd like to provide more detail, please email support@ravelin.com.