Core concepts
Disputes
A dispute occurs when the payer's bank challenges a payment. Merxian tells you with a webhook event, and records any money movement as an adjustment on the transaction.
On this page
What a dispute is#
A payer can ask their bank to reverse a payment, for example because they do not recognize it. The bank then opens a dispute. A chargeback is a dispute in which the bank takes the money back from the seller.
The API has no dispute resource and no dispute endpoints. Disputes reach you in two ways: an event on the payment, and adjustments on the transaction.
The dispute event#
When a dispute opens, Merxian sends dispute.opened. The payload is the disputed payment, with the state dispute_opened. Use transaction_id in the payload to find your record.
Chargebacks as adjustments#
When money moves because of a dispute, Merxian adds an adjustment to the transaction and sends transaction.adjusted. Read the transaction to see the new adjustment in adjustments.
| Adjustment | Meaning |
|---|---|
| Chargeback | The bank took the disputed amount back. |
| Second chargeback | The bank took the amount back again after a first decision. |
| Chargeback reversed | The dispute was decided for you, and the amount came back. |
Who pays#
A chargeback does not return the Merxian fee. You pay every chargeback amount, on every plan. See Fees.
Evidence#
The API has no endpoint to submit evidence for a dispute.
What to build#
- On
dispute.opened, stop further delivery for the payment, for example pause access to the product. - Keep the evidence of the sale: what the buyer bought, when, and proof of delivery.
- On
transaction.adjusted, read the transaction and update your records with the amounts that changed.