Set up Account Updater
Account Updater is a background service that works with card networks β Visa Account Updater (VAU) and Mastercard Automatic Billing Updater (ABU) β to automatically refresh expired or replaced card details stored in guest profiles. When a guest's card is reissued (because it expired, was lost or stolen, or the issuer assigned a new account number), Account Updater fetches the new details from the card network and silently updates the saved card token in Zenoti. The guest does not need to re-enter their card, and recurring payments continue without interruption.
Audience: Organization administrators and center managers who want to understand how Account Updater works and its impact on recurring payment success rates.
On this page
- Before you begin
- How Account Updater works
- What Account Updater covers
- Impact on recurring payments
- Fees
- What Account Updater does not cover
- Troubleshooting
- Contact Zenoti Support
- Related articles
Before you begin
Permission: No administrator configuration is required to enable Account Updater. The service is enabled at the processor level for supported processors and operates automatically in the background. There is no toggle in Zenoti settings to turn Account Updater on or off.
Supported processors:
- Adyen β Account Updater is included in the Adyen integration. Adyen participates in both Visa Account Updater (VAU) and Mastercard Automatic Billing Updater (ABU).
- Stripe β Account Updater is included in the Stripe integration. Stripe participates in both VAU and ABU and additionally supports its own card-network update framework.
If your center uses a processor other than Adyen or Stripe, Account Updater behavior depends on your processor's participation in card-network update programs. Contact your processor account team to confirm.
How Account Updater works
Account Updater operates as an automated background process between your processor and the card networks:
- Card issued or replaced. The guest's card issuing bank reissues the card β because the card expired, was reported lost or stolen, or the issuer changed the account number.
- Network notification. Visa (via VAU) or Mastercard (via ABU) notifies participating processors that the card has been updated.
- Token refresh. The processor (Adyen or Stripe) receives the notification and updates the card token stored on the guest's profile in Zenoti. The old token is replaced with a token representing the new card details.
- Transparent to the guest. The guest sees no prompt or notification from Zenoti β the card on file continues to work without any action. Front-desk staff also see no action required; the token update is silent.
- Transparent to recurring payments. The next scheduled recurring payment (membership auto-renewal, Auto-pay authorization, package installment) uses the refreshed token and processes normally.
The update cycle timing depends on the card network's batch schedule. VAU and ABU typically run nightly or on a per-billing-cycle cadence. There may be a gap of up to a few days between when the issuer reissues the card and when Zenoti receives the refreshed token.
What Account Updater covers
Account Updater handles three categories of card change:
| Scenario | How it is handled |
|---|---|
| Expired card | The card reaches its expiry date and the issuer reissues it with a new expiry date (and sometimes a new card number). The network notifies the processor; Zenoti token is refreshed. |
| Replaced card β lost or stolen | The issuer cancels the guest's card and reissues a replacement with a new account number. The network notifies the processor; Zenoti token is refreshed with the new account number. |
| Account number change from issuer | The issuer proactively changes the account number (for example, during a portfolio migration or fraud remediation sweep). The network notifies the processor; Zenoti token is refreshed. |
Note β update timing. Card networks batch Account Updater notifications. A card refreshed by the issuer today may not be reflected in Zenoti for 24β72 hours, depending on the network's batch schedule and your processor's processing cadence. If a recurring payment falls due in the gap before the token refreshes, the payment may still fail on the old card details. See Troubleshooting for how to handle this.
Impact on recurring payments
Account Updater directly reduces involuntary churn β payment failures caused by card changes rather than by the guest's intent to cancel. The following recurring payment types benefit:
- Membership auto-renewals β when a member's saved card is replaced or expired, Account Updater refreshes the token before the renewal attempt, allowing the charge to succeed without guest action.
- Auto-pay β Auto-pay pre-authorizes the guest's saved card at check-in. A refreshed token means the authorization succeeds even if the guest received a new card between visits.
- Package installment payments β guests on payment plans continue their installment schedule without needing to update their card manually.
- Scheduled recurring invoices β any scheduled collection against a saved card benefits from the refreshed token.
Important β no guarantee of success. Account Updater increases the likelihood that a saved card remains current, but it does not guarantee payment success. The card network may not have a record of the update (for example, if the issuer does not participate in VAU or ABU), or the card may be closed entirely (which Account Updater does not cover β see What Account Updater does not cover). Recurring payment failures should still be investigated; Account Updater reduces but does not eliminate them.
Fees
Card networks charge a per-update fee each time a card token is refreshed through the Account Updater program. The specific fee is set by your processor agreement:
- Adyen β the per-update fee is included in Adyen's billing to your merchant account. Review your Adyen agreement or the Adyen Customer Area for the current per-update rate.
- Stripe β the per-update fee is included in Stripe's billing to your account. Review your Stripe Dashboard or Stripe agreement for the current rate.
Zenoti does not charge a separate fee for Account Updater. The network fee is a pass-through from your processor.
Note β fee estimation. The volume of Account Updater events depends on your guest base's card-replacement rate, which varies over time (for example, it spikes after large bank data-breach reissuances). You cannot predict or cap the number of updates in advance. Review your processor's monthly billing statement to see Account Updater activity under the fee line items.
What Account Updater does not cover
Account Updater is not a universal solution for all payment failures. The following scenarios are not handled by Account Updater:
- Closed accounts. When a guest closes their card account entirely (rather than having it replaced), the card network does not issue an update β the account ceases to exist. The next recurring payment against the closed account will hard-decline. Configure your hard-decline flagging settings to suppress further retries on a closed account and prompt the guest to provide a new payment method.
- Debit card reissuances from non-participating issuers. Not all card issuers participate in VAU or ABU. If the guest's issuer does not participate, Zenoti never receives a token update for that card's changes.
- Guest-revoked authorization. If a guest has explicitly revoked their payment authorization (for example, via a dispute or a direct revocation request to the issuer), Account Updater does not reinstate the authorization. Do not attempt to retry a payment where the guest has revoked consent.
- Cards added manually by key entry. Account Updater applies only to tokenized saved cards (cards vaulted by the processor). Cards entered by key entry that were not saved to the guest profile are not tracked by Account Updater.
- Prepaid cards. Most prepaid cards are not enrolled in card-network update programs and do not participate in VAU or ABU.
Troubleshooting
Recurring payment failed even though Account Updater should have refreshed the card.
Possible causes and resolutions:
- Update not yet received. The card-network batch may not have run since the issuer reissued the card. Wait for the next billing cycle attempt β the token may be refreshed by then. If the payment is time-sensitive, contact the guest and ask them to update their card in their profile or in the Customer Mobile App.
- Issuer does not participate in VAU/ABU. Some issuers (typically smaller banks or credit unions) do not enroll in card-network update programs. Account Updater cannot refresh tokens for these cards. The guest must manually update their card on file.
- Account closed. If the card was closed rather than replaced, there is no updated card for the network to report. See What Account Updater does not cover. Enable hard-decline flagging to suppress further retries and flag the account for follow-up.
- Gap between issuance and Zenoti update. Card-network updates can take 24β72 hours. If the recurring payment ran during that window, a manual retry after the gap may succeed. Use the dunning retry controls in Configure recurring payment rules to schedule the retry.
I cannot find an Account Updater settings page in Zenoti.
This is expected. Account Updater has no admin configuration page in Zenoti β it is managed at the processor level (Adyen or Stripe) and operates automatically. There are no toggles to set. If you believe Account Updater is not working for your processor, contact Zenoti Support with the affected guest profile and a summary of the failed recurring payment attempts.
Contact Zenoti Support
Contact Zenoti Support through the in-product Help menu or your account manager for the following scenarios:
- A guest's card is being repeatedly refreshed but recurring payments continue to fail β this may indicate a processor token-refresh issue or a guest-side card problem requiring investigation.
- You believe Account Updater activity is generating unexpected fee volume on your processor statement and want to audit the refresh events.
- Your processor is not Adyen or Stripe and you want to understand whether Account Updater is available for your processor.
- A recurring payment failure has persisted across multiple billing cycles despite Account Updater being enabled.