Defend payment disputes
When a guest disputes a charge with their card issuer, you receive a dispute notification and have a limited time to respond. Use the dispute defense tools to review auto-generated evidence, attach supporting documents, and submit a defense to protect your revenue.
Important β response deadline. The card network sets the deadline; it is shown on each dispute as a Respond By date and varies by processor and dispute type. Use the Needs to be defended today filter on the disputes list to surface deadline-critical items. Do not assume a fixed window.
On this page
- What disputes are
- Pre-dispute inquiries
- When one challenge produces several dispute records
- View disputes
- View dispute details
- Defend a dispute
- Evidence formats
- What evidence to include (by reason type)
- Accept a dispute
- Dispute statuses
- Pre-dispute inquiry statuses
- Formal dispute statuses
- Non-defendable disputes
- Cross-currency disputes
- Partially won disputes
- Notification configuration
- Templates path (org-level)
- Distribution Management System (DMS) path
- Financial impact during an open dispute
- Fund transfers from disputes
- Dispute reporting (Digital Payments Report)
- BNPL disputes (Affirm via Stripe Express)
- Tips
- Troubleshooting
- Reduce your dispute rate (forward-looking)
Audience: Organization administrators and center administrators responsible for managing payment disputes and protecting revenue from chargebacks.
Before you begin
Permission: Dispute Payments (under Payments) β Required to view disputes, submit evidence, and manage dispute responses. Admin path: Configuration > Security > Security roles > [your role] > Permissions > Payments > Dispute Payments
Who can do this. Org-admin and center-admin roles with Dispute Payments (under Payments). Front-desk roles may need an escalation step. Verify your role's permission grant in the security role configuration.
The system surfaces all disputes returned by your configured payment processor. The defense workflow does not vary by processor.
What disputes are
A dispute (also called a chargeback) occurs when a guest contacts their bank or card issuer to challenge a charge on their statement. When a dispute is filed:
- The card network may temporarily reverse the disputed amount from your account.
- You receive a Respond By deadline (returned by the card network on each dispute).
- You may submit evidence supporting the validity of the charge before the deadline.
- The card network rules in your favor (Won), in the guest's favor (Lost), or on a partial outcome.
If you do not respond by the deadline, or if the evidence is insufficient, the dispute is decided in the guest's favor and the funds are permanently reversed.
Pre-dispute inquiries
Some card networks issue a pre-dispute inquiry before raising a formal dispute. During an inquiry, the bank requests evidence but does NOT withdraw funds. Responding promptly can resolve the issue before it escalates to a chargeback.
Pre-dispute inquiries appear in the disputes list under the Warning Needs Response status. After you respond, the status changes to Responded. If you do not respond, the status moves to Not Responded and the bank may escalate to a formal dispute. The term "Inquiry" refers to the bank-side investigation concept; Warning Needs Response is the Zenoti status label for this stage.
When one challenge produces several dispute records
A single guest challenge can appear as several separate records in your dispute list. This is expected, and each record is real β none of them is a duplicate.
There are two reasons it happens:
- Recurring collections are disputed one charge at a time. A membership or recurring pass is collected as a separate charge on each billing date. A dispute attaches to one charge, so a guest challenging several months of billing produces one record per collection.
- An inquiry and a formal dispute are separate records. If a charge starts as a pre-dispute inquiry and later escalates, the escalation is recorded separately from the inquiry rather than replacing it.
Respond to every record. Each one has its own Respond By deadline, and those deadlines can fall on different dates. A record you do not respond to is decided in the guest's favor when its deadline passes, even if you successfully defended the others. Before you start work, check the dispute list for other open records for the same guest and confirm how many records are open.
Saving a draft on one record does not carry to the others β the auto-submission behavior applies per record, and only where a draft was saved.
View disputes
Navigate to the disputes page to see all open disputes.
- Select Payments > Disputes management.
- Use the status tabs β All, Needs Response, Under Review, Won and Lost β to switch between groups of disputes.
- Use the filters to narrow the list, then select Apply (select Reset to clear them):
- Status β filter by dispute status.
- Dispute Type β filter by the type of dispute.
- Center β filter by center. You see only the centers your role can access.
- From and To β filter by date range.
- Or choose a Quick Views option: All Disputes, Needs Response (7 days), Defense Due Today or Won (Last 30 days). Use Defense Due Today daily to catch disputes whose deadline is today.
- Select View Details on a row to open the dispute.
The dispute list shows the following columns:
| Column | Description |
|---|---|
| Status | The current dispute status. See Dispute statuses. |
| Respond By | The deadline returned by the card network. |
| Guest Name | The guest associated with the disputed transaction. |
| Center | The center where the disputed transaction was processed. |
| Amount | The disputed amount. |
| Type | The type of dispute. |
| Reason | The reason returned by the card network (for example, fraudulent transaction, service not rendered, credit not processed). |
| Payment Method | The payment method used for the disputed transaction. |
| Evidence | Whether evidence has been generated or submitted for the dispute. |
| Created Date | When the dispute was created. |
| AI | Whether AI Dispute Manager handled the dispute. |
| Actions | View Details opens the dispute. |
View dispute details
Click a dispute to view its full details:
- Original transaction β reference, date, amount, payment method.
- Guest details β name and contact information.
- Reason for dispute β description of the reason code and what the guest is claiming.
- Response deadline (Respond By) β exact date and time by which you must submit evidence. This value is returned by the card network on the dispute object and varies by processor and dispute type.
- Dispute fee β the card network charges a dispute fee that Zenoti collects on behalf of your processor. The exact amount varies per processor contract β review your processor agreement or contact your account manager for the specific figure applicable to your organization.
- Original invoice link β opens the disputed invoice for context.
Defend a dispute
Important β Defend Dispute is irreversible. Once you select Defend Dispute and confirm, the evidence package is sent to the processor and cannot be re-edited. Save evidence while you gather supporting documents and only confirm when your package is complete.
- Select Payments > Disputes management and select View Details on a dispute. The system-generated evidence PDF appears on the page.
- Select Edit Evidence to open the evidence editor. Edit Evidence appears only while the dispute status is Needs Response or Warning - Needs Response, the dispute is defendable, and it was not automatically defended (an automatically defended dispute shows "This dispute was automatically defended.").
- Review and edit the Transaction Details, Cover Letter, and items in the Documents table in Edit Evidence.
- To attach your own files, select Upload Custom Evidence and choose a PDF, PNG, JPG, or DOC file. Each file is checked against the size limit for your processor when you choose it.
- Select Save Evidence to keep a draft. You can return up to the Respond By deadline.
- When your evidence package is complete, select Defend Dispute (or Defend at the top of the page), then Confirm to submit the evidence to the issuing bank. This action cannot be undone.
Auto-submission on deadline. If you have saved evidence but have not manually submitted by the Respond By deadline, the system automatically submits the last-saved evidence package on your behalf before the deadline closes. This prevents inadvertent non-response for disputes where a draft was started but not submitted. Auto-submission sends whatever was saved at that moment β ensure your saved draft is the best evidence package before the deadline; do not rely on auto-submission as a substitute for deliberate review.
After submission, the dispute status moves to indicate the defense is under review. The card network's decision typically arrives within the processor's review window; you receive a notification when the outcome is final.
To replace the system-generated document with a file of your own β or to switch back to the system-generated document β use Replace Document while the dispute can still be acted on. Replace Document offers two options: Upload Custom PDF (one PDF file) and Use System Generated.
Evidence formats
The following table summarizes available evidence formats and their intended use:
| Format | Use |
|---|---|
| System-generated document (default) | Built from your transaction and guest data. Review and edit it in the editor via Edit Evidence. |
| Files you add via Upload Custom Evidence | PDF, PNG, JPG, or DOC files attached to support your defense. |
| Replacement defense document (Replace Document) | Replaces the system-generated document with a single PDF (Upload Custom PDF), or reverts to the system-generated document (Use System Generated). Available for any dispute that can be acted on. |
Ensure all uploaded documents are clear, legible, and directly relevant to the dispute reason code.
Size limit. Each file you upload is checked when you choose it. The complete assembled evidence package is also checked when you save. Both checks apply the limit for your processor:
| Processor | Maximum size |
|---|---|
| Stripe | 4.5 MB |
| All other processors | 2 MB |
Each file must be within the limit, and so must the total package. You can upload several files that are each individually within the limit and still exceed the package limit. If the package is rejected, check the total size after assembly β not each file on its own. Remove or compress the least essential attachments and save again before submitting. Leave time before the Respond By deadline to re-save, because auto-submission sends whatever was last saved and a package that never saved cannot be sent.
What evidence to include (by reason type)
Different reason codes call for different evidence. The system does not auto-recommend evidence by reason code; the mapping below is documentation guidance only.
| Dispute reason | Recommended evidence |
|---|---|
| Fraudulent transaction (cardholder claims they did not make the purchase) | Signed service agreement or consent form; appointment confirmation; signed receipt; ID verification record; before/after service documentation. |
| Service not rendered | Appointment confirmation showing the guest checked in; service log signed by guest; before/after photos; provider notes. |
| Credit not processed (refund-related) | Refund record (transaction receipt for the refund); communication record explaining the refund timeline. |
| Product not received (retail) | Shipping confirmation, delivery proof, or in-store pickup record. |
| Duplicate charge | Transaction history showing the two charges are distinct (different services, different dates, different invoices). |
Worked example β fraudulent transaction dispute: A guest disputes a $180 deep-tissue massage, claiming they did not authorize the charge. Attach the following to the auto-generated document: (1) the signed service consent form the guest signed at check-in, (2) the appointment confirmation email sent to the guest's address 24 hours before the appointment, and (3) the provider's session notes. This combination demonstrates the guest's presence and consent.
Accept a dispute
If you choose not to defend a dispute, you can accept it.
Important: Once you accept a dispute, the decision is final. Accept a dispute only when the guest's claim is valid or you cannot provide sufficient evidence.
- Open the dispute detail view. Accept is available only while the dispute status is Needs Response or Warning - Needs Response, the dispute is defendable, and it was not automatically defended.
- Select Accept, then Confirm. The funds are permanently returned to the guest and the dispute status changes to Accepted.
Dispute statuses
The disputes list uses two categories of status: pre-dispute inquiry statuses (before a formal dispute is raised) and formal dispute statuses (once a chargeback exists in the system).
Pre-dispute inquiry statuses
Pre-dispute inquiries do not withdraw funds. The bank requests evidence before escalating to a formal dispute, giving you an opportunity to resolve the issue at lower cost.
| Status | What it means |
|---|---|
| Warning Needs Response | The cardholder's bank is investigating a complaint and requesting evidence before raising a formal dispute. No funds are withdrawn. Provide the requested information to avoid escalation to a chargeback. |
| Responded | You have submitted the evidence requested during the pre-dispute inquiry. |
| Not Responded | You did not provide the requested evidence. This may result in the bank raising a formal dispute. |
Formal dispute statuses
| Status | What it means |
|---|---|
| Not Requested | No dispute has been raised on this transaction. |
| Requested | A dispute has been requested by the guest's card issuer. The system has logged the request and is awaiting your defense or acceptance. |
| Initiated | Defense has been initiated; evidence has been submitted to the processor. |
| Under Review (Auto-defended) | The payment processor automatically handled the dispute without requiring evidence submission from your end. |
| Won | The card network ruled in your favor. Funds remain with you. |
| Lost | The card network ruled in the guest's favor. The disputed amount is permanently reversed. |
| Accepted | You voluntarily accepted the dispute and agreed to refund the guest. Distinct from Lost (card-network ruling) β this is a business decision. |
| Withdrawn | The guest withdrew the dispute before or after evidence was submitted. No funds are transferred. |
| Rejected | The dispute was rejected at intake (for example, malformed dispute payload or processor policy). |
| Invalid | The dispute is invalid (for example, a duplicate dispute on the same transaction). |
Processor-side state machine values (Accept, Create, Lost, NetworkReject, NetworkRejectReversal, Rebut, Reverse, Won) are tracked separately and may surface as additional context in the dispute timeline.
Non-defendable disputes
Certain dispute reason codes are classified by the card network as non-defendable β meaning the network's rules make defense ineffective regardless of evidence. Examples include certain ACH disputes and some BNPL refund flows.
Non-defendability is a function of the reason code returned by the card network, not a Zenoti setting. The system does not allow toggling defendability per dispute. When a dispute is non-defendable, the status display reflects this; the recommended action is to accept the dispute rather than spend resources on a defense that the network will not consider.
If you have proof of service completion for a dispute that the network has classified as non-defendable, you cannot override the classification. Your option is to accept and pursue alternative recovery (for example, contacting the guest directly).
Cross-currency disputes
A cross-currency dispute is one where the currency of the guest's card (the presentment currency) differs from the currency of the transaction, so exchange-rate movement can make the amounts differ. For example, a guest paying with a USD card for a GBP 500 transaction may see $655.95 on their statement.
To identify a cross-currency dispute:
- Select Payments > Disputes management.
- In the dispute list, look for a help icon next to the dispute amount. It marks a cross-currency dispute.
- Select the icon. Zenoti shows "This is a cross-currency dispute", with See history and Learn more. See history appears when the dispute has history.
- Select See history to open Dispute History. It lists the Created Date, Type, Transaction ID and Amount of each entry and names the presentment (card) currency.
Partially won disputes
A dispute is partially won when the card network rules that you recover only a portion of the disputed amount.
- The partially won status is displayed in both the dispute management view and the Digital Payments Report.
- Email notifications show the exact amount recovered and the updated status.
- The dispute fee applies even in partially won cases.
- The recovered amount is restored to your account; the remaining unrecovered portion is treated as a loss and appears as a separate line on the Digital Payments Report.
- There is no Zenoti-side appeal flow for a partial decision.
Notification configuration
Dispute notifications can be configured through two parallel paths. They are not interchangeable β they govern different aspects of notification delivery.
Templates path (org-level)
Navigate to Configuration > Notifications > Templates for email and text to control whether the dispute notification fires at all. Enable or disable the dispute notification template for the organization from this path.
Distribution Management System (DMS) path
Use the notification's recipient (distribution) settings to control who receives it. You can manage specific recipients by role, email, or username when you need granular per-recipient control beyond the org-level template enablement.
You typically configure both: enable the template via the Templates path so notifications fire, and add recipients via the DMS path so the right people receive them.
Financial impact during an open dispute
When a dispute is raised, the disputed amount is withheld from your next processor payout until the dispute is resolved. The withheld amount equals the original transaction amount; the dispute fee charged by the card network is applied separately at the time the dispute is filed.
- If the dispute is Won, the withheld amount is released back to you in a subsequent payout. The dispute fee is non-refundable by the card network on most chargeback types β confirm fee-reversal terms with your processor.
- If the dispute is Lost or Accepted, the withheld amount remains with the guest's card issuer and is not returned. The dispute fee is also retained.
For a membership or recurring-billing transaction that is disputed, the dispute itself does not automatically cancel the underlying membership. You can review and cancel the membership separately in the memberships console if you decide not to defend.
Fund transfers from disputes
When a dispute is accepted or lost, the system records fund transfers associated with the dispute. These transfers track the movement of funds between accounts as a result of the dispute resolution. Fund transfer details are available in the Track fund transfers workflow.
Dispute reporting (Digital Payments Report)
The Digital Payments Report export includes per-dispute fields used for reconciliation and audit:
| Field | Description |
|---|---|
| Dispute ID | Unique identifier for the dispute record. |
| Original transaction ID | The transaction that was disputed. |
| Disputed amount | The amount the guest challenged. |
| Reason code | The card-network reason code for the dispute. |
| Status | The current dispute status at time of export. |
| Respond By | The response deadline returned by the card network. |
| Processor | The payment processor that processed the original transaction. |
Additional fields under consideration for future releases include amount recovered (for partial wins) and processor name for businesses using multiple processors.
BNPL disputes (Affirm via Stripe Express)
Affirm disputes processed through Stripe Express differ from standard card disputes in four important ways. If your organization accepts Affirm payments, review these constraints before a dispute is raised.
Important β funds debited immediately. When an Affirm dispute is created, the disputed amount is debited from your Stripe Express account immediately, before any investigation. This differs from card disputes where funds are typically held pending investigation.
| Difference | Standard card dispute | Affirm via Stripe Express |
|---|---|---|
| Auto-evidence | System assembles evidence automatically from transaction data. | Not supported. You must prepare and upload evidence manually. |
| Evidence rounds | Multiple evidence submissions may be allowed. | One round only. Submit your strongest available evidence on the first attempt. |
| Funds timing | Disputed amount withheld from next payout during investigation. | Disputed amount debited immediately when dispute is created. |
| Dispute type | Varies (Inquiry, Chargeback). | Always classified as Chargeback β funds are already held from creation. |
Dispute status labels for Affirm: The Zenoti dispute status table in Dispute statuses applies to Affirm disputes. Affirm disputes use the standard dispute lifecycle: Requested β Initiated β Won or Lost. No Affirm-specific display labels exist.
Evidence to prepare for Affirm disputes: Because auto-generation is not available, prepare these manually before the Respond By deadline:
- Signed service agreement or consent form.
- Appointment confirmation showing the guest attended.
- Original invoice and payment confirmation.
- Any guest communication relevant to the dispute reason.
For Affirm disputes, contact your account manager if you need guidance on evidence effectiveness β Affirm's resolution criteria may differ from card-network dispute rules.
Tips
- Work the deadline view daily. Open the disputes list and choose the Defense Due Today quick view every morning. Missing a deadline results in an automatic loss regardless of the validity of your evidence.
- Check for sibling records before you start. A guest challenging a recurring membership produces one dispute record per collection, and an escalated inquiry sits alongside the inquiry it came from. Check the list for other records for the same guest first so you know how many deadlines you are working against.
- Save drafts early, submit deliberately. Select Save Evidence as soon as possible, even if the package is incomplete. Auto-submission fires on whatever draft is saved at the deadline β so a well-organized partial package beats an empty draft. Reserve Defend Dispute > Confirm for when your package is final.
- Match evidence to the reason code. Review the reason code before selecting evidence. A "fraudulent transaction" dispute calls for identity and presence evidence (signed forms, appointment confirmation); a "service not rendered" dispute calls for service delivery evidence (check-in records, provider notes). Mismatched evidence is unlikely to succeed.
- Attach the signed consent form for every service dispute. Signed intake or service consent forms are the single most effective piece of evidence across dispute types. Ensure your front desk collects and stores these digitally so they can be retrieved quickly.
- Configure DMS recipients before a dispute arrives. Dispute notifications only reach the right people if DMS recipients are configured. Set this up proactively β not after the first dispute lands in the wrong inbox.
Troubleshooting
Evidence will not save or submit, and the package is large. The assembled package exceeds the size limit for your processor β see Evidence formats. Check the total size after assembly, not each file individually: several files that are each within the limit can still push the package over the limit. Remove or compress attachments and select Save Evidence again. Leave time before the Respond By deadline to re-save, because auto-submission sends whatever was last saved and a package that never saved cannot be sent.
Edit Evidence is not visible. Check that your role has Dispute Payments (under Payments). Edit Evidence is also hidden when the dispute no longer needs a response (for example Won, Lost, or Accepted), when it was automatically defended (the page shows "This dispute was automatically defended."), or when the dispute is not defendable.
Several dispute records appeared for what the guest describes as one complaint. This is expected and none of the records is a duplicate. A recurring collection is disputed one charge at a time, so several months of billing produce one record per collection; and an inquiry that escalates is recorded separately from the formal dispute. Respond to every record β each carries its own Respond By deadline, those dates can differ, and a record left unanswered is decided in the guest's favor when its deadline passes even if you won the others. A draft saved on one record does not carry to the others.
Evidence submitted but status is still showing Initiated. Processor review takes time. After you confirm with Defend Dispute > Confirm, the dispute status moves to Initiated and remains there until the card network issues a ruling. No action is required. You receive a notification when the outcome (Won, Lost, or Partially Won) is final.
Defend Dispute is greyed out. Defend Dispute and Accept are available only while the dispute status is Needs Response or Warning - Needs Response, the dispute is defendable, and it was not automatically defended. If the dispute falls outside these conditions, no further action is available on that record.
A dispute is marked non-defendable but you have proof of service. Non-defendability is determined by the card network's reason code classification, not by Zenoti. Submitting evidence does not override the classification. The recommended action is to accept the dispute and attempt to resolve the matter with the guest directly outside the dispute process.
Dispute fee was charged even though you won. Dispute fees are charged when the dispute is created, regardless of outcome, and are non-refundable by the card network on most chargeback types. Confirm fee-reversal terms with your processor if you believe a specific dispute type qualifies for a fee refund.
Affirm dispute amount was debited immediately β is this correct? Yes. Affirm disputes via Stripe Express debit funds immediately at creation, before investigation. This is an Affirm/Stripe network behavior and not a Zenoti error. See BNPL disputes (Affirm via Stripe Express) for full details.
Reduce your dispute rate (forward-looking)
Although this article focuses on defending disputes, the most cost-effective long-term strategy is to reduce your dispute rate. Card networks penalize businesses with high dispute rates with monitoring programs, higher processing fees, or in extreme cases account termination. Practical steps to reduce disputes include: clear billing descriptors, automated email receipts, transparent refund policies, and signature capture at Point of Sale. A dedicated best-practices article is planned for a future round.