Sets canConfirm to false while updates are pending in Elements with Checkout Sessions
Updates canConfirm to false while a Custom Checkout server update is queued or in progress. After all pending updates finish, canConfirm reflects whether the checkout is otherwise ready for confirmation. This provides a signal that integrations can use to avoid confirming with outdated information. Elements with Checkout Sessions changes canConfirm to false while updates are pending, which could change behavior if you rely on canConfirm in your checkout flow. Previously, Stripe.js didn’t change canConfirm while server updates were pending.
docs.stripe.comquote checked- behaviour change
- Your codeby hand
Nemotron fixes
In its own wordsmatches the page ✓
| [Sets canConfirm to false while updates are pending in Elements with Checkout Sessions](https://docs.stripe.com/changelog/endive/2026-09-30/block-custom-checkout-confirmation-pending-updates.md) | Checkout, Elements | Breaking | stripejs |
Also readmatches the page ✓
Elements with Checkout Sessions changes `canConfirm` to `false` while updates are pending, which could change behavior if you rely on `canConfirm` in your checkout flow. Previously, Stripe.js didn’t change `canConfirm` while server updates were pending.
What Teire looks for in your code
nothing to search for: checked by hand
Does it reach your code?