This page explains what checkpoints are and how to use them.
A checkpoint is a key event within a customer’s journey where you can request a recommendation from Ravelin. The checkpoints you want to use within your integration will likely depend on the kind of behaviour you are trying to address and where you would like to intervene in the customer journey.
As part of your integration, we will work with you to best understand which checkpoints you should be using, when you should be using them, and what you should do with recommendations at that point in the customer journey.
To request a recommendation at a checkpoint, add the checkpoint query parameter to the request URL with
the corresponding query parameter value.
If you do not specify a checkpoint we will not return a recommendation. We will still process the request, and it will still be available to view in the Ravelin dashboard.
We support the following checkpoints for PSPs.
pspBeforeAuth)The point at which a customer is trying to place an order, but before you have performed authentication (3DS) or authorisation. The query string to use is ?checkpoint=pspBeforeAuth.
Note that the ?checkpoint=pspBeforeAuth query string at the end of your request URL is used for both payment fraud and transaction optimisation recommendations,
but you will need to include &transactionOptimisation=true to ensure you also receive the latter.
Was this page helpful?