• Resolved kevinliew

    (@kevinliew)


    We use this in our donation form, and for some reason, it show that error codes:

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

    According to my client, it was working again when he try again on the next day. And one of the customers, it worked after a few tries.

    I’m pretty sure everything was setup correctly and the fact that it works the next day, I don’t think my setup have any issue. Is this something to do with eWay?

Viewing 11 replies - 1 through 11 (of 11 total)
  • I have exactly the same issue with the exactly the same error code. eWay are saying that the client encryption is not coming through whilst this has been set up in the eWay Payments plugin for GF.

    It appears to be random but stops working almost every day. Any ideas?

    Plugin Author webaware

    (@webaware)

    V6111+V6010 means that:

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

    If you’ve set your Client Side Encryption key, then it could be that your site has a JavaScript error preventing Client Side Encryption from working. Please provide a link to the site so that I can inspect it.

    cheers,
    Ross

    https://www.rspcatas.org.au/donate/

    API Key/password, client side encryption and client ID have been entered.

    Plugin Author webaware

    (@webaware)

    Likely some interaction between the single vs recurring and eWAY vs PayPal you have going on there on that form. The free plugin really wasn’t set up to handle that well, so your developers must have done some nifty work to get that going. I recommend that you get your developers involved again.

    cheers,
    Ross

    Well, no – the PayPal form is a different plugin called “Recurring PayPal Donations” by wpecommerce. There are no console errors on the page.

    They have always worked side by side. Only recently did the eWay form stop working.

    Any other options?

    Plugin Author webaware

    (@webaware)

    It’s still most likely some interaction issue between recurring and one-off payments, and the tabbed form setup you have. I recommend asking your original developer to debug the problem in a development environment.

    You might be better off with the pro eWAY add-on, which has better support for different modes of payment, through separate payment feeds.

    cheers,
    Ross

    Thank you – we have now purchased the Pro version of your plugin. In this version there are no Settings for Options and Error Messages, is that correct?

    Just API Key and Password, Client Side Encryption Key and Customer ID, and licence number.

    I have disabled the PayPal option but would like to offer this as well. Are there any known conflicts between PayPal and eWay integrations?

    Thanks,
    Louise

    Also, do I deactivate the free version?

    Plugin Author webaware

    (@webaware)

    G’day Louise,

    The pro version works a little differently to the free version. You will need to create two eWAY feeds for your form, one for one-off payments and one for recurring payments. Here’s how to do that:

    https://gfeway.webaware.net.au/pro/create-a-feed/
    https://gfeway.webaware.net.au/faq/mix-standard-and-recurring/

    Once you’ve created the feeds and tested them, you can deactivate the free version. The two can work side by side, but each form can only use either the free or pro version; the are independent plugins.

    How it interacts with the PayPal part of your form depends on how that has been implemented. The pro plugin has no problems working with the Gravity Forms PayPal Standard add-on, but there may be other complications with your set up.

    You might prefer to continue this conversation privately now, starting with a support request on our support form:

    https://shop.webaware.com.au/support/

    cheers,
    Ross

    Thank you – had no idea this worked so differently. Set up the two feeds and the form seems to work without generating errors, so far… ??

    May need to check out the Gravity Forms PayPal Standard add-on next.

    Thank you – if I need further help, I will open a support ticket.

    Plugin Author webaware

    (@webaware)

    That’s good news! Well done. Yes, the pro version is a totally different plugin with much more happening. The free version was written ages ago before Gravity Forms made it easier to write add-ons.

    Let me know if you run into trouble again!

    cheers,
    Ross

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