How Subscription Payments Work: Vaulting, Renewals and Consent

A one-off order is paid once, with the customer present. A subscription renewal is paid again and again, with the customer absent. Almost every payment problem in a subscription business comes from that difference, so it is worth understanding exactly how a renewal gets paid.

The first payment sets everything up

When a customer subscribes, three things happen at checkout that do not happen on an ordinary order:

1. The payment method is vaulted — stored securely so it can be charged later.
2. The customer agrees to future charges — the amount, the frequency, and the terms.
3. The first charge is authenticated, where authentication applies — in Europe, typically through the customer’s bank app.

That first payment is the foundation of every renewal that follows. A subscription whose first payment was set up badly will not fail at checkout; it will fail at the second charge, a month later, when the customer is no longer there to help.

Renewals are merchant-initiated

Every charge after the first is a merchant-initiated transaction: the merchant starts it, without the customer present, under the agreement the customer gave at checkout.

That matters because the rules for customer-present and customer-absent payments differ. A merchant-initiated renewal generally does not need the customer to authenticate again — the original authentication covers it. But an issuer can still decline it, or send it back asking the customer to confirm, particularly if the charge departs from what was originally agreed. More on Strong Customer Authentication.

Who holds the card

This is the most important structural difference between subscription apps, and it is invisible on a listing page.

Built on the platform’s billing. On Shopify, an app can use Shopify’s own subscription billing: Shopify vaults the payment method, and the app asks Shopify to bill a contract. The app never sees a card, you inherit no PCI scope from it, and the subscription contract is an object in your store.

The app’s own vault. Other apps store payment methods themselves and charge through their own gateway integration. That is a second copy of your customers’ card details, somewhere other than Shopify — and because payment credentials generally cannot be moved between providers, leaving that app usually means asking every subscriber to enter their card again.

Ask about this before you install anything. The questions that separate subscription apps.

Which payment methods work

Not every payment method can be charged again later. A method has to support being stored and charged without the customer present. On a subscription checkout, methods that cannot do that simply do not appear — which surprises customers who always pay that way. Payment methods for subscriptions.

Where renewals go wrong

Renewals fail for a handful of reasons, and the right response differs for each:

Cause	What it needs
Insufficient funds	A retry, timed well
Expired or replaced card	The customer to update it — or a network update that does it for them
Authentication requested	The customer to confirm the charge
Card reported lost or stolen	A new payment method
Customer disputes a charge they didn’t expect	Better reminders next time

The last row is the most avoidable. A renewal the customer knew was coming is rarely disputed; one that surprised them often is. Pre-renewal reminders · Recovering failed payments.

Currency and tax on every renewal

Two things that are fixed on a one-off order can change on a subscription:

• Currency. A customer who subscribed in euros should renew in euros. Multi-currency subscriptions.
• Tax. Tax generally follows the delivery address, and subscribers move. Sales tax and VAT on subscriptions.

The short version

Set the first payment up properly, keep the card with the platform rather than a second vault, charge what the customer agreed to, and tell them before you do. Most subscription payment problems are one of those four done badly.