#jorvixsky_api
orchid cryptBOT
👋 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/1229859325149708288
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
jolly hingeBOT
vapid fog
Hello! Looking, hang on...
fading beacon
Hello Rubeus! Thank you 🙂
vapid fog
The Event you linked to is a payment_intent.succeeded Event, which contains the Payment Intent, but you didn't set any metadata on that Payment Intent. You set the metadata on the Checkout Session, and metadata doesn't carry over from a Checkout Session to a Payment Intent.
There are two different approaches you can take to fix this...
One is that you can listen for checkout.session.completed Events, which will contain the Checkout Session object and, thus, the metadata you set on the Checkout Session.
The other is that you can set payment_intent_data.metadata on the Checkout Session instead of, or in addition to, metadata: https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-payment_intent_data-metadata
fading beacon
Actually the 2nd one is what I do
And in test it was working, see this test request: req_Tdp3O49Id9YWUo
vapid fog
Look at the request you shared above in your Dashboard: https://dashboard.stripe.com/logs/req_UzpLDqqSt1Dk2W
Those parameters did not come through in that request.
They are present on that test mode request, but something is different on your end in live mode.
fading beacon
In theory we did not change anything after these last tests (the one I shared is one of the last we did before the client itself trying it out)
I just checked just in case we messed up in a commit or something like that and I see that no changes since that test to the api endpoint or the webhook
vapid fog
I mean, something is different. Your code is providing different parameters to our API.
fading beacon
Ok will retake a look at it and see if we can make it work again and if not I will take a look at the other option you suggested. Thanks for helping pinpointing where the issue is! 🙂
vapid fog
Happy to help!
fading beacon
https://dashboard.stripe.com/logs/req_jyfVAzExiElzil
Now seems to being sent properly like in the test one, right?
jolly hingeBOT
vapid fog
Yep!