Skip to main content

The Adobe Commerce Support Knowledge Base has migrated to the Adobe Commerce Documentation section of Adobe Experience League.
Click Support Knowledge Base to access our new Knowledge Base Home.
Knowledge Base articles, as well as other Commerce documentation, will be still searchable and available when creating support tickets from the Adobe Commerce Help Center.

This page has moved to Adobe Experience League and will be redirected soon.

Checkout is stuck when Authorize.net payment method is used

  • Updated

Checkout is stuck when Authorize.net payment method is used

This article provides an explanation and fix for the Adobe Commerce 2.3.X issue where the checkout gets stuck if Authorize.net is used, with the 'Cannot read property 'length' of null' error message in the browser console log.

Affected products and versions

  • Adobe Commerce 2.3.X
NOTE

The core Adobe Commerce Authorize.Net payment integration is deprecated since 2.3.4 and will be completely removed in 2.4.0. Use the official extension from marketplace instead.

Issue

Steps to reproduce

  1. Configure the Authorize.net payment method in the Commerce Admin.
  2. Go to the storefront.
  3. Add a product to the cart and proceed to checkout.
  4. Choose Authorize.net as a payment method.
  5. Click Place Order.

Expected result

The Authorize.net iframe is loaded.

Actual result

Ajax spinner is displayed, and the page never loads. The following JS error is displayed in the browser console log: 'Uncaught TypeError: Cannot read property 'length' of null at b (jstest.authorize.net/v1/AcceptCore.js:1)'

Cause

One of the most common reasons for this issue is the Public Client Key not being specified in the Authorize.Net configuration in the Commerce Admin.

Solution

Under Stores > Settings > Configuration > Sales > Payment Methods, in the Authorize.net section, check if the value is specified in the Public Client Key field. If it is empty, enter the key value from your Authorize.Net merchant account.

For the changes to be applied, clean the cache by running

bin/magento cache:clean
Was this article helpful?
1 out of 2 found this helpful
Return to top