EFT DEVELOPERS' DOCUMENTATION
Please find below further information and documents of use to developers when integrating to the range of EFT solutions. You should also check the User Documents for additional user information and installation information on the EFT products.
INFORMATION ON DOWNLOADING / VIEWING INFORMATION
The majority of the documents are in adobe PDF format and can be viewed with the free Adobe Viewer program. If you do not have the viewer it can be downloaded from the adobe website at www.adobe.com. The majority of the documents will require adobe reader version 5 or above.
In order to save documents from most browsers right-click the icon against the document you want and choose 'Save target as' ('Save link as' in Firefox). Otherwise clicking on the document name or icon is most likely to open up the document within your browser (depending on your browser and configuration).
MAIN MANUALS AND INTEGRATION GUIDES / NOTES
INTEGRATION HINTS AND TIPS AND FURTHER INFORMATION RESOURCES
This section contains additional hints, tips, FAQs and information useful when integrating your software to our card processing solutions..
MAIN INTEGRATION TEST SCRIPTS
These are the main test scripts that are used to validate your interface to the credit and debit card solutions. You should use these tests to supplement your own testing processes. They are not full application tests but are general card oriented tests directed at standard card authorisation responses and general error conditions that can result. You should ensure that your system passes the relevant tests before formal integration testing takes place.
GENERAL CARD INFORMATION AND DOCUMENTS
This section contains documentation relating to debit and credit cards for use in applications. The LUHN formula is used for the calculation of the check digit on debit and credit card numbers - that is the last digit of the card number. This formula can be used to quickly validate a card number and will catch most keying errors by people keying in their card number. Note that this only determines that the card number adheres to the rules for creating card numbers - not that it is actually a valid issued card or number that you are able to take the card. The LRC check digit is a final check digit on the magnetic stripe of a card to ensure the magnetic card data is not corrupt. On swipe systems the card reader should be configured to pass this check digit through to the application and onto the eft-pos card processing application.
WEB APPLICATION DEVELOPMENT GUIDES AND SECURITY INFORMATION
Please find below documents specific to development of card processing solutions for the web. If you are developing for web and eCommerce facilities you should also refer to the PCI Data Security Standard.
TEST SYSTEMS ACCESS AND INFORMATION
This section contains additional documentation relating to access to development software and systems.
OTHER DOCUMENTS AND INFORMATION
This section contains additional documentation relating to the integration of applications and debit and credit card software and systems. When WinTI or BatchPro start-up they create the IINTable.txt file. This file describes all the various card ranges, card number lengths and required information such as start date and issue number. This file may be read by your program for pre-validation of card details.
