Manage payment disputes
Payment disputes (also called chargebacks) occur when a cardholder contests a charge with their card issuer. Zenoti provides tools to view disputes and submit evidence to respond, for processors that support dispute management directly through Zenoti.
Before you begin
Permission: You need payment management permissions to view and respond to payment disputes.
Processor dispute-support scope
Dispute management in Zenoti is limited to processors that expose a dispute API Zenoti integrates with β primarily Adyen and Stripe Connect. For all other processors, disputes are visible and managed only on the processor's merchant portal, and sometimes directly with the processor's dispute-operations team.
| Processor | Dispute visible in Zenoti | Dispute response via Zenoti | Primary channel |
|---|---|---|---|
| Adyen | Yes | Yes | Zenoti + Adyen Customer Area for complex cases |
| Stripe Connect | Yes | Yes | Zenoti + Stripe Dashboard |
| Stripe (direct) | Limited | Limited | Stripe Dashboard |
| Sunbit | No | No | Sunbit support team |
| ZipPay | No | No | Zip merchant team |
| All other processors (AirPay, eGHL, Plutus, QNB, EBS, JusPay, Walletdoc, BBVA, FreedomPay, Element Express, Moneris, Payworks, Payment Express, Checkout.com, EzyPay, Amazon Payment Services, Zuora, etc.) | Typically no direct surface | No | Processor's merchant portal and support team |
[SOURCE GAP β PM VERIFY: per-processor dispute-flow matrix against latest code.]
External prerequisites
- A working login for the processor's merchant portal (for processors where disputes are managed externally).
- Evidence retention policy at the center β guest consent forms, signed invoices, service-delivery proof, and communication history should be stored for at least the scheme's dispute window (typically 120β540 days depending on card network and reason code).
Network requirements
Dispute management is a back-office operation. Standard outbound HTTPS (port 443) from Zenoti to the processor API is sufficient. Large evidence uploads require stable connectivity.
View disputes
- Select Payments > Disputes management.
- Active disputes are listed with:
- Guest name
- Dispute date
- Amount
- Reason code (for example, "Item not received", "Unauthorized transaction")
- Response deadline
- Status (Open, Responded, Won, Lost)
Respond to a dispute
- Select a dispute to open the dispute details.
- Review the dispute reason code and the original transaction details.
- Gather supporting evidence, such as:
- Signed receipts or invoices
- Guest consent forms
- Service delivery confirmation
- Communication history with the guest
- Select Edit Evidence, write your explanation in Cover Letter, and select Save Evidence. Add your own files with Upload Custom Evidence.
- Select Defend Dispute, then Confirm.
- Zenoti sends the response to the payment processor, who forwards it to the card network.
Dispute outcomes
- Won β The card network sides with the merchant. The disputed funds are returned to your account.
- Lost β The card network sides with the cardholder. The disputed amount is deducted from your account.
- Accepted β You accept the chargeback without disputing. The amount is deducted from your account.
Dispute β dual-system perspective
| System | What happens |
|---|---|
| Zenoti | The disputed transaction is flagged in the dispute list; a negative reserve appears against the day's collections if the processor debits pending-dispute funds. |
| Processor | The dispute is assigned a case ID; evidence is routed to the card network. On loss, the processor debits the merchant's settlement account and records a fee. On win, funds are returned. Match key: processor dispute / case ID or original transaction ID. |
Failure modes
| Failure mode | Cause | Resolution |
|---|---|---|
| Dispute deadline missed | No response submitted in time. | Automatic loss β funds debited. Prevention: calendarise response deadlines. |
| Evidence upload fails | Large or wrong-format attachments. | Use PNG, JPEG or PDF. Each file and the assembled package must fit your processor's limit β see Defend payment disputes. |
| Dispute visible on processor portal but not Zenoti | Processor's dispute API not integrated end-to-end for that processor. | Respond via the processor portal; keep a local record. |
| Currency / amount mismatch on reserve | Processor held a reserve in a different currency. | Reconcile with the processor's merchant portal β typically a rounding / FX artefact. |
| Dispute re-opened (pre-arbitration) | Cardholder or issuer escalates. | Gather additional evidence; respond within the new deadline. |
Reconciliation
Disputes affect both the Collections report (as reversals) and the processor-side settlement report.
| Source | Report / view | Match key |
|---|---|---|
| Zenoti | Collections report + Disputes list | Processor transaction ID + dispute / case ID |
| Processor | Processor dispute dashboard + settlement report | Same fields |
Recommended cadence: weekly for disputes; monthly for dispute-loss trend analysis (reason codes repeating across guests signal a service or policy issue, not a payment issue alone).
Tips
- Keep copies of guest consent forms and signed invoices β these are your strongest evidence in dispute responses.
- Respond before the deadline. Missing the deadline automatically results in a lost dispute.
- For Sunbit transactions, chargebacks are handled directly by Sunbit. Contact Sunbit support for Sunbit dispute resolution.
- For ZipPay, charge-backs are handled by Zip's merchant operations.