#bkrnetic
1 messages · Page 1 of 1 (latest)
I don't believe there's a difference really, both fields can be used for refunds. It just enables us to support merchants who are currently on the older Charges API
afaik
Oh ok. So basically using payment_intent is more up to date?
Correct
I am asking because whole docs on separate charges and transfers use charges in the examples and not intents: https://stripe.com/docs/connect/separate-charges-and-transfers#transfer-availability
afaik that's because source_transaction param expect the specific charge ID vs refunds API (which expects either)
ok, that clarifies it. As for the application fee, we are responsible to calculate it and pass it every time we create payment intent, right? There is no way to define it via dashboard and have it applied on each payment intent by default.
Correct
Thanks, that would be all. Cheers!