MultiTable

Last time we used the plugin, it was every order declined. We have not been using the Woo Plug-In since, because we didn’t want to cause issues with customer’s cards and we also get charged every time a card is declined. For the failed transactions, Authorize.Net just has “Card declined by issuer – Contact card issuer to determine reason.”

This was customer service’s response to me.
Hi Kenny,

So when I ran the card through Woo, the error message was “Card declined by issuer – Contact card issuer to determine reason.” Then I attempted to run it directly through Authorize.Net and the card was accepted.

Thanks,

Nicole

We have not been able to successfully accept cards on the backend of woo since this update?

We will give that a try. Thanks again. Great work.

Thanks again. We’ll get thru this. Thanks for all the help.

I was trying to place another customer order on the back end of Woo, and when I went to charge the customer’s card this error message popped up:

The ‘AnetApi/xml/v1/schema/AnetApiSchema.xsd:unitPrice’ element is invalid – The value ” is invalid according to its datatype ‘Decimal’ – The string ” is not a valid Decimal value.

Could you look into this please?

I’ll have my customer service team test when they get time. I changed the method in the field you added. You’ve been really helpful. I really appreciate your attention. I do not know how millions of companies are getting by without this.

Any word on the payment method printed to emails?

You are awesome thanks.

Thank you so much. I will be sure and blast 5 star reviews if we can get these small details ironed out. In the Authorize.net screen the report screen there is an Invoice Number column and the number populating there is a 5 digit number. We are using a plugin to change the order numbers called “WooCommerce Sequential Order Numbers Pro” I’m wondering if the number being passed to authorize.net is the order number before it’s converted possibly.