Recurring billing, set up the right way.

Recurring billing is a setup where a customer authorizes you once to charge their card or bank account on a schedule, and the payments then run automatically. It works best when the card or bank details are stored securely by your payment gateway, the customer’s permission is on file and someone watches for declines.

Medical and dental practices, schools, gyms, service companies, software sellers, nonprofits and B2B suppliers all use it. The details differ, but the moving parts are the same.

How recurring billing works

1. The customer agrees. They accept the amount, the schedule, how long it lasts and how to cancel.
2. Payment details are stored securely. The card or bank account is saved in your gateway’s secure storage, often called a vault. Your systems keep a token, a stand-in reference, instead of the real number.
3. The schedule runs. On each billing date, the gateway charges the stored card or sends an ACH debit.
4. You review the results. Approved payments settle to your bank. Declines and returns go on a list for follow-up.

The schedule can be fixed (the same amount every month) or variable (an amount that changes, such as usage-based service or a balance on a payment plan). Variable amounts usually need clearer notice to the customer, and it is good practice to send a receipt after every charge so the customer always knows what was taken and why.

Card or ACH for recurring payments

	Stored card	ACH debit
Customer provides	Card number and expiration	Routing and account number
Approval	Instant on each charge	No instant approval, returns can come later
Main failure	Expired, lost or replaced cards	Closed accounts, insufficient funds
Cost shape	Mostly a percentage of the amount	Often a flat per-payment fee
Good for	Smaller monthly amounts, consumers	Larger amounts, tuition, rent, B2B contracts

Many businesses offer both and let the customer choose. For a deeper comparison, see ACH vs. credit card for invoices.

The customer permission you need

Card-brand rules and ACH rules both expect you to get the customer’s agreement before you charge them on a schedule, and to keep a record of it. A good authorization covers:

• The amount, or how the amount is calculated if it varies.
• How often you will charge, and on what date.
• How long the arrangement lasts, or that it continues until cancelled.
• How the customer can cancel, in plain words.
• For ACH, the customer’s agreement to debit their bank account.

Keep a copy: a signed form, a checkbox record from your website with a timestamp, or a recorded phone approval. When a customer disputes a charge months later, that record is what answers the question. Some states also have rules on automatic renewals and cancellation, so check current rules for your business. This is general information, not legal advice.

Keeping declines and disputes low

Most recurring payments that fail do so for ordinary reasons: a card expired, a bank replaced a card after fraud, or an account ran short that day. A few habits help:

• Use a card updater where available. Some gateways can request updated card details from participating banks when a card is replaced.
• Retry thoughtfully. A second attempt a few days later often succeeds. Retrying over and over the same day doesn’t.
• Tell customers before the charge. A reminder email for annual or variable charges heads off “I don’t recognize this” disputes.
• Use a clear billing name. The name on the customer’s statement should be one they recognize.
• Make cancelling easy. A customer who can’t find a way to cancel often calls their bank instead, which turns into a chargeback.

Never store full card numbers in spreadsheets, notes or email. Use the gateway’s secure storage. It is safer for your customers and keeps more of your systems out of PCI scope. See PCI compliance help.

A setup checklist before the first charge

Most recurring billing problems start in the first week, not the first year. Before you switch on a schedule, run through this list with whoever owns billing:

1. Decide which plans, amounts and billing dates you will offer, and write them down in one place.
2. Choose card, ACH or both, and decide whether customers can switch between them.
3. Draft the authorization wording and get it on your sign-up form, website checkbox or phone script.
4. Turn on the gateway’s secure storage and confirm that staff never see or write down full card numbers.
5. Set the name that will appear on customers’ statements and make sure they will recognize it.
6. Choose a retry rule for declines and a template email asking customers to update their card.
7. Agree who checks the decline and return list, and how often.
8. Run one small test charge on a real card or account and confirm it reaches your bank and your accounting software.

For B2B contracts, add one more step: confirm whether the customer’s accounts-payable team wants a receipt or invoice copy with each charge. Many do, and sending one automatically saves calls. If your invoices come out of QuickBooks or an ERP, the receipt can often be generated there.

What PayZoom does

We set up recurring billing through your payment gateway, using its secure card storage, and add ACH debits where they fit. We help you write clear authorization language and connect billing to QuickBooks invoicing or your ERP where it makes sense. We help you stay PCI compliant instead of charging a non-compliance fee, and there are no early termination fees. When a schedule needs changing, a real person answers the phone. Related reading: payment links and invoicing.