#yang.tao
1 messages · Page 1 of 1 (latest)
👋 happy to help
I don't know if I described the problem clearly
I'm still reading give me a couple of minutes
Hi! I'm taking over this thread.
- What exactly is your question here?
- I'm not sure I follow. Could you maybe record a quick video of the issue?
Yes thanks! What were you expecting to happen instead? At the end of the video you want the card field to be empty and not with the 444 card?
Also did you follow a specific Stripe documentation page to build this flow?
I selected the 4444 card for the first time, and after removing it from the pop-up layer, the 4242 card is selected by default. I expect onPaymentOption to return the 4242 card, so that users will not be confused
Thanks! Give me a few minutes to look into this.
I wrote it with reference to this document
Hey! Taking over for my colleague. Let me catch up.
Sorry in this channel we support only English
👍
What do you mean by this ?
Is there any additional information with this ?
my english is average
Please help to watch the video above Question 2
Hello, I am an Android developer. I use stripe's flowController (Java) to implement stripe payment. I have two questions:
-
I use SetupIntent to create card information, and then, on the order page, call flowController.presentPaymentOptions() to pop up the card selection box of stripe. When I "edit"-"remove" all cards, the paymentOption in the PaymentOptionCallback.onPaymentOption of flowController.create is not empty
-
After calling flowController.presentPaymentOptions() to pop up the stripe card selection box, there are 2 cards (4444, 42424), select one of the 4444 cards, and display the picture and card number on the UI, and then pop up the stripe again After selecting the card pop-up box, "Edit" - "Remove" the 4444 card, and the 4242 card will be selected by default. At this time, I click the "Close" button in the upper left corner, but the paymentOption in the PaymentOptionCallback.onPaymentOption of flowController.create gets it Still 4444 cards
Many Thanks
No worries.
Let me check...
- After calling flowController.presentPaymentOptions() to pop up the stripe card selection box, there are 2 cards (4444, 42424), select one of the 4444 cards, and display the picture and card number on the UI, and then pop up the stripe again After selecting the card pop-up box, "Edit" - "Remove" the 4444 card, and the 4242 card will be selected by default. At this time, I click the "Close" button in the upper left corner, but the paymentOption in the PaymentOptionCallback.onPaymentOption of flowController.create gets it Still 4444 cards
When you click on the "Close" button, there is no Payment Setup attempt is called, so the callback is not called as a result ... The behavior you are having is expected and normal. You need to present the PaymentSheet when you want to collect new Payment Mehtods, but when charing the customer you need to list all the customer PaymentMethods
https://stripe.com/docs/payments/save-and-reuse?platform=android&ui=payment-sheet#charge-saved-payment-method
you can let your customer choose what PaymentMethod to use, but its last4, exp...
https://stripe.com/docs/api/payment_methods/object#payment_method_object-card-last4
And charge the customer. The choose of the existing PaymentMethods should be done in your UI and not using PaymentSheet.
PaymenSheet should be used just for collecting new PaymentMethods or doing the purchase using an exsiting PaymentMethods
But let me do a test and see if you can do this workaround actually using PaymentSheet...
But I can't get the paymentsheet in the flowcontroller way
What you mean by this exactly ?
I developed it according to this document
Yeah I understand that, but this document is using PaymentIntent and not SetupIntent, you did some adjustment in order to make it work with SetupIntent. So you need to do more adjustment to achieve what you want to do.
I just want to use paymentIntent, not setupIntent
If so you need to complete the purchase/payment using PaymentSheet, not just selecting the PaymentMethod and complete the checkout in your UI.
because, these are using different native sdk behind.
Let me do a quick test between.
Ok I see now what you want to achieve exactly.
The same is true for the first question. After selecting the card, the pop-up window will pop up again. After all the cards are cleared, close it, or keep the last paymentOption
I just run this sample app, and I did the exact same test scenario in your video
And I don't manage to reproduce your issue.
did you try to test/reproduce on the activity you are referring to ?
I have a card list page, use setupIntent to create the card, then there will be problem 2
I found that the card created with setupintent, when using the confige of paymentIntent, the flowcontroller.getPaymentOption in onsuccess is not empty.
I didn't click Close I hit the 0003 card. As mentioned above clicking close is considered as cancel request... but I agree with you this could be a miss UX alignment
let me check further..
Ok I see actually hitting the close button, is considered as cancel request... so there is no update propagated...
Here there will be different opinion on this...
I'll submit a feedback to the appropriate team about this behavior
can you please share your Account Id ?
OK
in order to keep you posted if there'll be any updated on this. If/while this isn't supported yet, the customer need to explicitly choose the PaymentMethod and not closing/canceling their choice
Chat account?
No your Stripe Account acct_123, you can find it at the bottom of this page:
https://dashboard.stripe.com/settings/user
I'm a developer, not a manager
Can you share a PaymentIntent Id ?
sorry
or whatever Stripe object (e.g. SetupIntentId)
No worries.
I'm just confused by some user-unfriendly operation when closing
for android
Thanks a lot, I'm off work 88
I didn't get any object Id in order to reachout to you again