eWAY Payment Gateway

1. Navigate to ‘Settings > Store > Payments’ on the menu
2. Activate the Eway payment gateway and click the Update button
3. Edit the Eway payment gateway settings by hovering your mouse over the gateway’s name and clicking the hidden ‘edit’ link
4. Enter your Rapid API key/password and Client Side Encryption keys for your live site and the sandbox
5. Select the appropriate settings for your site, including which checkout fields map to Eway fields

1. Navigate to ‘WooCommerce > Settings > Payment Gateways’ on the menu
2. Select Eway from the Payment Gateways menu
3. Tick the field ‘Enable/Disable’ to enable the gateway
4. Enter your Rapid API key/password and Client Side Encryption keys for your live site and the sandbox
5. Select the appropriate settings for your site

1. Navigate to ‘Classified > Settings > Payment’ on the menu
2. Click the Activate Eway checkbox
3. Enter your Rapid API key/password and Client Side Encryption keys for your live site and the sandbox
4. Select the appropriate settings for your site

1. Navigate to ‘Event Espresso > Payment Methods’ on the menu
2. Select Eway from the Payment Methods menu
3. Click the Activate Eway Payments button
4. Enter your Rapid API key/password and Client Side Encryption keys for your live site and the sandbox
5. Select the appropriate settings for your site

1. Navigate to ‘Events > Payment Gateways’ on the menu
2. Click the Activate link underneath the Eway gateway name
3. Click the Settings link underneath the Eway gateway name
4. Enter your Rapid API key/password and Client Side Encryption keys for your live site and the sandbox
5. Select the appropriate settings for your site

You should always test your payments first in the Eway sandbox. You will need to sign up for a sandbox account, and copy your Rapid API key/password and Client Side Encryption key from the sandbox MyEway. When you go to pay, only use dummy card numbers like 4444333322221111. This allows you to make as many test purchases as you like, without billing a real credit card.

• What is the sandbox and how do I get it?
• Test Credit Card Numbers

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.

Not yet. I know it can be done but I haven’t had a website that needs it yet, so have not written the code for it.

If you just need a simple way to record recurring payments such as donations, you might want to try Gravity Forms and Gravity Forms Eway which does support recurring payments.

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

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. Once the transaction has been authorized, you can complete it manually in your MyEway console. You cannot complete PreAuth transactions from WordPress.

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 in MyEway:

Settings > Sandbox > Direction Connection > PCI

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.

• WP eCommerce: the Eway transaction number and the bank authcode are shown under Billing Details when you view the sales log for a purchase in the WordPress admin.
• WooCommerce: the Eway transaction number and the bank authcode are shown in the Custom Fields block when you view the order in the WordPress admin.
• Event Espresso: the Eway transaction number and the bank authcode are shown in the Payment Details block when you view the transaction in the WordPress admin.
• Events Manager: from the Payment Gateways menu item or the Bookings menu item, you can view a list of transactions; the Eway transaction ID is shown in the Transaction ID column, and the authcode in the Notes column.
• Another WordPress Classifieds Plugin: not available yet

Yes, if you deactivate the Gold Cart’s Eway payment gateway and activate this one.

This is a common problem in local testing environments. Please read this post for more information.

The plugin will run in shared hosting environments, but requires PHP 7.4 or later.

Developers can refer to the code for filter hook parameters.

• wpsc_merchant_eway_invoice_desc for modifying the invoice description
• wpsc_merchant_eway_invoice_ref for modifying the invoice reference
• wpsc_eway_credentials for modifying the Eway credentials used in the transaction

Developers can refer to the code for filter hook parameters.

• woocommerce_eway_invoice_desc for modifying the invoice description
• woocommerce_eway_invoice_ref for modifying the invoice reference
• woocommerce_eway_icon for changing the payment gateway icon
• woocommerce_eway_credentials for modifying the Eway credentials used in the transaction
• woocommerce_eway_method_capture to allow per-order capture or authorize
• woocommerce_eway_error_msg to allow developers to provide richer error messages

Developers can refer to the code for filter hook parameters.

• awpcp_eway_invoice_desc for modifying the invoice description
• awpcp_eway_invoice_ref for modifying the invoice reference
• awpcp_eway_icon for changing the payment gateway icon
• awpcp_eway_checkout_message for changing the message above the checkout form
• awpcp_eway_credentials for modifying the Eway credentials used in the transaction

Developers can refer to the code for filter hook parameters.

• em_eway_invoice_desc for modifying the invoice description
• em_eway_invoice_ref for modifying the invoice reference
• em_eway_amount for changing the billed amount (e.g. adding fees)
• em_eway_credentials for modifying the Eway credentials used in the transaction

Developers can refer to the code for filter hook parameters.

• event_espresso_eway_invoice_desc for modifying the invoice description
• event_espresso_eway_invoice_ref for modifying the invoice reference