Disputes and chargebacks
When a customer disputes a charge with their bank, this is how you defend yourself from Cord, before the deadline.
What a dispute is
A dispute (chargeback) happens when a cardholder asks their bank to reverse a charge: because they don’t recognize it, because they say they didn’t receive what they paid for, or for another reason. The bank holds the amount while it’s resolved, and you have a limited time to present evidence that the charge was legitimate.
It applies to card payments processed by Cord Payments. A bank transfer (SPEI or with a reference) or a manual transfer has no card chargeback, and a bank debit charge is claimed under its scheme’s rules. Mercado Pago chargebacks are handled from your Mercado Pago account: Cord doesn’t read them today.
Requirements
| Requirement | Detail |
|---|---|
| Plan | All plans. |
| Permission | Collections or Payment settings. Without them, the dispute page shows “No access”. |
| Submission | Also confirming your identity with your password or your two-step verification code. |
Where it appears
- Cord records the dispute as soon as the processor reports it, with amount, currency, reason, status, and deadline.
- In Revenue › Payments, the Open disputes widget shows the total at stake and, for each dispute, “respond before [date]”.
- Opening a dispute takes you to its evidence page, Build a clear response, with the amount, the status, and the due date at the top.
The account owner also gets an email, in your account’s language, with the subject Action required: dispute for [amount], and Cord adds to Tasks a high-priority task titled “Respond to the [amount] chargeback” (in your account’s language), unassigned, linked to the payment’s quote, and due on the day, in your business’s time zone, the evidence deadline falls on. Because it’s unassigned, the email reminder for that task goes to the account owner. Like any task, it emits A task is created (task.created).
If you use the API or Workflows, Cord emits A dispute is opened (dispute.created) and A dispute is closed (dispute.closed, with the outcome). See Workflow triggers.
The deadline rules
If you don’t submit evidence before the deadline, you normally lose the dispute. The deadline is set by the card network, not by Cord: start working on it as soon as you see it.
Statuses
The status appears next to the amount with the processor’s name for it:
| Status | What it means |
|---|---|
needs response |
Evidence must be submitted before the deadline. |
under review |
You already submitted evidence and the customer’s bank is reviewing it. |
won |
You won: the held money returns to your balance. |
lost |
You lost: the amount leaves your balance. |
warning needs response, warning under review, warning closed |
An early inquiry from the bank that isn’t a chargeback yet. Respond anyway: it can become one. |
The evidence
The page arrives prefilled with what Cord already knows about the transaction. Review and correct each field:
| Field | What Cord proposes |
|---|---|
| Customer name and Customer email | Those on the quote’s customer record. |
| Service date | The quote’s approval date. Change it to the actual delivery date. |
| Approval IP | The IP address from the quote’s electronic signature, if there is one. |
| What the customer purchased | The quote’s items with their quantities. |
| Customer communication | Empty: paste the relevant messages here (acknowledgments, delivery confirmations). |
| Additional context | Empty: explain the case in your own words. |
| Receipt or supporting file | Optional: your own PDF, JPG, or PNG. If you don’t choose one, Cord prepares an automatic receipt. |
What Cord builds for you
On submission, Cord generates two PDFs:
- Transaction receipt: your business, the customer, the amount, the method, the transaction, the items and, when available, who signed the quote, on what date, and from which IP address. If you uploaded your own receipt, yours is used.
- Customer communication: a PDF with the text you pasted in that field.
Save a draft and submit
- Click Save draft as many times as you like. The draft stores only text in Cord: it doesn’t upload files or send anything to the processor.
- When ready, click Review and submit evidence. You’ll see a preview with the exact list of what will be transferred.
- Click Confirm and transfer and confirm your identity when Cord asks.
- You’ll see Evidence submitted and return to Payments.
Submitting is irreversible
Once submitted, the evidence can’t be edited or completed. Review every field before confirming.
Saving, preparing the PDFs, and submitting are recorded in your organization’s audit log.
What happens next
The processor delivers the evidence and the customer’s bank decides. It can take weeks and the outcome isn’t guaranteed: Cord helps you build the best possible case, but doesn’t decide. The status updates on its own on the dispute page.
| If… | Then |
|---|---|
| You win | The held amount returns to your balance. |
| You lose | The amount leaves your balance, along with a processor dispute fee. |
| Either way | Cord’s fee on the original payment isn’t returned. See Fees. |
How to prevent disputes
- Require an electronic signature on approval: the signature’s name, date, and IP are your best evidence. See Electronic signature.
- Use clear item descriptions and a recognizable business name.
- Answer your customers’ questions in the quote chat: that history is evidence too.
Limits
- Card payments processed by Cord Payments only.
- A single evidence submission per dispute.
- No Mercado Pago disputes in Cord.
Common problems
I can’t find the dispute. Check the dashboard’s date range and that you have the Collections or Payment settings permission.
The approval IP is empty. The quote had no electronic signature. Explain in the additional context how your customer confirmed the purchase.
Submitting asks for my password again. Identity confirmation lasts a few minutes; if more time passed, Cord asks again.