Error 10002 (“Merchant Authentication failed”) occurs when customers are redirected to CCAvenue during checkout; it previously worked. A screenshot of the error is included.
Platform stance and likely causes:
Shopify clarifies third‑party gateways are supported by the gateway provider.
Possible causes cited: incorrect merchant ID or access code (gateway credentials), or an order originating from an unregistered URL (domain not whitelisted at CCAvenue). Browser cache and version checks were also suggested.
Merchant update:
Reports Shopify’s checkout is using the wrong CCAvenue access code and not fetching the updated one even after re‑signing in. Both Shopify and CCAvenue support have not provided a fix, creating ownership uncertainty.
Additional context:
Another user notes CCAvenue does not offer “test mode”; attempting to use it leads to an “Oops” page. Validation must be done in Live mode.
Status and next steps:
No confirmed resolution. Recommended actions include verifying merchant ID/access code and registered URL with CCAvenue, ensuring Shopify pulls the correct access code, and testing in Live mode to confirm behavior.
I am trying to connect a payment gateway called CCavenue and it was working fine up until a few days ago.
Now, every time someone goes on the checkout page and gets redirected to CCavenue, it shows an error that says Error 10002 with a message “Merchant Authentication failed”.
I have contacted the people at CCavenue but they have not been able to fix it, as they say it is not on their end. I believe this is a problem with Shopify’s integration. I’ve tried reinstalling CCavenue to my Shopify store, that didn’t fix it either.
I also checked the forum and there have been other people with this problem but I could not find a solution. If anyone is aware of this issue or has found a fix please let me know.
Thanks for reaching out here in the Shopify Community.
I’d like to clarify a couple of points here to help you to get the support you need.
The first and most important thing to clarify is that third-party gateways such as this and their integrations with Shopify are supported by the gateway providers themselves rather than by us here at Shopify.
As such, if there is in fact an issue with the integration they created for use with Shopify, it is the responsibility of the gateway provider to maintain and provide support for this.
I did have a look around online for any information relating to the error code you shared here, and did find this external guide with some info.
It looks like this error can be caused by an incorrect merchant ID, an incorrect access code, or if the order originates from an unregistered URL.
As such I would double-check the info you are using from CCAvenue (merchant ID, access code) to ensure they match your account info with them.
I found the problem causing this issue. Shopify has registered the wrong access code when it opens the checkout which is causing the problem. My CCAvenue account’s access code is not matching with the one shown on Shopify even if I sign in again.
I believe this is on Shopify’s end with the CCAvenue integration as it is not fetching the new access code. This seems like a coding issue with the plugin and I’m confused as to how to go forward with this as I’m not really sure who has control.
I’ve tried contacting CCAvenue but they’ve not given me any solution so far and Shopify support is saying they can’t do anything about it even though it is their own plugin which has to fetch the access code from my CCAvenue account.
If you can help me to resolve this on Shopify’s end let me know. Thanks.
CCavenue is not providing any test mode option at their end, you will have to test the checkout process in LIVE mode, set the ccavenue payment gateway in Live mode and you will land on the transaction page of ccavenue. If you are landing at the ccavenue page, then you are good to go.
I was working on a project and I have installed ccavenue payment gateway on shopify but to be safe, I set it to TEST mode and landed on the same ‘Oops’ page of ccavenue, I have asked them why this is happening, they replied that they are not serving test mode, we will have to check the things in Live environment.
