Local integrations
With a local integration we mean a traditional setup where you connect the Electronic Cash Register (ECR) or POS to the Payment terminal via a physical connection. This could be via cable like with ethernet, USB and Serial RS232, or wirelessly via WiFi and Bluetooth as long as the two can talk to each other without the need for external access.
|
- Support for offline mode
- Supports multiple communication interfaces *
- Often requires handling of multiple scenarios for; terminal connection, terminal login, payment transaction, etc.
*Available communication method is currently Ethernet.
Feature comparison
| Classic: | Only supports EPAS |
|---|---|
| Carbon: | Support both EPAS and Nexo |
| EPAS | Nexo | required | |
| Socket connection |  | | Y |
| Keep alive | | | N |
| Host logon | | | Y |
Admin functions | - | ||
| |  | |
| | | |
| Purchase | | | - |
| Refund | | | - |
| Cancellation | | | - |
| Pre-Auth | | | - |
| Cash advance | | | - |
| Reversed Acquiring | | | - |
| DCC | | | - |
What is EPAS?
EPAS (Electronic Protocols Application Software) is a non-commercial cooperation between 24 organizations within the payment industry. One of its goals is to ensure the interoperability of protocols at a European level between ECR applications and payment terminals.
The EPAS protocol is one method of controlling a payment terminal from an Electronic Cash Register (ECR). The messages sent from the ECR to the payment terminal is sent in XML over a TCP/IP socket.
The interface between the payment application and the ECR provides a range of functionality including:
- ECR login
- Starting a transaction
- Handling message display on the ECR
- Printing receipts on the ECR
- Performing administrative functions
In an EPAS integration all transactions is initiated by the operator of the ECR, performed by the payment terminal and completed by the Customer. Example:
- The ECR operator sells a product and presses the "pay with card" button.
- The ECR sends a signal to the payment terminal to perform a payment for X amount.
- The customer is clearly instructed on the terminal of what to do and all messages on the terminal is reported back from the payment terminal to the ECR.
- The customer confirms and completes the transaction
- The payment terminal gives the customers a on-screen result of the transaction and reports back the result to the ECR.
- The ECR receives the result along with payment info and then prepares and prints a payment receipt.
What is NEXO?
nexo standards enables fast, interoperable and borderless payments acceptance by standardising the exchange of payment acceptance data between merchants, acquirers, payment service providers and other payment stakeholders. nexo’s messaging protocols and specifications adhere to ISO20022 standards, are universally applicable and are freely available globally.
The nexo retailer protocol is one method of controlling a payment terminal from an Electronic Cash Register (ECR). The messages sent between the ECR and the payment terminal is in XML-format over a TCP/IP socket.
The interface between the payment application and the ECR provides a range of functionality including:
- ECR login
- Starting a transaction
- Handling message display on the ECR
- Printing receipts on the ECR
- Performing administrative functions
In an nexo integration all transactions is initiated by the operator of the ECR, performed by the payment terminal and completed by the Customer. Example:
- The ECR operator sells a product and presses the "pay with card" button.
- The ECR sends a signal to the payment terminal to perform a payment for X amount.
- The customer is clearly instructed on the terminal of what to do and all messages on the terminal is reported back from the payment terminal to the ECR.
- The customer confirms and completes the transaction
- The payment terminal gives the customers a on-screen result of the transaction and reports back the result to the ECR.
- The ECR receives the result along with payment info and then prepares and prints a payment receipt.