mohsinoffline

Hi there,

This can happen only if you setup the Authorize.Net fraud detection suite to put the transaction on hold for review, for instance in case there is an AVS mismatch. When that happens you can simply change the order status to either “Processing” or “Completed” manually after reviewing the order and the plugin will capture the payment via an API request. Can you please check in Authorize.Net if these transactions are marked as “FDS/Hold for Review” or something similar?

Closing this since it has been more than a week since we have an update from the user.

Thanks for using our plugin. The block based WooCommerce checkout is only compatible with a limited amount of payment gateways. You can refer the document for more details.

https://woo.com/document/cart-checkout-blocks-status/

Our NMI extension is not yet compatible with it, but we are on it, and since it requires a significant amount of rewrite of the plugin, the release would come very soon in coming days. However, our plugin is fully compatible with the standard shortcode [woocommerce_checkout] checkout so you can revert back to it and use the gateway. Let me know if you need any help with switching your checkout page.

https://woo.com/document/cart-checkout-blocks-status/#section-6

Can you please update the plugin and let me know if it works now?

Hi again,

Just wanted to give you an update. We have identified the issue and will release a new version containing the fix in the next 24 hours. Thanks for your patience.

Closing this due to no further follow up.

All good, I am glad it is resolved now.

Hi there,

Can you list the steps I need to follow to see the issue? I wasn’t able to locate the error message in console on the homepage, cart or checkout pages.

Hi there,

I am sure you must have checked, but do you happen to have a different Authorize.Net plugin installed by any chance? The error message you mention is not something our plugin should display. Please let me know.

@platypusrex2018 I checked your site, it is the “Multi-Step Checkout for WooCommerce” plugin that hides the payment area when the checkout page loads. So when the NMI’s card fields (via the Collect.js library) are mounted it cannot detect the height of the container. You can switch to the checkout tabs element built in Avada, since we have added compatibility for it in the past:
https://avada.com/documentation/woo-checkout-tabs-element/

If that does not work, you can just remove the NMI tokenization key from the plugin settings page and it will switch to the direct post method, and WooCommerce’s built-in card fields will then appear.

I hope that helps.

@platypusrex2018 do you have a site URL that I can check?

Hi there,

If you setup the plugin to capture payments automatically, it will do so and trigger a “payment_complete()” event for the order in WooCommerce order after payment like any other payment gateway plugin. WooCommerce then decides what status to put the order into. Usually if you are selling virtual and downloadable products, WooCommerce puts the order directly into the “Completed” status, but with physical products the order status should become “Processing”. Just to be clear, our plugin does not decide the status between “Processing” and “Completed”, it will be left to WooCommerce.

The exception to this is when the plugin will set the order status to “On Hold”. This happens either when you set the plugin to NOT capture payments automatically, or if you setup Authorize.Net to put the transaction on hold for review, for instance in case there is an AVS mismatch. When that happens you can simply change the order status to either “Processing” or “Completed” manually after reviewing the order and the plugin will capture the payment via an API request. The plugin does not poll Authorize.Net, but it lets you capture the payment from the WooCommerce edit order screen via a status change. Again the only reason you cannot fully automate this is because you either chose to not capture payments in the plugin settings or setup your gateway account to put transactions on hold using Authorize.Net’s fraud detection system.

The plugin is setup upon the interpretation of WooCommerce of its own order statuses. I hope that makes sense.
https://woo.com/document/managing-orders/

Hi @eric4,

That was hopefully the last you see of the issue. So sorry for the trouble. Can you please update to 6.1.2? It should resolve the issue.

Hi there,

Sorry for the trouble, we have pushed a new release now to reverse the update. It should be back up.

Hi there,

Sorry for the trouble, we have pushed a new release now to reverse the update. It should be back up.