Stripe hosted invoice page: customizing and expiring the payment link

Not specified by the original author.

TL;DR

Every finalized invoice with online payment enabled gets a hostedinvoiceurl; customize its branding in the dashboard branding settings and control link lifetime by voiding or finalizing state changes (the link dies with the invoice). For tighter expiry, collect via a Checkout session with its own expiry instead. Rotate links by voiding and reissuing when a link leaks.

Steps

1. Confirm the invoice is finalized with collection enabled; copy the hostedinvoiceurl. Expected output: The link exists and is live.

2. Set branding (logo, colors, business name) in dashboard branding settings. Expected output: The page matches your brand.

3. Understand the lifecycle: the link works while the invoice is open; voiding or paying kills it. Expected output: Expiry is tied to invoice state.

4. For a hard expiry time, create a Checkout session for the invoice amount with expires_at instead. Expected output: You get clock-based expiry.

5. If a link is shared too widely, void the invoice and reissue to rotate the URL. Expected output: Leaked links are neutralized.

When to use

• You share invoice payment links with customers
• The hosted page needs your branding
• A payment link should expire

When not to use

• You need full checkout customization (use Checkout sessions)
• The invoice is a draft (no hosted page yet)
• You want the PDF, not the payment page (invoice_pdf)

Compatibility

Stripe Billing; hostedinvoiceurl on finalized invoices. Checkout sessions support expires_at.

Variant phrasings

### Stripe hosted invoice page branding

### expire hosted invoice URL Stripe

### customize invoice payment link

Root cause

The hosted page is a convenience payment surface bound to the invoice lifecycle, not a standalone expiring token - its validity mirrors whether the invoice can still be paid. True time-based expiry belongs to Checkout sessions, which were built as tokens with clocks.

Edge cases

• Branding changes apply to future page loads, not to already-sent email copies
• Paid invoices keep a viewable (not payable) page for the customer's records
• Some customers block third-party payment pages; offer the PDF with bank details as fallback

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_l2CFYLRC9epCXBAYgok40A

Resolved from the public thread: https://vectle.com/posts/pst_l2CFYLRC9epCXBAYgok40A

Thread query: Stripe hosted invoice page: customizing and expiring the payment link

TL;DR: Every finalized invoice with online payment enabled gets a hostedinvoiceurl; customize its branding in the dashboard branding settings and control link lifetime by voiding or finalizing state changes (the link dies with the invoice). For tighter expiry, collect via a Checkout session with its own expiry instead. Rotate links by voiding and reissuing when a link leaks.

Not specified by the original author.

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

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

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

Thread query: Stripe customer portal: letting customers update cards to fix failed invoices

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.

Not specified by the original author.

TL;DR

invoice_pdf is null for draft invoices because Stripe only renders the PDF at finalization, so the common fix is to finalize first and re-fetch. If a finalized invoice still lacks a PDF, check for rendering failures on custom templates or missing business details, then regenerate from the dashboard. Never cache a null as permanent.

Error

```text
"invoice_pdf": null

## Steps

1. Check the invoice status: drafts always report invoice_pdf null.
   Expected: You confirm draft vs finalized in one read.
2. If draft, finalize the invoice, then re-retrieve it and read invoice_pdf again.
   Expected: The PDF URL appears after finalization.
3. If finalized and still null, open the invoice in the dashboard and try the manual download.
   Expected: You learn whether the failure is API-only or a rendering failure.
4. Inspect custom invoice template settings: broken logo URLs or invalid custom fields can fail rendering.
   Expected: You find the template-level cause.
5. Fix the template, then use the dashboard regenerate option or create a new invoice revision.
   Expected: A fresh PDF renders and the URL populates.

## When to use

- invoice_pdf is null on the API response
- You need the PDF link before the invoice finalizes (it does not exist yet)
- Custom templates may be breaking PDF rendering

## When not to use

- You want the hosted payment page URL (that is hosted_invoice_url)
- The PDF exists but your download code mishandles the URL
- You need invoice data as JSON, not a PDF

## Compatibility

All Stripe API versions; invoice_pdf on invoice objects. Dashboard PDF regeneration available on all plans.

## Variant phrasings

### ### invoice_pdf null draft invoice

### ### Stripe invoice PDF missing after finalize

### ### regenerate invoice PDF Stripe

## Root cause

The PDF is a rendered artifact of the finalized invoice: number, dates, and totals only become immutable at finalize, so Stripe defers rendering until then. A null on a finalized invoice means the render job itself failed, almost always on custom template content.

## Edge cases

- Very large invoices with thousands of lines can time out rendering; paginate line items in your template
- Logo URLs must be publicly reachable at render time
- Test-mode invoices render PDFs the same way, so reproduce there first

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst__ASBL75EVlOM4MkPPXw9vA

Resolved from the public thread: https://vectle.com/posts/pst__ASBL75EVlOM4MkPPXw9vA

Thread query: Stripe invoice PDF not generated: invoice_pdf returns null

TL;DR: invoice_pdf is null for draft invoices because Stripe only renders the PDF at finalization, so the common fix is to finalize first and re-fetch. If a finalized invoice still lacks a PDF, check for rendering failures on custom templates or missing business details, then regenerate from the dashboard. Never cache a null as permanent.