|
|
|
|
|
|
Payment Services...effortless processing power |
| Pay & Go offers a wide range of payment services and Application Programming Interfaces (API's) which can be customised to suit any standard or complex requirements. |
|
|
Interactive Voice Response |
Pay & Go offers a range of hosted or stand-alone telephony solutions, from our bureau Interactive
Voice Response (IVR) service to fully scalable in-house 'Call Processing' software and hardware
solutions.
|
|
- Your customers can pay your bills from any telephone.
- Basic information only services also available.
- Outbound voice or SMS services can automatically call your customers to provide them with information or a payment reminder.
- All calls can be switched to a live operator if required.
- We can arrage 1300, 1800 or 1900 services for you.
|
|
WEB Payment Interface |
The Pay & Go web interface is designed to be integrated into a web application, where
the payment relates to a sale of goods or services. By implementing this service, the merchant's PCI
compliance requirements are significantly reduced, as the merchant or the merchant's web application
never sees the full credit card details. The complete transaction process (from collection of credit
card details to the retrieval of transaction result) is done securely within the CAS payment gateway.
Only the obscured transaction results and reference number are returned to the merchant's system.
|
|
When the customer reaches the payment phase of the merchant's web site,
the customer's browser is re-directed to the Pay & Go web interface. The customer then enters their
credit card details, or they can select an account from the secure Customer Information Vault. The
Pay & Go WEB interface then submits the details to the bank and retrieves the result.
|
|
Payment APIs |
A number of Payment APIs are available to suit different applications. They are easy to install, highly secure
and enable real time credit card transaction from any web site, IVR or custom built application.
|
 |
Customers who purchase goods via any of the APIs are protected by SSL encryption, giving
peace of mind that their credit card details are totally secure.
The various APIs support a range of payment notification options. Merchant's systems or staff can be notified
immediately whenever a successful transaction occurs. Notification methods include E-mail, Short Message Service (SMS), and ODBC Database update
Note: Since the merchant's application has access to the full credit card details, whenever any of these APIs
are implemented, the merchant is totally responsible for their own PCI Compliance. This means that the merchant's
infrastructure must be configured in a certain way, and specific procedores must be implemented.
|
|
Recurring Payments |
The Recurring Billing Service is a secure hosted service designed to handle any client's recurring
billing needs. They can set up the payment options, and focus on more important duties.
|
|
The card-holder's details are encrypted and secured in the Customer Information Vault.
The Recurring Billing Service automatically processes the transactions when they are due.
The Recurring Billing Service incorporates both Direct Debit and Credit Card payment services. The merchant interface
enables authorised staff to configure each of their customer's account, to set up the processing via credit card or
direct debit. Recurring transactions are usually based on a regular contract or leasing plan. however, this service
also allows for the processing of ad-hoc transactions or for the transaction amount to vary.
|
|
Batch Processing |
The Batch Processing system is a simple and secure managed data transfer service that enables bulk Card transaction details to be uploaded to the gateway for processing, via secure FTP, or via HTTPS web upload.
|
 |
The complete transaction process (from collection of credit card details to the retrieval
of transaction result) is done by the merchant's system as each transaction is completed, and stored in a file that is
transferred at a determined time. Remittance files can be processed as soon as they are uploaded, or at a particular
time of day.
When a remittance file is processed, unsuccessful transactions are logged in an exemption report, which is emailed to the
merchant after the remittance processing is finished. The exception report details all declined transactions as well as the
reason why the bank rejected the transaction.
Note: Since the merchant's application has access to the full credit card details, whenever
any of these APIs are implemented, the merchant is totally responsible for their own PCI Compliance. This means that the
merchant's infrastructure mut be configured in a certain way, and specific procedures must be implemented.
|
|
Direct Debit |
The Direct Debit Service is a secure hosted service designed to handle any merchant's direct debit billing needs.
The customer's details are encrypted and secured in the Customer Information Vault, and the Direct Debit Service
automatically processes the transaction each day.
|
|
The merchant interface enables authorised staff to configure the payment frequency
and amount, so that payments are processed at correct times.
Merchants should note that the Direct Debit service requires the merchant to secure authorisation from their
customer before a debit transaction can be processed. Whenever a direct debit transaction file is sent to the
Merchant's bank, it typically takes 2-3 days before the transaction is assumed to be completed. The receiving
bank could reverse any transaction if the customer's account has insufficient funds, and therefore there is
sometimes a delay with the confirmation of receipt.
|
|
Virtual Terminal |
Virtual Terminal is designed as a replacement for traditional, hardware based EFT terminals. Most
hardware terminals are provided by a particular bank, and can only be used with that bank. They also communicate
via dedicated phone lines, which are often slow, costly or unreliable.
|
 |
Virtual Terminal communicates via a standard Internet connection from any computer terminal. It requires no specialised hardware or software on the user's PC, and it may be linked to any bank - ie the banking arrangement may be changed at any time with no change to the technology. Your systems administrators store in a 'cookie' on the user's browser, and configure the merchant information, cards accepted and the minimum and maximum payments amounts.
The operator clicks on the icon to enter the payment information into Virtual Terminal, which encrypts the transaction details and submits them via a secure SSL connection. A receipt number is returned to the user interface so that the operator and/or customer can record the transaction and receipt number.
|
|
|
|
|
|
