The EPAS Client Library
Version history
See the Release notes
Glossary
| Term | Meaning |
|---|---|
| CHAOI | Cardholder and Operator Interface, see References |
| DCC | Dynamic Currency Conversion |
| ECR | Electronic Cash Register |
| EPAS | Electronic Protocol Application Software |
References
- EPASOrg: “Sale to POI Protocol Specifications”, v1.0, October 2010
- Swedbank / CEKAB: “Cardholder and Operator Interface”, v4.02, August 2009
- Swedbank bulletin: “Contactless”, v1.0 release 5
Background
The EPAS protocol is defines a large and complex protocol for the interaction of payment terminals and ECRs.
Westpay payment terminals implement a subset of this specification, but also some customisations and specialisations. This is because the world of payments and terminals has moved on substantially since 2010 and the documented protocol was not capable enough to do what was required.
The library
The combination of the complexity of EPAS and the Westpay customisations meant that integrating an ECR with a Westpay terminal was not a simple process, and there was an obvious need to have a client library that would make it much simpler to integrate an ECR with a Westpay payment terminal.
The EPAS Client Library is intended to greatly simply the task of ECR developers who are integrating their product with Westpay terminals.
The features of the EPAS Client Library are:
- Implemented as a .NET 4.7.2 module for easy integration.
- Provides a simple interface to operate the full range of supported transactions.
- Removes the need to know anything of the EPAS protocol.
- Removes the need to implement connectivity to the terminal.
Getting started
The first step is to integrate the library in your ECR application:
When that is done you are ready to start using the library to perform transactions with the terminal: