raul-f_webhooks | Stripe Developers | Page 1

proud cairnBOT Jul 16, 2025, 6:04 PM

#

👋 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/1395103738699583691

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

#

compact estuary Jul 16, 2025, 6:18 PM

#

Hi, event ordering is not guaranteed if you're waiting for the customer created event, https://docs.stripe.com/webhooks#event-ordering. From evt_1RTw8ZKUWAvyPhUxuNUjg11l, I can see the customer id. What error are you seeing? Can you share more please?

azure fox Jul 16, 2025, 6:27 PM

#

Here is the event we are receiving, the customer field is null, and it seems strange to me that the customer gets created and linked to the charge right afterward.

📎 message.txt

compact estuary Jul 16, 2025, 6:37 PM

#

That is because when you created the payment intent, https://dashboard.stripe.com/logs/req_QtiCEZ5yJDhcDX you did not pass the customer. Then you made another request to update the intent: https://dashboard.stripe.com/logs/req_cIBb9ESeeWCJMG

#

So if you pass the customer id when you create the PaymentIntent, it should work as you expected.

#

Does that help?

proud cairnBOT Jul 16, 2025, 6:50 PM

#

azure fox Jul 16, 2025, 6:52 PM

#

Let me check

#

So is this related to our client-side setup? Because our app only listens to these events.

compact estuary Jul 16, 2025, 6:57 PM

#

No, back end - https://dashboard.stripe.com/logs/req_QtiCEZ5yJDhcDX

#

You can pass the customer id: https://docs.stripe.com/api/payment_intents/create?api-version=2025-06-30.basil#create_payment_intent-customer

azure fox Jul 16, 2025, 7:04 PM

#

Yeah, I understand that part, but we don’t create any type of PaymentIntents — we only receive the webhook events and create the entities on our side.

#

Our clients are the one that connect our app on their end so we start receiving this events

vestal onyx Jul 16, 2025, 7:13 PM

#

Hello, taking over for my colleague who had to step away.
You would want to instruct them to pass the Customer ID to the Payment Intent during creation. If the customer is only attached after the fact then we can't pass that info along in the success event.

There is a subsequent charge.updated event however that shows the customer id being added. What you could also do is if you recieve a charge.succeeded event without a customer.id then wait for the charge.updated event that follows that adds the customer.id

#raul-f_webhooks