We are using your plugin:- Authorize.Net WooCommerce Addon

we want to know if your plugin is compatible with PHP 8.1 or not.

We would love to know ASAP.

Our finance department reported a spike in valid transactions getting stuck in the suspicious transactions fraud filter on Authorize.NET

Has anyone else experienced this? Is there a sensitivity setting that I need to check? Not sure how to troubleshoot but I fear that if I begin with tech support at Authorize I may not get anywhere.

• This topic was modified 2 years, 10 months ago by kgueter1. Reason: I hit submit "enter" in error while drafting

I’m using woo commerce + divi + authorized net woo commerce plugin + direct checkout plugin

I made a checkout template custom build on theme builder via divi, I add the checkout module from woo commerce.

When I launch my site, my woo commerce checkout module doesn’t show on my checkout page.

We are going to be using a different service for payments on our Woocommerce site. If I disable the authorize.net plugin will that end the monthly payments or is some other action required to end the monthly payments?

Can you help review what happened on partial refund? Ever since the update a few months ago the refund process is haywire. This partial refund used to work fine and it appears now it “VOIDS” the transaction and CANCELS it instead of only refunding the dollar amount entered.

Hi,

I am looking to use subscriptions on my site, and I was wondering if your plugin supportted ‘Authorise Subscriptions’ ?

Hi,

Thanks for this awesome plugin, I have noticed that if we enable this plugin, Add Payment” menu is no longer visible under My Account section, which can be accessible if we install Stripe Payment Gateway plugin.

Instead of displaying Add Payment menu it shows the following text :
“New payment methods can only be added during checkout. Please contact us if you require assistance.”

I want to display Add Payment details menu, so the user can add Payment details, can you help me to resolve this issue?

Thanks in advance

I have an issue when someone places and order, and the order is declined, Authorize.net wants them to wait 2 minutes before resending the transaction, which is forever for a user. In talking to Authorize.net, they said to add the variable duplicateWindow to the submission so they know how long to wait before they will allow a second transaction.

Has anyone else ran into this? It’s not an option that I can see on the dashboard, but I can make changes wherever is needed if I’m pointed in the right direction.

Just received this email from authorize.net. Does it affect the plugin in any way?

Authorize.Net is phasing out the MD5 based transHash element in favor of the SHA-256 based transHashSHA2. The setting in the Merchant Interface which controls the MD5 Hash option will be removed by the end of January 2019, and the transHash element will stop returning values at a later date to be determined.

We have identified that you have this feature configured and may be relying on MD5 based transHash in transaction responses for verifying the sender is Authorize.Net.

Please contact and work with your web developer or solutions provider to verify if you are still utilizing MD5 based hash and if still needed to move to SHA-256 hash via Signature Key.

Please refer your developer or solution provider to our Transaction Hash Upgrade Guide for more details and information on this change.

Authorize.net just sent out an e-mail (see copy below) about some changes to Supported Characters. Is this plugin being updated with the new Authorize.net security improvement?

Also found this for reference: https://community.developer.authorize.net/t5/News-and-Announcements/Changes-to-Supported-Characters-on-January-10-2019/td-p/65435

Dear Authorize.Net Merchant:

As part of ongoing security improvements, we’re making changes on January 10, 2019 that may affect your gateway account. After January 10, certain characters will be replaced with spaces if sent to the gateway.

Authorize.Net is changing how it handles some character data included in transactions submitted to our systems. Starting January 10, 2019, transactions that contain any of the characters listed in the table below will be replaced with a space (‘ ‘) before saving the transactions in our systems and/or passing the transaction data to the back-end payment processor. If you later query our systems for data on these impacted transactions, we will send back the edited content. This includes URL and HTML encoding of the ‘<’ and ‘>’ characters, and non-printable Unicode characters.

Invalid Character Inputs

I received an order on my website, customer used his credit card, and so the transaction is set to authorized on authorize.net as it should be. But I want to cancel that order and make a new order manually for him, but don’t want to lose his authorization (so he doesn’t have to pay again). So if I change the order status to cancelled in WooCommerce, does that affect the associated authorization? Or will the authorization remain? Thank you!

Hi, Can you let me know how this plugin functions as related to PCI compliance? It is an iFrame (SAQ A), tokenized, non-tokenized (SAQ A-EP)?

I am currently implementing 3D Secure and have updated my Authorize.net account with the check marks to allow the Visa and MC solutions. The 3D secure provider is saying the plugin needs to pass the CAVV value to Authorize.net. I ran some Visa tests with this plugin on my site and it is processing the test transactions but Authorize.net is not receiving the CAVV. I confirmed that the 3D secure part of my site is correctly generating the CAVV and they are approving the 3D secure from their side.

DOES ANY ONE KNOW WHAT IS CAUSING THIS?And How to Fix?

[24-Nov-2018 04:55:55 UTC] shipping_country was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Authorizenet_Gateway->process_payment, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.

My client is concerned that when entering in the cc information on the form, the “/” on the expiration date doesn’t get automatically added, thus leaving the customer potentially confused with an error message. Is there an easy workaround to this?

id was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Authorizenet_Gateway->process_payment, WC_Order->payment_complete, WC_Order->save, WC_Order->status_transition, do_action(‘woocommerce_order_status_pending_to_processing’), WP_Hook->do_action, WP_Hook->apply_filters, WC_Emails::send_transactional_email, do_action_ref_array, WP_Hook->do_action, WP_Hook->apply_filters, WC_Email_New_Order->trigger, WC_Order->get_order_number, apply_filters(‘woocommerce_order_number’), WP_Hook->apply_filters, change_woocommerce_order_number, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.

Does this plugin up to date/

I mean Is it “AKAMAI UPDATE COMPATIBLE” ?

can you please confirm this?

Thanks..

Getting errors at checkout:
wc_doing_it_wrong. This message was added in version 3.0.
mod_fcgid: stderr: add_to_cart_fragments is deprecated since version 3.0.0! Use woocommerce_add_to_cart_fragments instead.
mod_fcgid: stderr: The WC_Cart::get_cart_url function is deprecated since version 2.5. Replace with wc_get_cart_url.

We sometimes get a general error message saying payment failed and then the payment goes through.

Is there an update to the plugin that we need?

Thanks,
K Khalifa

How do I enable these options on the payment gateway

Authorize.net sends code 253 (authorize and hold for review)

This code means I want to hold the order until I approve it. Your plugin is not handling 253 correctly it places the order as processing instead of pending.

We lost over $3000 of products due to a hacker. The Fraud Detection setting Code 253 was allowed to go through… it marked the order as processing and the shipping the company shipped the products. I had not approved the payment in authorize.

Can you update the code to mark orders as Pending if you get code 253?

• This topic was modified 6 years, 6 months ago by ljgarnes.

Hey,

I know this doesn’t require SSL but if i have SSL activated will everything work ok?

Thank You

The error messages could use some improving or, better yet, make the error messages a plugin option that can be changed. Currently, if no credit card number is entered the error message reads “Merchant do not support accepting in unknown card.” Perhaps it could at least read “Please enter a valid card number.”

Hi,

Can your plugin allow GBP payment for the Indian Merchant. GBP will be transferred to Indian Bank Account later on.

Thanks and Regards

Hello,

I created a sandbox account at Authorize.NET and configured your plugin with the API and transaction keys. When I attempt to complete an order using Authorize.NET’s test card numbers, I receive the following error message: https://i.imgur.com/8kO8Ny6.png

However, the order still appears in my WooCommerce dashboard, marked as “Pending” and eventually “Cancelled.”

A few other details:

– I tried using both sandbox and live mode.
– I followed the steps outlined in #13 of the plugin FAQ
– My website is SSL-enabled

Do you have any suggestions for correcting this issue? Do you believe it would affect actual orders?

Thank you.

Hello,
We are using your plugin for our online shop, however we would like to add Paypal as an option next to accepted cards (Visa, Master). Authorize.net says they can connect Paypal account with Authorize.net account by API integration (instruction: https://developer.authorize.net/api/reference/features/paypal.html). Their instruction requires coding customization but we are looking for a simpler way to add it to Woocommerce. So my question is:
1. Does your plugin have the function to add Paypal as an option?
2. If you do not have this function at this moment, may I ask if you plan to add Paypal in your future development?
3. If we would like to have customization from your team, is it possible and could you help estimate how long it could take?
Thank you very much.

How to change order status Processing to Complete after successful payment ?

I sell wholesale and my customers get denied their transaction if they use more than 30 lines with this error message:

The number of line items submitted is not allowed. A maximum of 30 line items can be submitted.—AuthorizeNet Error:
Response Code: 3
Response Subcode: 1
Response Reason Code: 271
Response Reason Text: The number of line items submitted is not allowed. A maximum of 30 line items can be submitted.
on 22-Jan-2018 05:12:00 UTC using AUTH_ONLY

Everything else with this plug-in has been wonderful. This does, however, turn my big customers away. Can you help?

I have setup auth only mode for transaction.. When customer do order, I am getting this message in order note:

This transaction has been approved. on xx-Jan-xxxx xx:xx:xx UTC with Transaction ID = xxxxxxxxxx using AUTH_ONLY and authorization code xxxxxx
Here: I am getting all value when order received. and working perfect.

Case 1:
Now, When i do order status completed then It was not auto captured. I was looking auto-capture once order completed.

Case 2: I click on capture button on admin order details page manually. Then i get this message:

This transaction has already been captured. on xx-xx-xxxx xx:xx:xx UTCwith Transaction ID = 0 using PRIOR_AUTH_CAPTURE and authorization code
It is sending 0 value. instead of actual transaction id.

Support told me: the sale was authorized and recorded but our step to capture is not transmitting to Authorize. Customer service mentioned something about a ‘response code’ on Woo to confirm order was completed.

Expecting:
1. Can you fix Prior_Auth_capture issue?
2. Can we combine with completed status if possible?
3. If we need to partially accept payment then how can we do from this plugin?
Means if order $100 and we need to charge $50 for now. Remaining after sometime etc.

Hi, I just got this email from Authorize.net Will this affect your plugin in any way?Thanks!

Your Payment Gateway ID: xxxx
Dear Authorize.Net Merchant:

As you may be aware, new PCI DSS requirements state that all payment systems must disable earlier versions of TLS protocols. These older protocols, TLS 1.0 and TLS 1.1, are highly vulnerable to security breaches and will be disabled by Authorize.Net on February 28, 2018.

To help you identify if you’re using one of the older TLS protocols, Authorize.Net will temporarily disable those connections for a few hours on January 30, 2018 and then again on February 8, 2018.

Please refer to our TLS FAQs for important details.

Based on the API connection you are using, on either one of these two days you will not be able to process transactions for a short period of time. If you don’t know which API you’re using, your solution provider or development partner might be a good resource to help identify it. This disablement will occur on one of the following dates and time:

Akamai-enabled API connections will occur on January 30, 2018 between 9:00 AM and 1:00 PM Pacific time.
All other API connections will occur on February 8, 2018 between 11:00 AM and 1:00 PM Pacific time.
Merchants using TLS 1.2 by these dates will not be affected by the temporary disablement. We strongly recommend that connections still using TLS 1.0 or TLS 1.1 be updated as soon as possible to the stronger TLS 1.2 protocol. If your current Virtual Point of Sale (VPOS) is an Authorize.Net product, please call Authorize.Net Customer Support at 1.877.447.3938 for assistance in updating to TLS 1.2.

Note: If you are not using a current version of a web browser, please take a few moments to upgrade it now. Browsers released prior to 2014 may not support TLS 1.2. You can check your browser’s TLS support by visiting https://www.howsmyssl.com/.

If you have any questions about this email or the upcoming TLS disablement, please refer to our TLS FAQs. Thank you for your attention to this matter and for being an Authorize.Net merchant.

Hi, I tried to do a partial refund this morning through the WP admin area order edit screen, but when I logged into the gateway to verify, I noticed that the entire order amount was voided. So I had to ask the customer to place his order again, which he thankfully did. Are you aware of this?