It came to our attention that the previous email had links that were not easily accessible. We apologize for any confusion. Here are the correct links to the support articles with detailed instructions below:

? <u>Entrust to DigiCert SSL Certificate Migration (KA-05545)</u>

? <u>Latest Version of Authorize.net Server-Level SSL Certificates (000003009)</u>

Who is being affected: Merchants who utilize Authorize.net APIs and endpoint URLs in their websites or applications will need to make updates. They will need to integrate and use the newly-issued Root and Intermediate (CA) SSL certificates from DigiCert. This should be done before the scheduled revocation dates to avoid disruptions.

What you need to do: You must integrate and use the newly-issued Root and Intermediate (CA) SSL certificates from DigiCert by October 24 to avoid any disruptions. To help you fight fraud, AFDS is automatically enabled on your account, which gives you access to many powerful fraud filters, including:

Sincerely,

The Authorize.net team

“An error occurred, please try again or try an alternate form of payment”

the error appear once I clicked on “apple pay” button

note: I don’t use any cache or performance plugin

The problem is: I’m unsure what to do with it. I mean, I suspect I’m supposed to update the SQL for each user to add in the authnet_customer_id and authnet_card_id, and then switch the _payment_method from stripe to authnet in the wp_postmeta table. And then update the wp_woocommerce_payment_tokens table so that the user logging in can use their saved credit card on file. I attempted to do this for one user… however, nothing worked, and I didn’t want to go too far down as it was starting to make less and less sense.

Unfortunately, the Authorize.net Developer API guide is no help, because it appears to cover adding CC data from your website to your Authorize.net account, but I’m not trying to do that… rather, I’m trying to get my website to see the CC data that already exists within my Authorize.net account. Obviously WooCommerce knows that a client was once using Stripe and contacts Stripe for the CC data it has saved… so I’m just trying to tell it to use Authorize.net instead. What should I do? Thanks for your help!

EDIT: I also realize I can just go into the user’s subscription and insert their new Authorize.net info… but that info is not showing up in their own “Saved Payment Methods” page.

• https://www.ads-software.com/support/topic/accept-js-encryption-failed/

Basically, I’m seeking assistance with an issue related to credit card processing on my client’s website. Several of my client’s customers are encountering an error message that reads “Accept.js encryption failed” when attempting to add or change their credit card information, but I haven’t found any help or solution that has helped me resolve this issue.

Issue Overview:

• Users are unable to update their credit card info; doing so give them the error message: “Accept.js encryption failed”
• The error seems to be affecting multiple clients and is preventing them from updating their payment information or adding a second credit card.
• Attempts to troubleshoot the problem have been unsuccessful so far; the Authorize.net guide to “Accept.js” only provides a vague explanation of the issue: “A general error. Encrypting and transmitting the card data failed, either within the browser or at the Authorize.net servers.”

Troubleshooting Steps:

• I’ve attempted to reproduce the error and investigate potential causes within WordPress, WooCommerce, and the Authorize.net payment gateway; see relevant screenshot link below.
• However, I still haven’t been able to pinpoint the exact source of the issue or find a solution.
• Deleting existing payment methods and examining WooCommerce logs did not resolve the problem.

Additional Information:

• Here are screenshots of the error, as well as logs from WooCommerce.
  • USER’S SCREENSHOT: https://snipboard.io/plSCPW.jpg
  • MY REPRODUCED SCREENSHOT: https://snipboard.io/APD3IO.jpg
  • STEP BY STEP GUIDE OF HOW I REPRODUCED THE ERROR: https://snipboard.io/tGXHlA.jpg
  • WOOCOMMERCE SYSTEM STATUS REPORT: https://pastebin.com/kGBNk3LN
• More detailed information (such as relevant entries of the Woocommerce Error log) can be found in my previous thread linked at the top of this post.

Despite these efforts, I’m still unsure whether the problem lies with a faulty plugin or another aspect of the website’s setup. Any help or insights you can provide would be greatly appreciated. Thank you in advance for your assistance!

Unfortunately the only error message I got was “Accept.js encryption failed.” so I can’t even tell if this is a WordPress, WooCommerce or Authorize.net error. For example, searching for Accept.js bring up Authorize.net, and that particular error just gave me something vague (“A general error. Encrypting and transmitting the card data failed, either within the browser or at the Authorize.net servers.”) so I can’t tell what my next steps are to fix this.

Any help to either resolve or at least narrow down a solution would be greatly appreciated. Thanks!

Also, can you confirm that your plugin uses the Woocommerce checkout and does NOT redirect to a payment page hosted elsewhere?

Hi Sharif,

Thank you for your message and for approving the view access to your recording.

I now understand what the issue is and can reproduce it. I have also confirmed that everything works fine with only Elementor and Elementor Pro, and the inner container controls are in the widget panel. After activating the WooCommerce Authorize.Net Gateway plugin, the issue appeared, and the following error was triggered:?Error: noUiSlider (13.0.0): 'start' option is incorrect.

Most likely, this plugin isn't compatible with Elementor containers and causes the issue you are experiencing. There were similar reports in the past, and all were related to third-party plugin compatibility:?https://github.com/elementor/elementor/issues/8180

And needed to be fixed by the developers of those plugins. For reference:?https://www.ads-software.com/support/topic/incompatibility-with-elements-plus/

Please inform the third-party plugin developers about the issue:?https://www.ads-software.com/support/plugin/woo-authorize-net-gateway-aim/

While waiting for them to fix the problem, keep the conflicting plugin deactivated or look for an alternative solution to replace those features.

Please note that our Support Scope doesn't include third-party plugin modifications. So we are limited in this respect to what support we can provide:?https://elementor.com/help/how-do-i-get-premium-support/?. I hope for your understanding.

Have a great day,

Nemanja Tomanovic

Best Regards

Support takes quite a while to answer.