Skip to content

Disputes

What happens when a cardholder disputes a Cardencer payment, which webhooks you receive and how to respond.

A dispute (or chargeback) happens when a cardholder asks their bank to reverse a payment. The issuer pulls the funds back and gives you a deadline to respond with evidence.

How disputes reach you#

When a dispute is opened, Cardencer:

  1. sends a dispute_opened webhook with content.type: "dispute_details",
  2. notifies you with the reason and the evidence deadline set by the card scheme.

The webhook's content.object includes the dispute_id, payment_id, amount, currency, dispute_stage, dispute_status, the reason and the challenge_required_by deadline.

Dispute lifecycle events#

Event Meaning
dispute_opened The cardholder's bank opened a dispute.
dispute_challenged You submitted evidence and the dispute is under review.
dispute_accepted You accepted the dispute; the funds stay with the cardholder.
dispute_won The issuer ruled in your favour; the funds come back to you.
dispute_lost The issuer ruled for the cardholder.
dispute_expired The response deadline passed.
dispute_cancelled The cardholder or issuer withdrew the dispute.

Respond to a dispute#

  1. Check the reason and the challenge_required_by deadline in the webhook or the notification.
  2. Gather evidence: proof of delivery and tracking, invoices, the customer's communication, your terms and refund policy, and the 3D Secure result of the payment.
  3. Send it to Cardencer support before the deadline. Cardencer submits it to the acquirer.

Payments authenticated with 3D Secure usually shift fraud-related chargeback liability to the issuer, which is one more reason to keep 3DS on.

Reduce disputes#

  • Use a recognisable statement descriptor and a clear description.
  • Ship quickly, share tracking, and capture only what you deliver (manual capture).
  • Refund promptly when a customer asks: a refund costs less than a chargeback.
  • Make your contact details easy to find.