mohsinoffline

It will work for non-EU customers. The WooCommerce official add-on has new directions asking customers to contact Authorize.Net to be moved to CyberSource. https://docs.woocommerce.com/document/authorize-net-cim/#faq-3ds

From WooCommerce docs it is apparent that payment received is not the same thing as payment authorized but payment authorized AND captured, which is why “On-hold” for Authorized Only payments makes sense. Our extension is made to emulate Stripe, and since it is an official extension from WooCommerce we assume it to conform to the way Woo operates.

I understand that it does not fit into your workflow because you only want to capture payment after shipping your products, but others would want to capture it as soon as they are ready to process the order after keeping the order on hold for whatever reasons like checking physical stock availability and fraud checks with the option of voiding the authorization in case the order needs to be cancelled. In any case our extension will keep to how Stripe works.

This is what I was referring to in my initial reply:
https://www.cybersource.com/en-EMEA/psd2/upgrade.html

Apparently they have plans for EU merchants (migration to sister brand CyberSource) but not for non-EU merchants selling to customers in the EU, at least not yet.

The plugin cannot be SCA ready until Authorize.Net API/SDK support it.

If it doesn’t make sense to you, you should be contacting Authorize.Net to verify what changes they have made to their integration system instead of sending me a video about what is common knowledge.

From what I know, Authorize.Net accounts in EU are being migrated to CyberSource which integrated SCA via Secure Acceptance hosted payment pages. There is no information about Authorize.Net accounts from outside who are accepting payments from customers in the EU.

Closing due to the lack of follow up.

It is stored in the order meta called “_authnet_cc_last4”.

Please login to your Authorize.Net account, go to Settings -> Enhanced Card Code Verification page and check if you have set the transactions failing CVV match to be declined or not.

As replied with over email, the plugin does not store credit card metadata except last four digits.

That would happen if you had no card type selected from the plugin settings page. If you allow none of the card types to process, no transactions would process as a result. The warning has been fixed in the version 5.1.2 but you will need to select at least one card type.

Marking this as resolved since there is no follow up.

A) If you are using the plugin in sandbox mode:

Please make sure you are not using your live account credentials but a separate sandbox account for testing. The testing guide linked below states that you must sign up for it to use the sandbox mode:
https://developer.authorize.net/hello_world/testing_guide/

You can switching the payment mode from the one you have set to the other (sandbox to live or vice versa) in the plugin settings page and see if you see a different error message.

A) If you are using the plugin in production mode:

If you are using live account credentials you will only be able to use the plugin in the production mode and use real credit cards to process an order.

If it does not work in the production mode, it is usually because of an incorrect transaction key. You will need to generate a new one and enter it in the plugin settings and test.

Unfortunately, The current version (5.0.0) of the Authorize.net plugin is not using AIM because it is deprecated, and is using the Authorize.net API instead, so I would advise you to use an alternative method.

The 4.0.4 version of the plugin offers the same functionality and uses Authorize.Net AIM integration, so you can use it and change the transaction processing URL in the code. Make sure you DO NOT update thereafter or you will be upgraded to the latest API :).

We also offer an ePN extension that uses their standard TDBE method, it is a premium offering that is well supported and covers all bases:

https://pledgedplugins.com/products/eprocessing-network-payment-gateway-woocommerce/

This issue was addressed in the versions 4.0.3 and 4.0.4 of the plugin. Now the shipping fields are being sent along with order information.

Do not worry, we will make sure it remains working. It just does not require frequent updates. We will review it every few months and upgrade the Twilio SDK when required.