This page explains what checkpoints are and how to use them. What are checkpoints? 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. For example, to stop payment fraud you might want to request a recommendation when a customer registers a new payment method or at checkout.
Read MoreThere are two currencies sub-divided into 5 basic units, seven sub-divided into 1000, and eighteen without any subdivisions.
Read MoreYour customer service reps logging into customer accounts in your live system may result in them joining networks together.
Read MoreThis page explains how best to send Ravelin data about discounts. Many of our clients use different types of discounts in relation to the products they sell. This information is intended to to help guide you on how best to represent this information in Ravelin. There are 2 different ways you can share this information with us. Regardless of how you implement discounts, the guiding principle here should be that the order price sent to Ravelin via the API should match what the customer spent on the order.
Read MoreRavelin applies rate-limiting to stop any one actor impacting its availability to others, and Merchants should do the same with their customers.
Read MoreWas this page helpful?