Set up eWAY
The eWAY gateway takes card payments on eWAY’s own payment page (its Responsive Shared Page), so card numbers never reach your portal. A client can save their card there, and their invoices are then charged to it automatically, as with PayTabs and Stripe’s saved cards.
Before you start
Section titled “Before you start”- The API key. In MYeWAY, open My Account → API Key and copy the API Key and the API Password. They are not your MYeWAY login.
- Currencies. Your eWAY account takes the currencies eWAY set up for it (AUD for an Australian account). Each invoice is charged in its own currency, so give clients a currency your eWAY account takes.
- 3-D Secure. eWAY’s payment page asks for 3-D Secure when eWAY has turned it on for your account.
Set it up
Section titled “Set it up”- Install eWAY on System → Payment Gateways and open it.
- Copy the API Key and the API Password into the Live fields.
- Turn on Enabled and select Update Gateway. ClientFence checks the key and password with eWAY before it saves them.
ClientFence gives eWAY its own return address with each payment, so there is nothing to set in MYeWAY. eWAY sends no notices: ClientFence reads each payment back from eWAY when the client returns.
Test it first
Section titled “Test it first”eWAY’s sandbox has its own API key and password (log in at sandbox.myeway.com.au, then My Account → API Key). Turn on Test mode, fill in the Sandbox fields, and pay an invoice with one of eWAY’s test cards. A sandbox account comes with eWAY’s partner account.
Settings
Section titled “Settings”| Setting | What it does |
|---|---|
| Pay with the saved card | A Pay now button on the invoice that pays at once (on by default). |
| Pay once without saving the card | A Pay once with a card button (on by default). Off: clients can only pay by saving their card. |
| Set up on the Payment methods page | Clients save a card without paying an invoice (on by default). |
| Free orders | After a free order that renews, such as a free trial, a client without a saved payment method goes to eWAY to save a card (on by default). |
How clients pay
Section titled “How clients pay”On the invoice, the account owner selects Pay with a card and set up automatic payments, or, once a card is saved, Pay now with that card. Anyone with the invoice can select Pay once with a card. The saved card is the client’s saved method, charged as a recurring payment as described in Saved cards and PayPal accounts. Staff can charge it now with Charge on the invoice.
A declined charge emails the client with the bank’s answer, such as “D4451 Insufficient Funds”, and a link to pay the invoice. A card eWAY no longer knows is removed, so it is not tried again. Removing the card on the Payment methods page removes it from ClientFence. eWAY’s API has no way to delete a saved card, so it stays in MYeWAY, unused.
Refunds
Section titled “Refunds”When you refund an invoice paid with eWAY, choose Send it back through eWAY (see Refunds). The refund is recorded only when eWAY accepts it, and eWAY refuses one larger than what is left of the payment.
Moving from WHMCS
Section titled “Moving from WHMCS”The WHMCS import moves invoices and services that use WHMCS’s eWAY gateway to this gateway (see Import from WHMCS). The cards WHMCS saved at eWAY are not moved, so clients save their card once, on their next payment or on the Payment methods page.

