Errors since plugin update

  • Resolved ThatMarketingCo

    (@thatmarketingco)


    10 years, 4 months ago

    Hey have been using your plugin with GF for quite some time now. Currently working on an update to an existing site (redesign, new theme) and on the new version (which is currently staged on same domain in a subfolder) we’ve updated core and plugins. I’ve generated and entered all correct settings for API Key & Password as well as the Client Side Encryption Key however I just get the following errors when trying to test a simple $1 transaction. Have tried with Sandbox as well as live.

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

    Tried reverting the plugin back to previous version and settings (1.8.0) which seems to work find for single transaction. But strange errors have been happening with recurring payments (saying I need valid initial amount and valid start / end dates and formats, however all those are set correctly).

    Any ideas?

    https://ww.wp.xz.cn/plugins/gravityforms-eway/

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

    (@webaware)

    10 years, 4 months ago

    G’day ThatMarketingCo,

    That means the account isn’t configured to accept Direct Connection payments via Rapid API. You need to speak to eWAY about that.

    With the sandbox, you can flip that switch yourself:

    Settings > Sandbox > Direct Payment Method > PCI [checkbox]

    If you can’t get Direct Connection / Rapid API enabled in time for the client, just remove the Rapid API key/password and it will use the old XML API.

    cheers,
    Ross

    Thread Starter ThatMarketingCo

    (@thatmarketingco)

    10 years, 4 months ago

    Thanks Ross. Appreciate the quick response and helpful tip.
    What I had done was tested with API key/pass AND the encryption key, and then tested with all 3 removed. But removing just the API key/pass and leave the encryption key works.
    Will get client & eWay to configure the account for direction connection. Thanks again.

    Plugin Author webaware

    (@webaware)

    10 years, 4 months ago

    Removing the API key/pass should stop the encryption key being used. If not, I have a bug! Will check that — thanks for the heads up 🙂

    cheers,
    Ross

    Thread Starter ThatMarketingCo

    (@thatmarketingco)

    10 years, 4 months ago

    Just talking with the eWay support and they reckon all accounts can accept direct connection, as long as you are using Client Side encryption. They’re saying the only time you’d need to do additional work on the account is if you want to use Direct connection without the CSE, in which case the client needs to provide them with a PCI SAQ document proving their compliance.

    He’s confirmed you’re technically right. That you can get the transactions to work if client provides the PCI documentation – however this can be a lengthy process.

    He’s said those errors confirm valid API key/password and that the error codes suggest the requests are not using the correct connection method – or that no CSE is in use.

    They checked the responses/requests coming through and have confirmed the transaction requests are coming through with unencrypted card number and cvn. Have said to refer this to you – https://eway.io/api-v3/#client-side-encryption

    Plugin Author webaware

    (@webaware)

    10 years, 4 months ago

    Can you link me to a page with a form on it? It sounds like the CSE is failing, e.g. a JavaScript error.

    Thread Starter ThatMarketingCo

    (@thatmarketingco)

    10 years, 4 months ago

    Ok here’s the page. I’ve added the API Key and Password back in so that you can see the error. I can’t see any JS errors though.

    https://www.interplast.org.au/v2/donate/donate-now/

    It’s using the live API, and you’ll get the two errors listed above

    We also have a bit of custom JS/css just for display of the form/fields, however all values are correct where they need to be.

    Plugin Author webaware

    (@webaware)

    10 years, 4 months ago

    I can see that none of the CSE extras are being added to that form. Can you export the form as .json and email to me support (at) webaware.com.au please?

    Forms > Import/Export > Export Forms

    cheers,
    Ross

    Thread Starter ThatMarketingCo

    (@thatmarketingco)

    10 years, 4 months ago

    Ok have sent that to you

    Plugin Author webaware

    (@webaware)

    10 years, 4 months ago

    Thanks, I can replicate the problem. Hopefully a fix is coming soon 🙂

    cheers,
    Ross

    Plugin Author webaware

    (@webaware)

    10 years, 4 months ago

    For anyone following along, the problem occurs when a form conditionally uses Recurring Payments or one-off transactions. All one-off transactions will go via Rapid API if the API key/password are set, and require Client-Side Encryption on some websites. Recurring Payments doesn’t support Client-Side Encryption, so I don’t use it when a form as a Recurring Payments field.

    v2.1.3 has a fix, and will be released in a few days. If you require the fix sooner, please let me know.

    cheers,
    Ross

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘Errors since plugin update’ is closed to new replies.