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
When the user clicks the PAY button, I call createPlatformPayPaymentMethod to obtain the paymentMethod to send to our backend.
Our backend responds by requesting a confirmation action.
I use the confirmPlatformPayPayment function to confirm, and the payment is successfully processed.
This is more or less the same flow as on the website (with different function names, of course). Everything works, but from the user's perspective, it feels like they are paying twice because the same screen appears twice (both with createPlatformPayPaymentMethod and confirmPlatformPayPayment). This behavior is clearer in the attached video. This only happens with ApplePay, on Android the user action required it's just one.
This issue was reported in production, and I can’t tell whether it started happening at some point or has always been this way, though it seems strange to me. I am currently using version 0.39.
0f6706f9-5007-4ab1-a2e5-d1ba0e5d5e87.1.mp4
Any advice or suggestion?
The text was updated successfully, but these errors were encountered:
The flow of our application is as follows:
createPlatformPayPaymentMethod
to obtain the paymentMethod to send to our backend.confirmPlatformPayPayment
function to confirm, and the payment is successfully processed.This is more or less the same flow as on the website (with different function names, of course). Everything works, but from the user's perspective, it feels like they are paying twice because the same screen appears twice (both with createPlatformPayPaymentMethod and confirmPlatformPayPayment). This behavior is clearer in the attached video. This only happens with ApplePay, on Android the user action required it's just one.
This issue was reported in production, and I can’t tell whether it started happening at some point or has always been this way, though it seems strange to me. I am currently using version 0.39.
0f6706f9-5007-4ab1-a2e5-d1ba0e5d5e87.1.mp4
Any advice or suggestion?
The text was updated successfully, but these errors were encountered: