How to Set Up Recurring Billing, Step by Step

Setting up recurring billing takes four things, and they have to arrive in the right order. You need a merchant account underwritten for scheduled charges, a gateway or billing platform that can store a card and run the rebill, enrollment disclosures that meet the card networks’ subscription rules, and a plan for the payments that fail. Most guides start with the software because that is the fun part. Start with the account instead, because that is the part that can be declined, and because a subscription business that boards on the wrong account tends to find out at month four rather than week one.

Key takeaways

• Get the merchant account first. Scheduled charges change what an acquirer is underwriting, so a subscription model belongs in the application, not in a later surprise.
• The first charge sets up every charge after it. Card networks expect express, informed consent captured before you store the card, and each later rebill points back to that starting transaction.
• Visa requires an electronic reminder with a cancellation link at least seven days before you charge someone after a trial or promotional period ends (Visa, effective 18 April 2020).
• Build failure handling on day one. Stripe’s recommended default retry policy is eight attempts within two weeks, and it will not execute retries on nine specific hard decline codes until you supply a new payment method.
• Keeping the card current beats retrying it. Visa reports its tokenized online transactions show a 4.6 percent lift in authorization rates globally compared with sending the raw card number.

Step 1: Decide the billing model before you shop for software

Write down what you are charging, how often, and what happens when someone stops paying. That sounds obvious, and it is the step people skip. Every later decision follows from it.

Three questions settle most of it.

• Fixed or variable? A flat monthly membership is a fixed rebill. Usage-based billing, metered plans, and payment plans with a changing balance need a platform that calculates an amount before each charge.
• Is there a trial or introductory offer? If yes, you have taken on a specific set of network requirements, covered below. Free trials and introductory pricing are the highest-scrutiny version of subscription billing.
• What is the exit? Decide in advance how many failed payments end the subscription and what the customer sees at each stage. A billing system with no defined end state produces charges that land months late, which is the single most disputable transaction a subscription business can create.

This matters more in high-risk categories than anywhere else, because the model is often the whole business. Supplement brands, telehealth memberships, and credit repair services all live on scheduled charges, so a billing decision here is a revenue decision.

Step 2: Get a merchant account that expects scheduled charges

Your merchant account is the thing that can say no, so settle it before you build anything. Scheduled billing changes the risk an acquirer is looking at. One unhappy customer on a one-time sale produces one dispute. One unhappy subscriber can produce several, one for each cycle they did not notice, and the underwriter knows that.

Say so in the application. Tell them the model, the price, the cycle, the trial structure if you have one, and roughly what share of your volume is rebills. A processor that approves you knowing all of that has priced your risk correctly. A processor that finds out later starts a review, and reviews on subscription merchants tend to end in a reserve or a termination rather than a warning.

Be skeptical of anyone advertising guaranteed approval for subscription billing. Real underwriting looks at your category, your history, and your billing model, so a promise made before any of that is reviewed is a sales line rather than a decision. If your category is one mainstream processors decline outright, opening a high-risk merchant account walks through what that application actually involves.

Step 3: Store the card the way the networks expect

Recurring billing runs on a stored credential, which is a card you keep on file and charge later without the customer present. The first charge is different from all the ones that follow, and treating them the same is a common setup error.

That first transaction is the one the cardholder is present for. It establishes the agreement and produces the authorization that every later charge points back to. Before it happens, you need express, informed consent to the ongoing arrangement, and you need a record of it. After it, each rebill is a merchant-initiated charge that carries the right indicators through your gateway so the issuing bank can tell a scheduled subscription payment from an unexpected one.

Your payment gateway does most of this work, but only if it is configured for it. Two features are worth turning on before your first cycle rather than after your first bad month.

• An account updater. Visa describes its version as an automated clearinghouse that exchanges updated account information between participating merchants and Visa card issuers, covering account closures, lost and stolen cards, expiration changes, product upgrades, and portfolio conversions. Issuers submit those updates within two business days of a permanent change, and merchants are expected to update their billing files within five days of receiving them (Visa Account Updater fact sheet).
• Network tokenization. Instead of storing the card number, you store a network token that the card network keeps pointed at the customer’s current card. Visa reports its tokenized online transactions show a 4.6 percent lift in authorization rates globally compared with sending the raw account number, and a 30 percent reduction in fraud online against the same comparison (Visa).

An authorization lift on every cycle compounds in a way a one-time checkout improvement never does. If you are still comparing platforms, what to look for in a subscription gateway walks through the rest of the shortlist.

Step 4: Write the enrollment disclosures the rules require

The card networks publish specific requirements for subscription enrollment, and they read like design instructions for your signup flow and your emails. Visa’s policy for merchants offering free trials or introductory promotions, effective 18 April 2020, is the clearest published example.

At enrollment, Visa requires merchants to obtain express consent to the ongoing subscription and to send the customer an electronic copy of the terms, even when no money is due yet. That notice has to confirm the customer agreed to a subscription unless they cancel, state the start date, describe the goods or services, give the ongoing amount and billing frequency, and include a link or other simple mechanism to cancel later transactions online.

Then there is the timing rule that catches most merchants. Visa requires an electronic reminder with a cancellation link at least seven days before you initiate a recurring transaction once a trial, introductory offer, or promotional period has expired, and again when the nature of the agreement changes, such as a price or billing period change. Visa also requires an additional descriptor identifying a trial-related transaction on the first charge after a trial ends, so it is recognizable on the statement.

Two more requirements from the same policy are worth building to directly. Transaction receipts must disclose the length of any trial and state plainly that the customer will be charged unless they act. And cancellation has to be easy online regardless of how the customer signed up, with Visa comparing the standard to unsubscribing from an email list.

The other networks publish their own subscription requirements, so confirm the current rules for every network you accept. Read them as product requirements rather than paperwork, because that is how they behave.

Step 5: Plan for the payments that fail

Some rebills will decline, and how you handle that decides both your revenue and your dispute ratio. Sort declines before you retry them.

Soft declines, like insufficient funds or a temporary hold, are what retries are for. Hard declines are the issuer telling you the card will not work again. Stripe names nine such codes it will not retry automatically, including lost card, stolen card, and revocation of authorization, and it only executes further attempts once you supply a new payment method. Its recommended default policy is eight attempts within two weeks, and its custom option allows up to three retries on a schedule you define (Stripe).

Space the attempts out and set an end date. Then tell the customer before the retry rather than after it, so the charge arrives expected. A retry that succeeds four weeks late under a descriptor nobody recognizes is how a paying subscriber turns into friendly fraud, where a genuine customer disputes a charge they genuinely made. The full mechanics of retries and recovery notices are in what dunning is.

Step 6: Set the descriptor, the cancellation path, and the monitoring

Three small settings do most of the work of keeping a subscription account healthy.

Your billing descriptor should carry the brand on the website the customer signed up on, not your legal entity name. Your cancellation path should be a link that works, because every subscriber you push into calling their bank becomes a dispute instead of a churn statistic. And your dispute ratio needs watching from the first cycle, since the ratio that keeps an account alive is measured continuously, not reviewed at the end of the year.

It is also worth splitting the risk across rails. Card rebills carry expiration, reissue, and dispute exposure. Bank debits through ACH processing typically fail for a shorter list of reasons, most often insufficient funds or a revoked authorization, and they fit payment plans, high-ticket pulls, and B2B invoices well. Running both gives each customer a rail that works.

Getting recurring billing right the first time

Build in this order. Confirm the model, get an account underwritten for scheduled charges, store the card as a properly consented credential with an account updater and network tokens behind it, write the enrollment disclosures the networks actually require, define your retry schedule and its end date, and set a descriptor and cancellation path a customer will recognize and use.

None of that is exotic, and none of it is expensive compared with rebuilding a billing system after an acquirer flags your account. If you want the setup handled as part of the account rather than bolted on afterward, that is what recurring billing setup is for. Start your application and we will discuss the model, the gateway, and the pricing based on your current statement.