Account Updater is a feature that automatically requests updates for vaulted payment methods in the event that a customer's vaulted card expires or is replaced – helping you avoid failed transactions or gaps in services provided to your customers.
Pricing for Account Updater varies depending on your pricing model. Contact us for more information on fees.
Account Updater is available to merchants who use Braintree Direct and are either based in the US or transact primarily with US customers. Contact us to see if Account Updater is a good fit for your business.
Whether a card can be updated using Account Updater is dependent on the customer’s issuing bank and that bank's participation in this feature. As a result, even if a customer's card type is compatible, it may not be eligible for automatic updates if the issuing bank does not participate. Supported card types are:
Account Updater is not enabled on your account by default. We’ll work with you directly to make sure this feature is configured in a way that works best for your business. Contact us to get started.
When Account Updater is first enabled, we automatically send all vaulted Visa, Mastercard, and Discover credit card information to the card-issuing banks to request updates in batches of 200,000. If the issuing bank has opted to participate, they will respond with the new card number and/or expiration date – allowing us to update the vaulted card.
After the initial batch, we request updates for cards on a rolling basis when they meet any of the following criteria:
- Card is expired
- Card is set to expire in the current month
- Recurring billing payment is due within 2 weeks
- Relevant transaction activity suggests an update may be needed: card has been processed successfully in the last 13 months but was declined by the processor within the last 30 days
- Card has been flagged for Next Day Card Refresh
Next Day Card Refresh attempts to update vaulted cards if an authorization is declined with certain decline codes. This feature will only work if you have retry logic set up to re-attempt failed transactions – whether it’s through our recurring billing feature or logic you’ve built yourself. These are the decline codes that will trigger Next Day Card Refresh before being retried:
|2000||Do Not Honor|
|2005||Invalid Credit Card Number|
|2006||Invalid Expiration Date|
|2012||Processor Declined - Possible Lost Card|
|2013||Processor Declined - Possible Stolen Card|
|2022||Declined - Updated Cardholder Available|
|2043||Error - Do Not Retry, Call Issuer|
|2044||Declined - Call Issuer|
|2047||Call Issuer. Pick Up Card|
|2053||Card reported as lost or stolen|
Our Account Updater reporting shows you how many cards were updated, the reason for and date of each update, and whether the updates were successful or not. If you display the last four digits or expiration dates for customer's cards in your UI, you can also leverage these reports to ensure that you keep their displayed information up to date.
You can find reporting for Account Updater in three ways:
- In the activity history for an individual payment method
- By generating an Account Updater report
- By using a webhook
If you want to see the Account Updater activity for a specific payment method, you can find it in the payment method's transaction history:
- Log into the Control Panel
- Under Advanced Search, click Vault
- Enter your search criteria
- Click on the Vault record's ID
- Scroll down to the History section
Any history events that have the prefix AU in the Source Description field are events triggered by Account Updater. This box will also include the event description that was returned when the update was attempted.
The Account Updater report shows all Account Updater activity within a specified date range. To generate an Account Updater report:
- Log into the Control Panel
- Under Vault, click Export Customers
- Under Account Updater, click Export
- Choose your date range
- Click Filter and Download
If you'd like to review a daily report of Account Updater activity, we can enable an Account Updater webhook for you. This webhook links to a CSV file containing information on all vaulted payment methods that have been updated within 24 hours. Contact us to have this webhook enabled.
Event descriptions let you know why a payment method was sent by Account Updater, and whether it was successfully updated. These descriptions can be found in the activity history for a given payment method, the Account Updater report generated in the Control Panel, or the Daily Report generated via webhook. Here are the possible event descriptions:
- New account number
- New expiry date
- Call customer - account closed
- Call customer for updates
- Match found - card is current
- Call issuer for updates
- Do not retry
We will not attempt to resend any cards for updates that return the Call customer - account closed, Call customer for updates, Call issuer for updates, or Do not retry event descriptions until the payment method has been manually updated by a user in the Control Panel or via the API.
Still have questions?
If you can’t find an answer, contact us