Transaction failed V6111: Unauthorized API Access, Account Not PCI Certified V60

Sorry, I noticed that the complete error message did not show in my previous post. The complete error message is:

Transaction failed
V6111: Unauthorized API Access, Account Not PCI Certified
V6010: Invalid TransactionType, account not certified for eCome only MOTO or Recurring available

G’day @morgo75,

That error exactly means that:

• you’ve entered your Rapid API key/password and the Rapid API is being used
• your eWAY account requires Client Side Encryption
• the transaction is being sent without Client Side Encryption

You said you have entered your client side encryption key, so something else is messing things up. I looked at the WooCommerce checkout page and the usual stuff for client side encryption just isn’t there, so either you’ve removed the API key/password to get things working again, or something is stopping the scripts for client side encryption from being added to the page.

Are you able to try changing the theme to twentysixteen or something similarly vanilla? That will help test whether it’s your theme doing something weird.

Another possibility is that Cloudflare’s Rocketscript is messing things up. That thing can do weird things with JavaScript. I don’t think that’s the problem because my eWAY client side encryption scripts aren’t even showing up in the page source, but it’s still a possibility. If the theme switch doesn’t fix things, try turning off Rocketscript and see if that helps. And let me know!

cheers,
Ross

Hi Ross,

Tried all of that. I even regenerated the api passwords and client side encyrption keys. Still not working.

Also, I updated the eway plugin to today’s release.

Have you got any other ideas?

Thanks,
Dave

I was thinking, could there be a problem with the ssl?

By the way, I tested it using twenty seventeen.

Is there something I may need to do in the eway account to enable it to use the rapid api, or should it only be necessary to enter the api key, password, and client side encryption key?

Also, I forgot to mention that it wasn’t working the old way either (i.e. using customer ID).

G’day Dave,

Arg! Thanks for helping me find a bug.

Please tick the option “use WooCommerce standard credit card fields” in the eWAY settings

WooCommerce > Settings > Checkout > eWAY

Client Side Encryption scripts are not loading for the old custom credit card fields. I’ll get that fixed, but in the meantime, please use the standard WooCommerce credit card fields (they’re better anyway!)

cheers,
Ross

G’day Dave,

If you prefer to use the custom credit card fields, not the WooCommerce standard fields, please load this version of the plugin:

https://www.dropbox.com/s/t96jeevrb50of2b/eway-payment-gateway-4.0.2-dev.zip?dl=1

Thanks again for helping me find the bug!

cheers,
Ross

No worries, Ross. Thanks for attending to this so quickly.

I’m just about to test it using the standard Woocommerce credit card fields. I’ll let you know how it goes.

Cheers,
Dave

Yep, it’s working if the standard Woocommerce credit card fields are used. I’ll use them until you officially release an updated version of the plugin that fixes the bug when the standard fields are not selected.

Dave

Hi

https://walkingwombats.com.au/

I’m getting the error too, I have set the Credit Card Fields to ‘use WooCommerce standard credit card fields’ and I get this error ‘Transaction failed
(D4458)’ and when I untick the ‘use standard credit card fields’ I get this message ‘Transaction failed
V6111: Unauthorised API Access, Account Not PCI Certified
V6010: Invalid TransactionType, account not certified for eCome only MOTO or Recurring available’

I have contacted eway and this is their response
‘I have looked in our gateway logs and can see that the card details are not being encrypted.
This would indicate that the plugin you are using is not functioning correctly.
I would recommend contacting the plugin creator directly for assistance with the plugin not encrypting the card details before they’re posted to eWAY.’

I have activated theme 2017 to see if that would help but to no avail….
Please advise me on what to do??

G’day @tarawhitie,

Please open a new support ticket. Your problem is not the same problem (it just resembled it).

While you’re at it, please tick the option “use WooCommerce standard credit card fields” in the eWAY settings

WooCommerce > Settings > Checkout > eWAY

I have not yet released the fix I gave Dave, so you’ll need to run with the standard credit card fields for now (and I recommend you stick with them, they are better supported by themes).

BTW, I suspect that you are trying to use the test card number 4444333322221111 with the live gateway. This won’t work; only the sandbox gateway accepts that test card number.

cheers,
Ross