#Elringus
1 messages ยท Page 1 of 1 (latest)
Hi there. Let me check on this
Do you have a sample payment intent ID where I can see this?
I have an event id. Will that work?
Or session id.
Not sure where to find intent ID.
Either of those should work. Just as long as I can observe the behavior you're referring to
Ah, my bad, here it is: "payment_intent": "pi_3MyyQJGVcB1Dv1c92Dz0V9r8"
So the receipt will be null until a receipt has been sent to the customer: https://stripe.com/docs/api/charges/object#charge_object-receipt_number. Are you not sending receipts on all successful charges anymore? Could this be due to you changing that setting?
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Uhm, Stripe was automatically sending the receipts, so I've relied on that.
๐ stepping in
Can you clarify what you believe changed here?
Are you saying there is increased latency between when the Charge is updated to contain the receipt_number
Yeah, it's that, probably. Previously, I've used to retrieve the number on charge complete event and register the purchase on our end, but now it's not always available.
checkout.session.completed event, I mean.
Ah okay yeah I don't believe this is a behavior change overall. We never promise for the receipt_number to be available instantly. It is dependent on the receipt_email being sent and if that is delayed then so will the receipt_number on the Charge be delayed a bit
Ah, ok. Is there a way to force the number to generate after checkout? Like, will requesting the receipt url work?
Hmm maybe
Let me check
Yep actually looks like that should work. If you can trigger opening the receipt_url then the receipt_number will be populated
Ok, will try that. Thank you!
๐