# Why did a subscription payment fail A failed subscription payment does not have to mean a lost subscriber. Most payment failures are temporary and recoverable if you act on them correctly. This guide explains why they happen, what Subscribee does automatically to recover them, and what you can do as a store owner when automation is not enough. *** ## The Most Common Reasons a Subscription Payment Fails ### Expired Card The card your subscriber used when they first signed up has since expired. This is the single most common cause of failed subscription payments. The customer needs to update their payment method in their account portal. ### Insufficient Funds The charge was declined because the account did not have enough balance at the time of billing. This is often temporary. A retry a day or two later frequently succeeds. ### Bank Blocked the Charge Some banks flag recurring charges, especially from international stores or merchants the card has not been used with before. The customer may need to contact their bank to authorize future charges from your store. ### Card Number Changed The customer received a new physical card with a different card number (after losing their old one, for example) and has not updated their payment details yet. ### Card Reported Lost or Stolen The card on file was reported lost or stolen and has been deactivated by the bank. The customer will need to add a new card. ### Soft Decline vs. Hard Decline Not all failed payments are the same. A **soft decline** is temporary (insufficient funds, bank hold, network issue) and has a good chance of succeeding on retry. A **hard decline** is permanent (card cancelled, fraud flag) and will not succeed regardless of how many times you retry. Subscribee retries all failures the same way. As an admin, if you see a subscription that has exhausted all retries, it is worth checking the error message in the billing history to understand whether reaching out to the customer makes sense. *** ## What Subscribee Does Automatically Once a payment fails, Subscribee starts the dunning sequence based on your billing settings: 1. Sends the customer a **Payment failed** email 2. Waits the configured number of hours and retries the charge 3. Sends a **Retry failed** email for each unsuccessful retry 4. After all retries are exhausted, sends a **Last attempt failed** email 5. Marks the subscription as payment failed This happens automatically without any action required from you. {% hint style="info" %} Want to adjust how many retries happen and how far apart they are? See [How to Configure Billing and Dunning Settings](/subscribee/how-to.../how-to-configure-billing-and-dunning.md). {% endhint %} *** ## What You Can Do as an Admin ### Check the Billing History Open **Subscriptions**, find the affected subscription, and click the **Billing history** tab. This shows every charge attempt, the date, the amount, and whether it succeeded or failed. The error message for each failed attempt gives you clues about the cause. ### Trigger a Manual Charge If the customer has already updated their payment method, you do not need to wait for the next scheduled retry. Open the subscription detail page and click **Place order now** to trigger an immediate charge. ### Contact the Customer Directly For high-value subscribers who have not responded to the automated emails, a personal outreach often works where automation does not. The customer's email address is shown in the subscription detail view. A short, friendly message explaining the issue and linking to their account portal to update their card goes a long way. *** ## How to Reduce Failed Payments Before They Happen **Keep your payment failure emails active and customized.** The default emails work, but personalized subject lines using `{{customer_name}}` and `{{product_name}}` get opened far more often. **Send an upcoming payment reminder.** Subscribee's **Upcoming payment** email fires 3 days before each billing date. This gives customers a heads-up and a chance to check their card details before the charge attempts. **Make updating payment details easy.** Make sure the [Subscriptions page is added to your customer account portal](/subscribee/integrations/how-to-add-subscriptions-page-to-customer-account.md) so subscribers can update their card in one click without contacting support. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://penida.gitbook.io/subscribee/faq/why-did-a-subscription-payment-fail.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.