You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In my app I followed the steps here to...
Present an Apple Pay screen
Fetch a Payment Intent from my server
Confirm Apple Pay
...however in development I had an issue in my payment intent endpoint and while this was communicated back to the app immediately I had to wait for the Apple Pay screen to timeout (15s?) to inform the user.
Describe the solution you'd like
I've read a bunch of documentation and I don't think this has been considered yet. Happiest if the solution was just to use an existing method. Now, ideally all my endpoints work as they should all the time, but I'm a belt and suspenders kinda guy. If the server throws back an error it would be nice to manually cancel the Apple Pay screen. I was thinking about something like this...
Where cancelApplePay is just a method I could call to dismiss the Apple Pay screen immediately.
Describe alternatives you've considered
I have thought maybe I should just get the Payment Intent first which would allow me to skip the awkward situation caused by the above where Apple Pay presents and then dismisses with an error unrelated to Apple Pay. I think this is probably best as it requires no SDK change except for maybe different guidance in the example code or documentation. I generally try not to deviate from y'alls instructions though.
I've also thought about instead of my normal flow of immediately throwing from my Payment Intent endpoint instead providing a known invalid client secret to confirmApplePayPayment so it just fails quicker.
hi! going to close this as a duplicate of #447, but I really appreciate the thorough explanation, and we'll take this into account when building this feature 😄
Is your feature request related to a problem? Please describe.
In my app I followed the steps here to...
...however in development I had an issue in my payment intent endpoint and while this was communicated back to the app immediately I had to wait for the Apple Pay screen to timeout (15s?) to inform the user.
Describe the solution you'd like
I've read a bunch of documentation and I don't think this has been considered yet. Happiest if the solution was just to use an existing method. Now, ideally all my endpoints work as they should all the time, but I'm a belt and suspenders kinda guy. If the server throws back an error it would be nice to manually cancel the Apple Pay screen. I was thinking about something like this...
Where
cancelApplePay
is just a method I could call to dismiss the Apple Pay screen immediately.Describe alternatives you've considered
I have thought maybe I should just get the Payment Intent first which would allow me to skip the awkward situation caused by the above where Apple Pay presents and then dismisses with an error unrelated to Apple Pay. I think this is probably best as it requires no SDK change except for maybe different guidance in the example code or documentation. I generally try not to deviate from y'alls instructions though.
I've also thought about instead of my normal flow of immediately throwing from my Payment Intent endpoint instead providing a known invalid client secret to confirmApplePayPayment so it just fails quicker.
Additional context
None.
The text was updated successfully, but these errors were encountered: