#benomatis
1 messages · Page 1 of 1 (latest)
You would use a Setup Intent with the Payment Element: https://stripe.com/docs/payments/save-and-reuse?platform=web&ui=elements
You could set up a custom radio button using regular HTML/JS that your customers could click, which could then decide which Payment Element flow to send them to
you mean I'd set up 2 intents, one with, and one without setupFutureUsage?
yup! Assuming you want them to choose whether or not to save their cards for future usage. Most people just save cards for future usage without giving the customer and option, but it all depends on what you're going for
I want to make sure the experience is the same on web and mobile
mobile offers this checkmark out of the box
Right, okay. Then you're on the right path and a custom radio-button is your best bet for feature parity
I don't remember this many differences when I used CardElement for web
it was CardField for mobile
but maybe because I was only focusing on getting card details, never saved, and no other methods
anyways
thanks for the confirmation
Sure thing!
sorry, can I have a slightly related question?
a colleague of your said, albeit wasn't very sure I think, that Link wasn't available on mobile - is this true? When I look at the info site on Link, it is actually advertised with a mobile app animation
Is this for iOS or Android?
sorry, I just posted in the common chat, thought you needed to have a separate one opened for this
I thought instead of setting up a check mark, I could just use Link, provided it was available on mobile as well
this animates a mobile screen that shows Link
how?
That looks like Stripe Checkout, which definitely supports Link
does Checkout work on both, web and mobile? would that be the go-to solution if I wanted web vs mobile parity in terms of payment experience?
It works on both and they have feature parity. It sort of just depends on your desired payments flow
what exactly in my payment flow?
Checkout isn't as customizable as other Stripe products (like the Payment Element) so you can use both/either if you want, but ultimately it's a matter of taste
It works in Checkout on web too
sorry, I meant, is Link working on mobile other than inside Checkout?
Yup! The mobile payment element also supports Link: https://stripe.com/docs/payments/accept-a-payment?platform=ios&ui=payment-sheet#ios-flowcontroller
https://stripe.com/docs/payments/link/add-link-elements-integration
are you sure? where can you see it? because there it only features the Save this card checkmark, that is not Link
it says Link is Available in Elements, and that is "Responsive web and mobile native"
so how do I activate Link on the PaymentSheet?
I believe you just activate it in the Dashboard and it will show up if you don't explicitly set payment_methods on the Payment Intent. This guide mentions that here: https://stripe.com/docs/payments/accept-a-payment?platform=ios&ui=payment-sheet#ios-enable-payment-methods
unfortunately that's not the case
I had Link turned on, and it didn't appear on mobile, all I got was the "save this card" checkmark, but that's not Link
could it be due to the Payment method domains? how are those checked for mobile?
I mean I do have those set up, but the domains there are the domain where the web app is hosted
so how is the mobile app sending the domain name?
Everywhere I'm reading says that it's compatible with PaymentSheet, so there must be something going on in the integration somewhere
Do you have a Payment Intent that was created for the Payment Sheet? Or are you deferring the Payment Intent creation until after the Payment Sheet accepts the payment details?
If you do have a PI, can you send me the ID?
Hi there, stepping in and catching up
the only checkbox I saw presented was the Set up for future use
but a colleague here said that's different from Link, and that's my understanding as well
could it be that on mobile for some reason it required shipping to be set up on the PI?
you there...?
To summarize, are you saying that you have enabled Link. However, on mobile you're not able to see link vs. when you use Web?
We document that we require email address collection for link, https://stripe.com/docs/payments/link/add-link-elements-integration
yes, but how do I pass in the email into the PaymentSheet? or do I do it on the PI?
the doc you linked only talks about web
on PI.create I have receipt_email filled
in the interim, can you maybe check req_bYXKSWOHQaZhZa please why the API Version here shows 2020-08-27? I use stripe-node v13 to set up the PI and it should have
2023-08-16
Testing this
I was able to confirm that we currently do not support Link in Mobile: https://stripe.com/docs/payments/payment-methods/integration-options#support-link. We are working on this though
The reason you see that API version is because you're explicitely setting the API version on your end on that confirm call.
I don't want to, maybe it's forced somewhere somehow?
It's coming from your own code. You should look at your clinet-side code where you confirm the Payment Intent.
it's on a server-side code, and I'm definitely not enforcing that old version
It's definitely coming from your client-side code, https://dashboard.stripe.com/test/logs/req_bYXKSWOHQaZhZa. You create the PaymentIntent, https://dashboard.stripe.com/test/logs/req_HY1arhFxqqY2Q7 with the 2023 version on the server-side.
API requests made from Mobile SDKs are pinned to a specific API version that the Mobile SDKs support/expect. You can't control this
does this mean I'd have to upgrade the mobile SDK in order to update the API Version?
I'm on the latest there
No, it means that it doesn't matter and it's internal to the SDK