ZenotiHelp

Manage stored payment accounts

ZTZenoti Docs Team Updated October 19, 2026 10 min readGuide

Stored payment accounts let guests save their card details for future transactions. Zenoti stores only a secure token from the payment processor β€” never the actual card number. This makes future payments faster and enables recurring billing, online booking payments, and membership collections.

Audience: Front-desk staff who add, charge, and remove stored accounts for guests.


On this page


Before you begin

Permission: You need guest management or billing permissions to view and manage stored payment accounts.

Processor prerequisites

Not every processor supports stored payment accounts. Check the capabilities table in your processor's article before relying on this feature. Processors with stored-account support include: Adyen, AdyenDirect, Stripe, Stripe Connect, Element Express (Worldpay), FreedomPay, BBVA, Walletdoc, Fiserv, Moneris Canada, Payment Express, Xendit, EzyPay, Amazon Payment Services, Zuora (ZPay Lite), and MSLCC / MSLDD. Processors that do not support card-on-file include: AirPay, Plutus (PineLabs), eGHL, JusPay, EBS, QNB, Checkout.com, Payworks, CaisseAP, and Sunbit.

Processor capabilities to check

Four separate capabilities govern what you can do with stored accounts. Verify each one for your processor before you design a workflow around it.

Capability What it enables Where to verify
Stored accounts The processor can tokenize a card and keep it on file for later charges. The processor list above, and the capabilities table in your processor's article.
Save from a terminal Staff can create a stored account by swiping, inserting, or tapping the card on a payment terminal instead of keying the details in. Your processor's article and the article for your terminal model.
Global tokenization The stored token can be reused across processor instances in the same organization, which is what makes card migration possible. The tokenization model table below.
Automatic card updating A reissued card can be refreshed without the guest re-entering it. Automatic card updates, below.

Tokenization model

Tokenization type Meaning Processors
Local token The token works only within the processor that issued it; stored cards cannot be moved to another processor without re-enrolment. Most processors.
Global tokenization The token is shared across multiple processor instances in the same Zenoti organization (subject to processor rules). Adyen, AdyenDirect, Stripe Connect, Fiserv, Walletdoc, BBVA.

What Zenoti stores

Each stored account is linked to one guest and to the processor that issued the token. Alongside the token, Zenoti records:

  • Card brand β€” the network that issued the card, such as Visa, Mastercard, Discover, or American Express.
  • Expiry month and year β€” used to anticipate when the card will stop working.
  • Payment identifier β€” the last four digits, so staff and guests can tell one stored account from another.
  • Decline status β€” whether the most recent charge against this account was declined by the issuer.
  • Authorization status β€” whether the processor has authorized the account for use.
  • Funding source β€” the funding type the processor reports for the card.
  • Web-sharing capability β€” whether the account can be used for Webstore purchases.

Add a stored payment account

Add a card at checkout

  1. During checkout in the POS (Point of Sale) window, select Credit/Debit Card as the payment method.
  2. Process the payment.
  3. When prompted, select Save card for future use.
  4. The card is tokenized and stored against the guest profile.

Add a card from the guest profile

  1. Navigate to the guest profile.
  2. Select the Cards tab.
  3. Select Add Card.
  4. Enter the card details or swipe / tap the card on the terminal.
  5. The card is tokenized and stored.

Save a card automatically after the first transaction

Where your organization is configured to save cards automatically, a guest's card is stored after the first successful transaction without a separate prompt at checkout. Staff do not take any extra step, and the resulting stored account behaves exactly like one added manually β€” it can be charged, set as default, shared with the Webstore, and removed in the usual way.

Tip: Tell guests when their card is being kept on file, even when the save happens automatically. Guests who did not expect it are the most common source of removal requests.

Worked example: Dana Mercer pays a $120 invoice with a Visa ending 4242 and asks to keep the card on file for a monthly membership. The front-desk operator processes the payment and selects Save card for future use. Zenoti stores a token along with the brand (Visa), the payment identifier (4242), and the expiry (09/2027). In August 2027 the issuer reissues the card with a new expiry of 09/2030. The processor returns the new details, Zenoti updates the stored account in place, and the membership collection on 1 September 2027 runs against the new expiry without anyone at the center re-entering the card.

Share a stored account with the Webstore

A stored account can be made available for Webstore purchases, so a guest who saved a card at the front desk can reuse it when booking online.

Availability: Requires the Share payment account organization setting.

When the setting is off, stored accounts remain usable at the center but are not offered as a payment option in the Webstore.

View stored payment accounts

  1. Navigate to the guest profile.
  2. Select the Cards tab.
  3. All stored accounts are listed with the card type, last four digits, and expiry date.

Charge a stored account

  1. Open the guest's invoice in the POS window.
  2. Select Credit/Debit Card as the payment method.
  3. Select the stored account you want to charge from the guest's cards on file.
  4. Process the payment. Zenoti sends the stored token to the processor β€” no card details are re-entered, and the card does not need to be present.
  5. If the issuer declines the charge, the decline is recorded against the stored account. See Recover failed transactions.

Set a default card

  1. Navigate to the guest profile Cards tab.
  2. Select Set as Default next to the card you want to use as the primary payment method.
  3. The default card is used for recurring charges and quick checkout.

Remove a stored payment account

  1. Navigate to the guest profile.
  2. Select the Cards tab.
  3. Find the card to remove.
  4. Select Remove.
  5. Confirm the removal.

Note: Zenoti will not remove a card that still has membership, package or other scheduled collections due on it β€” it shows Unable to remove the payment account as it is linked to scheduled payments. Use Replace on the saved card instead; Zenoti moves those commitments to the new card. See Manage guest gift cards tab.

Guest-managed stored accounts

Guests can view and manage their own stored accounts from the Webstore and the customer mobile app (CMA), where your organization has those channels enabled. A card a guest adds online is tokenized by the same processor and produces the same kind of stored account as a card added at the front desk.

The removal restriction applies in every channel: a guest cannot delete a card that still has scheduled collections due on it, and must replace it instead.

Automatic card updates

Some payment processors can refresh a stored account when the guest's bank reissues the card β€” for example, with a new expiry date or a new card number. This reduces declined payments caused by stale card details.

Two different mechanisms exist, and they work in opposite directions. Do not assume behaviour from one applies to the other.

Processor Mechanism Trigger
Stripe, Stripe Connect Stripe's own built-in card updating service Proactive β€” runs ahead of the next charge
Element Express (Worldpay) Zenoti's account updater service Reactive β€” runs after a stored-account charge is declined
Xendit Zenoti's account updater service, where enabled by configuration Reactive
All other processors Not supported β€”

Stripe and Stripe Connect: proactive updates

Stripe obtains updated card details directly from the card networks and pushes them to Zenoti in the background. No Zenoti scheduled job is involved, and no decline is needed to start the process β€” the refresh happens before the next charge is attempted. Staff take no action and see no prompt.

Element Express (Worldpay): reactive updates

The Zenoti account updater runs only after a charge against a stored account is declined, and only for specific decline reasons returned by the processor: a straight decline, an expired card, a pickup instruction, or invalid card information. Any other decline reason does not mark the account for update.

When the account is marked, a daily scheduled job sends it to the processor's card-updater service and then polls for a response. Responses are not instantaneous β€” Zenoti waits at least 10 hours between status checks on the same request.

Only charges against stored accounts trigger this process. Manually keyed card entry, walk-in retail card payments, and gift card transactions never mark an account for update.

Which card networks are updated

Update requests are submitted for Visa, Mastercard, and Discover cards only. American Express is explicitly excluded, and JCB, UnionPay, and Diners Club are not supported by the updater service. For those brands, a reissued card must be re-enrolled by hand.

The card security code (CVC) is never part of an update. Whether a given transaction needs a CVC at all is determined by the card network and your processor configuration, not by a Zenoti setting, so the absence of a refreshed CVC does not by itself block a stored-account charge.

What happens when an update succeeds

A successful update is permanent. Zenoti overwrites the guest's stored account with the new expiry month and year, the new last four digits, and the new card brand, and records the before-and-after details in an internal audit log. The stored account keeps working for recurring collections and online purchases without any front-desk intervention.

The processor may also report that the card is still valid and needs no change, that the issuer has closed the account, that the cardholder must be contacted directly, that the submitted card data did not match its records, that the service is not permitted for the card, or that the request itself was rejected. Only the "updated" outcome changes the stored account.

What happens when an update fails

Updates are silent. Zenoti does not notify the guest or the front desk when a card is updated, when an update fails, or when the processor asks for the cardholder to be contacted. Internal audit logs and telemetry are the only record.

If the processor returns no updated details within 15 days, Zenoti marks the request as failed. The stored account keeps its original, outdated details, and later charges against it can be declined again by the issuer. There is no automatic retry and no dunning process for the card update itself β€” recovering the payment is a separate workflow. When the processor asks for the cardholder to be contacted, the account is flagged for manual review, but again no notification is sent.

Because of this, treat repeated declines on a stored account as the signal to contact the guest. For the full behaviour of both mechanisms, see Update card details automatically.

Troubleshooting

Failure mode Typical cause Resolution
Token orphaned after processor change The processor was disabled or replaced; tokens no longer resolve. Re-enrol the card with the new processor, or run a card migration if supported (see Migrate cards between processors).
Card decline on stored-card charge Issuer decline / expired card. Contact the guest; update the card; retry. See Recover failed transactions.
Authentication failed when charging stored card Processor credentials expired on the Zenoti side. Re-verify the processor configuration.
Settlement reversal (ACH (Automated Clearing House) / direct-debit bounce) Bank returned the debit unpaid days after the charge appeared successful. The invoice reopens; chase the guest. Normal behaviour for BBVA ACH and EzyPay direct debit.
Removal is refused with a scheduled-payments message The stored account still has membership, package, or other scheduled collections due on it. Use Replace on the card to move those commitments to a new card, then continue.
A reissued card was never refreshed automatically The card is American Express, JCB, UnionPay, or Diners Club, or the processor does not support automatic updating. Ask the guest for the new card and add it as a new stored account.
The card still carries old details weeks after a decline The update request timed out after 15 days, or the processor returned a terminal outcome such as a closed account. There is no retry. Contact the guest and re-enrol the card.
A guest says they were not told their card changed Automatic updates are silent by design; no guest or staff notification is sent. Confirm the current last four digits and expiry from the guest profile, and tell the guest what is now on file.

Reconciliation

Stored-card charges reconcile against the same pair of reports as any other transaction:

Source Report / view Match key
Zenoti Collections report (filter by payment method) Processor transaction ID + Zenoti invoice number
Processor Processor merchant portal transaction / settlement report Same fields

Recommended cadence: daily.

Tips

  • Always verify the guest's identity before adding or removing stored cards.
  • For guests with multiple stored cards, confirm which card to charge before processing recurring payments.
  • If you plan to switch processors in the future, ask your acquirer whether token migration is available for your processor pair β€” this is cheaper than forcing every guest to re-enrol.
  • Review stored accounts with an expiry date in the current or next month before running membership collections, especially for card brands the account updater does not cover.
  • Before a guest travels or changes banks, ask them to add the replacement card in advance rather than waiting for the first decline.
Was this article helpful?
Your feedback helps us improve our documentation.