Skip to content
This repository has been archived by the owner on Jan 3, 2024. It is now read-only.

Payment Method id for confirm (Setup) Intent Results #530

Merged
merged 3 commits into from
Aug 29, 2019

Conversation

fbartho
Copy link
Collaborator

@fbartho fbartho commented Aug 29, 2019

Proposed changes

My backend team really would like it if I submitted the paymentMethodId to the backend when using confirmSetupIntent/confirmPaymentIntent (when using the create payment method optional parameters) -- to do that I have to change the response object for those APIs.

Types of changes

  • Bugfix (a non-breaking change which fixes an issue)
  • New feature (a non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality not to work as expected)

I discussed this in Discord, but people were offline at the time, so I figured I'd make a PR.

I wrote an attempt at the Android implementation, but I haven't verified if this fully works on Android. (This is our current convention).

@fbartho
Copy link
Collaborator Author

fbartho commented Aug 29, 2019

@mindlapse -- They've already fixed my feature request: stripe/stripe-android#1445, this brings Android into line with iOS (re: the two iOS-only comments on PaymentIntent-related items).

Do you want me to patch this PR to remove the iOS-only comments and bump our minimum stripe-android to >10.3.1?

@mindlapse mindlapse merged commit b7c293b into experimental Aug 29, 2019
@mindlapse mindlapse deleted the experimental+paymentMethodIdForConfirmResults branch August 29, 2019 19:57
@Jackyaung
Copy link

@fbartho do you fix this already ? I am also like this way, but I found the tipsi-stripe doesn't have this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants