#michi_api
1 messages ยท Page 1 of 1 (latest)
๐ 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/1325927987664654407
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- michi_api, 3 days ago, 20 messages
Hello
I'm not sure I fully grasp the question. Can you elaborate?
latest_charge parameter replaced charges array a while ago in an API version update - https://docs.stripe.com/changelog/2022-11-15/removes-charges-attribute-paymentintent
Are you asking about that?
latest_charge is an expandable property - https://docs.stripe.com/api/payment_intents/object#payment_intent_object-latest_charge
meaning charge information is not included in the PaymentIntent by default but you can "expand" it if you need to look at the underlying charge.
Yes, I get charges via the following https://api.stripe.com/v1/invoices?limit=100 endpoint
Do you mean List all invoices endpoint? https://docs.stripe.com/api/invoices/list
Sorry I'm not sure I fully grasp what you're describing.
Charges is now deprecated?
Yes, charges field was replaced with latest_charge parameter
https://docs.stripe.com/changelog/2022-11-15/removes-charges-attribute-paymentintent
Great! Happy to help ๐
But I have still one understanding question:
Sure
What's the question?
What is the exact reason why a list of payments is no longer supported. For example, if I want to offer my end customers installment payments of $500 each for an $1.500 invoice. This will no longer be possible to receive those informations without a list.
Sorry, but it seems for me like a downgrade
How does listing charges affect the payment process exactly?
invoice.payment_intent.charges returned a list of charges associated with a specific PaymentIntent/Invoice. Meaning if there were more than 1 charge (like failed payment attempts), then charges would list all the charge objects. It doesn't have anything to do with collecting payments for multiple invoices?
I think you're misunderstanding the flows/logic of the parameter. If you're trying to integrate installments, then you should be able to use Subscription Schedules for this and charge customers automatically - https://docs.stripe.com/billing/subscriptions/subscription-schedules/use-cases#installment-plans
Okay, I think I got it. Thanks!