Gravity Forms eWAY Rapid 3.1 API support

Gravity Forms eWAY v2.0.0 has just been released. It has some big changes including support for eWAY Rapid 3.1 API.

Rapid API means better support for USA, UK, New Zealand, Singapore, Malaysia, and Hong Kong — that also means support for local currencies, not just AUD (Aussie dollars). It also means more meaningful error and validation messages from eWAY when a transaction fails.

Gravity Forms eWAY Rapid API settings

Gravity Forms eWAY Rapid API settings

The minimum Gravity Forms version is now 1.9, so please make sure that your Gravity Forms installation is also up to date. I needed to bump the minimum version to make some efficiency changes, and to simplify ongoing support for this plugin by removing some old code.

Gravity Forms eWAY no longer restricts credit cards, because that no longer makes sense. IMPORTANT: this means that you need to review your forms after upgrading, to ensure that the correct credit cards are enabled. Otherwise you could find icons for strange credit cards (e.g. Discover, which Australians never see).

I’ve changed the format for reporting recurring payment dates, to use the WordPress post date format. This means that it honours the settings for WordPress. Again, this is to accommodate reaching beyond Australia’s borders.

Recurring Payments hasn’t changed much otherwise, because eWAY don’t support automated recurring payments via their Rapid API. One small change that fixes a niggly problem is that it doesn’t attempt to use the real Customer ID for the Recurring Payments sandbox (only 87654321 works). This will prevent those strange failures with no error messages when using sandbox mode with a defined Customer ID. Phew!

And for those who want to allow non-administrator users to edit Gravity Forms settings, this now also works for Gravity Forms eWAY settings.

You can update to the latest version from your WordPress plugin admin page. Here’s the full changelog for Gravity Forms eWAY.

PS: Gravity Forms eWAY Pro is almost ready too, with Shared Page (hosted) transactions, feed-driven mapped fields, and more…

Posted on