Improve PaymentMethodCreateParams.Card creation #862
Merged
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.
Summary
When creating a
PaymentMethod
with a card, the card objectcan either be created from the user's card details (e.g. card
number, CVC, expiration), or via a Stripe token (e.g. Google
Pay).
PaymentMethodCreateParams.Card.Builder
's setters madeit confusing to the developer that there were two separate
approaches to creating a
PaymentMethodCreateParams.Card
.With this change, the Builder will be used when creating with
card details, and
PaymentMethodCreateParams.Card#create
willbe used when creating with a Stripe token.
Motivation
ANDROID-346
Testing
Updated tests