stripe payment link session expired error

Not specified by the original author.

stripe payment link session expired error

TL;DR

The checkout session behind the link expired (sessions live about 24 hours) or the link hit its limits. Check the link's settings in the Stripe dashboard, create a fresh payment link for the same product and price, and send it to the customer. Consider extending expiry if customers routinely take longer.

stripe payment link session expired error

Use this when

• Customers report session expired on a Stripe payment link
• The link worked yesterday but fails today
• The failure follows a long delay between opening and paying

Not for this skill when

• Card declined errors on an active link (payment method issue)
• Custom Checkout Session integrations (different expiry handling)
• Payment links deactivated intentionally (reactivate instead)

Steps

Step 1: Inspect the link settings

In the Stripe dashboard, open the payment link and check its expiry, payment limits, and active state. Expected: you know whether expiry, limits, or deactivation caused it.

Step 2: Create a fresh link

Generate a new payment link for the same product and price. Expected: a working link with a fresh session lifetime.

Step 3: Send it to the customer

Deliver the new link through the same channel as the original. Expected: the customer can open and pay without the expired error.

Step 4: Adjust expiry if needed

If customers legitimately need more time, extend the link's expiry or limits. Expected: fewer expired sessions for slow-to-pay customers.

Step 5: Confirm the payment

Watch for the completed payment in the dashboard. Expected: the payment succeeds and the order is fulfilled.

Tool compatibility

Stripe Payment Links; Stripe dashboard; Checkout Sessions (underlying expiry behavior).

Variant phrasings

Variant 1

stripe payment link expired session

Variant 2

stripe payment link session expired customer

Variant 3

stripe checkout session expired after 24 hours

Why it happens

A payment link is a friendly wrapper around a Checkout Session, and sessions expire after about 24 hours as a security and inventory measure. Customers who open the link, get distracted, and return the next day meet the expired session instead of a checkout form. Links can also carry payment count limits or explicit expiries that produce the same message. The confusion comes from the link looking permanent while the session behind it is not; the fix respects that split by minting a fresh session (a new link) rather than trying to revive the dead one.

Edge cases / pitfalls

• Links with limited payment counts expire the same way when the count is reached; check limits before assuming time expiry.
• Deactivated links show a similar dead end; confirm the link is still active.
• For high-consideration purchases, send links closer to the moment of payment or use invoices instead.

Provenance

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

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

Thread query: stripe payment link session expired error

TL;DR: The checkout session behind the link expired (sessions live about 24 hours) or the link hit its limits. Check the link's settings in the Stripe dashboard, create a fresh payment link for the same product and price, and send it to the customer. Consider extending expiry if customers routinely take longer.

Not specified by the original author.

TL;DR

checkout session expired is Stripe's checkout.session.expired event: the customer opened a Checkout Session and never paid, so Stripe expired it (24 hours after creation by default, or your custom expires_at) and no charge happened. On the webhook event, release whatever you held for that session (inventory, seats, a reservation), do not fulfill it, and optionally send the customer a recovery email with a link to a fresh Checkout Session. Do not confuse an expired session with a failed payment: expired means the customer walked away.

checkout.session.expired

Use this when

• Your webhook endpoint receives checkout.session.expired from Stripe
• A shopper tells you their Stripe Checkout page said the session expired
• You need cleanup logic for abandoned Checkout Sessions (release holds, mark the order abandoned)
• You want to know the difference between an expired session and a failed payment for retry decisions

Not for this skill when

• The error is an Adyen session expiry (14008 "Session has expired"). Adyen Checkout sessions live one hour and are renewed by creating a fresh session: https://vectle.com/skills/skl0ZCcyEiZR1dB0Xnn3NoNrg
• A Stripe Payment Link says session expired. Payment Links have their own expiry and limit settings; issue a fresh link: https://vectle.com/skills/sklM6eRms7YuSm3EZ6lr5a2A
• The session has not expired but the payment failed: handle checkout.session.asyncpaymentfailed instead (the customer tried; that gets dunning, not a recovery email)

Steps

1. Confirm which expiry you are dealing with. Check the webhook payload event type in the Dashboard under Developers, Events, or inspect the JSON: checkout.session.expired means expiry, checkout.session.asyncpaymentfailed means the payment failed.

Expected: you know the event type and can route it to the right handler.

2. Set the session expiry at creation so it matches your business. Pass expires_at when creating the Checkout Session, between 30 minutes and 24 hours from now. The default is 24 hours.

curl https://api.stripe.com/v1/checkout/sessions \
  -u [api key] -d mode=payment -d "line_items[0][price]"=[price id] \
  -d "expires_at"=[unix timestamp]

Expected: the API returns a session with your expires_at; you record that value in your own session record.

3. Handle checkout.session.expired in your webhook. Look up the session id from the event, release any inventory, seats, or reservations you held for it, and mark the order abandoned in your database. Never fulfill.

Expected: your inventory counts are back where they were before the session started.

4. Optionally send a recovery email. Create a new Checkout Session for the same line items and include its url in the email. Do not reuse the expired session id.

Expected: the customer gets a working payment link; the old session stays dead.

5. Distinguish expiry from payment failure in your retry policy. checkout.session.expired goes to the recovery-email flow above. checkout.session.asyncpaymentfailed and paymentintent.paymentfailed go to dunning instead.

Expected: abandoned carts and failed payments stop sharing one handler.

Variant phrasings

stripe checkout session expired

The Stripe Checkout Session API version of this failure: the session object is still in the API but has status expired and can never complete. Same steps: release holds (step 3), send a fresh link (step 4).

session expired on checkout

The shopper-facing wording of the same event: the Checkout page tells the customer the session expired and Stripe emits checkout.session.expired to your webhook. The fix is on your side: a fresh session, not a retry of the old one.

checkout session expired vs payment failed

Expired means no payment was attempted; nothing was declined. Failed means the customer paid and the charge or authorization failed. They need different follow-ups: recovery email for expiry, dunning for failure.

adyen session has expired

Adyen's equivalent message (error 14_008), but the mechanics differ: Adyen sessions live one hour. See the linked Adyen skill in Not for this skill when.

Root cause

Stripe Checkout Sessions have a fixed lifetime: 24 hours by default, or the expires_at you set at creation (30 minutes to 24 hours). After expiry Stripe emits checkout.session.expired and the session can never complete, because the customer did not pay in time. If your code never handles that event, holds linger forever and abandoned orders are never cleaned up.

Edge cases

• async payments (bank debits, vouchers): a session can complete after the customer leaves, so check for checkout.session.completed or asyncpaymentfailed before treating absence of payment as expiry.
• expiresat in the past or beyond 24 hours: the API rejects it; keep expiresat between 30 minutes and 24 hours from creation.
• Recovery emails that reuse the expired session url: the link stays dead. Always create a new session and use its url.
• Payment Links vs Checkout Sessions: link expiry is controlled by the link's own settings, not expires_at; use the linked Payment Links skill for those.

Tool compatibility

Stripe Checkout Sessions, all API versions that emit checkout.session.expired. Dashboard steps shown; the API fields are the same across SDKs.

Related skills

• Adyen: Session has expired (Checkout 14008): https://vectle.com/skills/skl0ZCcyEiZR1dB0Xnn3NoNrg
• Stripe payment link session expired error: https://vectle.com/skills/sklM6eRms7YuSm3EZ6lr5a2A
• Vercel 404 NOTFOUND, no deployment attached to that hostname: https://vectle.com/skills/sklmvyUa1NSOeqcMwybJ8ey0w

Provenance

Built from Stripe's event reference and the Checkout Session API reference documenting the 24-hour default and expires_at, linked in the evidence.

Stripe's event reference says checkout.session.expired occurs when a Checkout Session is expired. Verified live at https://docs.stripe.com/api/events/types. Sessions expire 24 hours after creation unless expires_at is set, per the Checkout Session API reference.

Not specified by the original author.

TL;DR: Check # Stripe checkout.session.expired: rebuild the session, do not retry it ## The symptom Customers report an error on a Stripe-hosted checkout page. Your logs show

Stripe checkout.session.expired: rebuild the session, do not retry it

The symptom

Customers report an error on a Stripe-hosted checkout page. Your logs show checkout.session.expired events, or retrieve calls on old sessions returning status: 'expired'.

Confirm the cause

A session expires at expires_at, default 24 hours after creation. Expired means abandoned, not declined: the customer never completed payment. Check session.expires_at vs now. If your app treats every non-completed session as a failed payment, expired sessions pollute your failure metrics.

The fix

An expired session is dead. You cannot reopen it; create a new one:

if (event.type === 'checkout.session.expired') {
  const session = event.data.object;
  await db.orders.markAbandoned(session.client_reference_id, { reason: 'expired' });
  await sendRecoveryEmail(session.customer_email, buildNewCheckoutLink(session));
}

expires_at rules:

• You can set a custom expiry between 30 minutes and 24 hours. Shorter windows suit flash sales and expiring carts; longer is the default.
• You can shorten or lengthen an open session with an update call, but once it is expired it is final.

Two pipeline details:

1. The expired event is not enabled on every webhook endpoint by default. Add checkout.session.expired in the dashboard webhook settings or you will never see it.
2. Log expired and failed payments separately. Expiry is a marketing/recovery event (send a fresh link). Failure is a payments event (fix the payment method). Mixing them sends the wrong email.

Verify the fix

Create a session with expires_at 30 minutes out, wait it out (or simulate via the event), and confirm your handler marks the order abandoned and the recovery email contains a fresh working session link. Confirm the old session id returns expired and cannot be reused.

When to use

You hit exactly this: Stripe checkout.session.expired: rebuild the session, do not retry it in Stripe checkout.session.expired.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Stripe checkout.session.expired.

Stripe's Checkout Session documentation sets the default session lifetime at 24 hours with a configurable expires_at between 30 minutes and 24 hours (docs.stripe.com/api/checkout/sessions). The expired webhook indicates an abandoned checkout, not a failed payment, and must be enabled on the endpoint to be received.