Transaction failed: V6111: Unauthorised API Access, Account Not PCI Certified

  • Resolved studio313

    (@studio313)


    7 years, 6 months ago

    Hi,
    Hoping you can help with an issue I am having with a clients site, we are getting the error below:

    Transaction failed:
    V6111: Unauthorised API Access, Account Not PCI Certified
    V6010: Invalid TransactionType, account not certified for eCome only MOTO or Recurring available error on a live eWay account.

    I have got the client to triple check all their settings, in particular the Client Side Encryption Key as I know this error is usually caused by a fault there. All is correct.

    I noticed a previous thread where the issue was that the eWAY Client Side Encryption script was being called as an internal resource rather than from the eWAY servers so I double checked this and that’s not the issue either.

    Do you know any anything else which could be causing the error or conflicting with the Encryption script?

    Please let me know if you need any further information and thank you in advance for your help.

    Cheers
    Chris

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author webaware

    (@webaware)

    G’day Chris,

    Normally, the Card Number and CVV fields are modified to have a custom attribute added to them, which my script uses when it calls the Client Side Encryption. That custom attribute (data-gfeway-encrypt-name) isn’t there, so something on your website is interfering with the process.

    Do you have anything that might be messing with the Gravity Forms filter gform_field_content? I use that to inject the custom attribute. e.g. a Gravity Forms related plugin, or something in your theme.

    cheers,
    Ross

    Plugin Author webaware

    (@webaware)

    Also, do you get a warning about your PCRE version? It’s a regular expression module used in PHP, and it must not be too old. The plugin will add a notice to your WordPress admin if you’re system has a very old version of PCRE. It can cause this exact problem.

    cheers,
    Ross

    Thread Starter studio313

    (@studio313)

    Hi Ross,

    Ta heaps for getting back so quickly.

    They have Gravity Forms CSS Ready Class Selector ( https://en-au.www.ads-software.com/plugins/gravity-forms-css-ready-selector/ ) and Gravity Forms HTML5 Validation ( https://en-au.www.ads-software.com/plugins/gravityforms-html5-validation/ ) also installed. Have you known one of these to cause the issue?

    Nope, we are not getting a PCRE version notice in the WordPress admin

    Cheers

    Chris

    • This reply was modified 7 years, 6 months ago by studio313.
    Plugin Author webaware

    (@webaware)

    G’day Chris,

    It’s the HTML5 Validation plugin — it modifies the HTML for the card number and cvv inputs, so my regular expressions were failing. Please try this updated version:

    https://www.dropbox.com/s/ylczxt7x3rt8gd9/gravityforms-eway-2.2.6-dev.zip?dl=1

    It’ll be released sometime this week, with these changes:

    * fixed: Gravity Forms 2.3 compatibility; don’t directly access database tables
    * fixed: amounts in Japanese Yen (JPY) are already in the lowest denomination; no need to shift to / from cents
    * fixed: Client Side Encryption fails when Gravity Forms HTML5 Validation plugin is active

    cheers,
    Ross

    Thread Starter studio313

    (@studio313)

    awesome, Cheers mate, will install the update and test the form again

    ta heaps for your help

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Transaction failed: V6111: Unauthorised API Access, Account Not PCI Certified’ is closed to new replies.