A declined card should not mean starting your subscription over. Now it does not.
What changed
When a payment failed, whether from an expired card or a temporary decline, the recovery path used to route you back through checkout as if you were signing up fresh. That meant going through the full checkout flow again just to fix a card problem, with the risk of ending up on a duplicate subscription or a different plan than the one you already had. Checkout is designed for new purchases, not for fixing an existing subscription's payment method, so pushing a failed-payment recovery through that same flow meant the experience did not match what was actually going wrong.
Now a failed payment routes you to a secure billing portal instead. From there you can update your card details and the existing subscription continues on the same plan, without a second checkout. Recoverable failures (the kind where updating payment details should fix the problem) are kept out of the checkout flow entirely, since checkout was never the right tool for that situation to begin with.
This distinction between recoverable and non-recoverable failures matters. A temporary decline or an expired card is something you can fix directly by updating your payment method, and the portal is built for exactly that. It is a narrower, more direct fix than starting over with a new purchase.
The portal itself is the same one you would use for any other billing task, like changing your plan or reviewing past invoices, so recovering from a failed payment does not require learning a separate flow. It is simply the place you already go for billing, entered automatically when a payment needs your attention.
How to use it
If a payment fails, you will see a prompt to fix it that takes you to the billing portal rather than checkout. From the portal, update your card information and confirm. FirstSales retries the payment against your existing subscription, and your plan continues without interruption once the payment succeeds. There is no need to reselect a plan, re-enter promotional codes, or worry about accidentally starting a second, overlapping subscription.
You can also reach the billing portal proactively from your account settings if you want to update your card before a payment is due, rather than waiting for a failure. This is worth doing whenever you know a card is about to expire or has been replaced, so you avoid the failure entirely rather than needing to recover from it.
The billing portal shows your current plan and payment method clearly, so you can confirm you are updating the right subscription before you submit new card details. If you manage billing for a team account, this same portal is where you go regardless of whether you are proactively updating a card or responding to a failed payment notice.
If you were previously routed through checkout after a failed payment and are unsure whether that resulted in a duplicate subscription, check your billing history in account settings or reach out to support to review your subscription state directly. Going forward, though, a failed payment always takes you to the portal, so this should not come up again.
Why it matters
Being sent through checkout after a failed payment was confusing and risky: it looked like you were starting a new subscription, and it opened the door to accidentally paying twice or landing on a plan you did not intend. That risk was not hypothetical. A checkout flow that does not clearly indicate it is only fixing an existing subscription can easily result in someone re-entering their card details for what they believe is a fresh purchase, only to discover later that they now have two active subscriptions.
Routing failed payments to the billing portal instead means fixing a card problem stays exactly that: a card fix, not a new purchase. It also means the experience matches the actual situation you are in. If your card was declined and you just need to update it, the portal gets you there directly, with your existing plan and billing history intact, instead of asking you to walk through a purchase flow built for people who do not have a subscription yet.
This kind of billing clarity matters more than it might seem, because payment failures are already a stressful moment for a customer. Nobody wants to see a failed payment notice. Making the recovery path simple and unambiguous, rather than adding confusion on top of an already frustrating situation, is a small thing that has an outsized effect on how trustworthy your billing feels overall.
It also reduces the number of support conversations that start with someone confused about why they were being asked to check out again for a plan they already had. A recovery flow that matches the actual problem, a card that needs updating, means fewer people need to reach out just to confirm they are not being double charged.
This fix also protects against a specific worst case: a customer who does not notice they landed back in checkout, completes it thinking they are simply fixing their card, and ends up paying for two active subscriptions on the same account. That kind of mistake is expensive and awkward to unwind after the fact, requiring a refund and a manual correction on both sides. Keeping recoverable failures out of checkout entirely removes the possibility of that outcome rather than relying on customers to notice and avoid it themselves.
A subscription business runs on customers trusting that their plan and their billing stay stable in the background while they focus on using the product. A confusing recovery path after a routine card decline works against that trust in a way that is easy to avoid. Directing recoverable failures to the same portal customers already use for every other billing task keeps that experience consistent, whether they are there to fix a declined card, update an expiring one, or just check their invoice history.
Availability
This fix applies to all subscription payment failures going forward.