Use Auto-pay
Auto-pay is a card-on-file feature that pre-authorizes a guest's saved card at appointment check-in and captures the final amount automatically when the invoice is closed. The guest does not need to interact with a terminal or sign at checkout β they walk out, and the receipt arrives by their preferred channel. This article covers Auto-pay setup, the authorization model, status states, failure handling on the desktop POS and Mobile POS, notification configuration, and how to recover when a card enters a stopped-retry state.
Audience: Organization administrators who enable and configure Auto-pay; center managers who set up notification templates and the additional authorization buffer; front-desk staff who process and resolve Auto-pay invoices at the point of sale.
On this page
- Before you begin
- How Auto-pay works
- Set up Auto-pay
- Guest opt-in (Customer Mobile App)
- Authorization at check-in
- Capture at checkout
- Auto-pay status reference
- Handle Auto-pay failures (desktop POS and Mobile POS)
- Auto-pay report and post-failure actions
- Guest lifecycle: change card, update tip, disable Auto-pay
- When a card stops retrying β and how to replace it
- Recurring membership and package payments
- Multi-entity payment routing and Auto-pay
- Supported card types
- Recommended notification templates
- Tips
- Troubleshooting
- If the problem persists
- Related articles
Before you begin
- Permission (organization): Edit (under Organization) β required to toggle the organization-level Enable Auto-pay setting.
- Permission (center): Edit (under Center Payment Settings) β required to toggle center-level Auto-pay, configure the additional authorization buffer, and edit the terms-and-conditions text.
- Permission (Auto-pay report): View and Edit (under Auto-pay Report) β required to view the Auto-pay report and execute Retry / Void / Manual-collect actions on failed transactions.
- Processor: Auto-pay works on every Zenoti payment processor that supports card vaulting (saved cards) and pre-authorization. Confirm your processor supports both vaulting and pre-auth before turning Auto-pay on.
- Saved card: The guest must have a saved card on file in Zenoti. Auto-pay does not work without a tokenized card on the guest profile.
- Self-service: Auto-pay is fully self-service for organization administrators. You do not need to contact your Customer Success Manager or Zenoti Support to enable it. The toggle lives in your organization settings.
Acronyms used in this article
- POS β Point of Sale (desktop or Mobile)
- CMA β Customer Mobile App (Zenoti Mobile in its guest-facing mode; distinct from the staff-facing Mobile POS)
- T&C β Terms and Conditions
How Auto-pay works
Guest checks in
ββΊ System computes authorization_amount = base_service + suggested_tip + additional_amount
ββΊ System pre-authorizes the saved card
ββ Success: status = authSuccess; "authorized at check-in" notification fires
ββ Failure: status = authFailed; FDO sees fallback to Manual Payment
Services rendered
Invoice closed at checkout
ββΊ System captures min(final_amount, authorization_amount)
ββ Success: status = captureSuccess; receipt sent; unused authorization buffer released
ββ Final exceeds authorization: re-auth attempted; if re-auth fails, FDO collects difference manually
ββ Capture failure: status = captureFailed; FDO sees Retry / Void / Manual-collect actions
The "Additional Amount for Authorization" is the buffer that covers post-check-in add-ons such as products, retail purchases, or upgraded services. If the guest's actual invoice ends up at or below the authorized total, the unused portion is released back to the cardholder when the invoice closes β they are not charged for the buffer.
Set up Auto-pay
Step 1: Enable Auto-pay at the organization level
- Open the organization settings page and expand the Zenoti-Go section.
- Find Enable Auto-pay and turn it on.
- Save.
This is the organization-wide gate; centers can opt in individually after this is on.
Step 2: Enable Auto-pay at the center level
- Open the center settings page and expand the Zenoti-Go section (Enable Zenoti-Go).
- Find Enable Auto-pay (Supported only on Zenoti Payments) and turn it on.
- Save.
Note: Auto-pay is available at a center only when both the organization-level setting and the center-level setting are on. Turning the organization setting off disables Auto-pay everywhere immediately, regardless of the per-center toggle state.
Step 3: Configure the additional authorization buffer
The buffer covers post-check-in additions to the invoice (products, retail, service upgrades). Pick a value that comfortably covers your typical add-on spend without being so large that it triggers card-issuer fraud declines.
- In the same Center Payment Settings screen, find Additional Amount for Authorization.
- Enter the buffer amount in your center's currency (commonly $25β$100 for spa and salon centers; higher for medical spa or premium services where retail add-ons are larger).
- Save.
Note: A buffer that is too small results in declined charges or manual top-up at checkout when the guest adds products. A buffer that is too large can trip the cardholder's bank fraud rules β issuers sometimes flag a $500 hold against a $30 service authorization as suspicious. Tune to your typical post-check-in spend.
Step 4: Configure the terms and conditions text
The Auto-pay opt-in screen in the Customer Mobile App (CMA) and on the Payment Link surface displays your organization's terms and conditions text. The guest must accept the T&C before Auto-pay can be enabled on their profile.
- Go to Configuration > Online Settings > Booking Experience > Zenoti Go and open Autopay Terms & Conditions Text.
- Enter the T&C text. Include at minimum: (1) what Auto-pay does (pre-authorize at check-in, capture at checkout), (2) the authorization buffer behavior, (3) what happens if the guest disputes a charge, (4) how the guest can opt out and update their saved card. Consult your legal team for specific compliance language for your jurisdiction.
- Save.
Important: The T&C is shown once at opt-in. Material changes (for example, increasing the authorization buffer or adding new fee categories) typically require re-opt-in β coordinate the rollout of T&C changes with your support team and consider notifying enrolled guests via email.
Step 5: Configure the suggested-tip label
The label "Tips" can be customized at the organization level. For example, you can change it to "Suggested Tip amount" so it appears as Suggested Tip amount in the CMA and on the Payment Link.
- Go to Configuration > POS > Tips and gratuity.
- Find Enter a label for tips and edit it.
- Save.
The label updates take effect immediately on all Auto-pay surfaces.
Step 6: Configure Auto-pay notification templates
Auto-pay supports four notification channels β email, Text (SMS), push (CMA), and WhatsApp. The structure is one umbrella configuration with per-channel templates, not four parallel screens.
- Go to Configuration > Notifications > Templates for email and text and open the Auto-pay templates.
- The umbrella configuration shows the available triggers: authorization at check-in, capture at checkout (success and failure), manual collection required.
- For each trigger, configure each channel:
- Set the channel to Yes (enabled).
- Open the message body editor.
- Compose the message using macros from the macro library (see Recommended notification templates below for starter examples). The macro library includes approximately 18 macros β guest name, invoice ID, service date, service amount, tip amount, additional amount for authorization, total authorized, captured amount, retry link, and others.
- Save.
- Repeat for each trigger / channel pair you want to enable. Channels you leave at No are skipped at runtime.
Important β WhatsApp: WhatsApp message templates must be approved by Twilio before they will deliver. Approval typically takes 1β3 business days but can take longer depending on Twilio's queue and the content of the template. Common rejection causes: promotional content, unverified business name, missing brand identity, or violating WhatsApp's Business Policy. If a WhatsApp template is rejected or pending, Auto-pay continues to function β the WhatsApp channel is skipped, and the other channels (email, Text, push) deliver as normal. Re-submit the template after revising the content.
Guest opt-in (Customer Mobile App)
The guest enables Auto-pay on their own profile via the Customer Mobile App. This is a guest-side action β front-desk staff cannot enable Auto-pay on a guest's behalf, but you may need to walk a guest through the steps if they ask for help.
The guest's flow:
- Tap the menu (the three lines at the top of the app).
- Tap Profile > Payments.
- Tap Auto-pay.
- Tap Enable Auto-pay.
- Select a saved card (or add a new card) to use for Auto-pay.
- Set the suggested tip default (the guest can override per visit).
- Read and accept the terms and conditions.
- Save.
Note: This is the guest-side experience and lives in CMA, not in the desktop or Mobile POS. If your business helps guests through this, ensure your front-desk team is aware of CMA navigation. For guest payment management through the mobile app, see Customer Mobile App.
Authorization at check-in
When the FDO checks in a guest who has Auto-pay enabled:
- The system reads the guest's Auto-pay configuration: saved card, suggested-tip default, and accepted T&C version.
- The system computes the authorization amount:
base_service + suggested_tip + additional_amount. - The system sends the authorization request to the processor against the saved card.
- On success, the appointment shows an "Authorized" indicator (Web POS Appointment Book) or the corresponding indicator on the Mobile POS appointment list. The status is
authSuccess. - The configured "authorization at check-in" notification fires across enabled channels.
If authorization fails, see Handle Auto-pay failures below.
Capture at checkout
When the FDO closes the invoice (no manual payment action required if Auto-pay is fully configured):
- The system computes the final invoice amount, including any post-check-in additions (products, retail, service upgrades, additional tip if the guest changed it).
- If the final amount is at or below the authorization amount, the system captures the final amount only. The unused portion of the authorization buffer is released back to the cardholder.
- If the final amount exceeds the authorization amount, the system attempts re-authorization for the difference. On success, the capture proceeds. On failure, the FDO is prompted to collect the difference manually (a different card, cash, gift card, etc.) β Auto-pay completes for the originally authorized portion, and the manual payment covers the rest.
- On capture success, the status moves to
captureSuccess, the receipt notification fires, and the invoice closes.
Auto-pay status reference
The Auto-pay invoice status is filterable in the Auto-pay report. Each value answers a different reconciliation question.
| Status | Meaning | What it means for the FDO and the guest |
|---|---|---|
Successful (captureSuccess) |
The invoice was authorized at check-in and captured at checkout. Funds have been charged to the cardholder. | Normal happy path. Receipt was sent. |
Failed (captureFailed or authFailed) |
Either authorization at check-in failed, or capture at checkout failed. | FDO must take action β see Auto-pay report and post-failure actions. |
Voided (voided) |
The transaction was voided by Zenoti or the FDO before processor settlement. The cardholder's authorization hold was reversed and no funds were captured. Use when an invoice is cancelled the same day. | No further action β voided records are reconciled as zero-net. |
Released (released) |
The authorization hold was released without capture. This happens when the invoice is cancelled (or the guest opts out before checkout) and the original authorization is freed back to the cardholder's available balance. | No action needed β the cardholder's balance returns to normal within the issuer's hold-release window (typically 1β7 days, issuer-dependent). |
| Pending | The authorization or capture is in progress and has not yet resolved. | Wait for the status to update. If it remains Pending for more than a few minutes, check the Zenoti Payments status page and contact support if needed. |
Reconciliation note: Voided and Released both result in zero net charge, but they happen at different points in the lifecycle β Voided is post-capture-attempt-but-pre-settlement; Released is post-authorization-but-pre-capture. The audit trail keeps both for ledger reconciliation.
Handle Auto-pay failures (desktop POS and Mobile POS)
Both the desktop POS and the Mobile POS surface Auto-pay failures, but the visual placement differs slightly.
Authorization failure at check-in
- Desktop POS (Web Appointment Book): The appointment block displays a red "Auth failed" indicator. Click the appointment, then click Take Payment to fall back to a manual payment flow. The Auto-pay attempt is logged in the Auto-pay report with status
authFailed. - Mobile POS (iPad / Android tablet): A failure message appears at the top of the appointment, and the Auto Pay option is disabled for this specific appointment. A Manual Payment button is shown β tapping it opens the standard manual checkout flow.
Capture failure at checkout
- Both desktop POS and Mobile POS: A capture-failed dialog appears with three actions: Retry, Void, and Collect Manually. Pick the action based on the failure cause.
The "authorization at check-in failure" notification fires (per Step 6) so the guest is aware before they walk out β they can update their card on file via CMA before checkout if they choose.
Auto-pay report and post-failure actions
The Auto-pay report (under Reports > Auto-pay report) lists every Auto-pay invoice with status, amounts, and available actions. You can filter by status: Successful, Failed, Voided, Released, Pending.
Report columns
| Column | What it shows |
|---|---|
| Invoice ID | The invoice number this Auto-pay attempt is associated with. |
| Guest | Guest name and profile link. |
| Service amount | The base service amount at check-in. |
| Suggested tip | The tip amount the guest set (or the default at the time of check-in). |
| Additional amount for authorization | The buffer amount that was added to the authorization. The unused portion is released after the invoice closes. |
| Total authorized | Sum of service + tip + additional amount. |
| Captured amount | The amount captured at checkout (zero if Auto-pay didn't capture). |
| Status | One of Successful, Failed, Voided, Released, Pending β see Auto-pay status reference. |
| Actions | Available post-failure actions on this invoice β see below. |
Available actions
| Action | Available when | Effect |
|---|---|---|
| Retry | Status is captureFailed or authFailed |
Re-attempts authorization (for authFailed) or capture (for captureFailed) against the same saved card. Use this when the failure was likely transient β temporary card-issuer block, network timeout, etc. |
| Void | Status is authSuccess and capture has not occurred |
Issues a pre-settlement void, releasing the authorization hold. Use this when the invoice was cancelled or the guest opted out before checkout. The status moves to voided. |
| Manual collect | Any failure state | Marks the Auto-pay attempt closed and prompts the FDO to collect payment via the standard POS flow (different card, cash, gift card, etc.). Use this when retry has failed or you don't expect retry to succeed (for example, the guest's card is actually expired). |
| (No action listed) | Status is Pending | Pending is not a failure β the authorization or capture is still in progress, so there is nothing to retry or collect yet. Wait for the status to update, then use the action for the status it resolves to. See Auto-pay status reference for how long to wait and when to escalate. |
Guest lifecycle: change card, update tip, disable Auto-pay
The guest manages their own Auto-pay configuration through CMA. Front-desk staff cannot make these changes on the guest's behalf, but you may need to walk a guest through the steps:
- Change the saved card: Profile > Payments > Saved Cards > Add or replace card. The new card is automatically used for the next Auto-pay authorization. The old card remains in the vault unless the guest explicitly removes it.
- Update the suggested-tip default: Profile > Payments > Auto-pay > Tip default. The new default applies to future authorizations; existing authorized appointments are unchanged.
- Disable Auto-pay: Profile > Payments > Auto-pay > toggle off. Existing authorized appointments are not affected β they will still capture at checkout. To void an existing authorization before its appointment, the FDO uses the Void action in the Auto-pay report.
- Card expiry: When a saved card expires, the next Auto-pay authorization fails with
authFailed. The system fires the configured "authorization at check-in failure" notification; the guest is prompted to update their card via CMA before the next visit.
When a card stops retrying β and how to replace it
After a card accumulates repeated failed collection attempts, Zenoti documents the card as stopped β no further Auto-pay or recurring collection retries are made against it. This state is a property of the card record itself.
Important: Editing the card details in place (for example, correcting the billing postal code on the existing saved-card record) does not clear the stopped state. The card remains stopped even after the edit. This is the most common reason a corrected card continues to fail β the stopped flag is still set on the original card record.
Check the billing postal code first
A mismatched billing postal code is one of the most common causes of the repeated failures that lead to a card being stopped. Before replacing the card, ask the guest to verify that the postal code on their saved card matches the billing address on their bank statement. If it does not match, the correct sequence is to replace the card (not edit it in place) with the accurate postal code.
Replace a stopped card β correct sequence
To restore Auto-pay for a guest whose card has been stopped, follow these steps in order:
- Add the new card to the guest's profile (Profile > Payments > Saved Cards > Add card). Enter the correct card details, including the billing postal code that matches the cardholder's bank statement.
- Switch the membership's (or Auto-pay's) default payment method to the new card. This is the step that re-enables Auto-pay and recurring collections β the system will use the new card going forward.
- Delete the old (stopped) card from the guest's profile. A card that is still attached to a membership or an active Auto-pay enrollment cannot be deleted until the default has been switched away from it. Attempting to delete before switching will result in an error.
Tip: If the guest is not present, you can add the new card via the guest profile in the desktop POS and switch the default on their behalf. The guest will need to confirm the new card details with you (last four digits, expiry, billing postal code).
Recurring membership and package payments
For recurring membership and package payments, Auto-pay routes the charge to the merchant account of the Business Unit (BU) assigned to the membership or package β not to the center's default merchant account. This applies to both the initial collection and all subsequent recurring charges.
If a recurring collection fails (for example, the guest's card is declined), the dunning rules configured for your organization determine how many retries are attempted and on what schedule. For membership billing configuration, see the Memberships category.
Multi-entity payment routing and Auto-pay
When the multi-entity payment processing setting is active for your organization, Zenoti routes each payment transaction to the merchant account linked to the invoice's Business Unit. Auto-pay follows the same routing rule.
Important: When multi-entity payment processing is enabled, each invoice must contain items from a single Business Unit only. If an invoice contains items from multiple Business Units, the system rejects the payment and displays an error. Split the invoice by Business Unit before attempting Auto-pay or any other payment method.
Service deposits are not supported when multi-entity payment processing is enabled. For organization and center payment settings, see the Configurations category.
Supported card types
Auto-pay works with cards saved to the guest's profile. Supported card types include:
- Visa
- Mastercard
- American Express
- Discover
Digital wallet support (Apple Pay, Google Pay) depends on the processor configured for the center. Confirm with your processor documentation whether digital wallet tokens can be vaulted and used for pre-authorization.
Recommended notification templates
These are starter templates. Edit them to match your brand voice and review with legal/compliance before publishing. The macro library includes approximately 18 macros β the snippets below use the most common ones.
Authorization at check-in β success (email)
Subject: We've checked you in for your service today
Hi {{guest_name}},
You're all set for your service at {{center_name}} today. We've placed a temporary hold of {{total_authorized}} on your saved card to cover today's services and any extras. Whatever you don't end up using will be released back to your card.
See you soon!
{{center_name}}
Authorization at check-in β failure (Text)
Hi {{guest_name}}, we couldn't authorize your saved card for today's appointment at {{center_name}}. Update your card in the app or pay at the front desk. {{retry_link}}
Capture at checkout β success (push)
Thanks for visiting {{center_name}}! We've charged {{captured_amount}} to your saved card. Receipt: {{receipt_link}}
Capture at checkout β failure (email)
Subject: Payment couldn't be captured for your visit today
Hi {{guest_name}},
We couldn't complete the charge for your visit today at {{center_name}}. The amount was {{final_amount}}. Common reasons include an expired card or insufficient available balance.
Please update your card in the app, or contact us to pay another way: {{center_phone}}.
Thanks, {{center_name}}
Manual collection required (WhatsApp β pending Twilio approval)
Hi {{guest_name}}, we've completed your appointment but couldn't auto-charge your card. Please contact {{center_name}} or update your saved card to settle the {{final_amount}} balance. Thanks!
Tips
- Tune the authorization buffer to your actual add-on spend. Review the Auto-pay report monthly and compare the "Additional amount for authorization" column against actual add-on amounts. If most guests never trigger the buffer, reduce it to lower the risk of issuer fraud flags. If guests frequently exceed the buffer, increase it to reduce manual top-ups at checkout.
- Notify guests before T&C changes take effect. If you update the Auto-pay terms and conditions text, send an email to enrolled guests explaining what changed and when. Guests who do not re-accept the new T&C will not be able to use Auto-pay until they do β proactive communication reduces front-desk friction on the day of the change.
- Use the Auto-pay report's status filter before busy periods. Filter by Failed and Pending at the start of each day to identify guests who may need a card update before their appointment. Reaching out proactively (via the retry link in the notification template) reduces no-shows and manual payment delays at checkout.
- Train front-desk staff on the two failure paths. Authorization failure (at check-in) and capture failure (at checkout) require different responses. Ensure staff know that the Retry action in the Auto-pay report is for transient failures, and Manual collect is for situations where the card is unlikely to succeed on retry (expired, stopped, insufficient funds).
- For stopped cards, always add-then-switch-then-delete. The three-step sequence (add new card β switch default β delete old card) is the only reliable way to restore Auto-pay for a guest whose card has been stopped. Editing the card in place does not clear the stopped state.
Troubleshooting
Auto-pay isn't appearing as an option for a guest who should have it. Confirm: organization-level Enable Auto-pay is on (Step 1), center-level Enable Auto-pay (Supported only on Zenoti Payments) is on (Step 2), and the guest has at least one saved card in their profile. If all three are true, ask the guest whether they accepted the T&C in CMA β opt-in is guest-driven, not auto-applied.
Authorization keeps failing for a specific guest. The most common cause is an expired or replaced card. Check the saved-card expiry date in the guest profile. If the card looks current, verify that the billing postal code on the saved card matches the cardholder's bank statement β a mismatched postal code is a frequent cause of repeated authorization failures. If the postal code is wrong, follow the add-then-switch-then-delete sequence described in When a card stops retrying rather than editing the card in place. If the issue persists across multiple guests, check the Zenoti Payments status page.
A corrected card keeps failing even after the guest updated their details. The card was likely stopped after repeated failures. Editing the card in place does not clear the stopped state. Follow the correct replacement sequence: add the new card, switch the membership or Auto-pay default to it, then delete the old card.
"Additional Amount for Authorization" results in declined transactions. The buffer is too large for the cardholder's risk profile β issuer fraud rules can flag large authorizations against small invoice amounts. Lower the buffer in Step 3. For most spa and salon centers, $25β$100 is sufficient.
WhatsApp messages aren't being delivered. WhatsApp templates must be approved by Twilio. Open Configuration > Notifications > Templates for email and text, open the Auto-pay template, select the WhatsApp channel, and check the template approval status. If pending, wait. If rejected, revise the content (avoid promotional language, include your verified business name, follow WhatsApp Business Policy) and re-submit. The other channels continue to deliver while WhatsApp is pending.
Captured amount is less than the total authorized. This is the buffer-release behavior β only the actual final invoice amount is captured; the unused additional-amount buffer is released back to the cardholder. The released amount returns to the cardholder's available balance within the issuer's hold-release window (typically 1β7 days).
Released vs Voided in the report β which one applies? Voided = the transaction was cancelled before settlement (still has a record in the audit trail). Released = the authorization hold was freed without any capture. Both result in zero net charge but happen at different lifecycle points; see Auto-pay status reference.
A recurring membership payment keeps failing after the guest updated their card. If the old card was stopped, updating the card in place does not clear the stopped state. Use the add-then-switch-then-delete sequence. Also confirm that the membership's default payment method has been switched to the new card β the system charges the membership's assigned default, not the guest's most recently added card.
If the problem persists
If Auto-pay is failing repeatedly for a guest or for a center after you've worked through Troubleshooting:
- Capture diagnostic detail. Note the affected invoice IDs, the exact status from the Auto-pay report, the saved-card last-four (not full PAN), and the time of the failure.
- Take the payment another way. Use the Manual collect action in the Auto-pay report, or process the payment via the standard desktop POS card flow. Keeping the guest checked out matters more than completing this specific Auto-pay attempt.
- Contact Zenoti Support. Open a support ticket with the diagnostic detail from step 1 plus the org-level and center-level Auto-pay setting state, and (for an org-wide issue) the start time of the impact so support can correlate with platform telemetry.