## TL;DR

The Stripe customer portal can let customers update payment methods, view open invoices, and pay them without a support ticket, but only if the configuration enables those capabilities. Turn on payment method updates and invoice history in the portal config, pass the configuration id in the session, and link customers straight from your dunning email. Add a post-payment redirect so they land back on your app with confirmation. This converts failed-invoice recovery from a support queue into a self-serve loop.

## The query

```text
Stripe customer portal: letting customers update cards to fix failed invoices
```

## Use this when

- Failed invoices pile up and you want customers to fix their own cards
- Configuring the Stripe customer portal for invoice recovery
- Reducing support tickets for expired-card payment failures

## Not for

- Building a fully custom billing page (use the portal only if you want hosted UI)
- One-off invoice payments for non-portal customers (send a payment link instead)

## Steps

1. In the dashboard, open the customer portal configuration and enable payment method updates and invoice history.
   Expected output: Customers can see and pay their open invoices in the portal.
2. Create portal sessions with that configuration id, ideally deep-linking to the invoice or payment method section.
   Expected output: The portal opens on the right screen for the task.
3. Add your failed-invoice dunning email template with the portal link and a clear pay-now call to action.
   Expected output: Open rates convert into portal sessions.
4. Set a return_url so customers land back on your billing page after paying.
   Expected output: Customers see confirmation instead of a dead end.
5. Test the full loop in test mode: expire a card, fail an invoice, walk the portal flow.
   Expected output: The path from email to paid invoice works end to end.

## Variant phrasings

### Stripe customer portal pay failed invoice

### let customers update card for failed subscription payment Stripe

### Stripe billing portal configuration invoice history

## Root cause

The portal is capability-gated per configuration, not globally on: customers can only do what your portal config allows. Most 'the portal does not let me pay' complaints trace to a config that never enabled invoice history or payment method updates.

## Edge cases

- Portal sessions expire; generate the link at send time rather than storing it
- Customers with multiple subscriptions should land on invoice history, not a single subscription page

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_H57MJYVPz6OfAKkxTLo-1A