For more information contact us on:
T: 0118 948 2588
E: enquiries@ackltd.co.uk
----------------------------------------
More support information.....
Chip & Pin - Questions and answers >More
Networking - Key to effective EFT, good data communication architecture >More
10 Steps to EFT integration >More
PCI DSS - FAQ, Background, Glossary >More
IP Connectivity and EFT >More
10 Steps to integration with ACKTerm
- Initial discussion
- First look testing
- ACK product testing
- ACK Basic EFT functionality testing
- Detailed bank testing
- Integrator provides ACKTERM configuration details to ACK
- ACK provides TIDs
- Merchant application form sent to acquirer
- Integrator connectivity testing to live host
- Onsite installation by the integrator
Step 1 - Initial discussion
An EPoS provider contacts ACK requesting an EFT solution.
ACK supply evalution software and documentation of how to incorporate ACKTERM into the EPoS system.
A member of the Intergator’s development team modifies the EPoS system to allow card payments through ACKTERM.
Step 2 - First look testing
The developer visits ACK with both the target hardware and the software.
ACK will setup a test account to the acquirer and prove that the system can dial out and get bank authorisation.
ACK will run through 20 tests. If the system fails any of these tests, the developer will need to modify the EPoS software until these tests are passed.
Step 3 – ACK product training
Arrangements should be made for the developer and one of the installation staff to have detailed product training on the ACK EFT software. This can either be provided at the same time as the first look testing or as a separate session.
When the developer returns to his office, he will need to have all the target hardware and software, that is proposed to be installed at the customers site.
The developer will need to be competent at installing and configuring the system prior to it being installed at the retailers site. This includes making the connection to the acquiring bank and getting online authorisations. If the target configuration is to be multiple tills communicating over the network to an ACK socket server, this configuration will need to be replicated in the developers office.
Step 4 - ACK Basic EFT functionality testing
If any updates are made to the EPoS software, the developer will e-mail these to ACK.
ACK will run through a Basic EFT functionality test script and confirm that the EpoS system is suitable to commence full bank testing.
If any problems are found, ACK will document these on an Issues List, which is then distributed to all relevant parties. As the problems are worked on and resolved, the developer e-mails updates to ACK, which ACK test and then update and re-distribute the issues list.
Step 5 – Detailed bank testing
ACK will liase with the banks and complete the required testing as detailed in the original request, including Mastercard Card ETEC, Visa ADVTK and the acquirers own tests.
As detailed bank testing can be extensive and very time consuming, ACKTERM online authorisation has already been accredited with Streamline, Barclays, Euroconex, HSBC, Lloyds, American Express and Diners Club.
Step 6 - Integrator supplies configuration details
Before a Merchant is allowed to go live with a Chip and PIN solution, the aquiring bank need to be happy that the each element of the system has been tested and certified. Eg: PIN Pad, method of operation, online connectivity and settlement file delivery,
ACK will supply a blank ACKTERM Implementation Planner spreadsheet, which needs to be completed for each merchant deploying a Chip and PIN solution and then returned to ACK.
Step 7 - ACK provides Terminal IDs (TIDs)
ACK will allocate a Terminal ID (TID) to each unit and update the Implementation Planner spreadsheet.
Step 8 - Merchant Application form sent to acquirer
Once the Implementation Planner spreadsheet is complete, ACK will use this as a basis to generate the appropriate Merchant Application form for the acquirer.
Once the Merchant Application form has been lodged with the acquirer, the store should be able to go live within 5 to 10 working days.
Step 9 - Integrator connectivity testing to live host
Once the Merchant Application form has been accepted, the acquirer will provide details of the live keys and Terminal Action Codes for the PIN pad..
ACK will prepare a default ‘Live’ configuration file ACKLTD.XML, for the developer to test with, using real cards.
It is important that the testing of live hardware and software (including socket server) is completed before going onsite to the retailer.
Step 10 - Onsite installation by the integrator
The installation of the EFT system is the responsibility of the integrator. If all the above steps have been carried out, the installation should run smoothly and attendance by ACK will not be required.
The only element not covered will have been to test the retailers telephone line.
It is known that Carrier Pre-Selection or Least Cost Routing on the line can severly disrupt on-line authorisation so that only 1 in 2 or 1 in 3 are succesful. This needs to be discussed with the retailer prior to onsite installation.