This endpoint is deprecated. Send chargeback details in a Dispute Request.
A chargeback happens when a customer disputes a payment on their credit card account. Communicate this event to Ravelin using the chargeback endpoint. This is a mandatory component of all integrations. Our ability to predict fraud comes from our understanding of previous examples of fraudulent behaviour.
Most PSPs will associate two IDs with every chargeback: a unique identifier for
the chargeback itself, and the identifier for the original transaction that is
being disputed. It is the latter that must be sent in the
field, and it should correspond to a previously sent transaction.
For PSPs that associate chargebacks via the Merchant transaction ID, such as
transactionId can be specified in lieu of the gatewayReference.
If only the original order ID is known, Ravelin will guess that the first
auth_capture transaction is the charge being
If no transaction with a matching
transactionId is found, this chargeback is ignored.
timestamp integer required
The time at which this data payload was valid. When sending events in realtime, this will usually be 'now'. This is used to merge data that arrives out-of-order.
A unix timestamp preferably as an
integer count of milliseconds since
chargeback object required
The chargeback coming from a fraudulent claim filed with the cardholder's issuer.
eventType string optional
An eventType should identify what event in your system triggered this API call.
orderId string optional
The ID of the order the chargeback originated from. When provided instead of gatewayReference and transactionId, Ravelin will set the gatewayReference and transactionId to that of the first successful transaction of the order.
customerId string optional
The ID of the customer this chargeback originated from. Ravelin will look this up from the referenced order or transaction.
Was this page helpful?