ZenotiHelp

Recover failed transactions

ZTZenoti Docs Team Updated August 20, 2026 4 min readGuide

Failed card transactions can occur due to network issues, declined cards, processor errors, or other problems. Zenoti tracks failed transactions and provides tools to review and retry them. The specific failure modes, retry semantics, and recovery options depend on the processor β€” always cross-check the processor-specific article (for example, Processor: AirPay, Processor: FreedomPay) for the authoritative list.

Before you begin

Permission: You need payment management permissions to view and retry failed transactions.

Common failure modes

Failure mode Typical cause User-visible symptom Resolution
Processor unreachable Zenoti or the POS (Point of Sale) cannot reach the processor's API (network, DNS, TLS). "Communication error" on the terminal or HPP (Hosted Payment Page). Check outbound HTTPS (port 443). Confirm the processor's status page. Retry when connectivity is restored. The invoice stays open.
Authentication expired API keys or OAuth tokens rotated on the processor side without a Zenoti update. Every attempt fails with an auth error. Re-copy credentials from the processor portal into Zenoti.
Card declined Issuer decline (insufficient funds, block, fraud hold). POS shows issuer decline. Guest retries with another card or method. No automatic retry for a one-off charge.
Expired / reissued card Stored card is past expiry or was reissued. Decline on the next scheduled charge. Depends on processor β€” see Update card details automatically. Stripe proactively updates; Element Express updates reactively after the decline; most other processors require manual re-entry.
Amount out of range Amount is below or above processor / scheme limits. Amount-limit error. Split or use a different payment method.
Currency mismatch Transaction currency not activated on the MID (Merchant Identifier). Currency error. Confirm center currency vs processor activation.
Settlement failure Transaction approved but missing from the processor's settlement report. Discrepancy at reconciliation time. Raise with the processor using the transaction ID; do not re-charge.
Network timeout mid-flow Approval occurred but the response never reached Zenoti. Invoice stays open; transaction may appear as "initiated." For online flows (AirPay, eGHL, JusPay, etc.) Zenoti polls for status for a processor-specific window before marking failed. For terminal flows, check the terminal's transaction log or the processor's merchant portal before re-charging.

Steps

Review failed transactions

  1. Navigate to Configuration > Reports > Payment Reports or the relevant transaction log.
  2. Filter for transactions with a Failed status.
  3. Select a failed transaction to view the error details returned by the payment processor.
  4. Review the error code and description to determine the appropriate action.

Retry a failed transaction

  1. In the failed transaction record, select Retry Payment.
  2. Confirm the retry.
  3. Zenoti re-submits the charge to the payment processor.
  4. If the retry succeeds, the invoice is updated to Paid.
  5. If the retry fails again, review the new error message and take corrective action.

Update payment details

If the failure was due to expired or invalid card details:

  1. Contact the guest to update their payment information.
  2. Navigate to the guest's profile and update the stored card under the Cards tab.
  3. Once the card is updated, retry the transaction.

Note: If your processor supports automatic card updating (Stripe or Element Express/Worldpay), expired or reissued cards may be updated automatically. For Element Express, the card update happens after the initial decline β€” the card is updated for the next charge. Check the guest's Cards tab to see if updated details have already been applied. See Update card details automatically for details.

Refund a mistaken charge β€” both perspectives

If a transaction was processed incorrectly, issue a refund from the invoice or the guest's payment history. Refund behaviour is dual-system:

System What happens
Zenoti A negative payment line appears on the invoice; Collections report shows a refund row referencing the original transaction.
Processor A separate refund record is created against the original transaction; it appears on the processor's merchant portal / settlement report. Match key: processor transaction ID or Zenoti invoice number.

Recover when the invoice is open vs closed

Invoice state What you can do
Open (unclosed) Retry, replace the failed line with a new payment, or void / refund depending on the processor.
Closed (posted but the charge later reversed β€” for example, ACH (Automated Clearing House) bounce or settlement failure) Reopen the invoice if your permissions allow, post a compensating refund line, and chase the guest for an alternative payment. The original line is preserved for audit.

Reconciliation and failed transactions

When triaging failed or ambiguous transactions:

Source Report / view Match key
Zenoti Collections report (filter by processor and status) + Failed transactions log Processor transaction ID + Zenoti invoice number
Processor Processor merchant portal transaction / settlement report Same fields

Recommended cadence: daily for any processor that accepts direct-debit, BNPL (Buy Now, Pay Later), or settlement-delayed payments β€” these can reverse after apparent success.

Retry schedule for recurring payments

For recurring payment failures (memberships, packages), Zenoti may automatically retry the charge according to the retry schedule configured for your organization. See Process recurring payments for the full dunning behaviour.

Tips

  • Address declined cards promptly to avoid service disruption for guests with active memberships.
  • Regularly review failed transaction reports to catch patterns such as expired cards before they affect guest experiences.
  • For processors without auto-card-update support (most non-Stripe, non-Element-Express processors), a proactive "card expiring soon" outreach is the best protection.
Was this article helpful?
Your feedback helps us improve our documentation.