Adyen vs Braintree Account Updater: Per-Update Fees and Default Behavior
Adyen runs Account Updater automatically on stored credentials with no per-update fee on most contracts; Braintree charges per successful update and needs explicit vault setup. Here's what that means for a subscription store's renewal math.
Adyen vs Braintree Account Updater
Adyen runs Account Updater automatically on stored card credentials with no per-update fee on most contracts; Braintree charges per successful update and requires explicit vault configuration.
Account Updater is the network-level service (Visa VAU, Mastercard ABU, Amex CardRefresher) that swaps expired or reissued card numbers in your vault before a renewal attempt fails. Adyen and Braintree both connect to the networks, but the commercial and operational defaults are very different.
Adyen treats Account Updater as part of its tokenization layer: it runs automatically on stored MITs (merchant-initiated transactions), and on most negotiated contracts the per-update fee is folded into processing pricing rather than billed separately. Braintree exposes Account Updater as a discrete service — you opt in at the vault level, and successful updates are billed per card per month or per update depending on the contract.
For a subscription store with €1–15M GMV, this difference compounds on every billing cycle. If 4–7% of stored cards expire or reissue each year, the choice between automatic-and-bundled and opt-in-and-metered changes both involuntary churn and the monthly PSP invoice.
The decision is rarely about the headline processing rate. It's about how Account Updater integrates with the rest of your retry stack — network tokens, smart retries, dunning emails — and whether you pay for updates you didn't strictly need.
Adyen vs Braintree: Account Updater behavior and pricing
| Dimension | Adyen | Braintree |
|---|---|---|
| Default behavior | Automatic on stored MITs | Opt-in per vault / per merchant |
| Per-update fee | Typically bundled in contract | $0.25–$0.50 per successful update (typical) |
| Update timing | Real-time at transaction + scheduled batches | Scheduled batch (daily/weekly) |
| Network coverage | Visa VAU, Mastercard ABU, Amex CardRefresher | Visa VAU, Mastercard ABU, Amex CardRefresher |
| Reporting granularity | Per-transaction in dashboard + API | Batch report via API / dashboard export |
| Network token support | Native, auto-provisioned | Network tokens via separate config |
| Best fit | EU-heavy subscription brands, multi-region | US-heavy, PayPal-integrated stacks |
Two columns matter most for renewal economics: default behavior and per-update fee. Adyen's automatic, bundled model means you don't think about Account Updater day-to-day — it just runs. Braintree's metered model means every saved card is a line item you can audit, but also a line item that scales with your subscriber base.
When Adyen wins
If your subscription base is in the EU or split across multiple regions, Adyen's automatic model removes a configuration step you'd otherwise repeat per merchant account. The real-time updater also fires at transaction time, not just on a nightly batch, which catches reissued cards on the renewal attempt itself rather than the day after a failed charge.
For a beauty or apparel store running monthly replenishment at 8,000–40,000 active subscribers, the operational simplicity is the win. You stop reconciling per-update line items, and Account Updater is one less knob your billing team has to monitor. Network tokens are provisioned in the same flow, so your involuntary churn rate drops without a separate integration project.
The hidden cost of "per successful update"
Braintree's per-update fee sounds small — a few cents to save a renewal worth €30–€60 of LTV. But on a 25,000-subscriber base with 6% annual reissue rate, that's 1,500 paid updates a year per vault refresh cycle. If you also run multiple updates per card (issuer batches sometimes return updates months apart), the line item can reach 4–5 figures annually. Audit your AU report before renewal negotiations — you may be paying for updates that wouldn't have caused a decline anyway.
When Braintree wins
Braintree's metered model is actually attractive when your subscriber base is small, US-heavy, or already integrated with PayPal. Below ~5,000 active stored cards, the per-update fees stay modest and you get full visibility into which cards updated when. That granularity helps if you're tuning a smart-retry waterfall and want to know whether a recovered transaction was due to AU or to a network-token re-attempt.
Braintree also tends to win when your stack already includes the broader PayPal Commerce Platform — Vault, Smart Payment Buttons, and Pay Later. Adding Account Updater inside that environment is a checkbox, and you keep one consolidated settlement. For US-domestic subscription brands under €3M GMV, the per-update fee is rarely the deciding factor; engineering simplicity is.
Estimated annual Account Updater cost per 1,000 active subscribers
Adyen (bundled)
Braintree (per-update)
Adyen vs Braintree Account Updater FAQ
On most negotiated Adyen contracts, Account Updater is automatic on stored MIT credentials and the per-update cost is bundled into your processing pricing. Smaller-volume accounts on standard pricing may see a small line item — confirm with your Adyen contract before assuming zero marginal cost.
Braintree's published pricing varies by contract and region, but typical merchants pay $0.25–$0.50 per successful update, billed monthly. Some contracts use a per-card-per-month model instead. You only pay when a card is actually updated, not for queries that return no change.
Yes — both Adyen and Braintree connect to Visa Account Updater (VAU), Mastercard Automatic Billing Updater (ABU), and Amex CardRefresher. Coverage of regional schemes (Discover, JCB, some EU domestic schemes) is roughly equivalent but worth verifying for your specific markets.
No. AU handles expired and reissued cards, which is typically 40–60% of involuntary churn causes. You also need smart retries for insufficient-funds declines, dunning emails for lost cards, and network tokens to reduce soft declines. Account Updater is one layer in the stack, not the whole stack.
Yes for time-sensitive renewals. Adyen can query the network at the moment of the transaction attempt, which catches reissues that happened between the last batch and now. Braintree's scheduled batch (typically daily or weekly) means you may attempt a charge on a now-stale card and recover only on the next retry.
Network tokens are issuer-managed tokens that update automatically when the underlying card changes — effectively a continuous AU. Adyen auto-provisions network tokens in the same flow as Account Updater. With Braintree you configure network tokens separately, but once active they reduce reliance on batch AU updates.
Card vault migration is possible but requires PCI-scoped coordination between both PSPs and usually a written request from the card networks. Adyen and Braintree both support inbound migrations, but expect a 4–8 week project. Don't switch PSPs purely for AU pricing without modelling the migration cost.
Both integrate, but the Shopify-native Shop Pay flow uses Stripe in most cases. If you're on Recharge or Bold with an external PSP, Braintree is the more common integration historically; Adyen is gaining ground for EU-heavy brands. Your subscription app's documentation will list which PSPs it supports natively.
No — Account Updater is a card-network service. PayPal, Apple Pay, and Google Pay use their own credential-on-file mechanisms that update automatically when the underlying card changes. For wallet-heavy subscription bases, AU coverage matters less; for card-direct subscriptions, it's central.
Pull a 90-day report of updated cards and cross-reference with renewal attempts. Count how many recovered transactions used an AU-updated card versus how many would have succeeded anyway (e.g., the card hadn't actually expired yet). On Braintree, this audit can reveal you're paying for updates that don't change renewal outcomes.
See Metricuno on your data
Bring your stack — Google Analytics, Stripe, a CRM, anything — and we'll walk through the metric tree that turns your funnel into one number.