What we do
Tools
Industries
Department
How we workLet's talk →
Home/Adyen/Adyen Recurring Payments
Adyen

Adyen Recurring Payments: One Token, Charged on a Schedule Adyen Leaves to You

The first payment stored the card. Now a renewal date comes round and something has to charge it. With Adyen recurring payments, Adyen keeps the token, refreshes the card behind it and can retry a refusal, but the calendar is yours: each renewal is a /payments call your system makes with the token, the shopperReference that owns it and a recurringProcessingModel that says what kind of charge it is.

The fields that matter

Storing the card: on the first payment, send storePaymentMethod: true once the shopper consents, a shopperReference unique to that shopper, and the recurringProcessingModel you'll charge under. Adyen keeps the details in its vault.

Getting the token: the recurring tokens webhook carries it in data.storedPaymentMethodId. Store it next to the shopperReference.

Charging a renewal: /payments with paymentMethod.storedPaymentMethodId, the same shopperReference, shopperInteraction: ContAuth and recurringProcessingModel: Subscription, or UnscheduledCardOnFile for charges at irregular intervals.

POST /payments

A recurringProcessingModel for each kind of Adyen charge

The charge Model Watch for
A plan billed every month or every year Subscription For charges on a fixed schedule. Your system starts each one; Adyen doesn't charge anything on its own.
Top-ups or usage billing with no fixed interval UnscheduledCardOnFile For charges when a balance runs low or usage is billed. The shopper still isn't present, so shopperInteraction stays ContAuth.
A returning shopper paying with a saved card at checkout CardOnFile The shopper starts this one-click payment, so it isn't a renewal. Apple Pay, Google Pay and Samsung Pay can't be used for one-click with a token stored at Adyen.

Renewals that fail before the card is to blame

A different shopperReference on the renewal

How you'll know: Token payments fail for shoppers whose stored card is fine.

Fix: The renewal has to send the shopperReference the token was stored with. Use a stable customer ID from your own system, not an email address that can change.

Only the Sessions flow is wired up

How you'll know: Checkout stores cards, and nothing on the server can charge them later.

Fix: Sessions covers the payment the shopper makes. Renewals, with no shopper present, go through /payments, so the server needs that call as well.

The wrong ID saved as the token

How you'll know: Your database holds a pspReference where the token should be.

Fix: In the recurring tokens webhook, eventId is the pspReference of the payment that stored the details. The token is data.storedPaymentMethodId. Older integrations read it from the RECURRING_CONTRACT webhook, which still works but is no longer developed.

Nobody is charged on renewal day

How you'll know: Cards are stored, and the due date passes without a payment.

Fix: Adyen doesn't keep a billing calendar. A scheduler in your system, or a billing platform that runs on Adyen, has to make each renewal call.

Adyen's half of a failed renewal, and yours

Adyen handles

The card and the retry

  • Real Time Account Updater: when a payment is declined over an outdated card, Adyen asks the scheme for new details, retries, and updates the token. Visa, Mastercard and Cartes Bancaires supply the updates.
  • Network tokens, requested automatically for stored cards where possible.
  • Auto Rescue: retries refused shopper-not-present card payments that have a chance of succeeding, within a rescue window, and reports each attempt by webhook. It can also send the shopper a payment link when a rescue ends without success.
Your systems decide

The subscription

  • Whether the customer keeps access while Auto Rescue is still trying.
  • When a renewal that failed for good becomes a paused or cancelled plan.
  • What the CRM, the support desk and the product show about that account at each step.

Adyen's webhooks say what happened to the charge. Turning each one into a status in the systems that grant access is the part someone has to build.

Adyen tokens and renewal questions

What is Adyen's account updater?

A service that refreshes a stored card's number or expiry date when the bank reissues the card. Real Time Account Updater works inside the payment: on a decline it fetches new details, retries and updates the token, and the new card data comes back in the payment response. Batch Account Updater works from files you send Adyen, and you apply the results with a later /payments request.

Does Adyen store raw card numbers for recurring payments?

Adyen stores them in its own vault, so your system never has to. With the shopper's consent you get a token, the storedPaymentMethodId, which you charge together with the shopper's shopperReference. Adyen also requests network tokens for stored cards where it can.

Does account updater catch every reason a renewal might fail?

No. It deals with reissued or expired card details. Insufficient funds, a closed account or an issuer's fraud flag still come back as declines. Auto Rescue retries the ones with a chance of succeeding, and a permanent decline, such as a closed account, isn't retried at all.

Does Adyen manage subscription plans and status, or just the charge itself?

Just the charge, plus the stored token behind it. Adyen describes subscriptions as transactions you initiate at regular intervals, so the plan, the billing date and the access a customer has live in your own system or in a billing platform that runs on Adyen.

Our cards are stored in Adyen. What still needs building for renewals?

For subscription businesses on Adyen, n-frames builds three pieces: the scheduler that calls /payments with each stored token on its renewal date, the webhook handler that records token and payment events, and the status changes that reach your CRM and product when Auto Rescue succeeds or stops. The request shapes match the ones on our Adyen API page.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.