Allow admins to regenerate Stripe Checkout Session for payment_pending claims#330
Merged
GsCommand merged 1 commit intoMay 24, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
payment_pendingclaim's existing checkout URL is expired, timed out, or has a bad redirect URL.cards_published -> payment_pendingtransition.Description
forceNewsupport toPOST /api/admin/create-checkout-sessionby readingforceNewfrom request body and honoring it whenclaim.status === 'payment_pending'. (file:api/admin/create-checkout-session.js).payment_pendingandforceNew !== true, and created a fresh Stripe session whenforceNew === true, updatingstripe_checkout_session_idandpayment_status = 'pending'while keepingclaim_requests.status = 'payment_pending'. (file:api/admin/create-checkout-session.js).(claim_id, provider)to safely update session info, and the inserted event usespayment.checkout_regeneratedwhen regenerating frompayment_pendingwhile only inserting thecards_published -> payment_pendingtransition when the prior status wascards_published. (file:api/admin/create-checkout-session.js).forceNewincreateCheckoutSessionand to show a Regenerate checkout session button forpayment_pendingclaims that calls the endpoint with{ claimId, forceNew: true }, shows a loading state, replaces the URL, and refreshes claim details. (file:public/admin/claims.html).tests/api-payments.test.js).Testing
npm testwhich completed successfully with all tests passing.cd examples/webhook-auto-verify && npm run checkwhich completed successfully.forceNewgenerates a new session and emitspayment.checkout_regenerated, and paid claims cannot regenerate checkout.Codex Task