Transaction lifecycle
Every payment in Zenoti follows a standard lifecycle from initiation through settlement. Understanding the transaction lifecycle helps you interpret statuses in the payment dashboard, troubleshoot processing issues, and manage your reconciliation workflow.
Audience: Front desk staff and administrators who track payments from authorization through payout.
On this page
- Before you begin
- Steps
- Payment lifecycle stages
- What a transaction record contains
- Saved cards and payment tokens
- Authorization holds
- Failed authorizations
- Hard-declined cards and flagged payment accounts
- Recurring and batch collections
- Disputes and chargebacks
- Offline transactions
- Daily collections
- Settlement, payout, and reconciliation
- When a charge appears on the guest's bank statement but not in Zenoti
- Tips
- Troubleshooting
- Related articles
Before you begin
- Your center must have an active payment processor configured before any transaction can be authorized. For payment processor setup, see the Integrations category.
- Transactions appear in the payment dashboard after the processor responds to the authorization request.
- You need the following permission:
Permission: Available to staff with payment-configuration permissions; specific security object under verification.
Steps
Search for a transaction
- Open the payment dashboard for the center you want to review.
- Enter your search criteria. You can search on a minimum and maximum amount, a start and end date, the card type, and the last four digits of the card.
- Run the search. Zenoti validates the amount range and the date range, then returns matching transactions in a paginated grid. A search returns up to 1,000 transactions, so narrow the date or amount range if you expect more results than that.
- Export the results to Excel or CSV if you need them outside Zenoti.
Check an authorization hold
- Find the transaction in the payment dashboard.
- Review the authorization status. A transaction that shows an authorization but no capture still holds funds on the guest's payment method.
- Capture the transaction once the final amount is known β for example, after the tip is added at checkout.
- If the hold has already expired, re-authorize the payment method before capturing. See Authorization holds.
Review a failed authorization
- In the payment dashboard, filter to the date range in which the failure occurred.
- Read the failure reason recorded against the attempt. See Failed authorizations for the common reasons.
- Confirm the card number, expiry date, and billing address with the guest, and correct any data entry errors.
- Retry the payment, or collect using a different payment method.
- If the processor reported a hard decline, Zenoti flags the payment account and blocks further attempts on that card. Collect using a different payment method. See Hard-declined cards and flagged payment accounts.
Follow a refund to completion
Permission: Refund (under Invoices) β Required to issue a refund against an invoice.
Important: A refund cannot be reversed once the processor accepts it. Confirm the amount and the items you are refunding before you submit the request.
- Open the invoice and select the refund action. You can refund the full amount or a partial amount. With a partial refund, the original transaction remains in place with a reduced balance.
- Zenoti queues the refund and sends it to the payment processor.
- When the processor accepts the refund, Zenoti updates the refund status, records the refund in the refund history for the transaction, and updates the invoice balance.
- If the refund fails, Zenoti retries it automatically at increasing intervals and records each attempt.
For the full refund procedure, see Process payment refunds.
Worked example: A guest checks out for a $120.00 facial with $10.00 tax and adds a $20.00 tip. Zenoti authorized $120.00 when the appointment started, then captures $150.00 at checkout. If your center passes card fees to guests at 3%, the surcharge is calculated on the full $150.00 β not on the $120.00 service price β so the guest is charged $154.50. The capture settles in that night's batch, and the funds reach your bank account according to your processor's payout speed. If the guest disputes the charge six weeks later, the dispute appears on the reconciliation batch for the period in which the dispute settled, not on the batch that contained the original $154.50 capture.
Payment lifecycle stages
Authorization β When a guest presents a payment method, the system sends an authorization request to the payment processor. The processor verifies the payment method and places a temporary hold on the funds. The authorization result includes an authorization code, card details (brand, last four digits), and validation response.
Capture β After the service or sale is completed, the system captures the authorized amount. This converts the temporary hold into an actual charge. The capture includes the base amount, tip amount (if applicable), surcharge fee (if applicable), and any donation amount.
Settlement β The payment processor groups captured transactions into a settlement batch, typically at the end of each business day. The processor submits the batch to the card networks or banking system for processing.
Payout β Settled funds transfer from your merchant account to your designated bank account. Payout timing depends on your processor and the configured payout speed.
You can track any transaction through these stages in the payment dashboard.
Important: When your center passes card fees to guests, the surcharge is calculated on the total transaction amount including tips and taxes β not on the base amount alone. In the United States, surcharges apply to credit card transactions only. Surcharges also apply to recurring collections, at the rate that is active on the collection date. See Configure surcharges to pass credit card fees to guests.
What a transaction record contains
Zenoti stores a record for every processor transaction. The following details are available for each one:
| Detail | What it shows |
|---|---|
| Transaction ID | The unique identifier for the transaction. |
| Amount | The amount authorized or captured. |
| Transaction type | Whether the entry is an authorization, capture, refund, or void. |
| Status | The current stage of the transaction. |
| Payment processor | The processor that handled the transaction. |
| Card details | The card brand and the last four digits. Full card numbers are never stored in Zenoti. |
| Authorization status | Whether the processor approved, declined, or is still holding the authorization. |
| Tip amount | The tip collected as part of the transaction. |
| Surcharge fee | The card fee passed to the guest, when your center is configured to pass card fees. |
| Secondary markup fee | An additional fee recorded when your organization uses the Surcharge on IC+ billing model. |
| Donation amount | Any donation collected as part of the transaction. |
| Settlement batch | The batch in which the transaction was submitted for settlement. |
| Business unit | The business unit the payment was routed to, when your organization routes payments by business unit. |
Zenoti also stores the processor's API response against each transaction. Support and finance teams use this record when investigating a payment or explaining a reconciliation difference.
Transaction status updates automatically as the processor confirms each stage β you do not need to refresh or re-enter anything for a status to move forward.
For more on the secondary markup fee, see Surcharge on IC+ (Secondary Markup) Billing Model.
Saved cards and payment tokens
When a guest saves a card for future use, the processor issues a token and Zenoti stores that token instead of the card number. The token record keeps the processor, the card brand, and the last four digits so front desk staff can identify the card at checkout. Zenoti logs each token request for audit purposes.
For stored payment account management, see the Integrations category.
Authorization holds
Pre-authorization holds reserve funds on a guest's payment method before the final amount is known. This is common for services where the final amount may include tips or additional items. The system tracks authorization holds separately and releases them when the final capture occurs or when the hold expires.
Note: Authorization hold durations are set by the card issuer, not by Zenoti. If a hold expires before capture, the system must re-authorize the payment method.
Failed authorizations
When an authorization fails, the system records the failure separately for monitoring. Common failure reasons include:
- Insufficient funds
- Invalid card number or expired card
- Card issuer declined the transaction
- Address Verification System (AVS) mismatch
Review failed authorizations in the payment dashboard to identify patterns that may indicate data entry issues or card problems.
Hard-declined cards and flagged payment accounts
Some declines are permanent β for example, a closed account or an invalid card number. When the processor reports a hard decline, Zenoti flags the guest's payment account so that staff and automated collections stop attempting to charge it.
Availability: Hard-decline flagging requires the organization-level payment account flagging setting and a supported processor: Adyen, Stripe Connect (US, Australia, Canada, UAE, UK, and multi-merchant configurations), or Stripe Connect Express (same regions). Other processors do not currently flag hard declines.
What happens once an account is flagged:
- Zenoti does not send transactions on a flagged card to the payment gateway. The attempt is blocked before it reaches the processor, so no further decline is recorded against the guest.
- Dunning retries stop for any recurring or scheduled payment linked to the flagged account. Membership billing and other recurring collections on that card pause until the guest provides a different payment method β there is no automatic recovery.
- The flag appears against the saved card so front desk staff can identify it before attempting a collection.
Two independent settings on the Other payment settings tab of the processor configuration (Configuration > Payments > Process payments > Payment processor onboarding) control what else happens while an account is flagged: whether staff can still run a manual collection against the flagged account, and whether Zenoti sends a system-generated email to the guest. The email is sent only when the flagged account is linked to a scheduled payment, and its content is not editable.
The flag does not clear on its own after a set period. It clears when the guest replaces the card with a new payment method, or when an administrator or a staff member with the appropriate permission records a resolution.
For the full configuration procedure, see Flag payment accounts for hard declines.
Recurring and batch collections
Not every transaction starts at the point of sale. Recurring and batch collections follow the same authorization, capture, settlement, and payout stages, but they are initiated by Zenoti or by an external system rather than by a guest at the front desk.
Recurring collections. Zenoti checks for recurring payments whose next collection date has arrived and collects each one using the payment method on file. On success, Zenoti creates the invoice for the collection and sets the next collection date. On failure, the collection enters dunning: Zenoti schedules the next retry according to your dunning rules and changes the collection status as your rules specify. If the payment method is a gift card with an insufficient balance, the collection fails and follows the same dunning rules. Cash and custom payment methods create an offline record for manual collection instead of contacting a processor. See Configure recurring payment rules.
Batch collections. An external system can submit a batch of collections to Zenoti. Zenoti accepts the batch, creates a payment entry for each request, and processes the payments in the background. ACH payments follow a separate schedule from card payments. The batch is marked complete once every payment in it has reached a final state. Each payment in a batch moves through its own status independently: from Initiated (the entry has been created) through Pending (queued for processing), Processing (the request is with the processor), Success or Failed (the processor has responded), and Cancelled, Refunded, or Chargeback if those actions occur later. See Manage batch payments and Track ACH payments.
Disputes and chargebacks
When a guest disputes a charge with their card issuer, the dispute becomes visible on the reconciliation line for the affected payout, with a status of Chargeback. If the dispute is later reversed in your favor, the line shows Chargeback Reversed.
Disputes are recorded in the period in which they settled, not in the period of the original transaction. A dispute raised against a transaction from a previous month appears on the current period's reconciliation batch β it does not change a batch you have already reconciled.
If an invoice is fully refunded including provider tips, the tip adjustment is deducted from the provider's MyZen Wallet balance and appears in the reconciliation report as a negative line item against the original payout.
To respond to a dispute, see Defend payment disputes.
Offline transactions
In scenarios where online connectivity is temporarily unavailable, the system can record offline credit card transactions. These transactions are queued and processed when connectivity is restored. Offline transactions carry additional risk because authorization is deferred.
Daily collections
The system tracks daily payment collections for each center, providing day-closure reporting that summarizes all transactions processed during the business day. This data supports register closure and end-of-day balancing.
Settlement, payout, and reconciliation
Reconciliation is the final stage of the transaction lifecycle. It matches the payouts your processor sends to the deposits that land in your bank account, so you can confirm that every settled transaction was paid out.
Two preferences govern reconciliation, and you can set them for the organization and for individual centers:
- Settlement frequency β Weekly or Monthly. This determines when payouts roll into a reconciliation batch.
- Automatic Approval β Determines whether a matched batch is approved automatically or held for manual review.
Important: Reconciliation runs one period behind. The current week's transactions are reconciled in the following week, and the current month's transactions in the following month. This reflects the time processors need to settle payouts to the bank β it is not a limitation you can bypass in the interface.
Each batch shows one of four states, and the action available on the batch row depends on that state:
| Batch state | What it means | Action available |
|---|---|---|
| Reconciliation Pending | The batch is ready but reconciliation has not started. | Start |
| Not Reconciled / Not Reviewed | Reconciliation is in progress and lines are still unmatched. | Review |
| Reconciled / Not Reviewed | Lines are matched but no one has reviewed the batch. | Payout Details or Collection Details |
| Reconciled / Reviewed | The batch is matched and reviewed. | Payout Details or Collection Details |
Each mismatched line shows a reason that Zenoti determines from the underlying transaction data. Common causes include processing fee deductions, partial refunds, disputes, currency-conversion differences, and tip reversals on refunded invoices. This is not a fixed list β when Zenoti cannot determine the cause, the line shows "unable to determine the exact reason for the discrepancy" and you can mark the line reconciled with your own notes.
Permission: Reconcile Payments (under Payments) β Required to open reconciliation batches.
For the full procedure, see Reconcile payment transactions.
When a charge appears on the guest's bank statement but not in Zenoti
Occasionally, an online purchase can fail after the payment processor has captured the payment but before Zenoti has created the invoice. In this situation, the guest's bank statement shows a charge, but no corresponding record exists anywhere in Zenoti β not on the guest's Payments tab and not in the digital payments report.
This is called an orphan charge. It is not a Zenoti processing error you can resolve from the front desk, because there is no invoice in Zenoti to refund against.
How to confirm the charge is absent from Zenoti:
- Open the guest's profile and check the Payments tab. Look for any transaction that matches the amount and date the guest reports.
- Open the payment dashboard and run a transaction search. Filter by the last four digits of the card and set the date range to cover the window in which the guest says the charge appeared.
- If neither search returns a matching record, the charge is confirmed as absent from Zenoti.
What to do next:
Once you have confirmed that no matching record exists in Zenoti, raise the issue with Zenoti Support. Because there is no invoice in Zenoti to refund against, the refund must be initiated through Support rather than through the standard refund workflow. Provide Support with the guest's name, the card's last four digits, the approximate transaction date, and the amount the guest's bank is showing.
Note: Do not ask the guest to dispute the charge with their bank before contacting Zenoti Support. A bank dispute (chargeback) triggers a separate process that may delay resolution and result in additional fees. Work through Support first.
Tips
- Search on the last four digits of the card together with a narrow date range to find a specific transaction quickly, rather than scrolling a full day's list.
- Export search results to CSV before your month-end close so you keep a snapshot of exactly what you reviewed.
- When a card is declined at checkout, check whether the payment account is flagged before you retry. Retries on a flagged account are blocked in Zenoti and never reach the processor.
- If your settlement frequency is Weekly, reconcile every week rather than waiting for month-end. The one-period lag means the current week's transactions only become available for reconciliation in the following week.
- Ask guests to replace a card as soon as it hard-declines. Membership and other recurring billing stays paused until a different payment method is on file.
Troubleshooting
| Problem | What to check |
|---|---|
| A transaction does not appear in search results. | Confirm the date range covers the transaction date and that the amount range includes the captured total, including tip and surcharge. A search returns a maximum of 1,000 transactions β narrow the criteria and search again. |
| An authorization succeeded but the funds were never captured. | The hold may have expired before capture. Card issuers set hold durations, not Zenoti. Re-authorize the payment method, then capture. |
| The same guest's card is declined every time, including on retries. | The processor may have reported a hard decline, which flags the payment account and blocks further attempts. Collect using a different payment method and ask the guest to replace the saved card. |
| A refund has not reached the guest. | Check the refund history on the transaction. Failed refunds retry automatically at increasing intervals, and each attempt is recorded. The time a completed refund takes to appear on the guest's statement is set by the card issuer. |
| The payout amount does not match the sum of the day's transactions. | Processing fees, surcharges, refunds, and disputes are deducted before payout. Open the reconciliation batch for the period and review the mismatched lines and their reasons. |
| An offline transaction is missing from the payment dashboard. | Offline transactions are queued until connectivity is restored and are only processed at that point. Confirm the center is back online, then check again. |
| A recurring collection did not run on its due date. | Check whether the linked payment account is flagged β dunning retries and scheduled payments stop on a flagged account. If it is not flagged, review your dunning rules for the retry schedule and collection status changes. |
| A batch payment is stuck in Initiated or Pending status. | Batch payments move through statuses independently. An entry that remains in Initiated or Pending may be waiting for processor capacity or for the ACH processing window. If the status has not advanced after one business day, contact Zenoti Support. |
| A guest's bank shows a charge but no record exists in Zenoti. | Check the guest's Payments tab and run a transaction search in the payment dashboard using the card's last four digits and the date range. If no record is found, contact Zenoti Support β there is no invoice in Zenoti to refund against, so the refund must be handled through Support. Do not ask the guest to dispute the charge with their bank before contacting Support. |