Vignesh

[robust shadow]

Hmm, do you have existing mandates offline for the previous collected details?

[finite basin]

No. We don't.

[robust shadow]

Then you'll need to collect payment details via our payment UIs which will create the necessary mandate(s) for you

[finite basin]

Yes, i'm moving the new banks over Payments UI. Is there any work around for already collected bank accounts? Also, will Stripe continue support for Charges API?
We are using charges API for fetching the charge details with the charge id of ACH payments and also for creating a new ACH charge.

[robust shadow]

No, you shouldn't use the Charges API

It's fully deprecated, you should use Payment Intents: https://stripe.com/docs/payments/payment-intents/migration

[finite basin]

Thanks. And no alternative for the already saved bank accounts?

Also, we rely on Charge.BalanceTransaction to fetch the txn fee. What is the alternative for the same in Payment Intent? Couldn't find it in the doc.

[robust shadow]

AFAIK, no not unless you have existing mandates collected elsewhere

[robust shadow]

It's the same. The Payment Intent still creates a Charge object and associated Balance Transaction object(s) when a payment is confirmed: https://stripe.com/docs/expand/use-cases#stripe-fee-for-payment

[finite basin]

oh, so if i'm right, I can't use the Charge retrieve API but i can retrieve the charge object by retrieving the payment intent associated?

[robust shadow]

Yes, you shouldn't create Charges directly but Charge objects are very much a part of the API still

You can retrieve a Charge directly, just don't create them

[finite basin]

ok. Thank you so much.

[robust shadow]

np