ResPax offers and supports an interface to the Merchant Gateway, eWAY, that offers a secure payment solution for your customers.
The Eway interface is only available in the ResPax Enterprise Application and for Public and Agent online bookings, and for Staff issued payment links to our online checkout. It is not available for ResPax Enterprise app.
Eway Application
The link below provides an eWAY Payment Gateway application with ResPax details so they will know you are a ResPax client.
Their pricing and terms and conditions are explained during this process.
Any queries regarding these points should be made directly to eWAY.
https://www.eway.com.au/contact-us/contact-sales/
Once you application has been approved they will send you an email confirmation.
You will need to log-in to the eWay portal and download your credentials. The following information is required for ResPax to proceed with the payment gateway integration.
- API Key: aReallyRandomLongKeyThatMayBeAsLongAsSeventyFiveCharactersInLength
- API Password: XXXXXXXX
- Public API Key: XXX-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
...
The same fields are required when a staff is creating the booking via the ResPax Booking Engine (RBE).
Eway Declined Payments
Issue: If you see the following error - "Credit card was not accepted" (see screenshot attached), this is because our OBE and RBE and Payment Hub send our server IP to the Payment Gateway as the IP instead of parsing through the IP of the client-browser. If Anonymous Proxy is not enabled in the Eway account, this will fail.
Workaround: Please make the following changes in the Eway account.
- Log into MyEway
- Go to Settings -> Fraud on the portal.
- Under Risk Settings, 'Anonymous Proxy', click on the drop down arrow and select to allow the transactions.
Note: Please bear in mind that there are sometimes multiple reasons to why a credit card is not accepted so if the workaround steps above don't work for you, please advise the support team here at Respax so we can investigate further.