System requirements
The requirement is to generate and perform an https post request from any server running SSL, and to receive and handle the response. The requirements to use the ePay API are:
An Internet Merchant Account from any of the participating banks. Participating banks are: Commonwealth, Westpac, Challenge, ANZ, Bank of Melbourne, NAB, St George, Advance, BankSA, and Bankwest. The bank will charge a negotiated % transaction fee on each transaction, and may charge establishment and monthly service fees.
A web site hosted on virtually any web server with an Internet connection. ePay does not require the installation of its own software.
Secure Sockets Layer (SSL) on the web server to enable encryption of transactions from the user’s web browser to the hosting web server.
A shopping cart or other means for customers to select products and provide their credit card details on an order form. We recommend that order details are stored in a database on the merchant web site, although ePay does allow details of the order and customer to be posted with the transaction and recorded on the ePay backend system.
A command line tool or progam server client installed on your web server, to enable a program to establish an https connection from the client web server to the ePay server. Examples are cURL or MSXML. Most web servers already have this installed.
Programming to integrate the payment gateway into the web site. This can be done in almost any technology e.g. ASP, PHP, JSP, CL4, XML, SOAP. Multibase provides reasonable technical support for the integration, or we can perform the programming work as an additional service.
How it works
The merchant’s shopping cart or other application (supplied by the merchant) collects details of the order and the buyer.
Establish a secure SSL (https) connection from the merchant’s web server to the ePay server. This requires SSL on the merchant’s web site.
Transmit values for certain parameters , and wait for the results from the payment gateway.
The transaction is processed and the merchant’s system receives the result, records (e.g. to a database) and reports as required.
Transaction prices
Transactions are sold in blocks of 500. Transactions do not expire. We notify you when you need to purchase more. Prices do not include GST.
| Number of transactions |
Price - ex GST |
Each |
| 500 |
$175.00 |
35c |
| 1,000 |
$300.00 |
30c |
| 2,000 |
$560.00 |
28c |
| 3,000 |
$810.00 |
27c |
| 5,000 |
$1,250.00 |
25c |
| > 5,000 |
Substantial volume discounts available - please contact us for details |
What's included
Support and setup support:
- initial setup on the system
- comprehensive documentation
- establish and maintain Test and Live accounts
- assistance to establish bank merchant account
- extended technical briefing for your developer at Multibase, or by phone
- telephone and email support (including code checks but not programming)
Annual fee includes:
- Camtech Merchant Server software licence
- reasonable telephone and email support
- online manual payment and refund system
- comprehensive online transaction reporting
- ongoing ePay updates and system maintenance
Transaction records
All transactions are logged and we provide real-time reports online, with the ability to search, sort order, and generate a delimited file for download.
It is also possible to program directly to the API to query and retrieve transaction records, allowing for example an order reconciliation system to be built.
ePay does not store credit card numbers; they are passed directly through the payment gateway to the bank.
Integration into your web site
Setup of the merchant facility does not include integrating it into your web site or providing a shopping cart. Your web site or shopping cart needs to send information to the payment gateway. This can be done by your own web developer or by Multibase, in almost any programming langauge and database.