|
Integration
The eMatters integration process can take as little as 30 minutes, depending upon your requirements. We currently have many different methods of integration. You are sure to find one that fits perfectly.
As soon as you apply for an eMatters Account, even before speaking with the bank, you can start integration and testing. You will be selling in less time because of this.
As soon as the bank issues your Merchant and Terminal Numbers, you account will usually be activated with hours. Nobody does it faster.
Ways to Connect to eMatters
POSTed Online
If you have your own SSL Certificate, and you adhere to the Visa AIS and Mastercard SDP programs, you can collect credit cards and POST them to us - server to server. Your customer is never redirected to our site, they never know of the existence of eMatters, and everything is done is record time. No DLLs, APIs, Java Servers or Registry Entries to be made. All you need is an SSL Certificate and an Internet connection. This will work on ANY SERVER, ANY SOFTWARE, ANY LOCATION. NO LIMITS !!!!!! And to make your job even easier, we can accept the POST in either standard HTTPS FORM POST or XML.
Go to the Download page for everything you need.
HOSTed Online
Our HOSTed Online Solution is perfect for a business without their own SSL Certificate, or those wishing not to collect card numbers.
Sample URL is shown below, which uses our testing page. Use this page for all testing, using these two card numbers:-
4557 0130 0031 4262 = Approved
4557 0130 0031 6242 = Declined
The explanation of the values are shown here:-
https://merchant.ematters.com.au/cmaonline.nsf/abasictemplate?OpenForm = the allocated payment page, provided at system application time.
&1.99 = the price in dollars and cents
&20030036 = the Reference number, vitally important for 3D Secure
&John+Doe = the Customer's name
&info@eMatters.com.au = the Customer's eMail Address
&http://www.yourserver.com/response.asp? = the URL we return to after processing
&13 = the Header number
&02 = the Category number, linked with our Merchant Desk Invoice Category List
Upon completion of the transaction, we redirect the customer back to yourserver.com (ie, your shopping cart, etc) with a Single Use Response Code (SURC). This SURC is unique for every merchant, for every transaction, for every amount. It ensures that the URL cannot be tampered with during the redirection. And, to increase security, the algorithm changes for every merchant at the time of signup - so no two merchants will have the same algorithm. The decoding algorithm can be downloaded from our Merchant Desk when your eMatters Application has been approved.
Virtual Terminal
The Virtual Terminal offers payment and refund modules to allow your back off staff to process manual transactions. Simple and quick, it handles Multiple Merchants for use in conference companies and call centres. In one case, it enabled a company with 60 locations to consolidate the reporting, while handing back 59 EFTPOS machines to the bank, cancelling 59 Telstra line rentals and saving over $40,000 each year. And, as a benefit, the head office can see instantly what each branch has processed, they can control all refunds and reporting and they can monitor the system for "unusual activity" (ie, high fraud rate, etc).
Go to the Download page for information on the Virtual Terminal.
HOSTED Offline
eMatters HOSTed Offline is a simple CSV file that is uploaded to our payment server, processed and returned to you as soon as it is completed. This is suitable for monthly payments from repeat billing companies.
Shopping Carts
Some of the Shopping Carts that allow seamless integration with eMatters are Trellian, Dansie, Bizar and BUG Mall. We offer an Authorize.net File Format Convertor, allowing many carts built for Authorize.net for function with eMatters. Contact us for full details.
Verified by Visa
In April 2003, eMatters processed the first live VbV Transaction in Australia with StGeorge Bank. eMatters operates MPIware.com as a stand-alone VbV Authentication service, allowing global merchants to obtain verification, then process the card as normal. MPIware.com integrates with eMatters, MerchantPartners.com, Authorize.net, 2Checkout.com and many others. It is available as an option with your eMatters account, and more information can be obtained by contact our office.
BillSmartTM
If you want your customers' transactions to be billed again in the future without their involvement, then BillSmart is the option to use. BillSmart securely stores the credit card data waiting for you to send another request to our system. Your request includes your Merchant ID and Password, the Customer Number, Invoice Number and Transaction Amount. BillSmart then re-assembles the transaction, delivers it to your bank and provides a response back to you - all within 5 seconds. More information can be found at the BillSmart Website or Refer to the Integration Manual.
OnBillTM
OnBill allows you to create and manage a recurring billing system for your customers. Suppose you are an ISP, wanting to bill your customers $24.95 each month. When you take their first payment, simply add a couple of flags to the form and we will take over. If the original transaction is approved, we will create an encrypted transaction, with a flag specifying when to next process. On the given day, we will process and send you a receipt. If it is OK, then we will keep processing, every month (or fortnight, or year etc) until you stop the transaction.
Refer to the Integration Manual on the Download page for details about OnBill.
SMS Gateway
As an added layer of security, eMatters can integrate your payments to our SMS Gateway. Now your customers can be sent a Unique PIN Code via SMS, which they must key back into your website. You can then use this as a sign that they received the message and have authorised the transaction. It replace our SURC (see above, in the HTTP Post). We charge just 15c per SMS, which is added to your monthly account. You need to speak with an Integration Consultant to configure this option.
Our Response Codes
The most commonly used response codes are listed here. Many you will NEVER see, and some that are not listed here will sometimes find their way to you. In summary, 08 is approved, everything else is declined.
All two digit codes are issued by the bank. All three digit codes are issued by eMatters.
The "Possible Explanation" is our definition and may not include all the possible reasons for the codes. Each bank supplies slightly different response codes for each situation, so our explanation may not be the actual reason for a particular response. |
Code | Response Text | Possible Explanation |
01 | See card issuer. |  |
04 | Call authorisation centre. | Card has been reported Lost, Stolen or Blocked. |
08 | Transaction approved. | Transaction has been approved and will be settled the following business day. |
12 | Invalid transaction type. | (i) Amex was processed but Merchant does not accept Amex, (ii) Card is not allowed to be used over the Internet (iii) Wrong CCV |
31 | See card issuer. |  |
33 | Card Expired | Expiry date may be valid (ie expires in 2 years time) but it is incorrect. |
39 | No CREDIT account. |  |
51 | Insufficient funds. | The cardholder’s card has not enough funds to complete the transaction. |
61 | Over card refund limit. | Applies to REFUNDS. Each Merchant can only refund up to a pre-set limit each day, returing this code once that limit is exceeded. |
91 | Issuer not available. | The cardholder’s bank is currently offline. Try later. |
96 | CVV invalid or missing |  |
707 | 3SO Activated – too many failed attempts | After three declined transactions, the UID is blocked for 24 hours. This reduces fraudulent transactions from reaching the Merchant’s bank account. |
708 | Non-Unique UID – Already accepted | Once we have approved a UID, it is then blocked for 24 hours – stopping duplicate transactions. |
710 | IGP Activated – transaction from high risk country | We block certain high risk countries based on our knowledge of global regions and fraud. |
711 | IGP Activated – IP Address Not Valid | The IP Address presented by your client is invalid, indicating that the transaction may be fraudulent. |
712 | Fraud Screen block – IP and Bank not matching. | The country of origin of the IP Address does not match the country of origin of the Credit Card. |
714 | Card from outside acceptable country range | The Merchant’s account is limited to only accept AU, NZ or AU&NZ cards. Cards from other countries are rejected. |
810 | Invalid Purchase Amount | The amount entered by the purchaser is incorrect. It must always be greater than $0 and less than $99,999 |
812 | Unacceptable Card Number | The card number provided by the purchaser fails our most basic tests. |
813 | Invalid Expiry Date Format | The expiry dates provided by the purchaser fails our most basic tests. |
816 | Card Expired | The expiry dates provided by the purchaser has already expired. |
901 | H-Check Failed – URLs do not match | Our HTTP Callback check determined that the transaction was fraudulent. |
902 | Readers set to an incorrect value in POSTed Transaction | The eMatters Login Code (eg MEL0029) does not exist. |
903 | Readers missing in POSTed transaction | The eMatters Login Code was not sent from the Merchant’s website. |
904 | MerchantID missing in POSTed transaction | The eMatters MerchantID (eg 29) was not sent from the Merchant’s website. |
910 | Transaction Aborted | The basic payment information received is completely wrong. |
911 | XML Error. | The formation of the XML sent to our server is incorrect. |
980 | Host Not Found, Bank System out of action | We did not receive a response from our bank within 30 seconds. |
990 | Carrier Lost, Bank line down | We did not receive a response from our bank within 30 seconds. |
|
|