EMV Terminal Type Apprval PCD Level 1 Administrative Prcess Versin 2.6b December 2016 permitted nly pursuant t the applicable agreement between the user and EMVC fund at www.emvc.cm. EMV is a registered trademark r trademark f EMVC, LLC in the United States and
Legal Ntice - Versin 2.6b Page i / 4 Legal Ntice This dcument summarizes EMVC s present plans fr evaluatin services and related plicies and is subject t change by EMVC at any time. This dcument des nt create any binding bligatins upn EMVC r any third party regarding the subject matter f this dcument, which bligatins will exist, if at all, nly t the extent set frth in separate written agreements executed by EMVC r such third parties. In the absence f such a written agreement, n prduct prvider, test labratry r any ther third party shuld rely n this dcument, and EMVC shall nt be liable fr any such reliance. N prduct prvider, test labratry r ther third party may refer t a prduct, service r facility as EMVC apprved, in frm r in substance, nr therwise state r imply that EMVC (r any agent f EMVC) has in whle r part apprved a prduct prvider, test labratry r ther third party r its prducts, services, r facilities, except t the extent and subject t the terms, cnditins and restrictins expressly set frth in a written agreement with EMVC, r in an apprval letter, cmpliance certificate r similar dcument issued by EMVC. All ther references t EMVC apprval are strictly prhibited by EMVC. Under n circumstances shuld EMVC apprvals, when granted, be cnstrued t imply any endrsement r warranty regarding the security, functinality, quality, r perfrmance f any particular prduct r service, and n party shall state r imply anything t the cntrary. EMVC specifically disclaims any and all representatins and warranties with respect t prducts that have received evaluatins r apprvals, and t the evaluatin prcess generally, including, withut limitatin, any implied warranties f merchantability, fitness fr purpse r nn-infringement. All warranties, rights and remedies relating t prducts and services that have undergne evaluatin by EMVC are prvided slely by the parties selling r therwise prviding such prducts r services, and nt by EMVC, and EMVC will have n liability whatsever in cnnectin with such prducts and services. This dcument is prvided "AS IS" withut warranties f any kind, and EMVC neither assumes nr accepts any liability fr any errrs r missins cntained in this dcument. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON- INFRINGEMENT, AS TO THIS DOCUMENT. EMVC makes n representatins r warranties with respect t intellectual prperty rights f any third parties in r in relatin t this dcument. EMVC undertakes n respnsibility t determine whether any implementatin f this dcument may vilate, infringe, r therwise exercise the patent, cpyright, trademark, trade secret, knw-hw, r ther intellectual prperty rights f third parties, and thus any persn wh implements any part f this dcument shuld cnsult an intellectual prperty attrney befre any such implementatin. Withut limiting the freging, this dcument may prvide fr the use f public key encryptin and ther technlgy, which may be the subject matter f patents in several cuntries. Any party seeking t implement this dcument is slely respnsible fr determining whether its activities require a license t any such technlgy, including fr patents n public key encryptin technlgy. EMVC shall nt be liable under any thery fr any party's infringement f any intellectual prperty rights in cnnectin with this dcument. permitted nly pursuant t the applicable agreement between the user and EMVC fund at www.emvc.cm. EMV is a registered trademark r trademark f EMVC, LLC in the United States and
Revisin Lg Versin 2.6b - Versin 2.6b Page ii / 4 Revisin Lg Versin 2.6b The fllwing changes have been made t the dcument since the publicatin f Versin 2.5a. Sme f the numbering and crss references in this versin have been updated t reflect changes intrduced by the published bulletins. The numbering f existing requirements did nt change, unless explicitly stated therwise. Sectin Reasn fr change 2.5 ICS replacement rules 2.6 Fee Table 4 Prcess Aligment permitted nly pursuant t the applicable agreement between the user and EMVC fund at www.emvc.cm. EMV is a registered trademark r trademark f EMVC, LLC in the United States and
Cntents - Versin 2.6b Page iii / 4 Cntents 1 Intrductin 5 1.1 Audience 5 1.2 Nrmative references 5 1.2.1 EMV Specificatins 5 1.3 Definitins 6 1.4 Ntatinal cnventins 8 1.4.1 Abbreviatins 8 1.4.2 Terminlgy & cnventins 9 2 PCD Type Apprval Overview 10 2.1 Scpe f PCD Type Apprval 10 2.2 PCD Type Apprval Life Cycle Cncept 11 2.2.1 PCD Life Cycle and Type Apprval Milestnes 11 2.2.1.1 Design Phase 11 2.2.1.2 Debugging Phase 11 2.2.1.3 PCD Type Apprval Phase 12 2.2.1.4 PCD apprval renewal Phase 12 2.2.1.5 End f Design Life 12 2.3 EMVC Cntactless Apprach 13 2.4 EMVC Cntactless Terminal Type Apprvals Descriptin 13 2.4.1 Cntactless Prduct Definitin 13 2.4.2 EMVC Cntactless Prduct Type Apprval Prcesses Overview 19 2.4.2.1 General: Registratin and Cntract 20 2.4.2.2 PCD Type Apprval 20 2.4.2.3 IFM Cntact Type Apprval 20 2.4.2.4 L2 kernel Cntact Apprval 20 2.4.2.5 Cntactless Prduct Apprval 20 2.5 ICS Submissin rules 21 2.5.1 ICS Submissin 21 2.5.2 ICS replacement 21 2.6 EMVC type apprval fee structure 22 3 Rles and respnsibilities 23 3.1 EMVC 23 3.2 EMVC CATA Secretariat 24 3.3 Test Labratry 24 3.4 Auditr Team 24 3.5 PCD Vendr 24 permitted nly pursuant t the applicable agreement between the user and EMVC fund at www.emvc.cm. EMV is a registered trademark r trademark f EMVC, LLC in the United States and
Cntents - Versin 2.6b Page iv / 4 4 PCD Type Apprval Prcedure 25 4.1 Registratin 26 4.1.1 EMVC Registratin 26 4.1.2 EMVC Cntract 26 4.2 PCD Type Apprval Test 27 4.2.1 PCD Vendr / Labratry cntract 28 4.2.2 Samples and ICS submissin 28 4.2.3 Pre-Validatin Test and Vendr Decisin 29 4.2.4 Analgue and Digital Tests 29 4.2.4.1 Analgue Test 30 4.2.4.2 Digital Test 30 4.2.5 Type Apprval Test Reprt 30 4.3 PCD Prvider Preparatin fr Apprval Request 32 4.3.1 PCD Vendr decisin n submissin t EMVC fr review 32 4.3.2 Submissin t Review 32 4.4 PCD Prvider Dssier 33 4.5 EMVC Review and Apprval 34 4.6 Type Apprval Renewal Prcess 35 5 Test Versin and Specificatin Change 36 5.1 Test Changes withut EMV Specificatins change 36 5.2 Test Changes Due t EMV Specificatins change 37 6 PCD Change Management 38 6.1 PCD changes 39 6.1.1 Minr and majr PCD changes 39 6.1.2 PCD change and PCD Type Apprval Level 1 need 40 6.2 Change f Name and Address 40 6.3 Re-Issuance f LA 40 7 Appendix 41 permitted nly pursuant t the applicable agreement between the user and EMVC fund at www.emvc.cm. EMV is a registered trademark r trademark f EMVC, LLC in the United States and
Intrductin - Versin 2.6b Page 5 / 37 1 Intrductin EMVC, LLC ( EMVC ) is the wner f the EMV Cntactless Specificatins fr Payment Systems Bk D Cmmunicatin Prtcl Specificatin, hereinafter called the EMV Specificatins. EMVC s bjective in establishing the Type Apprval Prcess described in this dcument is t create a limited mechanism fr testing Prximity Cupling Devices (PCDs) used in prximity integrated circuit chip card terminals fr sufficient cnfrmance with the EMV Specificatins fr their stated purpse as f the date f such testing, subject t all f the limitatins and restrictins f the Type Apprval Prcess set frth herein. All readers f this dcument are advised that type apprval, when granted by EMVC, shall nt be cnstrued as a warranty r representatin f any srt, nr may it be relied upn by any party as an assurance f quality r functinality f any prduct r service. Please nte the legal ntice stated abve at page ii f this dcument fr imprtant limitatins n the scpe f type apprval. This dcument describes the verall cntactless terminal level 1 Type Apprval Prcess and the templates and frms t be cmpleted by the participants in the prcess. 1.1 Audience The target audience f this dcument includes: PCD Vendrs Testing labratries accredited t perfrm the type apprval tests Auditrs qualified by EMVC t evaluate testing labratries fr EMVC accreditatin 1.2 Nrmative references 1.2.1 EMV Specificatins Table 1.1: EMV Specificatins Reference Publicatin Name Versin [Bk D] EMV Cntactless Specificatins fr Payment Systems Cntactless Cmmunicatin Prtcl Specificatin Versin 2.6, March 2016 [TB1] EMV Terminal Type Apprval Bulletin 185 First Ed September 2016
Intrductin - Versin 2.6b Page 6 / 37 1.3 Definitins The fllwing terms are used in this specificatin: Table 1.2: Definitins Term Analgue Test Card Reader Fully Integrated Terminal Intelligent Card Reader Cntactless Prduct Transparent Card Reader Device Test Envirnment Device Under Test (DUT) Digital Test EMV Kernel EMV Specificatins EMVC Entry Pint Definitin Set f tests that checks the Radi Frequency f the hardware and sftware/firmware f the PCD against the EMV Specificatins. Reader, t be cnnected t a Terminal, t allw the Terminal t perfrm a financial transactin, when the Terminal des nt embed the implementatin(s) needed fr its intended use. Terminal embedding a PCD, Entry Pint and POS System Architecture accrding t Bk A & B, and EMV Kernel(s) accrding t Bk C-1 t C-4. Card Reader, embedding a PCD, Entry Pint and POS System Architecture accrding t Bk A & B and EMV Kernel(s) accrding t Bk C-1 t C-4. Cmpnents can be either all in the reader (Single Cmpnent ICR) r nly part f cmpnent can be present (Multiple Cmpnent ICR). The final prduct accrding t definitin f sectin 4.2.2 fr Prduct Apprval. This Cntactless Prduct cntains the PCD cncerned by the present Level 1 Apprval Prcess. Card Reader, embedding a PCD, but n Entry Pint and n EMV Kernel(s). Part f the Test Envirnment needed t perfrm the Type Apprval Test, which the Vendr needs t develp and submit t the Test Labratry at the same time as the Samples. Sample within which the PCD submitted fr Type Apprval is actually tested. Defined set f tests that checks the sftware respnsible fr the data exchange between PICC and PCD against the EMV Specificatins. Sftware mdule that is develped fr exclusive supprt f the EMV cntactless debit/credit functins requirements accrding t EMV Bk C-1 t C-4. Set f dcuments defining the requirements, which the PCD shall cmply with fr PCD Type Apprval (and listed in the Nrmative References sectin f the PCD Type Apprval Administrative Prcess dcument). Organizatin established t maintain the EMV specificatins and administer Type Apprvals against thse specificatins. Sftware mdule accrding t Bk A, that is develped fr prtcl activatin and deactivatin as well as fr selectin f an EMV Kernel.
Intrductin - Versin 2.6b Page 7 / 37 Envirnment Implementatin Cnfrmance Statement (ICS) Landing Plane Lp-Back Applicatin Majr Mdificatin Minr Mdificatin Operating System (OS) Operating Vlume PCD Letter f Apprval (LA) PCD Type Apprval PCD Type Apprval Dcumentatin PCD Type Apprval Prcess PCD Under Test PCD Vendr Pre-validatin Test Pre-validatin Test Applicatin Prximity Cupling Device (PCD) Part(s) f the prduct cnstituted f cmpnents that are nt part f the PCD - as they are nt invlved in PCD functinality - but interface with the PCD (fr example used by, cnnected t,..) r have a direct impact n the behavir f the PCD. Frm cmpleted by the Vendr identifying the PCD implementatin and t be submitted t the Test Labratry alng with the Samples. The identified area where a cardhlder must tap their cntactless card r device t achieve a successful read. Test applicatin that the vendr needs t develp and implement in the Device Test Envirnment. Technical change t a characteristic f the PCD r f the prduct embedding it which can ptentially change its Cnfrmance. Technical change t a characteristic f the PCD r f the prduct embedding it which cannt ptentially change its Cnfrmance. Set f sftware cmpnents allwing the PCD sftware/firmware 3-dimensinal space in which the PCD can cmmunicate with a PICC by means f a magnetic field. Written statement that dcuments the decisin f EMVC that a specified PCD implemented within a specified Cntactless Prduct has demnstrated sufficient cnfrmance t the EMV Specificatins n the date f testing. Acknwledgment by EMVC that a specified PCD within a specified Cntactless Prduct has demnstrated sufficient cnfrmance t the EMV Specificatin. Set f dcuments and prcedures issued by EMVC t enable the PCD Type Apprval Prcess. Steps necessary t fr a PCD t btain an EMVC Letter Of Apprval. PCD embedded in the Sample that is actually tested during Type Apprval Test. Entity that submits the PCD fr PCD Type Apprval. Defined set f tests that checks whether a transactin takes place when a series f PICCs are presented in a series f parameterized psitins at the PCD Under Test. Test applicatin that the vendr needs t develp and t implement in the Device Test Envirnment. Peripheral device f the terminal, that uses inductive cupling t prvide pwer t the PICC and als t cntrl the data exchange with the PICC, up t the transprt layer (included), as specified in the EMV Specificatins.
Intrductin - Versin 2.6b Page 8 / 37 Prximity IC Card (PICC) Registratin Number Request fr apprval Sample Terminal Terminal Main Lp Test Test Bench Test Case Test Envirnment Test Labratry Test Reprt Card f the ID-1 frm factr (as defined in ISO/IEC 7810) r ther frm factr int which integrated circuit(s) and cupling means have been placed and in which cmmunicatin t such integrated circuit(s) is dne by inductive cupling in prximity f a cupling device. Unique identificatin number assigned by EMVC t a Vendr. Frm that accmpanies the PCD submissin t EMVC fr PCD Type Apprval. Cntactless Prduct, including the PCD t be submitted t Type Apprval, picked ut f prductin fr testing. Device used at the pint f transactin t perfrm a financial transactin and incrprating the hst cmmunicatin. It may als include ther cmpnents and interfaces (e.g. PCD, Entry Pint, Applicatin kernel...). Highest cntrl flw f the terminal which waits fr and dispatches events during an EMV Cntactless transactin using the functinality lcated in the PCD. Any activity that aims at verifying the cnfrmance f a selected prduct r prcess t a given requirement under a given set f cnditins. Defined cmbinatin f a set f test methds and test equipment used when perfrming a Test and wned by the Test Labratry. Descriptin f the actins required t achieve a specific Test bjective. Envirnment needed t perfrm the Test. It is cnstituted f a Test Bench in cmbinatin with a Device Test Envirnment fr PCD Type Apprval Test. Facility accredited by EMVC t perfrm PCD Type Apprval Test. Dcument prvided by the Test Labratry cntaining the Test results. 1.4 Ntatinal cnventins 1.4.1 Abbreviatins The abbreviatins listed in Table 1. are used in this specificatin. Table 1.3: Abbreviatins Abbreviatin Descriptin ICS DUT Implementatin Cnfrmance Statement Device Under Test
Intrductin - Versin 2.6b Page 9 / 37 Abbreviatin Descriptin LA OS PCD Letter f Apprval Operating System Prximity Cupling Devices 1.4.2 Terminlgy & cnventins The fllwing wrds are used ften in this specificatin and have a specific meaning: Shall May Shuld Defines a prduct r system capability which is mandatry. Defines a prduct r system capability which is ptinal r a statement which is infrmative nly and is ut f scpe fr this specificatin. Defines a prduct r system capability which is recmmended. The fllwing cnventins apply: Requirement Numbering Requirements in this specificatin are uniquely numbered with the number appearing next t each requirement: Fr example: 5.4.2.1 Example The PCD shall verify the BCC included in the UID CLn. The PCD shall cnsider an incrrect BCC as a transmissin errr. A requirement may have different numbers in different versins f the specificatins. Hence, all references t a requirement shuld include the versin f the specificatin as well as the requirement s number. Requirements may include infrmative statements. In this case the statement is written in the italic fnt and the verb may instead f shall is used
PCD Type Apprval Overview - Versin 2.6b Page 10 / 37 2 PCD Type Apprval Overview The fllwing sectins identify the scpe f PCD Type Apprval, the PCD Type Apprval Prcedure as well as Rles and Respnsibilities. 2.1 Scpe f PCD Type Apprval EMVC PCD Type Apprval establishes an increased level f cnfidence that PCD Vendrs have understd and can successfully implement the EMV Specificatins. The cmpnent(s) supprting the functinality required by the EMV Specificatins (as defined in the scpe sectin 1) is called the Prximity Cupling Device (PCD). The PCD Vendr is required t identify the PCD and assign it a unique label accrding t the PCD Vendr s naming cnventins. Nte: Cntactless Prduct architecture, identificatin and versin cntrl (naming) is utside the scpe f the EMV Specificatins. PCD Vendrs submit their card acceptance device (Terminal r Card Reader with embedded PCD) with the necessary Device Test Envirnment and apprpriate dcumentatin, including the Implementatin Cnfrmance Statement (ICS), t an EMVC accredited labratry fr testing. The labratry executes a set f EMVC defined Test Cases and prepares a test result dcument fr the PCD Vendrs that may then be submitted t EMVC fr evaluatin. EMVC s evaluatin f the test results cncludes with the issuance f Letter f Apprval r decline ntificatin. Apprval, when granted, applies t the vendr supplied EMV PCD identificatin. Majr changes r additins t the PCD create a new unapprved PCD that requires retesting and apprval befre EMV cmpliance can be claimed. Cmmn industry practice requires PCD vendrs t accmmdate lcal acquirer requirements in their card acceptance devices. These acquirer requirements are utside f scpe fr EMVC type apprval. EMVC limits type apprval t the EMV PCD as tested in the submitted card acceptance device, leaving the respnsibility t the apprpriate lcal acquiring entity (als referred t as the wner f the envirnment f use) t validate cntinued cmpliance with the EMV Specificatins functinality in the integrated acquiring envirnment. Obtaining an EMV PCD apprval frm EMVC has the advantage that: Acquirers have access t terminal implementatins in respect f which cmpliance t the EMV Specificatins has already been tested yielding a likely reductin in testing csts as well as imprved time t market fr final implementatins. PCD vendrs can sell standard terminal implementatin devices n a wrldwide basis and differentiate themselves frm the cmpetitin.
PCD Type Apprval Overview - Versin 2.6b Page 11 / 37 2.2 PCD Type Apprval Life Cycle Cncept The fllwing sectins identify the PCD Type Apprval life cycle which is a lgical cncept regarding the design and key apprval milestnes f a PCD. 2.2.1 PCD Life Cycle and Type Apprval Milestnes Type Apprval shall be dne n a Sample that is representative f future prductin. Therefre, the Type Apprval milestne shall ccur at a particular mment in the PCD Life cycle. Figure 2.1: Life cycle f a PCD Prduct/PCD design Debugging Apprval duratin Renewal duratin EMVC PCD Apprval *with representative Sample EMVC PCD Apprval Renewal EMVC PCD Apprval Renewal Start f design phase End f debugging phase Start f prductin phase End f first apprval Start f renewed apprval : Out f scpe f EMVC PCD Apprval 2.2.1.1 Design Phase The PCD is develped by an entity directly related t the PCD r terminal prvider and/r the manufacturer f the PCD(s). Mst imprtantly, PCD design and develpment must be in accrdance with the EMV Specificatins, as well as any ther applicable specificatins (e.g. gvernment standards). 2.2.1.2 Debugging Phase The PCD design is checked and tested against all related specificatins. EMVC recmmends that cnfrmance testing against the EMV Specificatins is cnducted n the representative Sample befre prceeding t type apprval, preferably with tls equivalent t thse used fr type apprval tests. Befre starting prductin, implementatins f the PCD type must be submitted fr type apprval tests t demnstrate cnfrmance with the required specificatins. The PCD Vendr must identify which ptins its PCD design has incrprated frm the EMV Specificatins and gather the infrmatin t be submitted in the PCD Type Apprval Prcess.
PCD Type Apprval Overview - Versin 2.6b Page 12 / 37 2.2.1.3 PCD Type Apprval Phase EMVC assesses cnfrmance f the PCD design against the EMV Specificatins. T determine cnfrmance, identified implementatins f the PCD type must underg predefined tests in a specified test envirnment (Test Labratry). The Samples submitted t Test Labratry must be representative f final prduct. After the PCD Letter f Apprval has been granted, it is valid as lng as the fllwing applies: The design and implementatin f the PCD within the Cntactless Prduct embedding it is the same in prductin as it was within the Samples, which was tested and apprved. The apprval is nt revked by EMVC. The renewal date is nt past. N nn-cnfrmance is fund at the Cntactless Prduct testing which impacts the PCD cnfrmance. Any change in the Cntactless Prduct design r any re-use f the PCD in anther Cntactless Prduct, as specified in the sectin titled PCD change management f this dcument, may als impact the PCD cmpliance. PCD apprval in this new r mdified prduct is nt presumed. 2.2.1.4 PCD apprval renewal Phase Prir t the renewal date, vendrs may request a renewal by submitting the riginally apprved prduct t EMVC fr renewal testing. The purpse f this renewal testing is t assure that these prducts pass the mst current EMVC testing. By passing the renewal test, the prduct will receive an extensin t the Letter f Apprval. After the renewal date, prducts nt passing renewal testing will be remved frm the apprved prducts list, and their Letters f Apprval will be cnsidered revked. Shuld there be a case where a prduct reaches its renewal date withut any applicable test plan updates, such prducts will be issued an extensin t their Letter f Apprval. 2.2.1.5 End f Design Life The end f the design life f an apprved PCD type is reached when prductin f that type is finally stpped.
PCD Type Apprval Overview - Versin 2.6b Page 13 / 37 2.3 EMVC Cntactless Apprach EMVC cntactless type apprval ascertains the level f cnfidence that Prduct Prviders have crrectly implemented the EMV Cntactless Specificatins. Prduct Prviders submit their Prduct with the sftware and apprpriate dcumentatin, including the Implementatin Cnfrmance Statement (ICS), t an EMVC accredited Labratry fr testing. The Labratry executes a set f EMVC-defined test cases and prepares a test reprt dcument fr the Prduct Prvider that may then be submitted t EMVC fr evaluatin. EMVC s evaluatin f the test reprt cncludes with the issuance f a Letter f apprval r decline ntificatin. Obtaining an EMV Prduct apprval frm EMVC has the fllwing advantages: Acquirers have access t terminal implementatins fr which cmpliance t the EMV Cntactless Specificatins has already been tested, yielding a likely reductin in testing csts as well as imprved time t market fr final implementatins. Prduct Prviders can sell the apprved EMVC cmpliant prduct n a wrldwide basis and differentiate themselves frm the cmpetitin. Nte: The integratin f an OEM prduct int a final Prduct may impact its analgue perfrmances. As a result, EMVC ds nt apprve OEM prducts, each final implementatin f an OEM prduct shall be separately submitted t EMVC Type Apprval. 2.4 EMVC Cntactless Terminal Type Apprvals Descriptin 2.4.1 Cntactless Prduct Definitin This sectin defines the Cntactless Prduct definitins that that vendr can implemented, based n the POS System defined in Bk A. A POS System is the device that cmmunicates with cntactless cards, prcesses cntactless transactins, and may supprt ther payment functinalities such as magnetic stripe r cntact chip transactins. The basic functins f the POS System include: cmmunicatin with cntactless cards. applicatin selectin and kernel activatin. displaying messages t the cardhlder. displaying messages t the merchant. accepting merchant data entry f the transactin amunt. cardhlder verificatin (e.g. signature). prvisin f nline cnnectins. prvisin f data capture fr clearing and settlement. Additinally Entry Pint and Kernels C-1 t C-4 shall be lcated in the POS System.
PCD Type Apprval Overview - Versin 2.6b Page 14 / 37 The physical architecture f the POS System can be any f the fllwing, accrding t Bk A definitin Fully integrated terminal FIT : All elements included in a single device. Intelligent card reader ICR : The reader handles mst f the cntactless transactin prcessing, passing the results fr cmpletin by the terminal. Cmbinatin f terminal and transparent card reader: The reader prvides cmmunicatin with the card, while kernels and ther prcesses are in the terminal. 1/ Fully Integrated Terminal (FIT): All elements f POS System included in a single device. Figure 2.2: Fully Integrated Terminal The FIT includes: Level 1 Cntactless PCD accrding t Bk D. Entry Pint and POS System Architecture accrding t Bk A and B EMV Kernels accrding t Bk C-1 t C-4 including: Kernel transactins flw, Kernel functins EMV data management, Cryptgraphy,. Cnsumer & merchant interface(s). If present, the cntact and mag stripe part f the FIT: IFM (L1), EMV cntact Kernel (L2), Acquiring Netwrk interface.
PCD Type Apprval Overview - Versin 2.6b Page 15 / 37 2/ Intelligent Card Reader (ICR), the reader handles mst f the cntactless transactin prcessing, transmitting the results fr cmpletin t the terminal, where tw implementatins are pssible: 2.1/ Single Cmpnent ICR (S-ICR), where all EMV cmpnents (EMV requirements defined in Bk A, B, C and D) are in the reader. Figure 1.3: Single Cmpnent ICR (example 1) Figure 2.4: Single Cmpnent ICR (example 2) The ICR includes: Level 1 Cntactless PCD accrding t Bk D. Entry Pint and POS System Architecture accrding t Bk A and B. EMV Kernels accrding t Bk C-1 t C-4 including: Kernel transactins flw,
PCD Type Apprval Overview - Versin 2.6b Page 16 / 37 Kernel functins EMV data management, Cryptgraphy,. If present, the cntact part f the ICR: IFM (L1), EMV cntact Kernel (L2), 2.2/ Multi Cmpnent ICR (M-ICR): In this secnd case, The M-ICR cntains mst f the EMV cmpnents (EMV requirements defined in Bk A, B, C and D) are in the reader. Figure 2.5: Multiple Cmpnent ICR (example 1)
PCD Type Apprval Overview - Versin 2.6b Page 17 / 37 Figure 2.6: Multiple Cmpnent ICR (example 2) The ICR include: A valid Level 1 Cntactless PCD with an EMVC Letter f Apprval accrding t Bk D. Part f Entry Pint and POS System Architecture accrding t Bk A and B Part f EMV Kernels accrding t Bk C-1 t C-4 If present, the cntact part f the ICR: IFM (L1) EMV Cntact Kernel (L2) 3/ Cmbinatin f terminal and transparent card reader: The reader prvides cmmunicatin with the card, while kernels and ther prcesses are in the terminal:
PCD Type Apprval Overview - Versin 2.6b Page 18 / 37 Figure 2.7: Transparent Reader Cmbinatin (example 1) Figure 2.8: Transparent Reader Cmbinatin (example 2) Nte: In case the reader cntain the PCD L1 Hardware and analg, and if the PCD L1 Digital sftware is nt present in the reader but in the terminal, then the Prduct is cnsidered as a Fully Integrated Terminal (FIT).
PCD Type Apprval Overview - Versin 2.6b Page 19 / 37 2.4.2 EMVC Cntactless Prduct Type Apprval Prcesses Overview The present dcument fcuses n the PCD Level 1 type Apprval nly. This sectin is fr infrmatin n the verall Cntactless Prduct Type Apprval. EMVC Cntactless Prduct Type Apprval is a prcess that tests a Cntactless Prduct fr cmpliance with the full set f EMV specificatins (Bk A, B, C & D). This sectin and figure 2.9 verview the EMVC Cntactless Prduct Type Apprval Prcesses. Figure 2.9: Prcess verview
PCD Type Apprval Overview - Versin 2.6b Page 20 / 37 2.4.2.1 General: Registratin and Cntract Vendr registratin and cntract(s) are required t start Type Apprval. Registratin Number and cntract(s) dcument will be sent by EMVC Type Apprval Secretariat upn receiving the registratin request frm. The registratin is valid fr all EMVC Type Apprval prcesses. 2.4.2.2 PCD Type Apprval PCD testing is designed t test the acceptance functinality, Analgue and digital interfaces f the PCD. 1. Pre-Validatin Test (PCD): t check the acceptance f a series f PICC presented at a parameterized psitins. Optinally perfrmed befre Analgue Test. 2. Analgue Test: t check the Radi Frequency f hardware and firmware 3. Digital Test: t check data exchange between PICC and PCD The PCD Letter Of Apprval (PCD LOA) is prvisinal. Indeed tday, sme PCD requirements can nly be tested nce EMV Kernel(s) are present. Therefre, EMVC retains the right t revke a PCD LOA if prblems relating t the PCD are fund during Cntactless Prduct Apprval. Further infrmatin fr PCD Type Apprval will be described in the fllwing sectins f this dcument. 2.4.2.3 IFM Cntact Type Apprval In case that the Cntactless Prduct cntains a cntact IFM, the IFM shall fllw the Cntact L1 Type Apprval as detailed in the EMVC Type Apprval Terminal Level 1 Administrative Prcess dcument, latest versin. 2.4.2.4 L2 kernel Cntact Apprval In case that the Cntactless Prduct cntains a cntact Level 2 kernel, the kernel shall fllw the L2 Cntact Type Apprval as detailed in the EMVC Type Apprval Terminal Level 2 Administrative Prcess dcument, latest versin. 2.4.2.5 Cntactless Prduct Apprval The verall Cntactless Prduct Apprval is detailed in the EMVC Type Apprval Cntactless Prduct Administrative Prcess dcument, latest versin.
PCD Type Apprval Overview - Versin 2.6b Page 21 / 37 2.5 ICS Submissin rules 2.5.1 ICS Submissin The initial ICS submissin t the EMVC is free f charge. The ICS submitted must be the ICS in pdf frmat, capable f imprting/exprting XML frmat and shall be digitally signed by the Prduct Prvider and the Labratry at the time f submissin t EMVC. The Labratry supplies the signed cpy f the vendr-supplied ICS t EMVC fr review prir t the start f the type apprval testing prcess. EMVC will review and apprve the ICS by returning the ICS in pdf digitally signed and with the fficial ICS number. In case the ICS is incrrectly filled, decline fee applies t Labratry. 2.5.2 ICS replacement One free ICS replacement is allwed during the ICS life cycle. Any subsequent ICS replacement requested will be charged t the Prduct Prvider. Same submissin prcess applies as fr initial ICS submissin (Labratry submits the changed ICS). This applies t any change in the ICS after the fficial apprval f the ICS by EMVC. After the start f the test sessin f the Prduct, ICS replacements (fllwing the rules f the previus bullet) are nly allwed fr administrative infrmatin update (such as name f prduct) but nt are nt allwed fr technical infrmatin update. Labratry shall ensure that any ICS change requested is nt made t hide a bug in the prduct (such as deactivatin a functin because this functin is nt wrking prperly). ICS replacement is n mre allwed after Test Reprt submissin t EMVC. Nte: ICS decline prcess remains and any errr reprted by EMVC will be charged t the Labratry (as Labratry is respnsible f reviewing the ICS prvided by the Prduct Prvider). ICS decline prcess applies t the initial ICS submissin and als t any ther ICS replacement (charged r nt charged t the Prduct Prvider).:
PCD Type Apprval Overview - Versin 2.6b Page 22 / 37 2.6 EMVC type apprval fee structure The fllwing fee structure is applicable: Initial Submissin ICS Replacement (starting at 2 nd Replacement) Renewal Declined ICS/Reprt (Labratry fee) LA reissuance Nte: The amunt f each fees are published in Terminal Type apprval Bulletin 185.
Rles and respnsibilities - Versin 2.6b Page 23 / 37 3 Rles and respnsibilities The fllwing sectins define the rles and respnsibilities fr the varius participants in the Type Apprval Prcess. 3.1 EMVC EMVC defines Type Apprval requirements and evaluates peratinal results. EMVC prvides the fllwing services: Defines mandatry auditr accreditatin requirements Accredits rganizatins that perfrm audits t establish Test Labratry accreditatin Defines mandatry Test Labratry accreditatin requirements Sets Test Labratry audit time frame Manages Test Labratry appeals prcess and reslves accreditatin disputes based n the statement f L1 cntract Determines the applicability f the EMV Specificatin and assciated test requirements Evaluates PCD type apprval summary results t determine if apprval requests shuld be granted r nt Ntifies apprpriate EMVC wrking grup f warranted specificatin crrectins, clarificatins, and enhancements that result frm the cnditinal apprval prcess Evaluates terminal and card failure cmplaints t determine if type apprval revcatin is apprpriate Maintain and publishes (via EMVC web-site) a list f PCD that have received EMVC type apprval ntificatin. EMVC Terminal Type Apprval Secretariat
Rles and respnsibilities - Versin 2.6b Page 24 / 37 3.2 EMVC CATA Secretariat The EMVC CATA secretariat is respnsible fr cmmunicating type apprval status t third parties and fr the administratin and maintenance f a database that prvides the fllwing: Qualified auditr list Accredited testing labratry list Type apprval test requirements Issue PCD apprval letters Apprved PCD list 3.3 Test Labratry The Test Labratry is an entity accredited by EMVC t cnduct testing f PCD(s) in accrdance with the type apprval test requirements and Test Cases. 3.4 Auditr Team The auditr team cmprises the persn(s) in charge f cnducting audits n behalf f EMVC. 3.5 PCD Vendr The PCD Vendr is the entity respnsible fr submitting Cntactless Prduct embedding PCD fr type apprval in cmpliance with PCD Type Apprval prcedures.
PCD Type Apprval Prcedure - Versin 2.6b Page 25 / 37 4 PCD Type Apprval Prcedure This sectin describes the PCD Type Apprval prcedure t be fllwed by PCD Vendrs, labratries, and EMVC. Figure belw shws the diagram f PCD Type Apprval prcedure. Figure 4.1: PCD Type apprval Prcedure
PCD Type Apprval Prcedure - Versin 2.6b Page 26 / 37 4.1 Registratin 4.1.1 EMVC Registratin Registratin prvides the vendr with entry int the apprval prcess fr when the vendr wants t submit their final Test Reprt t EMVC fr apprval. This registratin is valid fr all ther EMVC Type Apprval Prcesses including Cntactless Prduct Apprval, Cntact Level 1 Type Apprval and Cntact Level 2 Type Apprval. The PCD Vendr must cmplete a registratin frm and submit t EMVC Secretariat. EMVC Secretariat will send a Registratin Number t the vendr upn receiving the request frm. Please visit EMVC website t dwnlad the dcuments yu need. 4.1.2 EMVC Cntract The PCD Vendr must cmplete and sign the EMVC defined cntract. The cntract has t be signed with EMVC prir t submissin f prduct test reprt. PCD Vendr must submit the cntract, if nt already signed. This cntract stipulates, amngst ther prvisins, the PCD Vendr s acceptance f all specificatins, prcedures, terms and cnditins gverning EMVC PCD Type Apprval. The cntract is standard fr all PCD Vendrs t help ensure cnsistent requirements fr all participants. Cntract custmizatin fr individual PCD Vendrs is nt acceptable. Please visit EMVC website t dwnlad the dcuments yu need.
PCD Type Apprval Prcedure - Versin 2.6b Page 27 / 37 4.2 PCD Type Apprval Test The fllwing peratins shall be perfrmed by the PCD prvider and by the testing labratry in the type apprval prcedure: The PCD prvider is free t select any EMVC accredited labratry fr the purpse f achieving EMVC type apprval. The vendr and test labratry shall execute a cntract defining apprpriate rights and bligatins. At a minimum, the cntract shall cntain the requirements listed in the fllwing sectin. PCD prvider sends an Implementatin Cnfrmance Statement (ICS) t the chsen labratry fr each implementatin under test (IUT) that it submits. The ICS frmat and cntent requirements are determined by EMVC. The ICS submitted must be the ICS in pdf frmat, and shall be digitally signed by the PCD Prvider at the time f submissin t EMVC. The labratry supplies a cpy f the vendr-supplied ICS t EMVC fr review prir t the start f the type apprval testing prcess, digitally signed by the Applicatin Vendr and by the Labratry: As result EMVC prvide an unique ICS Reference Number PCD prvider and the test labratry must discuss IFM sftware requirements in rder fr the test labratry t execute the EMVC type apprval test. The testing labratry shall test the terminal in accrdance with EMVC test prcedures. Testing shall be perfrmed in Labratry premises with the cmplete slutin samples lcated in these premises. The PCD prvider prepares the Request Fr Apprval frm and submits it t EMVC. EMVC can then issue the invice fr the IFM prvider. RFA can be send nly after the ICS has been apprved by EMVC. PCD prvider submits payment t EMVC based n the received invice. The testing labratry shall send the final test reprt t the PCD prvider fr apprval befre fficial submissin t EMVC. When agreed by the PCD Prvider, the labratry shall submit the Test Reprt t EMVC, and ensures PCD Prvider has already submitted his cmpleted Request Fr Apprval frm. Nte: An Apprved ICS is valid 6 mnth. If the related request fr Apprval is nt submitted and the invice is nt paid within that perid, all related dcuments t this apprval request are n mre valid (ICS, RFA, reprt) and a new prcess shall be restarted. Nte that in this case the invice is nt be reimbursed. Nte: If the test sessin has nt started yet and the ICS already been apprved, when a new EMVC release f the ICS is published, then the ICS shall be resubmitted with new latest ICS versin befre labratry can submit the reprt.
PCD Type Apprval Prcedure - Versin 2.6b Page 28 / 37 4.2.1 PCD Vendr / Labratry cntract The PCD Vendr selects and cntacts an EMVC-accredited Test Labratry. The PCD Vendr is free t select any EMVC-accredited labratry fr the purpse f achieving EMVC PCD Type Apprval. A list f accredited labratries is published n the EMVC website. Once a labratry is selected, the PCD Vendr and Test Labratry shall execute a cntract defining individual rights and bligatins f the cntracting parties. The prvisins f PCD Vendr/labratry cntract are up t the cntracting entities and entirely ut f scpe f EMVC. Any fees payable t the labratry in respect f the tests t be cnducted are slely at the discretin f the labratry. Nte: Tpics likely t be included in the cntract between Test Labratries and Vendrs are mentined belw fr infrmatin purpses nly. Any labratry requirements needed fr testing including any sftware applicatin required interfacing with the labratry test equipment. Within the EMVC dcuments this is referred t as an Upper Tester. Reference t the cntract between the PCD Vendr and EMVC Agreement f mutual cperatin in prviding needed infrmatin and assistance Lead time fr the executin f the type apprval tests The number f Samples fr testing (minimum three) Arrangement fr the preparatin and delivery f Samples Right t keep all Samples fr the duratin f the test prcedure Recgnitin that n infringement n the independence r impartiality f the Test Labratry will be allwed during r after testing Agreement n the bundaries f use f the test reprt Prvisins fr cnflict reslutin Maintaining the Samples at the labratry during EMVC evaluatin f test results. Maintaining the Samples while the PCD is EMV apprved. 4.2.2 Samples and ICS submissin The PCD Vendr shall send t the chsen Test Labratry: a signed Implementatin Cnfrmance Statement (ICS) fr the PCD type that it submits. The ICS frmat and cntent requirements are determined by EMVC. The latest ICS template at the time f testing must be used. Please visit EMVC website t dwnlad the dcuments yu need. the agreed number f Samples as defined by the Test Labratry (minimum three.) Samples presented must: have cntactless symbl at the center f the landing plane as specified in the specificatins.
PCD Type Apprval Prcedure - Versin 2.6b Page 29 / 37 have an unique check sum fr PCD firmware, and unique and specific identificatin f the PCD hardware. embed a PCD type that implements PCD functins specified in the EMV Specificatins annex related t PCD Test Envirnment be submitted alng with a Device Testing Envirnment cmpliant with requirements described in EMVC PCD Type Apprval Device Test Envirnment dcument, i.e. that: ü fr Pre-Validatin Test, implements a Pre-Validatin Test Applicatin (Optinal). ü fr Analgue Test, allws a number f PCD functins t be accessible in a step-by-step mde. ü fr Digital Test and part f Analgue Test, implements a Lp Back Applicatin. ü prvides a means fr the different cmmand/respnses t be displayed. (e.g. n the display f a PC). ü includes manual, cables and any necessary PC sftware (where required). ü includes ther cmpnents that allw the peratin f the PCD if the Cntactless Prduct in which it is embedded des nt cnstitute an perable device alne. prvide identificatin f the Landing Plane including the final psitin f the cntactless symbl. be identical, i.e. there shall be n hardware, firmware r sftware difference between the samples presented. be representative f the final prduct. 4.2.3 Pre-Validatin Test and Vendr Decisin The Test Labratry ptinally perfrms Pre-validatin Test n the Samples in accrdance with EMVC prcedures. Pre-validatin Test uses card samples apprved by payment system t check the PCD acceptance at varius psitins. If the Pre-validatin Test is successful, the Test Labratry cntinues with the next step. If the result f this testing is nt successful, the PCD Vendr is infrmed by the Test Labratry befre Analgue Test starts. The PCD Vendr then decides either nt t start frmal testing and stp the PCD Type Apprval Prcess r cntinue with frmal testing at PCD Vendr s risk. 4.2.4 Analgue and Digital Tests The Test Labratry perfrms the fllwing tests n the Samples in accrdance with EMVC prcedures. These tests respectively cnfirm the cmpliance f the electrical characteristics f the pwer and data exchange between PICC and PCD and the cmpliance f the digital data exchange between PICC and PCD:
PCD Type Apprval Prcedure - Versin 2.6b Page 30 / 37 4.2.4.1 Analgue Test Related dcument Cntactless Terminal Level 1 PCD Analgue Test Bench and Test Cases Requirements details the tests that a labratry must perfrm based n EMV-established requirements (intended fr all participants in the PCD Type Apprval Prcess). 4.2.4.2 Digital Test Related dcument Cntactless Terminal Level 1 PCD Digital Tests details the tests that a labratry must perfrm based n EMV-established requirements (intended fr all participants in the PCD Type Apprval Prcess). 4.2.5 Type Apprval Test Reprt The Test Labratry prvides the PCD Vendr (wner f the test results) with a signed Test Reprt in a nn-mdifiable and electrnically signed frmat. The Test Reprt, called Test Reprt fr PCD Type Apprval includes, at a minimum, the fllwing items: The unique identificatin f the Test Reprt Test Labratry infrmatin Tested Prduct Infrmatin Implementatin Cnfrmance Statement Reference Number Identificatin f PCD Vendr Identificatin f the Samples Identificatin f any ther vendr equipment r cmpnents (e.g. terminal mdel) submitted t allw testing Picture f the Sample under test taken by the labratry Test methd infrmatin EMVC specificatin/each Test Case versin used fr all tests Identificatin f all labratry testing equipment and sftware versins used during the tests Descriptin f the labratry envirnmental cnditins during testing Test results infrmatin Dates when test were perfrmed The results f Pre-validatin Test (Optinal) The results f Analgue Test The results f Digital Test A summary test reprt fr each test including: ü Test Case numbers that were executed with a pass r fail indicatin ü A detailed descriptin frm the Test Labratry f failed tests including lgs f the test results fr each reprted discrepancy in the failed test.
PCD Type Apprval Prcedure - Versin 2.6b Page 31 / 37 ü A detailed descriptin f any exceptinal test(s) perfrmed, equipment utilized and a descriptin f related test results ü A detailed descriptin f the PCD mdificatins that may be required fr the purpse f executing the EMVC Test Cases The signed Implementatin Cnfrmance Statement fr PCD submitted t the labratry prir t starting the fficial PCD Type Apprval Prcess Nte: The labratry shuld maintain all test result lgs fr all Test Cases and make thse available fr EMVC review as requested.
PCD Type Apprval Prcedure - Versin 2.6b Page 32 / 37 4.3 PCD Prvider Preparatin fr Apprval Request 4.3.1 PCD Vendr decisin n submissin t EMVC fr review The PCD Vendr determines whether test results resulting frm labratry testing will be submitted t EMVC fr evaluatin. Submitting test results t EMVC fr evaluatin indicates vendr acceptance that the test results are a true representatin f PCD perfrmance. Test results may be submitted t EMVC fr evaluatin up t 90 days frm the date the PCD was tested. Test results that exceed the 90 day validity perid have expired and cannt be submitted. PCD re-testing is required t create a current test reprt if the validity perid is exceeded and EMVC evaluatin is desired. The vendr must ensure that the Samples assciated with test results submitted t EMVC fr evaluatin remain unaltered and accessible in a timely manner during the evaluatin prcess. It is required that the Samples remain in the pssessin f the labratry when test results are submitted t EMVC until EMVC has apprved r declined the request fr apprval. The PCD Vendr must ensure that Test Reprt is ready t be submitted t EMVC. 4.3.2 Submissin t Review T cmplete the request fr apprval previusly sent, (see 5.2.3.2), the labratry shall submit t EMVC an riginal signed cpy r electrnic cpy digitally signed f the Test Reprt. Nte 1: Vendr must give cnsent fr the labratry t submit the Test Reprt t EMVC directly. Nte 2: This step can be dne at the same time as r after the EMVC fee payment. Hwever Vendr shall be aware that EMVC review will nly start nce the fee paid. The request fr review is cnsidered cmpleted nce EMVC has received: The Request Fr Apprval frm filled-in, including the fficial name f the PCD Vendr requesting the apprval as well as their registratin number. The cmplete Test Reprt received frm the Test Labratry, including the signed cpy f the Implementatin Cnfrmance Statement (ICS), as submitted by the PCD Vendr t the Test Labratry.
PCD Type Apprval Prcedure - Versin 2.6b Page 33 / 37 4.4 PCD Prvider Dssier The dssier submitted t EMVC will cmprise: A signed cpy f the Implementatin Cnfrmance Statement (ICS), received frm the testing labratry Letter requesting apprval (Request Fr Apprval frm) received frm PCD Prvider PCD prvider payment The cmplete and unchanged Test Reprt received frm the testing labratry Any additinal supprting dcumentatin the vendr believes is apprpriate
PCD Type Apprval Prcedure - Versin 2.6b Page 34 / 37 4.5 EMVC Review and Apprval Upn receiving the dssier and internal validatin f the fee payment, EMVC will review the submitted test reprt and determine if type apprval shuld be granted. The PCD Letter f Apprval is prvisinal until Prduct Apprval is granted, meaning Level 1 apprval stands by itself, but can be revked based upn a Level 2 prduct test. Depending n the decisin, EMVC will: Issue PCD Letter f Apprval, if apprpriate (Letter f Apprval will nly be issued electrnically and sent by email) Prvide ntificatin f PCD Type Apprval PCD LA identifies: the apprved PCD name and its tw sub-sets: PCD hardware name, PCD firmware/sftware name, the Cntactless Prduct name in which it was tested, the EMV Specificatins versin against which it was tested, the renewal date, Limitatins f the current LA, e.g.: If the PCD perfrms a RESET befre r after a prprietary plling cmmand f the PCD, the LA will cntain the sentence EMVC cannt guarantee interperability because this PCD prvides additinal prprietary functinality and features such as plling fr ther technlgies, that are beynd the scpe f EMVC Nte: As described earlier, nn-cnfrmance f EMV Specificatins requirement may be fund during Cntactless Prduct testing. In that case, EMVC will decide whether the PCD LA has t be remved frm the apprved PCDs list psted n EMVC website. PCD Vendr may need t cme back t PCD Type Apprval.
PCD Type Apprval Prcedure - Versin 2.6b Page 35 / 37 4.6 Type Apprval Renewal Prcess The renewal date fr the PCD is 4 years frm the date EMVC issued the Letter f Apprval. After the renewal date, prducts nt passing renewal testing r nt applied t renewal testing will be remved frm the apprved PCDs list and their Letter f Apprval will be cnsidered revked. Prir t the renewal date, PCD prviders may request a renewal by submitting the riginally apprved prduct t EMVC fr renewal. Tw situatins may ccur: the test plan is unchanged since previus apprval: the renewal date will be extended autmatically fr anther 4 years. the test plan has been updated: within the 6 mnths befre the renewal date, PCD prviders may submit the riginal sample t a Test Labratry fr Renewal Test. Renewal testing is needed t ensure these prducts pass the mst current EMVC testing. By passing the renewal test, the prduct will then receive an extensin t the Letter f Apprval. If the test plan is nt updated, the renewal date will be extended autmatically fr anther 4 years.
Test Versin and Specificatin Change - Versin 2.6b Page 36 / 37 5 Test Versin and Specificatin Change The fllwing sectins identify the prcess managing PCD Type Apprval Test changes due t EMV Specificatins r Test Cases change. 5.1 Test Changes withut EMV Specificatins change EMVC reserves the right t change Type Apprval Test at any time in rder t increase the accuracy and integrity f the tests versus the EMV Specificatins, r fr any ther reasns. Figure 5.1: Example f the timing fr test changes EMVC will infrm all participants f the new tests and fix the date(s) fr activatin f the new tests and deactivatin f the ld. Ntice may be given by psting t the EMVC website. EMVC may determine a time perid during which either the ld r new test versin may be used in the Type Apprval Prcess.
Test Versin and Specificatin Change - Versin 2.6b Page 37 / 37 5.2 Test Changes Due t EMV Specificatins change After a change in the EMV Specificatin, EMVC will decide: If and when the type apprval tests must be changed t accmmdate the new specificatins When t intrduce the new type apprval test versin When t stp testing with the previus type apprval test versin EMVC will infrm all participants f the new tests and the date(s) f the activatin f the new test versin and deactivatin f the ld test versin. Ntice may be given by psting t the EMVC website. Erreur! Nus n avns pas truvé la surce du renvi. identifies the impact f specificatin changes n the Type Apprval Prcess. Figure 5.2: Timeline fr test changes fllwing changes in EMV Specificatin