Changes to the Payment Intent APIs for the next API version #1501
Conversation
This file contains 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
remi-stripe
force-pushed
the
remi-payment-intents-changes
branch
from
6308fb1 to
2d323b5
Compare
remi-stripe
changed the title
remi-stripe
force-pushed
the
remi-payment-intents-changes
branch
from
2d323b5 to
206a44c
Compare
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.
We are going to ship some changes to the Payment Intent APIs in the next API version. Though are fairly self-contained and pave the way for future changes. Changes are:
status: removerequire_sourceandrequire_source_actionand addrequires_payment_methodandrequires_actionnext_source_actionrenamed tonext_actionallowed_source_typesrenamed topayment_method_typesauthorize_with_urlrenamed toredirect_to_urlboth in the type of next action and in the hash that describes that next action.cc @stripe/api-libraries @danwang-stripe