V6111 and V6010 Error

  • Resolved jennywickham

    (@jennywickham)


    8 years, 9 months ago

    I am trying to test a form with eway and working in sandbox setup

    I get these errors when putting in a test credit card

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

    Eway have told me to contact you directly to get this resolved.

    It is fresh install of wordpress, I have loaded gravity forms, eway payment gateway, your plug in and the only other plug in loaded is ithemes security

    there is no content on the site, as i just wanted to test the form first before i go ahead with the build, because if i can’t get the form to do what the client wants then i need to find another solution.

    I have looked through other supports on this but i dont think any of them relate to my issues, the client side encryption key is in and checked with eway

    thanks in advance!

    https://www.ads-software.com/plugins/gravityforms-eway/

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

    (@webaware)

    G’day Jenny,

    You need to set your Client Side Encryption key. You are getting this message because the transaction is being sent without encrypting the credit card number and cvn.

    https://gfeway.webaware.net.au/faq/do-i-need-a-client-side-encryption-key/

    Each of the live and sandbox accounts have their own CSE key, so be sure to copy your sandbox CSE key to your sandbox settings.

    cheers,
    Ross

    Thread Starter jennywickham

    (@jennywickham)

    Hi Ross

    As I said above I have put the client side encryption in and eway have also checked it is correct, hence why I am now messaging you to help out.

    Plugin Author webaware

    (@webaware)

    G’day Jenny,

    Yes, but did you get the CSE key from the sandbox settings, or your account settings? The message you are getting is very specifically related to sending the credit card details without encryption.

    Another possibility is that something on your website is breaking the JavaScript. My money is on iThemes “Security” ?? but check your browser console for JavaScript errors. Also check your page source to see if the page is loading a file “ecrypt.js”, which is eWAY’s code for encrypting the credit card details.

    If you would prefer not to post a link to your website here, please send me a link via my support page and I’ll have a quick look for you.

    cheers,
    Ross

    Thread Starter jennywickham

    (@jennywickham)

    Hi Ross

    The CSE came from my account settings. I went through all of this with eway support chat.

    I can send you a link to the form, will send via your support page, as it is being built at the moment. thanks.

    Thread Starter jennywickham

    (@jennywickham)

    Hi Ross

    I have sent you a second message via the support page, as the first link I gave you might not be any good, so have just popped the form into a page

    thanks in advance!
    Jenny

    Plugin Author webaware

    (@webaware)

    Thanks, received. Conversation shifted to emails for the moment.

    cheers,
    Ross

    Plugin Author webaware

    (@webaware)

    Notes for completion: server was running an old version of PCRE (regular expression library) that didn’t process \K. Have recommended upgrading server to latest PHP and PCRE.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘V6111 and V6010 Error’ is closed to new replies.

Tags