#will-fossard_api
1 messages ยท Page 1 of 1 (latest)
๐ 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/1377656534800142377
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
this is the payment sheet working as expected. However if i close the sheet by hitting the x, i get the default canceled response. As mentioned, we are certain we were getting that error carrying over about 2 weeks ago as we built a lot of custom logic to handle those situations. i've also provided a short code snippet of the payment sheet section.
Hi there, I'll be right with you. I'm working another thread.
no problem - i was just adding extra info ๐
Hello ๐
Jumping in to help out
My understanding is that PaymentSheet has always handled the sheet getting dismissed the way you're seeing right now.
The user closing the PaymentSheet is considered "user initiated cancellation" as the Sheet is equipped to handle API error automatically
Have you updated the SDK in the last few weeks? If so, can you downgrade and see if you're back to the "old" behavior?
for sure it makes sense. We have two people on our team convinced it was bringing that error outside of the sheet as well a couple of weeks ago
no updates in the last few weeks
Do you use custom flow and complete payment in your own UI within your app?
https://docs.stripe.com/payments/accept-a-payment?platform=react-native#react-native-flowcontroller
I assume not but that's the only flow where the error is accessible outside the Sheet
no we don't but that's certainly something to look at
i've seen the confirm payment method before but didn't realise it could be implemented alongside the payment sheet
Yeah that flow allows you to collect payment method and confirm payment in two different steps so that customers can review their order details before "paying".
But to come back to your original question, I am 99.99% sure we haven't changed the behavior recently. This is how it's always been.
If we were to change it OR if it was an unintentional bug, it still be tied to a new SDK version. Since you've not upgraded the SDK, that's not the case either.