Andorpay
Back to the blog

Published on · Updated on

Failed subscription renewals: recover payments

Check payment status, guide customers and coordinate retries with access. Handle failed renewals without duplicate charges or unclear outcomes.

Renewal calendar and card with a warning beside a magnifying glass for checking the payment.

When a subscription renewal fails, first establish what happened to the payment. A decline, a pending operation and a confirmed charge require different responses. You can then notify the customer, request an action when needed and apply the agreed access policy. Repeating a charge before resolving the previous attempt can create a duplicate payment.

Improving renewals means finding where the journey breaks down and fixing that part: scheduling, the payment attempt, the bank response, customer communication or service access. At AndorPay, we connect payment and subscription status with your operations so that you can identify the issue and choose the next action with the relevant context.

A renewal can be in several different situations

Reaching the scheduled date does not mean the money has been collected. A scheduled action may not have run yet. An attempt may be in progress. A transaction may have finished while the application has not yet received or processed its result.

It is also useful to separate the customer's intention to continue from payment confirmation. Someone may want to keep using the service but encounter a problem with their payment method. Alternatively, they may have cancelled, in which case a continuing payment schedule is the issue. These situations call for different records and different decisions.

Always connect the customer, subscription, service period and transaction. That relationship tells you what was being collected and why. A list of error messages without identifiers forces your team to reconstruct the story each time and makes it easier for two people to act on the same case independently.

Check the status before requesting another payment

A browser message is evidence about the customer's experience, but not sufficient evidence of the financial outcome. If someone says “the page kept loading”, do not assume their payment failed. Check the transaction and relevant notifications before asking them to try again.

Our payment lifecycle documentation separates confirmed payment from subscription changes. Use the confirmed result for the financial operation and period information for the service. A subscription being created or updated does not replace checking the charge itself.

Observed situation What to check Next action
Confirmed payment Associated customer and period Update access and close payment follow-up
Confirmed decline Result and required action Apply the recovery route supported by the available information
Pending confirmation Current status of the same transaction Continue checking without creating another charge
Renewal not started Schedule, configuration and execution Resolve the cause before initiating the intended attempt
Payment confirmed, access incorrect Event delivery and application update Repair access using the existing payment
Cancellation before renewal Effective date and scheduled actions Review and stop an action that should not occur

The table gives the investigation an order. It does not replace system detail, but it prevents every incident being labelled a declined card. When money is confirmed and access is missing, the outstanding work is service delivery.

Separate payment problems from integration problems

A declined transaction may require customer action. A renewal that never started points towards scheduling or configuration. An unprocessed notification may leave a successful payment absent from the application. Grouping these situations hides the cause and encourages fixes that do not address it.

For each incident, retain the subscription reference, expected period, transaction, attempt time, confirmed status and last action. Add the owner and next step. You do not need to copy sensitive card data for this record to be useful.

If you use WooCommerce Subscriptions, its renewal process documentation explains how that product relates renewals and orders. It helps you understand that specific tool; it does not establish that another installation uses the same rules. Identify which system schedules your payments and which processes the outcome.

Write messages that help customers take action

A useful message says what you know and provides a next step. Do not attribute a decline to insufficient funds unless the result supports that explanation. Do not announce cancellation when you have only identified a pending payment. Precision matters, particularly when customers can see a transaction in their banking application.

When the payment method needs updating

A practical notice could say: “We could not complete your service renewal. Please update your payment method using the link provided so that we can continue processing it. Your access remains available until the date shown in your account.” Only use that final sentence if it reflects your actual policy and the date is available.

The link should lead to the relevant action and clearly identify the service. Sending customers to a generic page where they must search for a solution adds support work. Test the journey with a test account, including what happens after the update has been completed.

When the outcome is still pending

You might say: “We are checking the result of your renewal. You do not need to repeat the payment at this stage. We will let you know the next step once the result is confirmed.” This message requires real follow-up. Assign an owner rather than leaving the customer waiting without anyone responsible for checking.

When payment succeeded but access is missing

State both facts: “Your payment is confirmed. We are updating your service access; you do not need to pay again.” The repair should use the existing transaction. Requesting another payment to unlock a screen does not resolve the inconsistency and may charge the customer twice.

Give payment retries one clear control rule

A retry needs a known reason, a resolved previous outcome and a rule identifying who initiates it. Some issues require customer action; others require an integration fix or review of the banking setup. There is no universal sequence that recovers every declined payment.

Before another attempt, check that the period is still unpaid, that no confirmed or ongoing operation exists, and that no other action is already scheduled for the same charge. Then associate the new attempt with the same payment obligation so that the history remains understandable.

If your software already manages retries, review its rules before adding another automation. The WooCommerce Subscriptions retry documentation describes that product's own process. A manual action and a scheduled action can conflict if nobody coordinates them.

In AndorPay, payment and payment-method events communicate changes to the integration. Our webhook guide explains their meanings. The recovery scope must be defined for your installation; an event name alone does not establish that a particular automatic retry schedule is enabled.

Prevent duplicate effects when handling notifications

The same notification may be delivered again. Your application needs to recognise that the corresponding business action has already happened. Confirming an existing payment again should not extend access a second time, create another delivery or record another sale for the same period.

Also distinguish repeating a message from repeating a financial operation. Reprocessing a notification to repair access may be part of technical recovery. Creating another charge is a different action and requires checking the earlier financial result. Keeping these separate prevents a screen repair from affecting the customer's money.

A simple record helps the team coordinate: “October period, payment confirmed, access pending, owner assigned.” That is more actionable than “subscription broken”. The next person can see what remains to be fixed and which action would be unnecessary.

If two people can handle the same queue, agree how an incident is claimed and updated. The aim is practical coordination: one person checks the result, another can see that work is underway, and the final action is recorded. You do not need a complicated process to avoid contradictory interventions.

Align access with a policy customers can understand

Decide what happens during recovery. You may offer a grace period or suspend service depending on the product. Explain the rule and apply it consistently. The payment system should not accidentally define your commercial policy.

For a content service, you may need to distinguish reading existing material from starting new activities. For a work application, define what a user can view while the issue is being resolved. These are product decisions implemented using the subscription and period state.

Once payment is confirmed, update the relevant access and close outstanding notices. Continuing to send unpaid-renewal messages after the customer has resolved the issue harms the experience. Recovery includes stopping actions that no longer make sense.

If the customer cancels during follow-up, check the effective date and the period associated with any attempt. Cancellation must not disappear among reminder messages. It also does not automatically mean a refund has occurred: these are separate facts and need separate records.

An example: successful payment, unchanged access

Imagine a confirmed renewal payment whose notification was not processed in time. The customer signs in and finds access suspended.

The review finds the confirmed transaction and correct service period. The next action is therefore to repair the access update while keeping that payment as the reference. Afterwards, check that the customer can use the service and that a repeated notification does not extend the period again.

Close the incident when payment and service delivery agree, rather than when someone triggers an action without checking the result. A later reviewer should be able to understand what failed, what was corrected and why another charge was unnecessary.

Compare this with a renewal that never ran. In that case there is no confirmed payment to apply; the schedule needs reviewing and the outstanding attempt needs handling under the agreed rule. The same customer complaint can have different causes, which is why diagnosis starts with the transaction.

Measure each stage to identify the right improvement

First define what counts as an expected renewal. It should be a period genuinely due for renewal after accounting for cancellations and current rules. Then separate renewals that started, those confirmed on the first attempt, those recovered later and those still unresolved at the reporting cutoff.

Count periods as well as attempts. A renewal requiring several operations still relates to one service period. Counting every attempt as a different customer distorts both failures and recovery. Keep both figures, but use them to answer different questions.

For example, identify expected periods that never reached a payment attempt. That points towards scheduling and integration. Among attempted renewals, confirmed outcomes let you examine recovery. Among paid periods, check whether access was delivered correctly. This separates collection from fulfilment.

Use comparable observation windows. A group reviewed on its due date has had less recovery time than one reviewed a week later. Record the cutoff before comparing results. You do not need to promise a percentage improvement to identify a part of the journey that needs attention.

Also keep unresolved results visible. Moving them into a generic failure category may make a report appear complete while hiding the cases most likely to cause an inappropriate retry. A useful review distinguishes “known unsuccessful” from “not yet established”.

A repeatable operational review

Start with unresolved payment outcomes and confirmed payments without access. Continue with declines requiring action and renewals that never started. Finally, check that closed incidents no longer have outstanding reminders or incompatible payment attempts.

Leave four facts for every case: confirmed result, owner, next action and review time. This keeps follow-up from relying on one person's memory. It also makes patterns easier to spot, such as a shared configuration among renewals that did not start.

If you are setting up the system, our guide to subscriptions using an existing payment setup explains how to connect the calendar, payment and application. If incidents are already recurring, tell us how you manage renewals: your bank, platform, visible statuses and what happens to access. We can review the journey and identify the work needed.

Frequently asked questions

Should I retry when the customer cannot see confirmation?

First check the same transaction's status. Missing visual confirmation does not prove the charge failed. If payment is confirmed, repair access or the screen using that payment rather than asking for another one.

Can every decline be solved with another attempt?

No. The customer may need to update their method or complete another action, or the configuration may need correcting. The next step should follow the available result without promising guaranteed recovery.

How do I know the incident is closed?

The payment result is resolved, access matches the applicable policy and no incompatible actions remain scheduled. Record the check so that another person can understand the closure without reconstructing the entire case.

WhatsApp