Initially opting-in to Account Updater happens after enabling our Advanced Vault feature. Once Advanced Vault is enabled AU can be enabled at the organization level - all environments will be affected. For more granular control, you may choose to enable Account Updater on a per environment basis. Please refer to How do I enable Account Updater? or to the Environment-Level Controls documentation for more details.
By turning on the Account Updater feature, you confirm that all eligible cards will be sent to the card brands for updates twice monthly, but you will only be charged for those cards that are actually updated or flagged. These updates happen automatically by Spreedly in the background and your customers can continue using your service without interruption.
Once you opt in, you can select which of your cards will be sent to the card networks for updating. By default, all payment methods are going to be included. The only fields that may be updated are card number and/or expiration date (year/month). All other fields are ignored.
In order to exclude payment methods from being sent to Account Updater, you will need to set the value "eligible_for_card_updater" to false. This value can be set when creating a payment method or by using .
Note: Account Updater does not share the card's first name or last name during processing. If there are concerns of missing or incorrect customer data, this will not be used during the updating process.
Please refer to the Account Updater Configuration Matrix for expected results in various configuration scenarios.