Authorize.Net CIM: Error at checkout: We did not receive the expected Accept.js data

"We did not receive the expected Accept.js data. Please verify payment details and try again. If you get this error twice, contact support."

Normal Resolution

When receiving this error at checkout, the normal cause of the issue can stem from having previously hit an API error and needing to refresh the checkout once and entering all of the correct data again to submit the order.

Malicious Changes

If you continue to encounter this error even after the above check, we recommend checking that your files have not been modified (but do not modify or fix your files right away). You can do this in Chrome of Firefox by pressing F12 while on the payment step of checkout and clicking on the "Sources" (Chrome) / "Debugger" (Firefox) tab. After clicking into the tab press Ctrl+p and type "authnetcim" and select the file that is in the js/view/payment/method-renderer/ directory (there will be two files with the same name).

Please ensure in the Magento Admin that your extension version is 4.2.0 or above. If the authnetcim.js file does not have a line of code with "delete" in it (if it is in min.js format, you can use Ctrl+f after opening the file to search for the phrase), the file has been modified to leave the raw credit card value intact. This will cause Accept.js to fail with the message you've seen above. You will want to disable the Authorize.net CIM payment method and have someone perform an audit on your store to determine the full scope of any file changes. Leaving the files as they are will help determine a time frame of possible changes.

Conflicts

If the file mentioned above has no changes and you have even gone so far to ensure the extension files are fully intact and up to date but you are still seeing this error, there is likely a JavaScript or CSS conflict on your store. This can range from your sites theme to another extension, or just a broken JavaScript file on your store. If you can pinpoint when this error started occurring and if any changes were made in that same time frame you may be able to pinpoint the exact cause of the error for your store.

If this is something that you can replicate on a development site, the following steps can help narrow down the possible issues until you notice the error goes away:

• Disable the sites theme and use the default Magento Luma theme
• Disable modules in chunks, ensuring files are not cached and static content is flushed or rebuilt. When you hit a chunk that resolves the issue, narrow down the exact module.

Once you determine the cause of the conflict you will need to reach out to the developer or extension company responsible for the code that kicks off the error in our extension. JavaScript errors tend to have a domino affect, so although our extension is throwing an error it may not be the source of the full error.