Ravelin recommends whether you should accept, challenge, or prevent payments from customers.
In assessing each customer, Ravelin will look at their identity, prior orders, transactions/payment attempts, cards/payment methods, and where they are ordering from. It is important that you send the data to Ravelin cleanly to paint a full, accurate picture from which to attain good fraud prevention results.
When considering this information, it is important that Ravelin has as much of this data as possible before being asked to score a customer in order for us to make a fully-informed recommendation.
A customer places many orders, attempts many transaction payments, spends on many payment methods, logs in from many devices, and files many chargebacks. If customers are not required to sign up to your website/app in order to make a purchase, we recommend using their email address as the customerId in all cases.
Customer information should be sent to Ravelin when:
An order is placed by one customer, has a price and currency, has many order items describing what is being bought, may have multiple failed transaction payments, hopefully has a successful transaction payment, is placed from one device, and has disputing chargebacks. The multiple order items may describe cab rides, food orders, concert tickets, hotel bookings, something else, or some combination of each.
Order information should be sent to Ravelin when the customer has shown intent to purchase:
and generally progress through pending (pre-scoring), accepted (passed fraud check; merchant intends to fulfill), into fulfilled, cancelled, or failed.
A transaction is an attempt to pay for one order placed by one customer, has an amount and a currency, has one payment method and gateway processor, eventually has a gateway reference, success flag and authentication/check information, and may have multiple chargebacks associated with it. A transaction spans one attempt to pay by one customer.
Transaction information should be sent to Ravelin when:
A payment method is used by one customer to provide funds to fulfill many transactions and many orders. The payment method can be a payment card (having a scheme, issuer, BIN, last-four digits, and a globally-identifying instrumentID), a voucher, cash, PayPal account, or many other means of sending funds.
Payment method information should be sent to Ravelin when:
Disputes (including chargebacks) inform us that a customer who made a payment was likely not the real cardholder. Sending us disputes allows us to report fraud rates and improve our automated fraud prevention to better differentiate between genuine and fraudulent behaviour in the future.
Disputes are associated with a transaction, payment method, order and customer. Disputes have a stage, outcome, amount (usually the disputed transaction amount plus a penalty) and currency.
See Ravelin’s guide to disputes to learn more.
In a marketplace, suppliers (e.g. drivers, couriers or restaurants) may also be involved in fraud. Supplier information should be sent to Ravelin when: