#jan-vdh_unexpected
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/1501183989476626493
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
hey there ๐ thanks for flagging this
when you say you didn't manage to reproduce, was the redirect successful for you? did you try in live or test mode?
I started one payment flow in the morning where I was able to reproduce this behavior (pi_3TTfdlRqVdMQzre712LHHMOZ) on live, but if I try it again at the moment it seems to work fine
I see - thanks for confirming
checking some logs on our end which may take a few minutes
sure, no rush on this! it's not breaking our system, it's just a bit weird ๐
yeah for sure! looking at the logs, I see that the redirect URL was configured correctly for that Checkout Session, so it looks like this was a transient issue on PayPal's side
it looks like the raw React Server Components (RSC) payload was rendered as plain text for some reason
the fact the redirect to paypal.com succeeded means the issue occurred on PayPal's infrastructure, not Stripe's - the fact that it is now working correctly suggests a fix was deployed from their side, though I'm surprised we didn't receive more reports of this!
if you're able to reproduce again, or if the issue reoccurs, then we can definitely follow up from our side, but for the moment I think it's safe to say this was a transient PayPal-side issue
that's what i feared, paypal support is a bit ... lets say... not that great
can we leave the chat open in case i can reproduce it later?
we do need to close/lock threads after around ~30mins if not active, but you can always open a new thread again later if you need
we'll be able to refer back to this thread for context