A classic library integration for ECR refers to a situation where a Market Pay library is part of the ECR software. Over the years, we have noticed several disadvantages of such integrations. To overcome the disadvantages, we fully support nexo retailer protocol. Because of the advantages of Terminal API, we are deprecating the libraries.
Why are we depreciating libraries?
Aspect | Classic libraries | Terminal API |
|---|---|---|
Implementation | Requires setup and development work because the library is part of the ECR. | No dependency with ECR and does not require to embed anything in the ECR. |
Access to updates | Takes a longer time because it requires ECR updates and sometimes synchronous updates. | No dependency with ECR. |
New features and fixes | ECR run on different operating systems, each requiring a different library. This slows us down in development, testing, and maintenance. | Development of new features, testing, and maintenance are far more scalable for us. This means we can do more in less time. |
What does it mean for you?
Our libraries are still compatible with our payment application but we stopped maintenance and development of new features on it. If you implemented such library, you can keep using it but we do not plan any enhancement on it. Backward compatibility is maintained.
You can currently find supported libraries below:
.png)