---
title: "Recurring payments: A guide to how they work and why they fail"
slug: recurring-payments-guide
excerpt: "Recurring payments let a business charge a customer's stored payment method on a schedule. This guide explains how the flow works, why payments fail and how they're recovered, the rules that apply, and what to look for in subscription billing software."
customExcerpt: "Recurring payments let a business charge a customer's stored payment method on a schedule. This guide explains how the flow works, why payments fail and how they're recovered, the rules that apply, and what to look for in subscription billing software."
metaTitle: "Recurring payments: How they work and why they fail"
metaDescription: "Learn how recurring payments work, from stored cards to retries, why they fail, and what subscription billing software should handle for you."
featureImage: "https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/images/2026/09/blog-How-recurring-payments-work.png"
status: published
publishedAt: "2026-09-18T07:29:57.000Z"
updatedAt: "2026-09-19T07:31:00.000Z"
createdAt: "2026-09-09T06:00:37.511Z"
tags:
  - { name: Payments, slug: payments }
  - { name: "#Subscriptions", slug: subscription }
authors:
  - { name: Liv Carr, slug: oliviacarr }
  - { name: Keisha Singleton, slug: keisha }
---

# Recurring payments: A guide to how they work and why they fail

## Key takeaways

- Recurring charges depend on a stored-credential chain: customer authorization, tokenization, and renewals that reference the first transaction.
- Cancellation revokes your right to charge the card, so bill fixed commitments as disclosed installment plans instead.
- Choose billing software for proration, dunning, taxes, pauses, and plan changes – not just for charging cards.

Recurring payments are automatic charges to a customer's stored payment method at agreed intervals (weekly, monthly, or annually), after the customer authorizes them once. 

They're what make subscriptions work; nobody completes each transaction by hand.

Subscription billing software is what runs them, storing the payment method and scheduling the charges. Collecting payment is only one part of running a subscription business, though. 

Billing software can also manage pricing plans, trials, upgrades and downgrades, pauses, cancellations, invoices, failed-payment recovery, taxes, and reporting across the subscription lifecycle.

This guide explains how recurring payments actually work behind the scenes, why they fail and how billing software recovers them, the card network rules that apply to subscriptions, and what to look for when choosing a provider. 

## What is a recurring payment?

A recurring payment is a charge a business initiates on a schedule, using a payment method the customer saved and authorized once. 

The customer isn't present for the renewal; the business submits it under the agreement made at signup. That's what distinguishes it from a one-off purchase, and it's why the card networks, banks, and regulators treat it differently.

Any business selling ongoing access uses them: [SaaS](https://whop.com/blog/choosing-the-right-saas-billing-solution-for-your-business/), streaming, paid communities, courses, [memberships](https://whop.com/blog/sell-memberships-online/), coaching, and subscription boxes.

### What is subscription billing software?

[Subscription billing software](https://whop.com/blog/subscription-billing-software/) automates recurring billing and manages everything that can change what a subscriber pays, including plans, renewals, upgrades, downgrades, pauses, and cancellations. 

Most billing software can also generate invoices, calculate taxes, retry failed payments, send payment reminders (known as dunning messages), and track revenue.

Say a customer upgrades halfway through the month. The software can calculate the prorated amount, update their subscription, and charge only the difference. If their next payment fails, it can retry the charge and contact the customer – without someone on your team stepping in.

According to The Business Research Company, the subscription billing management market value is expected to grow to $20.61 billion by 2030 at a compound annual growth rate (CAGR) of 17.2%.

### Subscription billing vs subscription management vs recurring billing

These terms overlap, but they describe different parts of the subscription stack:

<table>
  <thead>
    <tr>
      <th>Term</th>
      <th>What it covers</th>
      <th>Example</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Recurring billing</td>
      <td>The mechanical act of charging a stored payment method on a schedule</td>
      <td>A $29 charge hitting a customer's card on the 1st of every month</td>
    </tr>
    <tr>
      <td>Subscription billing</td>
      <td>Recurring billing plus the pricing logic around it – plans, trials, proration, discounts, invoicing, tax</td>
      <td>Moving a customer from a $29 plan to a $59 plan on day 15 and charging the prorated difference</td>
    </tr>
    <tr>
      <td>Subscription management</td>
      <td>The full customer lifecycle – signup, plan changes, pauses, cancellations, win-back, reporting</td>
      <td>A customer pausing for two months from their account page, then resuming without re-entering card details</td>
    </tr>
  </tbody>
</table>


In practice, most subscription billing platforms also provide subscription management, [payment processing](https://whop.com/blog/payment-processors/) integrations, dunning, tax, and reporting, so vendors often use "subscription billing" and "subscription management" interchangeably.

Not every recurring payment requires sophisticated subscription billing. 

Fixed monthly payments can be simple; subscriptions become more complex once plan changes, trials, or failed payments alter what's owed from one cycle to the next. 

## How do recurring payments work? (Step by step)

Recurring payments work by getting the customer's permission to save a payment method and charge it again on an agreed schedule. After the initial setup or payment, the business can submit future renewal charges without asking the customer to enter their card details each time.

Behind that relatively simple experience is a chain of authorization, tokenization, transaction tagging, billing logic, and settlement. 

Here's what happens from signup all the way through to renewal.

### 1. The customer authorizes the recurring charge

The entire recurring payment process starts when the customer agrees to the subscription and gives the business permission to charge them again in the future. 

The checkout should make the repeated nature of the purchase clear, including what the customer is buying, how much they'll pay, how often they'll be charged, and the applicable cancellation or subscription terms.

That consent matters beyond the initial purchase. A merchant-initiated transaction (MIT) must be based on an agreement that allows the business to initiate later payments without the customer actively starting each transaction.

Example: Someone joining a $30/month membership isn't simply authorizing today's $30 payment. They're also agreeing that the business can initiate another $30 payment on the next billing date, subject to the subscription terms.

This is the same process whether you're signing up for a local gym membership, paying for career coaching, or joining a stock trading community. 

#### What about minimum terms and lock-in periods?

Minimum commitments are legal in the US and most other markets, but they're treated as a material term: under ROSCA and state auto-renewal laws (California's law names "the minimum purchase obligation" specifically), the term and any early-termination fee must be disclosed clearly before you collect payment details, and the customer has to actively agree. 

The DOJ, acting on an FTC referral, sued Adobe in 2024 over a buried early-termination fee. Adobe agreed to a $150 million settlement in March 2026, split between a civil penalty and free services.

**Card networks also have guidelines**: under Visa and Mastercard rules, when a customer cancels, they withdraw permission to charge their card – even if the contract still has months to run. Keep charging and you'll [lose the disputes](https://whop.com/blog/chargebacks/). 

That means that any balance still owed has to be collected separately, by invoice or collections. So, if you want a fixed commitment billed by card, structure and disclose it as an installment plan (often sold as "split payments"), which the networks treat differently from an open-ended subscription. 

### 2. The payment method is stored as a token, not a card number

When a customer enters their card at checkout, the business doesn't keep the card number. The payment provider swaps it for a token – a reference that points to the card but is useless on its own – and that token is what gets charged at every renewal.

Tokens shrink the security problem – less card data in your systems means less to protect and a smaller PCI DSS footprint, though not zero. PCI DSS still applies to any business that handles card data or can affect the security of the systems that do.

There are two kinds. A provider token is issued by your payment provider and works only with them (which is why switching billing platforms usually means migrating tokens). 

A network token, on the other hand, is issued by Visa or Mastercard. These tokens are tied to the card account rather than the 16-digit number, so when a card is reissued after expiry or loss, the token keeps working (and the renewal goes through). 

In a September 2023 press release, Adyen reported an average 3% uplift in authorization rates among businesses using its network tokenization – but this is just one provider's data, not an industry benchmark.

### 3. The first charge is a customer-initiated transaction (CIT)

When the customer is present and starts the subscription, the initial payment is normally a customer-initiated transaction, also known as a CIT. 

This establishes the payment relationship and records that the credential is being saved for future use when the customer isn't present. 

In markets with Strong Customer Authentication (SCA) rules, such as the UK and EU, this is also where authentication such as [3D Secure](https://whop.com/blog/whop-3d-secure/) (3DS) takes place. The first payment generally needs to satisfy SCA before later payments can qualify for the recurring-payment exemption. 

3DS2 (the version in use today) can often authenticate in the background, so the customer doesn't necessarily see an extra challenge screen.

3DS isn't required in the US, but sellers can still run it on the first charge. 

Whatever happens with authentication, the provider stores the ID of this first transaction, and every renewal that follows references it.

### 4. Renewals run as merchant-initiated transactions (MITs)

On the next billing date, the subscription system initiates the payment automatically instead of waiting for the customer to return to checkout. 

For card payments, the renewal is flagged as a stored-credential MIT, so the card network and the issuing bank can see the business is charging a card the customer already approved under an existing agreement. 

That's why a subscriber normally doesn't have to complete 3DS every month. In SCA markets, qualifying subsequent recurring payments or MITs can be processed without the customer actively authenticating each charge. 

However, the issuing bank can still require authentication, in which case the business needs a way to bring the customer back on-session to complete it.

Each renewal carries the ID of that first transaction from step 3, which is how the issuer can tell a $30 charge is month four of an agreement the customer approved, rather than a random card-not-present purchase. 

A renewal can be declined like any other card charge (expired card, insufficient funds, or a bank's fraud filter), which is where failed-payment recovery comes in.

### 5. The payment settles and the customer gets a receipt or invoice

Once the issuer authorizes the renewal, the payment follows the normal card flow, it's captured and then settled to the business through its payment provider or acquiring bank (usually within a day or two). 

The billing platform records the successful payment against the customer's subscription and updates its status for the new billing period. 

Depending on the setup, it can also generate an invoice or receipt, email it to the customer, update revenue records, and pass the transaction into accounting or reporting systems. 

Receipts aren't just a courtesy: Visa requires subscription receipts to include a simple way to cancel online, and Mastercard recommends sending one after every billing with cancellation instructions.

If the issuer declines the renewal instead, the subscription doesn't end on the spot – subscription billing software will usually try to recover it. 

### 6. The billing system handles upgrades, downgrades, pauses, and cancellations

Recurring billing isn't just a timer that charges the same amount every month; the amount and next billing date can change as the subscription changes. 

Billing systems keep track of the customer's plan, payment cycle, credits, discounts, usage, and subscription status so the next charge reflects what they're actually subscribed to.

Take a customer paying $30 per month who upgrades to a $60 plan halfway through a 30-day billing period. They've already paid $30 for the month, but there are 15 days remaining:

- Unused old plan credit: $30 × 15/30 = $15 credit
- New plan for remaining 15 days: $60 × 15/30 = $30
- Prorated amount due: $30 − $15 = $15

The customer therefore owes an additional $15 for the remainder of that billing period, then $60 at the next full renewal. A billing platform can calculate that adjustment automatically rather than charging the customer twice for the same 15 days. 

So, what about downgrades? They tend to work in the opposite direction by creating a credit for unused time. 

Pauses can stop future billing, while cancellation can either end access immediately or keep the subscription active until the period the customer has already paid for expires. Cancellation also retires the stored credential so no further MITs are attempted. 

## Types of recurring payments and billing models

Recurring payments fall into three main types: fixed, variable, and hybrid. The subscription can then use different billing models such as flat-rate, tiered, per-seat, or usage-based. 

Fixed recurring payments charge the same amount each billing cycle, while variable payments change based on factors such as usage or quantity. Hybrid payments combine a predictable base charge with a variable component.

**Subscription billing software manages both sides**: when a customer should be billed, and how much they owe for each billing period. 

<table>
  <thead>
    <tr>
      <th>Model</th>
      <th>Type</th>
      <th>How it works</th>
      <th>Example</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Flat-rate</td>
      <td>Fixed</td>
      <td>One price for one plan</td>
      <td>$20/month community access</td>
    </tr>
    <tr>
      <td>Tiered</td>
      <td>Fixed</td>
      <td>A few plans at different price points, each with its own features or limits</td>
      <td>Basic $10, Pro $30, Team $80</td>
    </tr>
    <tr>
      <td>Per-seat</td>
      <td>Variable</td>
      <td>A price per user, so the bill scales with team size</td>
      <td>$15 per member/month</td>
    </tr>
    <tr>
      <td>Usage-based</td>
      <td>Variable</td>
      <td>Charged on what was consumed (API calls, messages, storage), calculated once the cycle ends</td>
      <td>$0.10 per API call</td>
    </tr>
    <tr>
      <td>Hybrid</td>
      <td>Fixed + variable</td>
      <td>A fixed base fee with a usage component on top</td>
      <td>$100/month + overage</td>
    </tr>
  </tbody>
</table>


Typically, fixed billing is the simplest because the system already knows the amount of the next charge. 

Variable and hybrid billing require the platform to collect usage or quantity data, apply the correct pricing rules, and calculate the final amount before an invoice or payment can be created.

### Which payment methods can you use for recurring billing?

Subscriptions can be charged to [payment methods](https://whop.com/blog/payment-methods/) like cards, bank debits (such as ACH and SEPA), and supported digital wallets. Recurly's State of Subscriptions Report for 2026 showed debit cards were the most popular payment method at 48.8% of Recurly's own transactions in the US, followed by credit cards at 34.7%. 

The best option depends on where your customers are, how quickly you need payment confirmation, transaction cost, and how likely the underlying credential is to change.

Cards are popular because they authorize fast and nearly every consumer has one, but card credentials can expire or be replaced – and even when they don't, the card can be declined for lack of funds. 

ACH and SEPA debit pull money from a bank account instead, avoiding card-expiry failures. The downside to bank payments is that they generally take longer to confirm. Bank debits also fail differently from cards. 

When a bank debit fails, it comes back days later as a return code rather than an instant decline. Under Nacha's rules, an insufficient-funds return can be retried at most twice, and a closed-account return can't be retried at all.

Wallets can make checkout easier, but recurring-payment support depends on the wallet, market, and payment provider. Look at the actual authorization, return, and recovery rates for your own customer base.

## What happens when a recurring payment fails?

When a recurring payment fails, the billing system will usually retry the payment automatically, ask the customer to update their payment method, or eventually pause or cancel the subscription if it can't collect the money. 

What happens next depends on why the payment failed. Some declines are temporary and may succeed on a later attempt, while others require a new or updated payment method. 

[Stripe](https://whop.com/blog/what-is-stripe/) states its revenue recovery tools recover 55% of failed payments on average, recovering $8.2 billion in failed payments in 2025. 

### Why do recurring card payments fail?

Recurring card payments can fail because the customer has insufficient funds, the card has expired or been replaced, the account has been closed, the issuer suspects fraud, or the issuer declines the transaction for another reason.

In Churnkey's State of Retention 2025 report, insufficient funds accounted for almost half of all failed card payments.

Card changes are more common than most sellers assume: Visa says about 30% of the card accounts in an issuer's portfolio get a new number, a new expiry date, or are closed every year. 

Billing platforms handle this through account updater services, where the card networks push the new details to the business automatically, so the next renewal goes through without the customer re-entering anything.

Subscription billing platforms commonly distinguish between soft and hard declines:

- A soft decline may be temporary or recoverable. Insufficient funds is the obvious example: the same transaction might work once the customer's payday has passed. Most failures fall into this bucket – [Chargebee](https://whop.com/blog/chargebee-ultimate-review/)'s analysis of 5.36 million transactions found 80–90% of declines were soft, which is why retrying works as often as it does.
- A hard decline indicates that simply submitting the same payment again is unlikely to fix the problem. A closed account is one example, where the customer would need to provide another payment method.

That distinction usually determines what happens next. Repeatedly retrying a genuinely unrecoverable card wastes authorization attempts and can create a poor customer experience, while immediately canceling a subscription after a temporary decline can turn a short-lived payment problem into unnecessary [churn](https://whop.com/blog/what-is-churn/).

### How do retries and dunning recover failed subscription payments?

Retries and dunning recover failed subscription payments by trying recoverable charges again when they're more likely to succeed, or contacting the customer when their action is needed. 

A dunning flow can include automatic retries, failed-payment emails, prompts to update a card, a grace period before access is removed, and eventual cancellation if payment can't be collected.

Instead of canceling a subscription after the first decline, the billing system can keep it in a past-due or grace-period state while it attempts to collect the outstanding payment.

And when you retry matters as much as whether you do: Adyen's data shows US payments succeed more often at the start and middle of the month, when most people are paid, while UK payments spike toward month-end. 

**Checkout.com's guidance is blunter**: a payment declined for insufficient funds "is not going to go through if you immediately retry it."

Retries aren't unlimited, though. Visa caps them at 15 attempts in 30 days, and bans them entirely for declines the issuer will never approve, like a closed account. Go past that and you pay a fee for every extra attempt.

With Mastercard, most declines come with an advice code that tells you what to do next – try again later, get new card details, don't try again, or wait a set time before retrying.

## What the card networks require of subscription sellers

Visa and Mastercard both set rules for how subscriptions are sold and canceled, and they apply to any business taking recurring card payments. 

Both networks require sellers to disclose recurring billing terms, capture affirmative consent, confirm enrollment electronically, and provide a way to cancel future payments online. 

**Extra rules apply to some trials**: Visa requires a reminder at least seven days before the first charge following a qualifying [free trial](https://whop.com/blog/add-free-trials/) or introductory offer, while Mastercard requires a three-to-seven-day reminder before trials lasting more than seven days end. 

A capable billing platform should make these requirements easier to meet by recording consent, scheduling required notifications, providing online subscription management and cancellation, and stopping future charges after cancellation. 

The seller still needs to configure the offer correctly and make sure its pricing, renewal frequency, trial terms, and cancellation terms are clearly disclosed at checkout.

## What to look for in recurring payment and subscription billing software

The best way to compare subscription billing platforms is to ask what you'll still have to build or manage yourself.

The best recurring payment and billing software handles recurring card transactions correctly, stores credentials securely, and sets the right CIT/MIT and recurring-transaction indicators – rather than simply saving a card and running it again. 

- What happens when a payment fails? Does the platform automatically distinguish recoverable failures, schedule retries, contact customers, and give them a way to update their payment method, or will your team need to build that logic?
- Can subscriptions change without manual intervention? Check how the platform handles upgrades, downgrades, quantities, pauses, cancellations, credits, and trials – including what happens to the customer's next invoice when a change occurs halfway through a billing period.
- Which payment methods can customers use? Card support is the baseline. Depending on your market, you may also want ACH, SEPA Direct Debit, digital wallets, and local payment methods.
- How is tax handled? Find out whether the platform calculates tax itself, integrates with a tax provider, or leaves calculation, collection, and filing to you.
- What can you actually see? At minimum, a subscription business should be able to view its recurring revenue, active subscriptions, new and canceled subscriptions, churn, failed payments, and recovered revenue. If you have to export transaction data and reconstruct those numbers yourself, you're still building part of the billing system.

### How recurring billing works on Whop

Whop makes it simple to [set up recurring billing](https://whop.com/blog/recurring-billing-for-saas/) for SaaS, community access, coaching, and more.

When a payment fails, Whop moves the subscription to past due, emails the customer to update their card, retries over five days, and lets you decide whether access continues in the meantime. 

Your members see a self-service portal (with a link you can drop into emails or your app) where they can change cards, see invoices, and cancel their subscriptions without emailing anyone. Invoices are auto-generated as part of your billing. 

At checkout, sellers can add a free trial, a one-time setup fee, or split payments – so a higher-ticket annual plan can be billed as a set number of installments, the structure the card networks treat differently from an open-ended subscription.

Whop supports cards, PayPal, bank transfers, local payment methods, crypto, and BNPL, though some wallets and BNPL options are one-time only. 

You can also opt in to [tax calculation](https://whop.com/blog/whop-tax-service/), collection, and remittance as a 2% add-on. 

### What does recurring payment and billing software cost?

Subscription billing software can be charged as a fixed monthly fee, a percentage of billing volume, or pricing may be bundled into a broader payments product. 

That makes headline prices difficult to compare, as one provider may charge separately for billing and payment processing, while another combines them.

At the mid-market end, standalone billing products can run into hundreds of dollars per month. Many providers instead charge a fraction of each dollar billed, meaning the software cost scales with subscription revenue. You then need to add [payment processing fees](https://whop.com/blog/payment-processing-fees/) where they're separate.

Here's a look at five of the top providers, their billing fees, processing rates, and how that works out for a seller billing $10,000 a month across 500 subscriptions at $20.

For providers that don't offer processing, we've used Stripe's card rate as an example.

<table>
  <thead>
    <tr>
      <th>Provider</th>
      <th>Billing fee</th>
      <th>Processing fee</th>
      <th>Total/month</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Whop</td>
      <td>0.5% ($50)</td>
      <td>2.7% + $0.30 ($420)</td>
      <td>$470</td>
    </tr>
    <tr>
      <td>Stripe Billing</td>
      <td>0.7% ($70)</td>
      <td>2.9% + $0.30 ($440)</td>
      <td>$510</td>
    </tr>
    <tr>
      <td>Chargebee Flow</td>
      <td>0.8% ($80)</td>
      <td>Via your gateway, e.g., 2.9% + $0.30 ($440)</td>
      <td>$520</td>
    </tr>
    <tr>
      <td><a href="https://whop.com/blog/recurly-review/">Recurly</a> Starter</td>
      <td>$249 flat, first $40K/mo included ($249)</td>
      <td>Via your gateway, e.g., 2.9% + $0.30 ($440)</td>
      <td>$689</td>
    </tr>
    <tr>
      <td><a href="https://whop.com/blog/what-is-paddle/">Paddle</a></td>
      <td colspan="2">5% + $0.50 all-in, including processing, billing, and tax ($750)</td>
      <td>$750</td>
    </tr>
  </tbody>
</table>


On Whop, standard payment acceptance is 2.7% + $0.30 per successful domestic card transaction, with +1.5% for international cards and +1% for currency conversion. Billing is 0.5% per transaction when enabled, including automated invoice generation, retries, and lifecycle handling. 

**[Whop pricing](https://whop.com/network/pricing/)**

## Manage recurring payments, subscription billing, and migrations with Whop

![Video thumbnail](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/05/mailmend_thumb.jpg)
[Watch video](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/05/mailmend.mp4)

Collecting the first customer payment is the easy part. 

What tends to make subscription billing harder for businesses is everything that happens afterward: renewals, reissued cards, retries that still respect the network's limits, receipts, [invoice generation](https://whop.com/blog/whop-invoices/), managing cancellations, and upgrades. 

You can build all of that yourself, and some businesses do. But for most sellers, the point of recurring payment software is that someone has already built it and tested it. 

Whop's billing handles it all as a layer within payment acceptance: retries and dunning over five days, a self-service portal your customers can actually use, and pricing that scales with what you bill.

Already billing through Stripe? Whop Migrations moves your active subscriptions and their payment tokens across in one click, so customers keep renewing on their normal date without re-entering a card.

Create a product, set the billing cycle, share the checkout link, and the second charge takes care of itself.

**[Sell subscriptions with Whop](https://whop.com/network/)**

---

## Subscription billing and recurring payment FAQs

### What is the difference between recurring payments and subscription billing?

Recurring payments are automatic transactions made on a set schedule, while subscription billing manages the rules that determine when and how much a customer is charged. For example, subscription billing tracks plans, billing cycles, trials, upgrades, taxes, and failed payments, then uses that information to generate the appropriate recurring charge.

### What is an example of a recurring payment? 

A $20 monthly membership that automatically charges the customer's saved card each month is an example of a recurring payment. Other examples include SaaS subscriptions, streaming services, gym memberships, insurance premiums, and usage-based services that automatically collect payment on a regular billing cycle.

### Are recurring payments secure? 

Yes. Recurring payment providers tokenize card details, so the business never stores the raw card number. That token is what gets charged for each renewal. Businesses accepting cards must still follow PCI DSS requirements for protecting cardholder data, but the right subscription billing software handles most of this for you as part of its infrastructure.

### What happens if a customer's card expires or their payment fails? 

The billing platform may update the stored card credential automatically or retry a failed payment before canceling the subscription. Account updater services and network tokens can keep credentials current when participating cards are replaced or expire. For recoverable declines, billing software can also schedule retries and use dunning emails to ask the customer to update their payment method.

### Do recurring payments require 3D Secure or SCA every time? 

No. Where SCA rules apply, the customer authenticates once, on the first payment that sets up the agreement. Later renewals are merchant-initiated transactions and run without the customer present, so no 3D Secure challenge is needed. But an issuer can occasionally request authentication, in which case the customer is brought back to verify.

### Can a business keep charging my card after I cancel? 

A business shouldn't continue making recurring charges after you've canceled and withdrawn authorization for future payments. Card-network rules provide dispute mechanisms for recurring transactions made after authorization has been withdrawn. However, canceling future recurring payments doesn't remove an outstanding balance you already owe.

### How do I stop or cancel a recurring payment? 

You stop or cancel subscriptions through the business you originally authorized to take the recurring payments. This is usually available through its account or billing portal. Keep the cancellation confirmation for your records. If charges continue after you've withdrawn authorization, contact the business and, where appropriate, your card issuer or payment provider to dispute the transaction.
