ZenotiHelp

Dispute Management

ZTZenoti Docs Team Updated October 23, 2026 4 min readGuide

Zenoti tracks payment disputes (chargebacks) filed against processed transactions, allowing organization administrators to view dispute details, submit evidence, and configure dispute fees.

Audience: Organization administrators who manage payment disputes and chargeback responses.

Before you begin

  • A dispute must have been filed against a processed payment before you can take action.

  • You need the following permission:

    Permission: View (on the Export Admin security role) β€” required to view and export dispute data from payment reports.

  • Confirm that your payment processor supports dispute management through Zenoti. Contact Zenoti Support if you are unsure whether your processor routes dispute data into Zenoti.

  • Prepare your supporting files before you start. Evidence files you add yourself must be PNG, JPEG, or PDF. For accepted formats and size limits, see Defend payment disputes.

Note: Dispute management covers chargebacks filed against payments already processed through your payment processor. For processing payments at the point of sale, see Point of sale.

Steps

View disputes

  1. Navigate to Payments > Disputes management.
  2. Review the list of disputes. Each dispute entry shows the associated payment and its current status.

Review dispute evidence details

  1. Select a dispute from the list to open its detail view.
  2. Review the evidence details associated with the dispute, including transaction information and any previously submitted documentation.
  3. Note the dispute status and any deadlines indicated by your payment processor.

Important: Dispute response deadlines are set by the card network and your payment processor. Missing a deadline may result in an automatic ruling against your organization. Review deadlines before submitting evidence.

Submit evidence for a dispute

You add evidence from the dispute detail page, through the evidence editor.

  1. Open the dispute detail page for the dispute you are responding to.

  2. Select Edit Evidence to open the evidence editor.

  3. Review the Documents table in Edit Evidence. This table shows the documents that make up your evidence package for this dispute.

  4. To attach your own files, select Upload Custom Evidence and choose the file to upload. Custom documents must be PDF, PNG, JPG or DOC files. For the full list of accepted formats and the size limits that apply, see Defend payment disputes.

  5. Repeat the previous step for each additional file you want to include. Useful evidence includes:

    • Appointment records showing the service was completed
    • Guest acknowledgment or signature records
    • Invoice details and payment confirmation
  6. Select Save Evidence to retain your changes to the evidence package.

    Important: Saving keeps your work but does not send it to the payment processor. Review the Documents table in Edit Evidence and confirm every file you intend to include is listed before you continue β€” once evidence is submitted, you cannot add to the package for this dispute.

  7. Select Defend Dispute to proceed, then select Confirm to send the evidence package to the payment processor.

Tip: Gather all supporting documentation and convert it to a supported format before you open the editor. Incomplete submissions may weaken your dispute response.

Configure dispute fee settings

  1. Navigate to Configuration > Payments > Payment settings.
  2. Locate the dispute fee configuration section.
  3. Update the dispute fee settings as needed for your organization.
  4. Select Save to apply the changes.

Note: Dispute fees are charges assessed when a chargeback is filed. Configuring this setting determines how Zenoti records and applies those fees to affected invoices.

Tips

  • Act promptly on new disputes. Payment processors and card networks impose strict response windows. Check Payments > Disputes management regularly so you do not miss a deadline.
  • Keep appointment and invoice records complete. Detailed records β€” including service completion notes, guest signatures, and closed invoices β€” are the most effective evidence in dispute responses. Ensure front-desk staff close invoices and capture relevant service data at checkout.
  • Save as you build the evidence package. Select Save Evidence after adding each set of files so your work is retained, and select Defend Dispute then Confirm only when the Documents table in Edit Evidence is complete.
  • Review dispute fee configuration after processor changes. If your organization changes payment processors or updates processor settings, verify that dispute fee configuration still reflects your intended setup.

Troubleshooting

Problem Likely cause Resolution
Disputes do not appear in Payments > Disputes management Your payment processor may not route dispute data to Zenoti, or the disputes have not yet been transmitted Confirm with your payment processor that dispute notifications are enabled; contact Zenoti Support if disputes are expected but not visible
Evidence submission does not save Required fields may be incomplete, or a session timeout may have occurred Review all required fields in the editor, re-enter any missing information, and select Save Evidence again
A file you added does not appear in the Documents table in Edit Evidence The file may be in a format that is not accepted, or the upload may not have completed Confirm the file is PNG, JPEG, or PDF and within the published limits β€” see Defend payment disputes β€” then select Upload Custom Evidence and upload it again
Evidence was saved but the payment processor shows no response The package was saved but not submitted Reopen the dispute detail page, select Edit Evidence, confirm the Documents table in Edit Evidence is complete, then select Defend Dispute and Confirm
Dispute fee configuration changes do not take effect Settings may not have been saved, or a center-level override may be in place Confirm you selected Save after making changes; check whether a center-level setting is overriding the organization-level configuration
Was this article helpful?
Your feedback helps us improve our documentation.