ZenotiHelp

Process recurring payments

ZTZenoti Docs Team Updated August 20, 2026 4 min readGuide

Recurring payments automatically collect membership dues, package installments, and other scheduled charges from a guest's stored payment account. The system processes these payments on the scheduled collection date without manual intervention.

Before you begin

Permission: You need billing management permissions to configure and review recurring payments.

Prerequisites

  • The guest must have a valid stored payment account. See Manage stored payment accounts.
  • The payment processor must support recurring payments and card-on-file storage. Not all processors do. Processors that do NOT support recurring card charges include: AirPay, Plutus (PineLabs), eGHL, JusPay, EBS, QNB, Checkout.com, Payworks, CaisseAP, Sunbit, and ZipPay. Always check the processor's article before configuring a recurring schedule on that center.

Network and processor-side prerequisites

Recurring payments run as back-end charges. Standard outbound HTTPS (port 443) from Zenoti to the processor's API is required at the scheduled run time. If the processor uses direct-debit / ACH (Automated Clearing House), allow extra time for bank returns (up to 5 business days in some markets).

Processor role Source of value
Which card token to charge Guest's default card, set via the Cards tab on the guest profile, or the card specifically attached to the membership.
Which MID (Merchant Identifier) to charge through Center-level active processor (V1) or org-level onboarded processor (V2).
Dunning / retry schedule Organization-level recurring-payment configuration.

How recurring payments work

  1. A guest enrolls in a membership or purchases a package with installment billing.
  2. Zenoti stores the guest's card token with the payment processor.
  3. On the scheduled collection date, Zenoti automatically initiates a charge against the stored card.
  4. If the charge succeeds, the membership or package is updated as paid.
  5. If the charge fails, Zenoti records the failure and may retry according to the configured retry schedule.

View scheduled recurring payments

  1. Navigate to Configuration > Reports > Billing or the membership / package management section.
  2. Filter for upcoming scheduled charges.
  3. Review the list of guests and amounts due.

Manually trigger a recurring payment

To process a recurring charge before the scheduled date:

  1. Navigate to the guest's membership or package record.
  2. Select Collect Payment.
  3. Confirm the payment details.
  4. Select Process.

Handle failed recurring payments

  1. Navigate to the failed recurring payment record.
  2. Review the failure reason (declined card, expired card, insufficient funds, etc.).
  3. Contact the guest to update their payment method if the card is expired or invalid.
  4. Update the stored card in the guest's profile.
  5. Retry the charge.

Failure modes

Failure mode Typical cause Resolution
Processor unreachable at run time Outage or Zenoti-side network issue. Zenoti retries per the dunning schedule. Manual retry is available from the failed-payment record.
Authentication expired Processor credentials rotated without a Zenoti update. Re-verify credentials; retry the batch.
Card declined Insufficient funds, block, fraud hold. Contact the guest; retry or replace the card.
Card expired (no auto-update) Card passed its expiry; processor does not support Account Updater. Contact the guest for a new card. See Update card details automatically for the list of processors that do auto-update.
Amount out of range Charge is below processor minimum or above maximum. Adjust the membership amount or split into multiple charges.
Currency mismatch Recurring schedule currency different from center / processor currency. Align the three; processors do not perform FX silently.
ACH / direct-debit reversal Bank returned the debit unpaid (BBVA ACH, EzyPay DD). Invoice reopens; chase the guest. Normal for DD processors.
Settlement reversal Charge approved then reversed at settlement. Raise with the processor using the transaction ID; reopen the invoice.

Edit or reverse a recurring charge

Invoice state What you can do
Open (charge pending) Cancel the upcoming charge from the membership record; modify the amount or card if needed.
Open (charge processed, invoice unclosed) Void (if the processor supports void and settlement has not occurred) or refund.
Closed Reopen if permissions allow, or post a compensating refund. Original line preserved. Cancel future recurring charges if the guest is terminating the membership.

Refund of a recurring charge — dual-system perspective

System What happens
Zenoti Negative payment line on the membership invoice; Collections report shows the refund row. Membership status may need manual adjustment depending on your refund policy.
Processor Refund record linked to the original charge. Match key: processor transaction ID or Zenoti invoice number.

Retry schedule (dunning)

When a recurring payment fails, Zenoti may retry the charge automatically on subsequent days according to your organization's retry configuration. Review failed payments regularly to address card issues before the retry window expires. The configuration is typically an organization-level setting — review with your billing lead to confirm the current schedule.

Automatic card updates and recurring payments

If your processor supports automatic card updating (Stripe or Element Express/Worldpay), stored cards that are reissued by the bank may be updated automatically. This helps prevent recurring payment failures due to expired cards.

  • Stripe: Card details are updated proactively in the background. Recurring payments continue with the updated card details without interruption.
  • Element Express (Worldpay): Card details are updated after a charge is declined. The initial collection fails, but the card is updated for the next collection attempt.

Not all card types are eligible — Amex cards are excluded from automatic updating. For full details, see Update card details automatically.

Reconciliation

Source Report / view Match key
Zenoti Collections report (filter by payment method) + membership / package collection reports Processor transaction ID + Zenoti invoice number
Processor Processor merchant portal transaction / settlement report Same fields

Recommended cadence: weekly for volume monitoring; daily if the processor uses direct-debit or BNPL (Buy Now, Pay Later) (reversals arrive asynchronously).

Tips

  • BNPL options (Sunbit, ZipPay, Stripe BNPL) cannot be used for recurring payments — these are for one-time transactions only.
  • Review the recurring payment report monthly to ensure all memberships are collecting correctly.
  • Processors without auto-card-update require a proactive "card expiring" outreach programme to avoid churn from technical failures.
Was this article helpful?
Your feedback helps us improve our documentation.