---
title: "Deprecation of classic libraries"
description: "Why and when you will not be able to use POS libraries anymore."
url: "https://docs.adyen.com/point-of-sale/classic-library-deprecation"
source_url: "https://docs.adyen.com/point-of-sale/classic-library-deprecation.md"
canonical: "https://docs.adyen.com/point-of-sale/classic-library-deprecation"
last_modified: "2021-03-25T11:21:00+01:00"
language: "en"
---

# Deprecation of classic libraries

Why and when you will not be able to use POS libraries anymore.

[View source](/point-of-sale/classic-library-deprecation.md)

A *classic library* integration for point of sale refers to a situation where an Adyen library is part of the cash register software. Over the years, we have noticed several disadvantages of such integrations. To overcome the disadvantages, we developed:

* Adyen Terminal API as a replacement for the libraries.
* New payment terminal software that interfaces with Terminal API.\
  This new software is only available on terminals that have PCI approval.

Because of the advantages of Terminal API, we are deprecating the libraries. This means you need to migrate to a different type of integration. If you are currently using eVo terminals, you also need to update your terminal fleet because the [PCI approval of eVo terminals is expiring](#may-need-new-terminals).

## Why you should switch to Terminal API

Soon (see the [time line](#time-line)), we will completely stop supporting classic libraries. You will no longer be able to make transactions through a classic library.

If you are currently using a classic library, you need to switch to Terminal API. Ultimately you will benefit from this switch because Terminal API has important advantages over classic libraries:

| Aspect                 | Classic libraries                                                                                                                                                                                             | Terminal API                                                                                                                           |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Implementation         | Requires a lot of setup and development work because the library needs to be part of the cash register software.                                                                                              | Easy to implement and update because it has a request/response JSON messaging format instead of custom libraries, callbacks, and SDKs. |
| Access to updates      | Takes a long time because the cash register software is updated infrequently - in many cases only once a year.                                                                                                | Quick and easy; not dependent on libraries.                                                                                            |
| Support                | Takes longer because not every [Support Team](https://ca-test.adyen.com/ca/ca/contactUs/support.shtml?form=other) member or Adyen implementation manager knows all the ins and out of every integration type. | Better support, independent of the cash register software.                                                                             |
| New features and fixes | Cash registers run on different operating systems, each requiring a different library. This slows us down in development, testing, and maintenance. Libraries are currently in maintenance mode.              | Development of new features, testing, and maintenance are far more scalable for us. This means we can do more in less time.            |

Some examples of new features that are supported with Terminal API but not with libraries:

* [Pay at table](/point-of-sale/pay-at-x)
* [Tipping](/point-of-sale/tipping)
* [Card acquisition](/point-of-sale/card-acquisition)
* [Shopper input](/point-of-sale/shopper-engagement/shopper-input)
* [Shopper recognition and tokenization](/point-of-sale/shopper-recognition)
* Payment methods: Cartes Bancaires, girocard

If your current integration uses the Xstore POS system with the Java Native Interface (JNI) library, we offer OPI instead of Terminal API. OPI uses an XML request/response messaging format and has the same advantages as Terminal API.

## Why you may need new payment terminals

If you are currently using payment terminals from the **Verifone Verix** range — known as **eVo** terminals — you need to update your terminal fleet. In a few years, we will no longer allow transactions with eVo terminals because:

* The PCI security approval of eVo terminals is expiring.

  Most eVo terminals have **PTS PCI 3** approval: they are compliant with version 3 of the PIN Transaction Security (PTS) requirements of the Payment Card Industry (PCI) Security Standards Council. The Council has determined that PTS PCI 3 expires on 30 April 2021 and that PTS PCI 3 devices must be retired by April 2023.\
  Some eVo terminals have **PTS PCI 4** approval, which expires in April 2023.

* Verifone will stop delivering, supporting, and repairing eVo terminals.

To remain PCI compliant, you need to switch from eVo terminals to the **Verifone Engage** range — known as **VOS** terminals. VOS terminals have PTS PCI 5 approval and offer excellent alternatives to eVo:

| Type       | eVo Verix terminals | VOS Engage terminals                               |
| ---------- | ------------------- | -------------------------------------------------- |
| Countertop | VX820, VX820 Duet   | VOS: P400 Plus or V400c Plus                       |
| Mobile     | e315, e355          | VOS: e285p or e285p Android: AMS1 or S1E2L         |
| Multimedia | MX925               | VOS: M400                                          |
| Portable   | VX675, VX680, VX690 | VOS: V400m, or V240m Plus for Brazil Android: S1F2 |

## Time line for the deprecation

**Libraries** - Affects entire Verifone eVo range of terminals

* January 1, 2022: no new library integrations allowed.
* 2022: POS partners must be ready for migration. They must have a Terminal API integration available, and are not allowed to onboard new merchants on a library.
* March 29, 2024: end of support and maintenance. If you need to process transactions using classic libraries past this date, contact your Adyen Account Manager.

**PCI 4 eVo terminals** - e355 and VX690

* March 31, 2021: no new orders possible, repairs only.
* March 31, 2023: end of repair service.
* April 2023: PTS PCI 4 expires.
* March 29, 2024: end of support, transactions no longer allowed.

**PCI 3 eVo terminals** - e315, MX925, VX675, VX680, VX820, and VX820 Duet

* January 1, 2020: no new orders possible, repairs only.
* April 30, 2021: PCI 3 expires.
* March 31, 2023: end of repair service.
* March 29, 2024: end of support, transactions no longer allowed.

![](/user/pages/docs/03.point-of-sale/68.classic-library-deprecation/2024_03_18-UpdatedDeprecationTimeline.jpg)

## See also

* [Choose a terminal](/point-of-sale/what-we-support/select-your-terminals)
* [Terminal API](/point-of-sale/design-your-integration/terminal-api)
