Is there any way to prevent / reduce chargeback of the E-Commerce API?
We have a couple of merchants having chargeback issue.
We suggest the configuration below to the merchants to avoid chargeback but it is still not really helpful for some.
How To Avoid Chargeback Of E-Commerce API
Fraud Tools settings are the best way to help prevent chargebacks. What kind of tools are your merchants looking for in terms of chargeback prevention?
As they're using Clover E-Commerce API and using the configuration shown in the image, is there any other tools can be combined together with the E-Commerce API to prevent chargeback?
We already use the iFrame of E-Commerce API and using https://docs.clover.com/reference/postordersidpay for transaction.
Any suggestion would be much appreciated.
@richelleherrli
When the merchant already enabled all of the AVS setting (other than the address verification) and still have chargeback issue, is there any other way to prevent that happening?
Forcing customer to fill in the address on each transaction is very bad for user experience in my opinion. Our app is an online ordering for restaurant. For E-Commerce maybe it's more suitable because the user doesn't order on daily basis.
The best way to protect against fraudulent chargebacks would be to enable all the fraud settings possible. If you choose to enable/disable some for customer convenience, you of course increase risk. Does the merchant understand why they are getting chargebacks? Do they have a good billing descriptor?
Welcome to the
Clover Developer Community
3 People are following this question.
