#rachel_express-checkout-eleemnt-interface
frosty narwhalBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1375122967868080159
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
unborn python
This is also very difficult for us to troubleshoot as the Apple Pay button on Chrome is only showing up in our Production environment, not on our Staging. Is there a way for us to get the Apple Pay on Chrome feature in our staging environment? Such as a feature flag we can toggle?
visual crown
Hey there, this should also apply in test mode though my recollection is that we're still rolling this out so it doesn't always show
unborn python
Good to know! Could you confirm that the Express Checkout onCancel event is being triggered when the user submits the order on their mobile device? We think this is happening based on our tracking logs, but we are unsure.
visual crown
I would expect a successful completion to product a confirm event on Express Checkout Element
so that you can complete the payment
unborn python
So when the QR code closes on the browser during the submit event, it should not trigger on onCancel?
visual crown
Are you getting only cancel, or cancel and a confirm event?
Note that in some browsers, the payment interface might be dismissed by the customer even after they authorize the payment. This means that you might receive a cancel event after receiving a confirm event. If you're using the cancel event as a hook for canceling the customer's order, make sure you also refund the payment that you just created.
unborn python
We are getting cancel and a confirm as the payment does go through
visual crown
Gotcha, so that caveat there seems to apply, you might sometimes get a spurious cancel after a confirm
unborn python
We thought the customer may be closing out the QR code after submitting on their phone, but when testing on production, the problem still happens even when the user does not manually close out the QR code.
So we are thinking Stripe is triggering the onCancel event
visual crown
That's possible, it could be related to the cross-browser behaviour. I agree this seems a little odd to me, though the documented scenario suggests this is sometimes expected.
unborn python
We received two orders with Apple Pay chrome browser and both times the payment was submitted without data (as it has been cleared by the onCancel), so we do not think the payment interface is being dismissed by the customer.
"The cancel event is triggered from an Express Checkout Element when the payment interface is dismissed." The payment interface is dismissed by Stripe when the user submits the order on their mobile device, as the browser QR code disappears.
visual crown
Right, so I'm not sure what's going on here so I don't think I can repro this to test myself.
I'm going to have our bot send you a link you can use to submit a support case that should come straight to my team for us to investigate with the Apple Pay team here.
frosty narwhalBOT
Hello @unborn python, we have sent you a direct message, please check it at https://discord.com/channels/@me/1367531880458748064
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
unborn python
Thank you!
visual crown
NP!
frosty narwhalBOT