#jayamini_code
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/1304078313282867211
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- jayamini_testing-async-pms, 22 hours ago, 40 messages
- jayamini_webhooks, 23 hours ago, 6 messages
Is there a way to differentiate this processing redirection from an actual cancellation, so we can display a more accurate message to users?
hi! hmm I don't think we would redirect to the cancel_url unless the user actually cancelled(clicking the back arrow/your merchant logo in the top left). If the payment is submitted and processing I'd expect we redirect to the success_urL
Is there a way to differentiate this processing redirection from an actual cancellation, so we can display a more accurate message to users?
retrieve the CheckoutSession and look at that https://docs.stripe.com/payments/checkout/custom-success-page
this same issue was reported by a user on live mode
payment_status only got paid, unpaid status to check in this scenario so we can't find out if the payment is processing just with the session object
do we need to check for the db record or the payment intent to check the processing state then?
you can call the Retrieve PaymentIntent API on session->payment_intent and then check payment_intent->status
thanks
this would be a rare incident, still this seems the only solution right?
also during checkout.session.completed
if payment_status is unpaid
can we set a record on our side with payment status as processing or pending do we need to check payment intent status before doing so
I mean it shouldn't happen that we redirect to the cancel_url, but it's always possible that the customer clicked the link on the Checkout page that does that; or that someone visited the URL directly
to your other question : I think it's fine to assume you can put "unpaid" in the DB at that time yes
yeah we thought so too, we'll test this again