Repository navigation
Update the payment browser check for stale fee inputs - #292
Merged
Merged
Conversation
nonprofittechy
deleted the
test/refresh-stale-payment-browser-assertion
branch
October 8, 2026 18:51
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
1 participant
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.
The opt-in payment browser test timed out after a second tab removed a waiver document because it expected the older missing-document error. The endpoint now checks the fee-input token first and correctly rejects the stale page.
Assert HTTP 409 and the current reload instruction while retaining the check that Review remains disabled. Application behavior is unchanged.
Validation: the complete opt-in payment browser flow passed (1 test); JavaScript syntax and ESLint checks passed.