“I want to cancel.”
Voluntary cancellation
Coffee subscription
Subscription canceled
Your cancellation is confirmed.
StatusCanceled
Make leaving clear and easy.
Respect the request. Confirm the cancellation.
Subscriptions & Recurring Billing
The first payment is only the beginning.
Keep the second payment, the tenth payment and every renewal moving.
Month 1
First order
Payment approved
Month 2
Next delivery
Renewal approved
Month 3
Ready to ship
Payment declined
A subscription payment changes after the first transaction.
Each billing cycle is its own payment event. The first payment and later charges can behave differently with issuers.
Customer-Initiated
The customer starts the subscription.
At signup, the customer authorizes the first payment and agrees to store their credential.
Merchant-Initiated
The merchant submits the next scheduled payment.
Later renewals use the stored credential and appropriate recurring indicators.
Illustrative example
- 01
Sign up
- 02
First payment & credential stored
- 03
Renewal approved or declined
- 04
Appropriate next action
Measure recurring performance separately from initial checkout.
Explore Approval Rate Optimization →The customer may stay. Their payment credential may not.
Cards expire, accounts are replaced and issuers update credentials. Account updater services and network tokens can help keep stored credentials current.
Updater and token capabilities depend on the provider, network, issuer, region and integration. Updates are not universal — not every credential can be updated.
Renewals, retries & customer continuity
A decline does not automaticallymean ‘try again.’
The right response starts with understanding why the payment was declined.
Renewal declined
Review the issuer response before acting.
Choose the next step
Same declined payment.Different next steps.
Temporary issue
Wait or retry where appropriate.
Follow the issuer response and applicable retry rules.
Credential issue
Update payment details or contact the customer.
Check whether the stored payment method needs attention.
Stop instruction
Stop further attempts as required.
Follow the stop instruction rather than repeating the payment.
Read the response. Then choose the next step.
There is no universal retry schedule. Appropriate action depends on the issuer response, billing model, provider capabilities and network rules.
- Credential updates
- Billing cadence
- Customer communication
- Provider configuration
Illustrative examples. A retry is not guaranteed to be approved.
Can your subscriptions move with you?
Changing providers can mean migrating stored credentials — or asking customers to update their payment details.
Migrate existing tokens.
*30 days plus to migrate, if approved. Transactions processed during the migration window will not transfer.
Confirm timing and transfer scope with the providers.
Preferred route
Send customers a payment update link.
Faster to initiate. No waiting for token migration.
Customers still need to complete the update.
Illustrative examples. These scenario notes are not guaranteed provider service levels. Where credentials are tokenized and stored affects whether subscriptions can continue if you change gateways, processors or billing platforms.
Gateway, processor and network tokens carry different provider dependencies. Token ownership, export and migration capabilities vary by provider and integration; tokens cannot always be exported or migrated.
Explore Gateways & Token Portability →Subscriptions & customer experience
Keep the customerexperience clear.
A customer who cancels and a payment that fails need different responses.
“I want my next delivery.”
Payment failure
Coffee subscription
Your payment didn’t go through
Update your payment details if you want the next delivery.
Next step: update payment method.
Make fixing a payment clear and easy.
Explain what happened and provide a clear next step.
Illustrative customer messages—not live account controls.
Payment recovery should never prevent customers from exercising legitimate cancellation rights.
Upcoming renewal
Your next coffee renewal is approaching.
Payment issue
Please update your payment method.
Clear confirmation
Confirm the update or cancellation.
Illustrative examples.
Balance recovery with customer experience.
Review fraud controls and chargeback risk alongside recovery. Clear receipts and recognizable billing descriptors also matter.
Measure before changing.
Change one meaningful variable. Compare what happens next.
Approvals
Separate first payments from renewals.
Declines & retries
Understand reasons and recovery outcomes.
Credential updates
Review updater and token activity.
Customer & risk
Track cancellations, refunds and disputes.
- Baseline
- Controlled change
- Measure
- Compare
- Expand / revise / reverse
Analysis depends on transaction volume, integrations and available data. Testing methods also depend on processors and billing platforms.
Review the environment behind every renewal.
Assess
Map the billing platform, gateway, processor, merchant accounts (MIDs), token setup and recurring authorization performance.
Advise
Identify opportunities across retries, credential updates, token portability, architecture and customer communication.
Implement
Help coordinate approved changes with processors, gateways, subscription platforms and other technology providers.
Optimize
Measure recurring-payment performance and keep evaluating as volume and customer behavior change.
Architecture consideration
One processor and merchant account is often appropriate. As volume, brands or risk grow, additional MIDs or routing may deserve evaluation — subject to compatibility, underwriting and processor, acquirer and card-network rules.
Explore Payment Architecture →Review My Recurring Payments
Understand the failure before choosing the fix.