Add support for SetupFutureUsage on PaymentIntent update and confirm
#1687
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
|
Could you Please also add this property to the SessionPaymentIntentDataOptions ? @remi-stripe |
remi-stripe
force-pushed
the
remi-add-setupfutureusage
branch
from
311391b
to
2e35d71
Compare
|
r? @ob-stripe |
ob-stripe
suggested changes
Jul 5, 2019
src/Stripe.net/Services/PaymentIntents/PaymentIntentConfirmOptions.cs
Outdated
Show resolved
Hide resolved
remi-stripe
force-pushed
the
remi-add-setupfutureusage
branch
from
2e35d71
to
ca967c5
Compare
|
@ob-stripe PTAL |
ob-stripe
approved these changes
Jul 5, 2019
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.
Waiting for this to be ready in the API
cc @garrett-stripe @stripe/api-libraries-releasers