Gravity Forms Eway Plugin

Eway is a leading provider of online payments solutions with a presence in Australia, New Zealand, and Asia. This plugin integrates with Eway so that your website can safely accept credit card payments.

No. This plugin integrates Eway with Gravity Forms so that you can add online payments to your forms. You must purchase and install a copy of the Gravity Forms plugin too.

Yes, for standard card payments. See the Eway website for details.

Recurring Payments is only available for Australian merchants. PreAuth is only available for Australian, Singapore, Malaysian, & Hong Kong merchants.

Yes. This plugin uses the Direction Connection method to process transactions, so you must have HTTPS encryption for your website.

Go Pro to use Eway’s Responsive Shared Page without requiring an SSL/TLS certificate on your website with standard payments. Recurring payments requires an SSL/TLS certificate with the Free and the Pro add-ons.

Capture charges the customer’s credit card immediately. This is the default payment method, and is the method most websites will use for credit card payments.

Authorize checks to see that the transaction would be approved, but does not process it. Eway calls this method PreAuth (or Stored Payments in the old XML API). Once the transaction has been authorized, you can complete it manually in your MyEway console. You cannot complete PreAuth transactions from WordPress/Gravity Forms.

You need to add your Eway API key and password to see PreAuth transactions in the sandbox, so that the Rapid API is used. The old Stored Payments XML API does not have a sandbox.

NB: PreAuth is currently only available for Australian, Singapore, Malaysian, & Hong Kong merchants. Do not select Authorize if you are a New Zealand merchant!

Client-Side Encryption is required for websites that are not PCI certified. It encrypts sensitive credit card details in the browser, so that only Eway can see them. All websites are encouraged to set the Client-Side Encryption Key for improved security of credit card details.

If you get the following error, you must add your Client-Side Encryption key:

V6111: Unauthorized API Access, Account Not PCI Certified

You will find your Client-Side Encryption key in MyEway where you created your API key and password. Copy it from MyEway and paste into the Eway Payments settings page.

V6010: Invalid TransactionType, account not certified for eCome only MOTO or Recurring available

It probably means you need to set your Client-Side Encryption key; see above. It can also indicate that your website has JavaScript errors, which can prevent Client-Side Encryption from working. Check for errors in your browser’s developer console.

If your website is PCI Certified and you don’t want to use Client-Side Encryption for some reason, then you will still get this error in the sandbox until you enable PCI for Direct Connections. See screenshots

Settings > Sandbox > Direction Connection > PCI

Gravity Forms normally logs the card type with a partial card number when you have a credit card form. With Client-Side Encryption, Gravity Forms no longer sees the credit card number so it cannot detect the card type. When that happens, the card type is listed simply as “Card”.

You can still see the card type and partial card number in MyEway transaction details.

Beagle Lite is a service from Eway that provides fraud protection for your transactions. It uses information about the purchaser to suggest whether there is a risk of fraud. Configure Beagle Lite rules in your MyEway console.

NB: Beagle Lite fraud detection requires an address for each transaction. Be sure to add an Address field to your forms, and make it a required field. The minimum address part required is the Country, so you can just enable that subfield if you don’t need a full address.

Any Gravity Forms license will do. You can use this plugin with a Personal, Business or Developer license.

Successful transaction details including the Eway transaction number and bank authcode are shown in the Info box when you view the details of a form entry in the WordPress admin.

Recurring payments don’t get a transaction number when the payment is established, so only the payment status and date are recorded.

Browse to your Gravity Form, select Notifications and use the Insert Merge Tag dropdown (Payment Amount, Transaction Number and AuthCode will appear under Custom at the very bottom of the dropdown list).

When the sandbox is enabled, the payment amount is rounded up by default, because the Eway sandbox server can return different error codes when the amount has cents. This can be a useful feature for testing how your website displays errors, but you normally don’t want it when testing a payment form.

When your form has a Credit Card field, it accepts very sensitive details from your customers and these must be encrypted. You must have an SSL/TLS certificate installed on your website, and your page must be accessed via HTTPS (i.e. the page address must start with “https:”). You can force a page with a credit card form to be accessed via HTTPS by ticking Force SSL on the Credit Card field advanced settings page; see screenshots.

Recurring Payments is only available for Australian merchants. This feature is available thanks to the generous sponsorship of Castle Design.

If you use conditional logic to hide/show a Product field and a Recurring Payment field, you can even let customers choose between a one-off payment and a recurring payment. Payments can be scheduled for weekly, fortnightly, monthly, quarterly, or yearly billing.

NB: some banks do not accept recurring payments via the Eway Recurring Payments API. I’ve heard that Bendigo Bank is one that does not. Please check with Eway and your bank for more information.

This is a common problem in local testing environments. Read how to fix your website SSL configuration.

Developers can use these filter hooks to modify some Eway invoice properties.