#mike_api

1 messages ¡ Page 1 of 1 (latest)

inner tinselBOT
#

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

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

naive shale
#

Here's a screenshot of the 2020-08-27 response:

image.png
#

And here's the 2024-12-18.acacia response

image.png
#

I'm providing expand[] latest_charge , when creating the payment intent. that's why latest_charge has an object, however balance_transaction is null

simple wagon
#

Hello, in newer API versions we default to asynchronous capture. Basically there is an authorization step and a capture step for each payment, authorization is when the issuer approves the payment and capture is what makes the funds actually get send to your accound. We used to default to automatic capture which meant that we did both of those steps synchronously and the confirm call waited for both to finish to return. With async capture, we return after the authorization step, which is faster but means some Stripe objects aren't in place yet.
https://docs.stripe.com/payments/payment-intents/asynchronous-capture

#

So you can specify capture_mode='automatic' if you want to go completely back to the old behavior. Otherwise we reccommend listening for charge.succeeded webhooks as those will contain the balance transaction once the capture actually succeeds.

naive shale
#

Ahhh that makes perfect sense. Thank you!! Are there any other downsides to capture_mode='automatic' other than what you mentioned? Is this mode deprecated and will be removed in the future? Or safe to use for foreseeable future

simple wagon
#

Nothing I can think of, it really is just a difference in what is bundled under the confirm call. We don't have any plans to deprecate it that I'm aware of

naive shale
#

Perfect. Makes sense. Ok that solves my needs, I can see it working as expected now. Thanks so much!!