#bkrnetic

1 messages · Page 1 of 1 (latest)

kindred jewelBOT
verbal egret
#

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

vestal latch
#

Oh ok. So basically using payment_intent  is more up to date?

verbal egret
#

Correct

vestal latch
verbal egret
#

afaik that's because source_transaction param expect the specific charge ID vs refunds API (which expects either)

vestal latch
#

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.

verbal egret
#

Correct

vestal latch
#

Thanks, that would be all. Cheers!