#tdibaja_api
solemn riverBOT
👋 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/1324795351491678329
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
digital cypress
Hello! It depends on what you have capture_method set to on the Payment Intent: https://docs.stripe.com/api/payment_intents/create#create_payment_intent-capture_method
See the docs here for more information: https://docs.stripe.com/payments/payment-intents/asynchronous-capture
tacit fulcrum
I am using default values for this (not setting anything currently). I'm specifically handling card and paypal payments only, nothing longwinded.
digital cypress
The default depends on the API version you're using.
tacit fulcrum
Ok. Latest and greatest. This is a new integration.
digital cypress
Okay, so if you're on that API version or later then the default is automatic_async and the docs I linked above should have the information you're looking for.
tacit fulcrum
Ok. What I understand is that the fee information is only available later and cannot be gotten from Stripe at moment of purchase. Could you confirm this is correct?
digital cypress
It's not if you're using automatic_async, correct.
tacit fulcrum
Understood. Thanks for your help.
tacit fulcrum
If you don't mind, just one last question --- is there any information on how much capture_method=automatic would slow down the payment capture? Are we talking about milliseconds, a few seconds, longer?
digital cypress
I don't believe there's a set amount of time, and even if there was it would be subject to change as we made internal changes on our end.
tacit fulcrum
What I'm after is rather: is it a problematic delay for the user in a synchronous operation, or something unnoticeable?
digital cypress
It's noticable. That's why automatic_async exists. 🙂