Stripebreaks on upgrade

Checkout Sessions have lower latency and new update semantics

This version offers improved latency on all Checkout Session APIs for subscription-mode Sessions, including when your customer confirms the Session. Because this change creates the subscription after the user has completed the payment, payment_intent doesn’t reference an invoice until the Checkout Session fully completes. This means the checkout.session.status property must be complete before the invoice is created.

docs.stripe.comquote checked
behaviour change
Your codeby hand
Nemotron fixes

In its own wordsmatches the page ✓

| [Checkout Sessions have lower latency and new update semantics](https://docs.stripe.com/changelog/basil/2025-03-31/checkout-legacy-subscription-upgrade.md) | Checkout | Breaking | api |

docs.stripe.com/changelog.mdfrom the provider's own sitechecked 2026-11-04#5f64b8106e

Also readmatches the page ✓

Because this change creates the subscription *after* the user has completed the payment, `payment_intent` doesn’t reference an invoice until the Checkout Session fully completes. This means the `checkout.session.status` property must be `complete` before the invoice is created.

docs.stripe.com/changelog/basil/2025-03-31/che…from the provider's own sitechecked 2026-11-04#c1e50cd110

Subscriptions are now created after the user completes payment.

What Teire looks for in your code

nothing to search for: checked by hand

Does it reach your code?

Fix in all Scan a repo

Worker running

Stripebreaks on upgrade

Checkout Sessions have lower latency and new update semantics

This version offers improved latency on all Checkout Session APIs for subscription-mode Sessions, including when your customer confirms the Session. Because this change creates the subscription after the user has completed the payment, payment_intent doesn’t reference an invoice until the Checkout Session fully completes. This means the checkout.session.status property must be complete before the invoice is created.

docs.stripe.comquote checked
behaviour change
Your codeby hand
Nemotron fixes

In its own wordsmatches the page ✓

| [Checkout Sessions have lower latency and new update semantics](https://docs.stripe.com/changelog/basil/2025-03-31/checkout-legacy-subscription-upgrade.md) | Checkout | Breaking | api |

docs.stripe.com/changelog.mdfrom the provider's own sitechecked 2026-11-04#5f64b8106e

Also readmatches the page ✓

Because this change creates the subscription *after* the user has completed the payment, `payment_intent` doesn’t reference an invoice until the Checkout Session fully completes. This means the `checkout.session.status` property must be `complete` before the invoice is created.

docs.stripe.com/changelog/basil/2025-03-31/che…from the provider's own sitechecked 2026-11-04#c1e50cd110

Subscriptions are now created after the user completes payment.

What Teire looks for in your code

nothing to search for: checked by hand

Does it reach your code?

Fix in all Scan a repo

Failed payment attempts no longer result in an incomplete subscription with a finalized invoice.

An invoice isn’t present until the Checkout Session is in the complete state.

#### Ruby

ruby

require 'json'

require 'stripe'

# Don't put any keys in code. See https://docs.stripe.com/keys-best-practices.

# Find your keys at https://dashboard.stripe.com/apikeys.

client = Stripe::StripeClient.new('<<YOUR_SECRET_KEY>>')

# Using Sinatra

post '/webhook' do

payload = request.body.read

event = nil

begin

event = Stripe::Event.construct_from(

JSON.parse(payload, symbolize_names: true)

)

rescue JSON::ParserError => e

# Invalid payload

status 400

return

end

# Handle the event

case event.type

when 'payment_intent.succeeded'

payment_intent = event.data.object # contains a Stripe::PaymentIntent

# The subscription and invoice might not have been created at this stage.

# Then define and call a method to handle the successful payment intent.

# handle_payment_intent_succeeded(payment_intent)

when 'checkout_session.completed'

checkout_session = event.data.object # contains a Stripe::CheckoutSession

# checkout_session.payment_intent is a string here,

# but you can use this payment_intent token to fetch the associated invoice payment

# through the /v1/invoice_payments API method and its guaranteed associated invoice

# and invoice payment are non-null at this stage.

# Then define and call a method to handle the successful completion of a Checkout Session

# handle_checkout_session_completed(checkout_session)

# ... handle other event types

else

puts "Unhandled event type: #{event.type}"

end

status 200

end