#omah-payments
round shore
Hello!
- You would still continue to listen to the same webhook events - disputes are tied to charges, which you can then tie back to a Payment Intent. The same for refunds - there is no equivalent event for Payment Intents - you'd continue to use the same one
- Yes, you should be able to use the Payment Intents API to charge customers that were previously being charged with the Charge API
gilded minnow
In our case, this user will be subsequently charged without their permission because it's like an auto biller. won't this throw an authentication error?
round shore
It depends on when these cards were saved - see https://stripe.com/docs/strong-customer-authentication/previous-authorization-agreements#eligibility. I also want to note, it's always possible for the bank to require authentication if they choose not to accept the exemption so you need to make sure your flow allows customers to come back on session and complete payment
gilded minnow
Thanks Karbi. I'll try this out and reach out if there's any issue.
If I upgrade the version from Our stripe dashboard version is 19th, May 2019 to the current version, will there be any backward incompatibility with any other stripe API that we are using? and will it affect our customers in any way?
round shore
I would strongly discourage you from upgrading your default API version without doing some in-depth testing. You should read through this: https://stripe.com/docs/upgrades#how-can-i-upgrade-my-api
gilded minnow
Thanks.