morgo75

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

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

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).

By the way, I tested it using twenty seventeen.

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

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

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

Excellent. Thanks, Ross.

Righto. Thanks, Ross.

Hi Ross,

I just tried to use the sandbox again but with your sandbox customer id (87654321), and the transaction went through without any problem.

When I subsequently tried to use my own sandbox customer id, I got the same error as before. Any ideas as to why this is happening?

Cheers,
David

Yes, that’s fine. Thank you very much.

I’ve just submitted my 5 star review.

That seems to have fixed that particular issue. Good work!

By the way, instead of inserting the code into the filter’s custom style area, I inserted it into my child theme’s css file so that the code won’t disappear with subsequent updates to the plugin. I assume that this is the correct approach?

Thank you.

Hi,

Thank you for your response.

The website should now be available. Please note however that it may be a little slow as we are presently having page loading speed issues that are apparently being caused by the activation of the Geolocation (with page caching support) feature in Woocommerce (you wouldn’t by any chance have struck a similar issue and know the fix for it, too?).

Thank you.

Great. Thank you.

I look forward with eager anticipation to the updated plugin becoming available.