Please note that Helcim hybrid integration has reached end of life. The documentation remains only for current Helcim merchants who are using this platform.
Welcome to the Helcim POS Hybrid Integration
Our Point-of-Sale (POS) Hybrid terminals allow developers to quickly integrate their POS system with our EMV terminals. This developer section will provide you with the code samples and specifications to quickly deploy your own POS payment integration. Please ready our frequently asked questions below.
What is POS Integration?
Integration between a point-of-sale system and a payment processor typically implies that the POS can trigger new transactions automatically. Instead of the clerk starting a new sale on the credit/debit terminal and entering the amount, the clerk initializes the transaction using the POS system, and the customer is prompted on the terminal screen. The POS system is also typically able to track the individual transactions and batch totals, allowing for consolidated reporting at the end of each day.
EMV vs. Swipe Integration
Prior to the switch to EMV (Chip & PIN) cards, POS integrations were much easier to achieve with the use of a simple mag-stripe reader on the side of the POS to capture the credit card data. However with the arrival and EMV and PIN-based transactions, payment integrations have typically proven to be much more complicated and expensive for POS providers. Our Hybrid-Terminal SDK bridges that gap, allowing for very easy EMV integration with the point-of-sale.
What is a hybrid terminal?
A hybrid terminal is a traditional stand-alone terminal that can also accept incoming transaction requests from a point-of-Sale system. The POS system sends a transaction request (such as amount, clerk ID or invoice ID) to the terminal’s API. The terminal will automatically prompt the customer to insert their card and complete the transaction. Once approved, the terminal communicates back to the originating POS system with the approval notification and detailed transaction response.
What are the advantages over a traditional full-integration?
There are a number of drawbacks with a full hardware integration. First, there are considerable costs and lengthy timelines to certifying and maintaining your own PIN pads and terminal devices. Most importantly, by allowing the credit card data to flow through the point-of-Sale, the system falls within the scope of PCI compliance, which adds considerable complications for both the POS provider and their merchants.
How much does it cost to integrate?
Developers receive full access our SDKs and code samples. There are no integration or certification fees, you simply need to purchase a terminal for testing (please inform our customer service staff that you require a demo unit and not a regular one). Merchants also do not need to pay any additional fees for hybrid-integration. We offer the same low rates offered to our all our customers under our retail merchant pricing.
Do I need to do any certifications or additional courses?
There are no certifications needed. Since the full card data does not flow through the POS system, the system remains out-of-scope and does not need to be part of the PCI-DSS or PA-DSS compliance. In the cases where the transaction flows through your POS system (such as with the iCMP units), we use certified end-to-end (E2E) encryption, once again leaving the point-of-sale system out of scope.
App sends inputed data to the class Class parses the data into its correct output format Class then converts final output data into bytes Class uses TCP/IP and creates a socket with the given IP & port Class opens input and output streams then sends the bytes to the IP & port Terminal keeps a heartbeat with class Cardholder inputs necessary information for transaction Terminal connects to bank and returns Approved or Declined Receiving data gets sent to class in bytes Terminal then ends the connection Class converts the bytes and parses the data in its corresponding properties
|Ingenico iCT220||Available||Coming Soon|
|Ingenico iCT250||Available||Coming Soon|