Support requires_action state on spend requests - #248
Merged
sylwang-stripe merged 1 commit intoAug 13, 2026
Merged
Conversation
jlau-stripe
approved these changes
Aug 13, 2026
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
2 participants
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.
Spend requests can now come back with
status: "requires_action"when step up/user action needs to happen before they can proceed (eg, SSN/identity verification, etc). Previously these either surfaced as an error or got conflated with a denial. Now the CLI shows what's needed (a message and, where relevant, a URL) across create, retrieve, and approval flows. Docs (README, CLAUDE.md, the create-payment-credential skill) are updated to describe the new status and how to handle it--format json:
