ZenotiHelp

Flag payment accounts for hard declines

ZTZenoti Docs Team Updated September 17, 2026 11 min readGuide

When a payment processor returns a hard decline (the card is closed, invalid, or otherwise unusable), Zenoti flags the saved payment account so that subsequent retries and scheduled payments are suppressed. Use this configuration to control whether front-desk staff can still attempt manual collections on a flagged card and whether the guest is automatically notified.

Audience: Organization administrators who configure payment behavior for the organization.

Note: For conceptual background on how payments are processed and tracked, see Zenoti payments platform.


On this page


Before you begin

Availability: Hard-decline flagging requires the organization-level payment-account flagging setting and a supported processor β€” Adyen, Stripe Connect, or Stripe Connect Express. See Supported processors.

Permission: Configure Payment Settings (under Payments) β€” Required to view and change hard-decline flagging behavior. Manage Payment Settings (under Payments) also opens this page.

  • Hard-decline flagging must be turned on for your organization. Contact Zenoti Support if the settings are not visible.
  • Your processor must be on the supported list (see Supported processors). On unsupported processors, hard declines still occur, but the flagging feature does not apply.
  • Decide in advance whether front-desk staff should be able to charge a flagged card in person. That decision drives which of the two toggles you turn on.

What hard-decline flagging does

A hard decline is a card-issuer response that indicates the card cannot be used (closed account, expired card, stolen card, restricted card, invalid card details). Hard declines differ from soft declines, where the issuer might approve a retry (insufficient funds, temporary processing issue).

When Zenoti detects a hard decline on a saved payment account:

  • Zenoti flags the account.
  • Subsequent dunning retries on that account are suppressed β€” Zenoti does not send the card to the processor for further attempts.
  • Membership and other recurring billing on the flagged card is paused β€” there is no automatic recovery.
  • Front-desk attempts at the POS are blocked at the application layer unless the manual-collections toggle is on (see Steps).
  • Optionally, the guest receives an email about the flag (see Steps).

The flag persists on the saved payment account until it is resolved (see Resolve a flagged account).

Steps

Open the hard-decline settings

  1. Go to Configuration > Payments > Process payments > Payment processor onboarding, open your processor's configuration, and select the Other payment settings tab.
  2. Locate the settings that control what happens when a payment account is flagged after a hard decline. These settings appear only when payment-account flagging is turned on for your organization and at least one supported processor is configured.

Review the two toggles

The hard-decline configuration exposes two independent toggles.

Toggle Effect when ON Effect when OFF
Enable manual collections on flagged payment account Front desk can charge a flagged saved card from the POS for in-store collections. Dunning re-attempts and scheduled-payment use remain suppressed. The flagged saved card is unusable for any payment attempt at the POS; front desk must collect via a different payment method.
Send an email to guest when their payment account is flagged When a hard decline causes a flag, the system sends a system-generated email to the guest. The email fires only when the flagged account is linked to a scheduled (recurring/membership) payment. No email is sent on flag.

Note β€” manual collections is a plain override. The toggle is on or off. There is no warning banner, manager-approval flow, or acknowledgment step at the POS β€” when the toggle is on, the flagged card appears the same as any other saved card from the front-desk view, with the indicator described under Indicator. When the toggle is off, the flagged card cannot be selected.

Note β€” the email is system-generated. The email content is not a configurable template; you cannot edit or rebrand it from this settings page.

Allow manual collections on a flagged card

Turn this on when you want front-desk staff to be able to complete an in-store sale on a card that has already hard-declined, rather than being blocked from selecting it.

  1. Turn on Enable manual collections on flagged payment account.
  2. Select Save.
  3. Confirm the behavior at the POS: the flagged card remains selectable for in-store collection, while dunning retries and scheduled payments on that card stay suppressed.

Notify guests when their payment account is flagged

Turn this on when you run recurring memberships or other scheduled payments and want the guest alerted as soon as automatic billing stops.

  1. Turn on Send an email to guest when their payment account is flagged.
  2. Select Save.
  3. Remember the trigger condition: the email is sent only when the flagged payment account is linked to a scheduled payment. A one-off card-on-file decline does not generate the email.

Choose the behavior combination for your business

The two toggles are independent, which produces four operating combinations.

Manual collections Send guest email What happens at the POS when a card hard-declines
OFF OFF Card silently flagged; no email sent; POS attempts on this card blocked. The guest discovers the issue at next checkout.
OFF ON Card flagged; if linked to a scheduled payment, guest emailed; POS attempts blocked. Guest may still discover the issue at non-scheduled checkout but is alerted in advance for the scheduled flow.
ON OFF Card flagged but charge-able at POS; no email; the guest discovers the issue only when staff explains why the card was flagged.
ON ON Card flagged; if linked to a scheduled payment, guest emailed; charge-able at POS for in-store collections.

The settings are configured at the organization or center level (verify scope per your org).

Worked example. Serenity Day Spa runs recurring memberships on Stripe Connect Express. The organization turns on Send an email to guest when their payment account is flagged and leaves Enable manual collections on flagged payment account off. In March, a guest's Visa ending 4242 is closed by the issuing bank. The next membership collection of $89.00 returns a hard decline, Zenoti flags the card, and dunning retries stop. Because the flagged card is linked to a scheduled payment, the guest receives the system-generated email. When the guest arrives for a facial two days later, the flagged Visa cannot be selected at the POS, so the front desk collects on a different card and saves that card to the guest profile β€” which restores automatic collection for the membership.

Indicator

A flagged card is visually distinguished in both the guest profile and POS card-selection UI. When the manual-collections toggle is OFF, the flagged card is disabled in the POS selector; when ON, it appears with a visual indicator alongside other selectable cards.

What you should observe:

  • In the guest profile, the saved card row visibly distinguishes flagged cards from unflagged ones.
  • In the POS card selection, the flagged card is either disabled (when the manual-collections toggle is OFF) or shown with an indicator alongside other selectable cards (when the toggle is ON).

Real-time decline experience

When a card hard-declines during a live POS transaction, the front-desk staff sees the same processor decline path as any other failed authorization β€” an error message returned by the processor. Zenoti does not surface a real-time "this is a hard decline" badge during the live transaction. The flag is applied after the decline (so that subsequent retries and scheduled payments respect it), not during the live attempt.

If the only saved card the guest has is the one that hard-declined and the manual-collections toggle is OFF:

  • The card is unusable for any payment attempt going forward (immediately after the decline).
  • Front desk must collect via a different payment method (a different card the guest has on hand, cash, alternative payment).

Resolve a flagged account

A flagged card does not auto-resolve. Two paths return the guest to a working state:

  1. Guest adds a new payment method. New cards are unflagged and immediately usable. The flagged card remains in the saved-cards list with the flagged indicator (so future investigations have an audit trail).
  2. Guest contacts the issuer bank. If the card was hard-declined for a recoverable reason (for example, reissued under the same number after a temporary freeze), the guest may want to provide the new card details from their bank. Add the new card details as a new payment method in Zenoti β€” the prior flagged record is not unflagged automatically.

Front-desk script

When a flagged card is encountered at the POS:

Step Action
1 Inform the guest that the card on file isn't currently usable for payment. Avoid card-issuer specifics; the system does not surface the decline reason in real time.
2 Offer alternatives β€” a different card, cash, or another supported payment method.
3 Encourage the guest to add a new payment method (if a different card is available). Adding a new method through the guest profile is the primary resolution.
4 If the guest is on a recurring/membership billing plan, remind them that automatic billing is paused until they update the payment method.
5 (Manager) Document the interaction in the guest profile for context on future visits.

Impact on memberships and recurring billing

This is the highest-stakes consequence of a hard decline for membership-based businesses. When a saved card linked to a membership is flagged:

  • The membership's recurring billing stops attempting automatic collection on the flagged card.
  • The membership status is not automatically suspended by the flag β€” the membership remains active in the platform's terms.
  • Charges that should have been collected (per the membership schedule) accrue as outstanding in your usual billing flow until the guest provides a new payment method.

Configure your membership-collection workflow to surface members whose primary card is flagged. The platform does not currently include a built-in "flagged-cards report" in this settings page β€” see Bulk management.

Supported processors

Hard-decline flagging is currently supported on:

  • Adyen
  • Stripe Connect (US, Australia, Canada, UAE, UK, MultiMid variants)
  • Stripe Connect Express (US, UK, Australia, Canada, UAE, MultiMid variants)

Other processors do not currently surface hard-decline flagging. The flag-detection logic is processor-specific (each processor returns a slightly different set of decline indicators) and adding a processor requires explicit enablement at the platform layer. Contact Zenoti Support if your business uses a processor not on the list and you need hard-decline flagging.

Decline reason codes

Payment processors return reason codes (for example, "lost card", "stolen card", "expired card", "card not activated", "restricted card", "do not honor"). Zenoti's hard-decline flagging is a flag/no-flag classification β€” it does not currently surface the per-decline reason on the saved card.

To investigate why a specific card was flagged:

  • Check your processor's dispute or decline log directly (Adyen Customer Area, Stripe Dashboard, and similar).
  • Use Payment dashboard & transaction search to locate the failed transaction by amount, date, card logo, or last four digits.

Interaction with card-auto-update

Account Updater checks with the issuer for updated card details when a payment is refused. The following behaviors apply:

  • A flagged card is not automatically retried by the dunning system.
  • A new card added through Account Updater appears as a new, unflagged payment method.
  • A successful update on a flagged card does not retroactively clear the existing flag.

For configuration details, see Set up Account Updater.

Bulk management

The hard-decline settings page is configured per organization or per center. Identifying flagged accounts across many guests is not currently a built-in capability of this page.

For now:

  • Use existing reporting (member dashboards, recurring payment audit reports) to identify members with paused billing.
  • Contact Zenoti Support if you need a bulk export of flagged accounts.

Resolve hard declines (summary)

Action Who When
Add a new payment method Guest (in profile or with front-desk help) Primary resolution. The new method is usable immediately.
Contact issuer bank for replacement card Guest When the card was reissued or the issue is recoverable.
Communicate the decline situation Front desk staff At the POS when a flagged card is encountered. Use the Front-desk script.
Pause membership billing manually Manager or billing admin When a flagged primary card affects a recurring membership and the guest needs more time to provide a replacement.

Tips

  • If you run recurring memberships, turn on the guest email. Dunning stops the moment a card is flagged, so without the email the first signal your business gets is a missed collection.
  • Leave manual collections off when your priority is capturing a fresh, working payment method at the counter β€” the blocked card forces the conversation.
  • Turn manual collections on in high-volume walk-in centers, where blocking a saved card mid-checkout costs more than the risk of a second decline.
  • Review recurring-collection reporting on a fixed cadence (weekly works for most centers) so flagged members are caught before several billing cycles are missed.
  • Before rolling the setting out across a multi-center organization, confirm every center's processor is on the supported list β€” centers on other processors will not see flagging behavior.

Troubleshooting

Symptom Likely cause Resolution
The hard-decline settings are not visible in Payment settings. Payment-account flagging is not turned on for the organization, or the configured processor is not supported. Confirm your processor against Supported processors. If the processor is supported, contact Zenoti Support to turn on payment-account flagging.
A card was hard-declined but the guest received no email. The email toggle is off, or the flagged account is not linked to a scheduled payment. Turn on Send an email to guest when their payment account is flagged. Note that the email fires only for accounts linked to recurring or scheduled payments, not for one-off card-on-file declines.
Front desk cannot select the guest's saved card at the POS. The card is flagged and Enable manual collections on flagged payment account is off. Collect on a different payment method and save a new card to the guest profile, or turn on manual collections if in-store charges on flagged cards should be allowed.
A membership stopped billing with no failed-payment follow-up. The linked card was flagged, so dunning retries were suppressed. Open the guest profile, check saved cards for the flagged indicator, and ask the guest to add a new payment method.
The guest's bank reissued the card, but payments still fail. The flag stays on the original saved card record; it is not cleared automatically. Add the reissued card as a new payment method rather than expecting the flagged record to recover.
You cannot tell why a specific card was flagged. Zenoti records the flag, not the processor's per-decline reason code. Look up the failed transaction in the payment dashboard, then check the decline detail in your processor's own dashboard.
Was this article helpful?
Your feedback helps us improve our documentation.