Update card details automatically
When a guest's card is reissued by their bank β for example, when the card expires and a new one is sent β Zenoti can automatically update the stored card details so that future charges continue without manual intervention. How this works depends on your payment processor.
Audience: Organization administrators, billing managers, front-desk managers
On this page
- How automatic card updates work
- Zenoti Payments (Stripe)
- Element Express (Worldpay) β Account Updater
- Supported card networks
- What guests and staff see
- When an auto-update fails
- Limitations
- Related articles
How automatic card updates work
Processor scope: Card auto-update is supported by Stripe (proactive) and Element Express/Worldpay (Account Updater) only. Most other processors do NOT support automatic card detail updates.
Zenoti supports automatic card updating through two different mechanisms. These are architecturally distinct features β each works differently depending on your payment processor.
| Mechanism | Processor | When it happens | How it works |
|---|---|---|---|
| Stripe built-in card updater | Stripe, Stripe Connect | Proactively, before any charge | Stripe obtains updated card details from the card networks in the background and pushes them to Zenoti automatically |
| Account Updater (PASS Updater) | Element Express (Worldpay) | After a stored card transaction is declined | Zenoti marks the card for update, a daily scheduled job sends the request to the processor, and the processor returns updated details |
Important: Automatic card updates apply only to stored payment accounts (tokenized cards saved on a guest's profile). Cards entered manually at the point of sale are not eligible for automatic updates.
Zenoti Payments (Stripe)
If your organization uses Stripe or Stripe Connect as the payment processor, card details are updated proactively through Stripe's built-in card updating service.
How Stripe card updates work
- When a card network (Visa, Mastercard) reissues a guest's card, the network notifies Stripe.
- Stripe updates the stored card token with the new details (new expiry date, and in some cases a new card number).
- Stripe pushes the updated details to Zenoti automatically.
- The guest's stored payment account in Zenoti is updated with the new card information.
This process happens in the background, before any charge is attempted. Recurring payments (memberships, packages) continue to process successfully with the updated card details.
Supported card networks (Stripe)
| Card network | Auto-update support |
|---|---|
| Visa | Supported β USA, Canada, and additional Stripe-supported regions |
| Mastercard | Supported β available globally in Stripe-supported regions |
| American Express (Amex) | Not supported β Amex does not participate in Stripe's automatic card updating |
| Discover | Support varies β check Stripe's documentation for current coverage |
| JCB, UnionPay, Diners Club | Not supported |
American Express cards are NOT supported for automatic card updates on any processor.
Visa: Auto-update is supported for USA and Canada only.
Mastercard: Auto-update works globally across all supported regions.
CVC and Stripe card updates
When Stripe updates a stored card, the CVC is not part of the update. Stripe processes subsequent charges using the stored token without requiring the CVC. Whether a transaction requires CVC verification depends on the card network rules and the transaction type β this is managed by Stripe and the card network, not by a Zenoti setting.
Element Express (Worldpay) β Account Updater
Region scope: Element Express Account Updater applies to all card types in the US region only.
If your organization uses Element Express (Worldpay) as the payment processor, card details are updated reactively through Zenoti's Account Updater service (PASS Updater).
How Account Updater works
Unlike Stripe, the Account Updater does not update cards proactively. Instead, it is triggered when a stored card transaction fails:
- A charge is attempted against a guest's stored card (for example, a membership collection).
- The processor declines the transaction for one of these reasons:
- The card was declined by the issuing bank
- The card has expired
- The card has been flagged for pickup
- The card details are invalid
- Zenoti marks the stored account for update. The initial decline still occurs β the original transaction fails at this point.
- A daily scheduled job sends the marked accounts to the Element Express PASS Updater API.
- The PASS Updater checks with the card networks for updated card details.
- Updated card details are returned (this can take up to 15 days).
- Zenoti updates the guest's stored payment account with the new card information β the new expiry date, last four digits, and card brand are saved permanently to the guest's profile.
- The next charge attempt uses the updated card details.
Key difference from Stripe: The Account Updater is reactive β the first charge still fails. The card details are updated for the next charge, not for the one that triggered the update. The guest may see a single declined transaction before the update takes effect.
Supported card networks (Account Updater)
| Card network | Auto-update support |
|---|---|
| Visa | Supported |
| Mastercard | Supported |
| Discover | Supported |
| American Express (Amex) | Not supported β Amex cards are excluded from the Account Updater |
| JCB, UnionPay, Diners Club | Not supported |
Which transactions trigger the Account Updater
Auto-update triggers when all three of the following conditions are met:
- (a) The transaction amount is non-zero.
- (b) The charge is a recurring or service/pre-booking charge.
- (c) CVC is not required for the transaction.
The Account Updater is triggered when a stored card transaction returns specific decline codes from Element Express. This includes:
- Recurring membership or package collections
- Charges initiated for a service or pre-booking using a stored card
- Any other transaction that uses a tokenized card from the guest's profile
The Account Updater is not triggered for:
- Walk-in transactions where the guest swipes, taps, or manually enters card details at the terminal
- Retail product purchases paid with a card not saved on the guest's profile
- Gift card transactions
- Transactions on card networks other than Visa, Mastercard, and Discover
Other processors with Account Updater support
Xendit may support the Account Updater on a conditional basis (requires configuration). All other processors (Adyen, FreedomPay, Moneris, BBVA, etc.) do not support Zenoti's Account Updater service.
Supported card networks
The following table summarizes card network support across both mechanisms:
| Card network | Stripe auto-update | Account Updater (Element Express) |
|---|---|---|
| Visa | Supported | Supported |
| Mastercard | Supported | Supported |
| Discover | Varies (check Stripe docs) | Supported |
| American Express (Amex) | Not supported | Not supported |
| JCB | Not supported | Not supported |
| UnionPay | Not supported | Not supported |
| Diners Club | Not supported | Not supported |
What guests and staff see
Automatic card updates are a silent, background process. There is no notification sent to the guest or the front-desk operator (FDO) when a card is auto-updated.
| Event | Guest notification | FDO notification | Visible in Zenoti |
|---|---|---|---|
| Card successfully auto-updated | None | None | The guest's stored card on the Cards tab shows the updated expiry and last four digits |
| Card update failed | None | None | The stored card retains its old (outdated) details |
| Stripe proactive update | None | None | Updated details appear on the guest's profile |
| Account Updater triggered (initial decline) | Guest may see a declined transaction | FDO sees the failed transaction in the payment reports | Failed transaction appears in the failed transactions log |
For reconciliation and customer service: If a membership charge succeeds after a card was auto-updated, the only way to confirm the card changed is to check the guest's Cards tab β the updated expiry or last four digits will be different from what was originally saved. Internal audit logs track all card update activity, but these are not visible in the standard Zenoti admin interface.
Updated card details persist
When an automatic card update succeeds β whether through Stripe or the Account Updater β the new card information is permanently saved to the guest's stored payment account. The updated details include:
- New expiration month and year
- New last four digits (if the card number changed)
- Updated card brand (if applicable)
The update is not a one-time recovery. All future charges, including recurring membership collections, use the updated card details going forward.
When an auto-update fails
Stripe
If Stripe cannot obtain updated card details from the card network (for example, if the issuing bank does not participate in the card updating program), the stored card retains its old details. The next charge attempt using that card will be declined. At that point:
- The declined transaction appears in the failed transactions log.
- There is no automatic retry specific to the card update failure.
- The FDO or billing team should contact the guest to collect updated card details manually.
- For memberships, the standard retry schedule (dunning) applies to the failed collection, but the retry will use the same outdated card unless the guest updates it.
Account Updater (Element Express)
If the PASS Updater does not return updated card details within 15 days, the update request is automatically marked as failed. The stored card retains its old (outdated) details. Consequences:
- Subsequent charges using that card will likely be declined again.
- There is no automatic retry or dunning for the card update itself (though membership dunning applies to the failed charge).
- There is no notification sent to the guest or the FDO about the update failure.
- If the update response indicates "Contact Cardholder," the system flags the account for manual review, but no notification is sent automatically.
- The FDO should contact the guest to update their payment information manually.
Tip: Regularly review the failed transactions report (Configuration > Reports > Payment Reports) to identify guests whose stored cards are consistently declining. These may be cases where the automatic card update failed and manual follow-up is needed.
Limitations
- Processor support is limited. Automatic card updates work only with Stripe (built-in) and Element Express/Worldpay (via Account Updater). Most other processors do not support automatic card updating through Zenoti.
- Amex cards are excluded. American Express does not participate in the automatic card update programs used by Zenoti.
- No CVC in updates. Automatic card updates do not include the CVC (security code). Transactions that require CVC verification β which is determined by the card network and processor, not by a Zenoti setting β cannot use auto-updated details until the guest provides the CVC manually.
- No notifications. Neither guests nor staff are notified when a card is auto-updated or when an update fails. Monitor stored account health through reports.
- Account Updater is reactive, not proactive. For Element Express, the first charge using an outdated card will fail. The card is updated for future charges only.
- 15-day timeout. Account Updater requests that do not receive a response within 15 days are automatically marked as failed.