Configure recurring payment rules
Recurring payment rules control how Zenoti automatically collects payments for memberships, packages, and other subscription-based charges. Properly configured rules ensure that collections run on schedule, failed payments are retried appropriately, and your organization minimizes revenue loss from missed payments.
Note: For membership billing configuration, see the Memberships category. This article covers the dunning and collection infrastructure that supports recurring billing.
Before you begin
Permission: Configure Payment Settings (under Payments) β Required to configure recurring payment rules, dunning schedules, scheduled payments, hard-decline flagging, and zero-amount collection behavior.
- Recurring payment rules apply at the organization level and affect all centers unless overridden at the center level.
- Before configuring dunning schedules, decide on your organization's policy for retry attempts and failed payment handling.
What recurring payments are
Recurring payments are automatic collections that the system processes on a defined schedule. These collections apply to memberships, packages, royalty payments, and any other charges that recur on a regular basis. Instead of manually collecting payment each billing cycle, the system charges the guest's stored payment method automatically.
The system supports specialized processing for each payment type β memberships, packages, and royalty payments each have their own collection logic to handle type-specific requirements.
Collection methods
The system supports eight payment collection methods for recurring charges:
- Credit card β The most common method. The system charges the guest's stored card on file.
- Check β The system records a check-based collection for manual processing.
- Cash β The system records a cash-based collection for manual processing at the center.
- Gift card β The system deducts the recurring charge from the guest's gift card balance. If the balance is insufficient, the collection falls back to the configured failure handling.
- Custom payment types β Any additional payment methods your organization has configured.
- Offline variants β Offline versions of the above methods for scenarios where online processing is unavailable.
You configure which collection methods are available for recurring payments in the payment settings area. The system attempts the guest's primary payment method first and falls back to alternative methods based on your configuration.
Dunning configuration
When a recurring payment fails, the system automatically retries the collection based on a dunning schedule that you define. Dunning helps recover revenue from failed payments without requiring manual follow-up for each one.
Dunning schedule
Define the parameters of your dunning schedule:
- Retry attempts β Set the maximum number of times the system retries a failed payment. Each retry is a separate collection attempt.
- Retry interval β Set the number of days between each retry attempt. For example, if you set the interval to 3 days, the system waits 3 days after each failed attempt before trying again.
- Escalation actions β Configure what happens at each stage of the dunning process, such as sending a notification to the guest or alerting center staff.
Failed payment handling
After all retry attempts are exhausted, the system marks the payment as failed. You can configure the system to:
- Send a final notification to the guest
- Alert the center manager
- Suspend or freeze the guest's membership or package until payment is resolved
Decline fees
You can optionally charge a decline fee when a recurring payment fails. This fee is added to the guest's account balance. Configure the decline fee amount in the payment settings area.
Note: Decline fee policies vary by region. Verify that your decline fee configuration complies with local regulations before enabling this feature.
Scheduled payments
Set up future-dated payments with authorization holds. Scheduled payments allow you to authorize a payment in advance and capture it on a specific date. This is useful for large purchases or deposits where you want to guarantee the payment before the service date.
The system places a hold on the guest's payment method for the authorized amount. On the scheduled capture date, the system automatically completes the transaction. Status changes are logged for tracking purposes.
Note: Authorization holds typically remain valid for 7 days for most card networks, though the issuer can release the hold earlier or extend it for specific card types. If the hold expires before the scheduled capture date, the system must re-authorize the payment before capture.
Hard decline flagging
Flag payment accounts that receive hard declines to prevent repeated failed attempts. A hard decline is a permanent failure, such as an invalid card number, an expired card, or a closed account. Unlike soft declines (which may succeed on retry), hard declines do not resolve on their own.
When you enable hard decline flagging, the system marks the guest's payment method after a hard decline. Future recurring collections skip that payment method until the guest updates their payment information. This reduces unnecessary processing attempts and the fees associated with them.
The end-to-end setup β including the manual-collections toggle, the guest-email toggle, the supported-processor allow-list (Adyen + Stripe Connect / Express variants), the front-desk experience when a flagged card is presented at the POS, and the unflag workflow β is documented in Flag payment accounts for hard declines.
Zero-amount collections
Configure whether the system processes or skips collections that have a zero-dollar due amount. This can occur when a guest has a credit balance, a promotional discount covers the full amount, or a membership has a $0 billing cycle.
- Process zero-amount collections β The system creates a collection record with a $0 amount and marks it as completed. This maintains a complete billing history.
- Skip zero-amount collections β The system does not create a collection record when the amount due is $0.
Choose the option that best fits your organization's reporting and record-keeping needs.