#arpit-gupta_code
woeful hedgeBOT
👋 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/1337146077794668546
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
north thorn
Hi 👋
So, just so I'm clear, the issue is with how many tabs are opened when you are attempting to confirm a CashApp payment?
buoyant hare
Yes. Actually a new tab opens to authorize payment in test mode. And hence when the redirect is done after confirming payment, bith the tabs are active and subsequent api calls to our server happens in both the tabs which is causing redundancy
woeful hedgeBOT
buoyant hare
Either the tab shouldn't change and everything should proceed in the current tab or if it is opening in new tab to confirm authorization of payment, then it should auto-close after confirmation and the redirect flow should work as expected in the active tab from where the request was initiated.
north thorn
Okay but I think that behavior is performed because we're trying to mimic the scenario where a user would need to scan the QR to open their CashApp application
buoyant hare
Then you are saying that it will happen only in test mode?
In live mode the user will be able to scan in same tab and pay instead of a new tab being opened?
But I need to be sure about it. Because if same behaviour happens in live mode on our production build then customers will report issues
I tested it for ideal payment method also which is a bank redirect payment method. For that this issue didn't come in test mode also. Everything happened in the same tab
north thorn
I see what you mean, I get redirected on both tabs.
However, that is something your integration should be able to handle without a problem.
buoyant hare
But the user experience would also be not nice if everything is being handled from backend also. Because on frontent customer will see same thing in 2 tabs
If you want I can share test link to you to replicate the issue
and this is happening only for cashapp
north thorn
No I can see the behavior. I know what you are talking about
But, what I am saying, is that we (Stripe) are trying to simulate the fact that your customer will need to use a separate app (CashApp) to make those payments. So they won't open a new tab in a browser, they would open an entirely separate application.
I think our test mode needs to not redirect but instead close the tab and I can file a feature request for that behavior.
buoyant hare
Sure. But I just want to be sure that this new tab thing won't happen in live mode right?
So in live mode the customer will be able to scan the QR in the same tab using cashapp application and make payment without a new tab being opened right?
Can you please confirm this behaviour?
trail shoal
Hi there 👋 jumping in as my teammate needs to step away soon. Bear with me a second while I catch up on the thread here.
buoyant hare
Sure
trail shoal
Based on what I'm seeing in our documentation, what my teammate described is correct. No tab will be opened as the customer will scan the QR code using their mobile device.
https://docs.stripe.com/payments/cash-app-pay/accept-a-payment?web-or-mobile=web&payments-ui-type=direct-api#handle-redirect
Unfortunately though, we don't have a way to test this in livemode to provide a more definitive answer. If you're looking for something more concrete, I'd recommend reaching out to our Support team.
https://support.stripe.com/?contact=true