#Mark Edwards-setup-flow-prb
1 messages ยท Page 1 of 1 (latest)
Hello ๐
Is there a reason Stripe doesn't fall back to the "Set up Apple Pay" flow, or the equivalent on Google Pay?
I remember talking about this to someone a few days ago. As far as I can tell, when we were working on PaymentRequestButton API, the "Set up Apple Pay" flow wasn't very refined and it resulted in bad UX.
Are devs expected to build that fallback manually?
I don't think so. If the wallet isn't configured, we default to ApplePay isn't available.
right, but that's not a good UX for our case. so my question was, does Stripe consider this a custom case and its up to the dev to implement if needed, or does Stripe not implement this because it is a poor flow?
it sounds like its neither ๐
I'm trying to decide whether to go down this rabbit hole and try to implement a fallback to Apple Pay or Google Pay setup.
definitely understand. I can flag it internally as a feature request but as far as I know, the flow isn't currently supported as a "custom case" too.
as I read the docs, I think I can just implement a custom fallback button, which then reloads the PaymentRequestButtonElement when the user is finished with setup. so I think it can be done without any dependency on the Stripe code.
but it would be nice if Stripe made this available, then I wouldn't have to deal with it ๐
mainly I was searching for some horrible blocker that makes this a non-starter, so I can avoid wasting time. but it seems like its worth attempting unless you know of a specific reason it won't work well.
Can't think of a reason why it wouldn't work. However, I've not personally tested this flow so I'm not 100% sure ๐
what do you think the chances of Stripe adding support for this are?
is it worth me opening some kind of support case for it? or a github issue?
to be honest, I don't know what the chances are.
Happy to raise it internally and see if I can get some more context on this.
So yeah as I mentioned above, Back when we originally implemented Apple Pay the Apple Pay card enrollment process was somewhat arduous and introduced a fair bit of friction, which could lead to lower conversion rates, so the decision was made to hide Apple Pay if the Apple Pay wallet did not contain a valid card. Same for google pay.
I'll raise it internally to see if we can revisit this decision as there have been improvements since then.
If you want to write in to our support about this, I can grab it from the queue and as soon as I hear back I'll send you an update.
You can send an email to support@stripe.com providing the context from this thread
don't forget to mention that you spoke with hanzo on discord, so that I can find the right ticket ๐
Let me know once you write in (i'll grab it right away)
done, thanks
Thanks.
I do see kind of an issue with Apple Pay, in my initial experimentation. when the Set Up button is clicked, the user gets bounced out to System Prefs to add a card, and there's no way to know that they have done it so the button can be refreshed.
so the user comes back to the page and the button still says "Set up Apple Pay"
that could be a pretty serious issue in web
perhaps this is why Stripe declined to do this?