#charlie-fanbase_api
pine brambleBOT
👋 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/1333394663603961867
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
whole whale
👋
Each API request have an id generated in the header responses unless the API call didn't reached out to Stripe infrastructure.
twin salmon
OK I'll check for it, but generally the question still stands
RequestId = req_1bD0clyhlILYcg, didn't return the requested expand
whole whale
Can you share a sample PaymentIntent Id ? that didn't expanded ?
whole whale
Are you making the get by iD directly after confirming the PaymentIntent
however when using the new API, the capture is made async
So you need to listen to a webhook in order to get notified when the charge is captured and then you can get the chargeId and the balance transaction:
https://docs.stripe.com/payments/payment-intents/asynchronous-capture
twin salmon
yip making it right after
twin salmon
ok thanks, can we opt out of the async capture?
or is it on by default when upgrading the API?
whole whale
it's the new default, but you can specify to use auto capture when creating the PaymentIntent:
https://docs.stripe.com/api/payment_intents/create#create_payment_intent-capture_method
This was introduced in order to improve auth performance.