{"title":"Deprecation of classic libraries","category":"default","creationDate":1616667540,"content":"<p>A <em>classic library<\/em> 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:<\/p>\n<ul>\n<li>Adyen Terminal API as a replacement for the libraries.<\/li>\n<li>New payment terminal software that interfaces with Terminal API.<br \/>\nThis new software is only available on terminals that have PCI approval.<\/li>\n<\/ul>\n<p>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 <a href=\"#may-need-new-terminals\">PCI approval of eVo terminals is expiring<\/a>.<\/p>\n<h2 id=\"switch-to-terminal-api\">Why you should switch to Terminal API<\/h2>\n<p>Soon (see the <a href=\"#time-line\">time line<\/a>), we will completely stop supporting classic libraries. You will no longer be able to make transactions through a classic library.<\/p>\n<p>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:<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Aspect<\/th>\n<th style=\"text-align: left;\">Classic libraries<\/th>\n<th style=\"text-align: left;\">Terminal API<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Implementation<\/td>\n<td style=\"text-align: left;\">Requires a lot of setup and development work because the library needs to be part of the cash register software.<\/td>\n<td style=\"text-align: left;\">Easy to implement and update because it has a request\/response JSON messaging format instead of custom libraries, callbacks, and SDKs.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Access to updates<\/td>\n<td style=\"text-align: left;\">Takes a long time because the cash register software is updated infrequently - in many cases only once a year.<\/td>\n<td style=\"text-align: left;\">Quick and easy; not dependent on libraries.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Support<\/td>\n<td style=\"text-align: left;\">Takes longer because not every <a href=\"https:\/\/ca-test.adyen.com\/ca\/ca\/contactUs\/support.shtml?form=other\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Support Team<\/a> member or Adyen implementation manager knows all the ins and out of every integration type.<\/td>\n<td style=\"text-align: left;\">Better support, independent of the cash register software.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">New features and fixes<\/td>\n<td style=\"text-align: left;\">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.<\/td>\n<td style=\"text-align: left;\">Development of new features, testing, and maintenance are far more scalable for us. This means we can do more in less time.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Some examples of new features that are supported with Terminal API but not with libraries:<\/p>\n<ul>\n<li><a href=\"\/pt\/point-of-sale\/pay-at-x\">Pay at table<\/a><\/li>\n<li><a href=\"\/pt\/point-of-sale\/tipping\">Tipping<\/a><\/li>\n<li><a href=\"\/pt\/point-of-sale\/card-acquisition\">Card acquisition<\/a><\/li>\n<li><a href=\"\/pt\/point-of-sale\/shopper-engagement\/shopper-input\">Shopper input<\/a><\/li>\n<li><a href=\"\/pt\/point-of-sale\/shopper-recognition\">Shopper recognition and tokenization<\/a><\/li>\n<li>Payment methods: Cartes Bancaires, girocard<\/li>\n<\/ul>\n<p>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.<\/p>\n<h2 id=\"may-need-new-terminals\">Why you may need new payment terminals<\/h2>\n<p>If you are currently using payment terminals from the <strong>Verifone Verix<\/strong> range &mdash; known as <strong>eVo<\/strong> terminals &mdash; you need to update your terminal fleet. In a few years, we will no longer allow transactions with eVo terminals because:<\/p>\n<ul>\n<li>\n<p>The PCI security approval of eVo terminals is expiring. <br><\/p>\n<p>Most eVo terminals have <span translate=\"no\"><strong>PTS PCI 3<\/strong><\/span> 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.<br \/>\nSome eVo terminals have <span translate=\"no\"><strong>PTS PCI 4<\/strong><\/span> approval, which expires in April 2023.<\/p>\n<\/li>\n<li>\n<p>Verifone will stop delivering, supporting, and repairing eVo terminals.<\/p>\n<\/li>\n<\/ul>\n<p>To remain PCI compliant, you need to switch from eVo terminals to the <strong>Verifone Engage<\/strong> range &mdash; known as <strong>VOS<\/strong> terminals. VOS terminals have PTS PCI 5 approval and offer excellent alternatives to eVo:<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Type<\/th>\n<th style=\"text-align: left;\">eVo Verix terminals<\/th>\n<th style=\"text-align: left;\">VOS Engage terminals<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Countertop<\/td>\n<td style=\"text-align: left;\">VX820, VX820 Duet<\/td>\n<td style=\"text-align: left;\">VOS: P400 Plus or V400c Plus<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Mobile<\/td>\n<td style=\"text-align: left;\">e315, e355<\/td>\n<td style=\"text-align: left;\">VOS: e285p or e285p <br> Android: AMS1 or S1E2L<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Multimedia<\/td>\n<td style=\"text-align: left;\">MX925<\/td>\n<td style=\"text-align: left;\">VOS: M400<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Portable<\/td>\n<td style=\"text-align: left;\">VX675, VX680, VX690<\/td>\n<td style=\"text-align: left;\">VOS: V400m, or V240m Plus for Brazil <br> Android: S1F2<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"time-line\">Time line for the deprecation<\/h2>\n<p><strong>Libraries<\/strong> - Affects entire Verifone eVo range of terminals<\/p>\n<ul>\n<li>January 1, 2022: no new library integrations allowed.<\/li>\n<li>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.<\/li>\n<li>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.<\/li>\n<\/ul>\n<p><strong>PCI 4 eVo terminals<\/strong> - e355 and VX690<\/p>\n<ul>\n<li>March 31, 2021: no new orders possible, repairs only.<\/li>\n<li>March 31, 2023: end of repair service.<\/li>\n<li>April 2023: PTS PCI 4 expires.<\/li>\n<li>March 29, 2024: end of support, transactions no longer allowed.<\/li>\n<\/ul>\n<p><strong>PCI 3 eVo terminals<\/strong> - e315, MX925, VX675, VX680, VX820, and VX820 Duet<\/p>\n<ul>\n<li>January 1, 2020: no new orders possible, repairs only.<\/li>\n<li>April 30, 2021: PCI 3 expires.<\/li>\n<li>March 31, 2023: end of repair service.<\/li>\n<li>March 29, 2024: end of support, transactions no longer allowed.<\/li>\n<\/ul>\n<div class=\"hint--right\" data-hint=\"Deprecation time line for libraries and eVo terminals\">\n<p><img alt=\"\" src=\"\/user\/pages\/docs\/03.point-of-sale\/68.classic-library-deprecation\/2024_03_18-UpdatedDeprecationTimeline.jpg\" \/><\/p>\n<\/div>\n<h2>See also<\/h2>\n<div class=\"see-also-links output-inline\" id=\"see-also\">\n<ul><li><a href=\"\/point-of-sale\/what-we-support\/select-your-terminals\"\n                        target=\"_self\"\n                        >\n                    Choose a terminal\n                <\/a><\/li><li><a href=\"\/point-of-sale\/design-your-integration\/terminal-api\"\n                        target=\"_self\"\n                        >\n                    Terminal API\n                <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/point-of-sale\/classic-library-deprecation","articleFields":{"description":"Why and when you will not be able to use POS libraries anymore.","feedback_component":true,"last_edit_on":"25-03-2021 11:21"},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/point-of-sale\/classic-library-deprecation","title":"Deprecation of classic libraries","content":"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:\n\nAdyen Terminal API as a replacement for the libraries.\nNew payment terminal software that interfaces with Terminal API.\nThis new software is only available on terminals that have PCI approval.\n\nBecause 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.\nWhy you should switch to Terminal API\nSoon (see the time line), we will completely stop supporting classic libraries. You will no longer be able to make transactions through a classic library.\nIf 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:\n\n\n\nAspect\nClassic libraries\nTerminal API\n\n\n\n\nImplementation\nRequires a lot of setup and development work because the library needs to be part of the cash register software.\nEasy to implement and update because it has a request\/response JSON messaging format instead of custom libraries, callbacks, and SDKs.\n\n\nAccess to updates\nTakes a long time because the cash register software is updated infrequently - in many cases only once a year.\nQuick and easy; not dependent on libraries.\n\n\nSupport\nTakes longer because not every Support Team member or Adyen implementation manager knows all the ins and out of every integration type.\nBetter support, independent of the cash register software.\n\n\nNew features and fixes\nCash 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.\nDevelopment of new features, testing, and maintenance are far more scalable for us. This means we can do more in less time.\n\n\n\nSome examples of new features that are supported with Terminal API but not with libraries:\n\nPay at table\nTipping\nCard acquisition\nShopper input\nShopper recognition and tokenization\nPayment methods: Cartes Bancaires, girocard\n\nIf 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.\nWhy you may need new payment terminals\nIf you are currently using payment terminals from the Verifone Verix range &mdash; known as eVo terminals &mdash; you need to update your terminal fleet. In a few years, we will no longer allow transactions with eVo terminals because:\n\n\nThe PCI security approval of eVo terminals is expiring. \nMost 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.\nSome eVo terminals have PTS PCI 4 approval, which expires in April 2023.\n\n\nVerifone will stop delivering, supporting, and repairing eVo terminals.\n\n\nTo remain PCI compliant, you need to switch from eVo terminals to the Verifone Engage range &mdash; known as VOS terminals. VOS terminals have PTS PCI 5 approval and offer excellent alternatives to eVo:\n\n\n\nType\neVo Verix terminals\nVOS Engage terminals\n\n\n\n\nCountertop\nVX820, VX820 Duet\nVOS: P400 Plus or V400c Plus\n\n\nMobile\ne315, e355\nVOS: e285p or e285p  Android: AMS1 or S1E2L\n\n\nMultimedia\nMX925\nVOS: M400\n\n\nPortable\nVX675, VX680, VX690\nVOS: V400m, or V240m Plus for Brazil  Android: S1F2\n\n\n\nTime line for the deprecation\nLibraries - Affects entire Verifone eVo range of terminals\n\nJanuary 1, 2022: no new library integrations allowed.\n2022: 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.\nMarch 29, 2024: end of support and maintenance. If you need to process transactions using classic libraries past this date, contact your Adyen Account Manager.\n\nPCI 4 eVo terminals - e355 and VX690\n\nMarch 31, 2021: no new orders possible, repairs only.\nMarch 31, 2023: end of repair service.\nApril 2023: PTS PCI 4 expires.\nMarch 29, 2024: end of support, transactions no longer allowed.\n\nPCI 3 eVo terminals - e315, MX925, VX675, VX680, VX820, and VX820 Duet\n\nJanuary 1, 2020: no new orders possible, repairs only.\nApril 30, 2021: PCI 3 expires.\nMarch 31, 2023: end of repair service.\nMarch 29, 2024: end of support, transactions no longer allowed.\n\n\n\n\nSee also\n\n\n                    Choose a terminal\n                \n                    Terminal API\n                \n","type":"page","locale":"pt","boost":18,"hierarchy":{"lvl0":"Home","lvl1":"Terminais","lvl2":"Deprecation of classic libraries"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/point-of-sale","lvl2":"\/pt\/point-of-sale\/classic-library-deprecation"},"levels":3,"category":"In-person payments","category_color":"green","tags":["Deprecation","classic","libraries"]},"articleFiles":{"UpdatedDeprecationTimeline.png":"<img alt=\"\" src=\"https:\/\/docs.adyen.com\/user\/pages\/docs\/03.point-of-sale\/68.classic-library-deprecation\/UpdatedDeprecationTimeline.png\" \/>","Oct21-UpdatedDeprecationTimeline.jpg":"<img alt=\"\" src=\"https:\/\/docs.adyen.com\/user\/pages\/docs\/03.point-of-sale\/68.classic-library-deprecation\/Oct21-UpdatedDeprecationTimeline.jpg\" \/>","2024_03_18-UpdatedDeprecationTimeline.jpg":"<img alt=\"\" src=\"https:\/\/docs.adyen.com\/user\/pages\/docs\/03.point-of-sale\/68.classic-library-deprecation\/2024_03_18-UpdatedDeprecationTimeline.jpg\" \/>"}}