| | | rePay recurring payments | rePay is a hosted web service that can be integrated transparently into an existing web site. It is an extension of Multibase’s ePay online payments system, so an ePay API account and a bank Internet merchant approval is required to process your transactions. Your customer stays completely within your web site, using your own application and domain specific SSL. Your site needs the ability to collect details of the transactions required. Your own web site does not necessarily have to be highly complex. Any competent web programmer can integrate rePay into your system, or Multibase can do the work for you. The price for rePay includes documentation, telephone and email support. Each transaction counts as one ePay transaction - there are no additional fees up to 1,000 transactions per month. Generous volume pricing is available. How recurring payments are authorised
| Managing payment sequences and client details |
An merchant’s authorised administrator from the merchant can log in through a secure web page to the recurring payments database to input and manage recurring payments. |
| Programmatic access |
The system can be accessed programmatically, where an external application (such as a merchant’s web site) forwards details of the payments to be made. In this case, process the first transaction through ePay, and if it is successful, add the transaction sequence to the rePay database. |
| Bulk upload |
Original data can be uploaded in bulk, via an easily generated file. This might be useful where a CSV file can be generated simply from an existing application and the update of details is not frequent enough to warrant automation of this bulk process. |
| Flexible rules for recurrence |
The rules for payments are very flexible. Each sequence has a start and an end date, and rules about frequency. Almost any combination of rules can be applied - daily, weekly, monthly, annually. |
| Delivering a response to the merchant application |
As well as receiving input from your merchant application or web pages, the result of the transaction can be received from rePay so that your system can update its own database. This could be used, for example, to provide continuing access to an online subscription system. |
How rePay transactions are processed and reported
| Daily processing |
Each night, the recurring payments application runs, inspecting the database to determine whether there are any payments due that day. Payments due will be submitted to the payment gateway and successful payments will be credited to the merchant’s bank account. |
| Transactions recorded |
All transactions are recorded in the database. Failures are flagged, without affecting subsequent payments due. A merchant can log in to the system to obtain a report of transactions that need your attention due to failures e.g. the response might be to contact the customer, edit credit card details, cancel the sequence etc. |
| Accessing transaction history |
Transaction history is accessible through the existing ePay system. Merchants can view reports of successful and failed recurring transactions on the new system, with failed transactions flagged for merchant action. |
Security of recurring payments
| Login and password |
Access to the Merchant Administration Centre requires a login and password. This can be changed on a predetermined schedule if required. |
| Secure storage |
The rePay database is not available on the Internet, meeting the requirement not to store credit card numbers on the web. Details are stored in encrypted form and are not accessible by any one indivudal. |
| Secured transactions |
While being transmitted over the Internet, transactions are secured with 128 bit SSL. Cryptographers consider 128 bit encryption impossible to break, since it would take millions of years with the fastest computers to try all the possible combinations. |
| Updating details |
It is not possible to view credit card numbers stored in ePay. It is however possible to retrieve a payment sequence and to change credit card number, expiry date, amount, or payment sequence details. |
| Audit details |
Certain details cannot be changed, for security and audit reasons. A payment sequence can instead be disabled and a new one entered. |
|
| - The customer completes a web form on the merchant’s web site, which includes authorisation for the recurring charge.
- rePay processes the first payment. If it is successful, the payment sequence will be reported to the secure, off-line rePay system.
- When the next payment is due, the system will process the next payment. Failures are reported to the merchant.
- The customer completes a web form on the merchant’s web site, which includes authorisation for the recurring charge.
- rePay processes the first payment. If it is successful, the payment sequence will be reported to the secure, off-line rePay system.
- When the next payment is due, the system will process the next payment. Failures are reported to the merchant.
| | |
|
|