#laurentiu_webhooks
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/1331725299213140048
đ 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.
- laurentiu_webhooks, 35 minutes ago, 5 messages
hey there! I had to reopen the ticket as in the previous one I couldn't respond in the chat.
Hello, I don't see a client reference ID being provided when that Checkout Session was created. Can you tell where you are seeing this reference ID being set for that session?
Hey! I am not sure where exactly to check that info. I am seeing the client reference ID being passed correctly in the pricing table component on my side
This is the script that corresponds to the pricing table component:
script.src = "https://js.stripe.com/v3/pricing-table.js";
I could see this issue as well which describes the same behaviour: https://stackoverflow.com/questions/74316784/stripe-client-reference-id-does-not-persist-on-stripe-panel-when-using-pricing-t.
I have seen this happen before when client-reference-id was set to an empty string (client-reference-id="") which can happen if something goes wrong in your server's code for rendering the page
Can you reproduce this issue on your side? If so it might be good to use the web inspector to make sure that the client-reference-id parameter is being set properly for the table when reproducing this error
I actually added this snippet last week to even prevent the pricing table from being loaded:
if (!user || !user.id || !user.email) {
console.error('Invalid user data:', user);
return null;
}
Gotcha, and is that triggering when this happens? I still think it would be useful to double check if you can reproduce this yourself. Sometimes weird things happen where something is set at one place in code but was at least temporarily null or empty somewhere else