#ubi
true gyro
dawn wyvern
Hi, yeah you can share the Payment Intent id if you'd wish. However, it would be best practice for your end users to have a more readable oreder/ confirmation id such as 'Order123' instead of a long string. As you mentioned, you can store this in the metadata to then later use.
dawn wyvern
can you share the request id with me please for when you created this payment? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
dawn wyvern
When you retrieve the Payment Intent, https://stripe.com/docs/api/payment_intents/retrieve you can use the expand function, https://stripe.com/docs/expand to expand the latest charge, https://stripe.com/docs/api/payment_intents/object#payment_intent_object-latest_charge, you can attain this receipt number, https://stripe.com/docs/api/charges/object#charge_object-receipt_number.
weary edge
Do I have to use the retrieve function or could be done when I create the payment intent?
😦 dont want to add yet another network call and add some potential failure to the request
dawn wyvern
No, there is not a restriction.
You can use the Expand function when you create the Payment Intent.
weary edge
Roger! Thank you so much!