Terminal Type Approval

 

  1. Where can the Terminal ESD Evaluation be found?
  2. Where can I find information on Payment Tokenisation Type Approval?
  3. What does the EMVCo Terminal Type Approval activity cover?
  4. Where can the EMV Contactless specifications be found?
  5. How can I ask EMVCo to reissue a LoA?
  6. I am an Accredited Laboratory and would like to open a new location, what should I do?
  7. Where can I find a list of Products that have been approved by EMVCo for Contact Level 1, Contactless Level 1, Contact Level 2 and Contactless Product?
  8. What is an 'Application Contact Kernel'?
  9. What is an ‘EMVCo Contactless Kernel C-n'?
  10. What does ‘Application Contact Kernel testing’ meanl?
  11. What does ‘Contactless Product testing’ mean?
  12. When do I use the option “new” in the ICS Form?
  13. When do I use the option “replacement” in the ICS Form?
  14. If I am interested in purchasing a previously approved contact IFM, Contactless PCD or Application Contact Kernel from a Product Provider, how do I know that it will be compatible with my device?
  15. What are the definitions of ‘terminal’ and ‘interface module’ in the context of a fully integrated Contact POS system?
  16. How can I become registered for EMV Contact Level 1, Contactless Level 1, Contact Level 2 or Contactless Product Type Approval?
  17. Do I need the support of an acquirer to submit a terminal for Type Approval?
  18. Is it possible to ‘self-certify’ an EMVCo compliant terminal?
  19. Where can I find a list of EMVCo approved type accredited laboratories?
  20. How can I obtain test tools to assist in the development of an IFM, PCD, Application Contact Kernel or Contactless Product?
  21. Which laboratory should I use for Type Approval testing?
  22. How can I obtain an editable electronic copy of the Request For Approval (RFA) Form?
  23. Could you please advise the usual turnaround time for obtaining approval after the submission of official Type Approval test result?
  24. Please identify the steps required for Terminal Type Approval.
  25. I am a developer of POS terminals and I would like to get approval from EMV. Besides getting Terminal approval can I get Card approval too?
  26. What is the cost of Type Approval testing?
  27. How do I know if my device can become Contact Level 1, Contactless Level 1, Contact 2 or Contactless Product compliant?
  28. Is it possible to combine different IFMs and Application Contact Kernels?
  29. Is it possible to combine contact components developed to different versions of the EMV 4.3 specification?
  30. Can I reconfigure previously approved Application Contact Kernels?
  31. Is it possible to modify the EMVCo contract?
  32. What fees do EMVCo assess for the approval process and how are these payments made?
  33. What does EMVCo require when requesting that the Product Provider identifies the IFM, the PCD or Application Contact Kernel “as tested in”?
  34. How should I assign my IFM, PCD or Application Contact Kernel to an Identifier?
  35. Can you clarify the Test Report Validity Policy?
  36. How do I indicate the Terminal Type Description when submitting an Application Contact Kernel?
  37. How is approval of an IFM, PCD or Application Contact Kernel extended to other terminals not tested by EMVCo?
  1. Where can the Terminal ESD Evaluation be found?

    Details on Terminal ESD Evaluation and the related processes will be available on the EMVCo website in due course.

  2. Where can I find information on Payment Tokenisation Type Approval?

    EMVCo is currently working on Payment Tokenisation Specifications. In parallel the Type Approval processes and related test requirement will be defined. The time frame to complete this will be announced when available..

  3. What does the EMVCo Terminal Type Approval activity cover?

    EMVCo has written and published Test Requirements, Type Approval Administrative Processes and Test Cases for:
    -    Terminal Contact chip card interface: IFM (Level 1),
    -    EMVCo Level 2 Application Contact Kernel (Level 2),
    -    Contactless interface: PCD (Level 1),
    -    Contactless Product.

    EMVCo has furthermore accredited Tools implementing the Test Cases and Testing Laboratories to deliver testing services to terminal, IFM or PCD Product Providers and application providers. Finally, EMVCo issues a Letter of Approval for approved products.

  4. Where can the EMV Contactless specifications be found?

    The EMV contactless Specifications can be found within the Specifications section of the website. Please also check the EMVCo website for specific details on Contactless device testing and the related processes and requirements for obtaining test tools or information on recognized laboratories.

  5. How can I ask EMVCo to reissue a LoA?

    If as a result of a company name change, address change or contact change, EMVCo needs to re-issue an existing LoA on explicit request from the application provider, EMVCo will request an administrative fee per LoA re-issuance. The fee is described in the Administrative Process, or please contact the CATA secretariat terminal_approval@emvco.com for further information.

  6. I am an Accredited Laboratory and would like to open a new location, what should I do?

    The laboratory has to provide an updated Laboratory request for registration form which is provided on demand by CATA. Please contact the CATA secretariat terminal_approval@emvco.com for further information.

  7. Where can I find a list of Products that has been approved by EMVCo for Contact Level 1, Contactless Level 1, Contact Level 2 and Contactless Product?

    Regularly updated lists of Level 1-approved interface modules, Level 2-approved application kernels, Level 1-approved PCD and approved Contactless Products can be obtained from the EMVCo website (Type Approval section).

  8. What is an 'Application Contact Kernel'?

    An Application Contact Kernel is a software module, core, or library, forming part of a complete terminal application architecture that is developed for exclusive support of the EMV contact debit/credit functions and application requirements. Since Application Contact Kernels are functionally tested and approved by EMVCo as standalone components, they may be ported to other hardware platforms under certain conditions such as those sharing identical Operating Systems.

  9. What is an ‘EMVCo Contactless Kernel C-n'?

    It is a self-contained software Module compliant to one of the EMVCo Book C-n Contactless Specifications.

  10. What does ‘Application Contact Kernel testing’ mean?

    Application Contact Kernel testing is testing of the Application Contact Kernel Level 2 (according to EMV 4.3 books) in an EMVCo accredited laboratory. This kernel is the part of the terminal payment application that deals with EMV specific functions for contact transactions. Testing of payment scheme specific brand settings is the responsibility of the payment systems themselves.

  11. What does ‘Contactless Product testing’ mean?

    Contactless Product testing is the testing of EMVCo Terminal software built to Book A & B Specifications (Entry Point) containing an approved PCD and at least one of C-n Kernels in an EMVCo accredited laboratory. Contactless Product testing also involves Kernel Independency testing and Modular testing (if supported).  Note that for Contactless Product Type Approval, the approval and testing covers a complete Contactless Product and not components within this Product.

  12. When do I use the option “new” in the ICS Form?

    The option new in the ICS is to be used for the first ICS request or when resubmitting an ICS with no ICS reference issued in the first place due to ICS contents not being correct and therefore importation of data was not possible.

  13. When do I use the option “replacement” ICS Form?

    The option ”replacement” in the ICS is to be used when an ICS reference has already been generated and the ICS is to replace the previous issued ICS due to a change of information.

  14. If I am interested in purchasing a previously approved contact IFM, Contactless PCD or Application Contact Kernel from a Product Provider, how do I know that it will be compatible with my device?

    Those interested in purchasing approved components should contact the appropriate equipment provider directly to discuss price and compatibility. Previously approved components can be integrated into new hardware platforms, provided there are no changes made that could potentially have a negative effect upon the functionality of the component. Type Approval Bulletin #11 provides guidelines about the conditions under which a previously approved component can be integrated without requiring retesting by an EMVCo laboratory. This applies for Contact Level 1, Contactless Level 1, Contact Level 2 only as for Contactless EMVCo approval the complete Contactless Product is approved and not separate components.

  15. What are the definitions of ‘terminal’ and ‘interface module’ in the context of a fully integrated Contact POS system?

    The interface module (IFM) is defined in Book 1 of EMV 4.3, while the terminal definition is given in Book 3. These specifications are applicable to integrated POS, stand-alone POS or ATMs. Integrated POS systems may differ from other POS systems regarding software modularity. Some independent software modules may require association with other hardware or software modules before EMV compliance testing may begin.

  16. How can I become registered for EMV Contact Level 1, Contactless Level 1, Contact Level 2 or Contactless Product Type Approval?

    The Type Approval procedure is explained in the EMVCo Type Approval Terminal Contact Level 1, Contactless Level 1, Contact Level 2 or Contactless Product Administrative Process documents available from the EMVCo website and the registration forms are available .

    All forms should be completed and submitted electronically to: terminal_approval@emvco.com

  17. Do I need the support of an acquirer to submit a product for Type Approval?

    No, Terminal Application, Contact Kernel testing or Contactless Product testing can be performed independently from the acquirer infrastructure. Payment Scheme testing is separate from EMVCo testing.

  18. Is it possible to ‘self-certify’ an EMVCo compliant terminal?

    EMVCo does not recognize in-house approval testing. A Product Provider can nevertheless purchase test tools to perform in-house debug testing before being submitted to an EMVCo laboratory for formal testing. Some testing laboratories offer preliminary testing to debug the IFM, PCD, the Application Contact Kernel or the Contactless Product.

  19. Where can I find a list of EMVCo approved type accredited laboratories?

    A list of accredited laboratories can be obtained from the EMVCo website. Please note that some testing laboratories perform Contact Level 1, Contactless Level 2, Contact Level 2 and Contactless Product testing while others provide only one of the services.

  20. How can I obtain test tools to assist in the development of either an IFM, PCD, Application Contact Kernel or Contactless Product?

    Please contact the testing laboratories directly about the availability of test tools. A listi of laboratories can be obtained from the EMVCo website.

  21. Which laboratory should I use for Type Approval testing?

    Product Providers are free to select any accredited laboratory of their choosing. Since the services and associated costs of each laboratory will vary, the Product Provider is encouraged to contact multiple laboratories to discuss fees and availability of testing.

  22. How can I obtain an editable electronic copy of the Request For Approval (RFA) Form?

    An editable version of the Request For Approval form can be downloaded from the EMVCo website.

  23. Could you please advise the usual turnaround time for obtaining approval after the submission of an official Type Approval test result?

    EMVCo strives for a 2-week turnaround for approval requests after all pre-requisites (contract, approval requests, and payment) have been satisfied. Test result evaluation and approval notification will take longer if the test result evaluation identifies questions, incomplete tests, or test failures.

  24. Please identify the steps required for Terminal Type Approval?

    Please refer to the Administrative Process documentation for the steps necessary for Type Approval. The general process is as follows: Registration, Contract, Testing, Approval Request, Invoice & Payment, Test Result Evaluation, and Approval or Decline notification.

  25. I am a developer of POS terminals and would like to get approval from EMV. Besides getting terminal approval, can I get Card approval too?

    EMVCo manages terminal Type Approval, as per the Terminal Type Approval section on the EMVCo website and the Card Type Approval section on the EMVCo website.

  26. What is the cost of Type Approval testing?

    While EMVCo assesses certain administrative costs associated with the Type Approval process, the actual cost of testing varies, depending upon the laboratory used. Since the laboratories assess different fees for the services they provide, the Product Provider is encouraged to contact multiple laboratories. The geographic location of the laboratory may also be a consideration.

  27. How do I know if my device can become Contact Level 1, Contactless Level 1, Contact 2 or Contactless Product compliant?

    EMVCo cannot review or make recommendations concerning the compliance of your products. It is the responsibility of the Product Provider to review the appropriate technical specifications to ensure they meet all the requirements set by EMVCo. Any Product Provider should then be able to submit a product for testing and approval consideration with relative ease, provided they meet all the requirements set by EMVCo.

  28. Is it possible to combine different IFMs and Application Contact Kernels?

    IFMs and Application Contact Kernels are approved as independent functional components. It may be a minor change to combine previously approved components that may never have been used in combination before -- including components that may have been developed according to different versions of the EMV specification. For example, it is possible to use an EMV 4.2-compliant IFM in conjunction with an EMV 4.3-compliant Application Contact Kernel, provided that the combining of components does not require additional modifications that could negatively impact the functionality of either component. If an IFM and application kernel can be combined without requiring any of the modifications categorized as major for either component, the process of combining the components can be considered a minor change.

  29. Is it possible to combine contact components developed to different versions of the EMV 4.3 specification?

    Yes. You may use or submit components, that have been developed to different versions of the EMV specification, for Type Approval testing. For example, it is possible to submit an Application Contact Kernel for EMV4.3 Level 2 approval using an IFM that was previously approved to EMV4.2. There is no requirement that you upgrade your EMV4.2 IFM to be EMV4.3 compliant.

  30. Can I reconfigure previously approved Application Contact Kernels?

    EMVCo laboratories test only pre-defined configurations as per the Multiple Configuration Kernel (MCK) process. An Application Contact Kernel can be tested for one or more configurations. However, Application Contact Kernels can be used only with configurations that have been previously tested by an EMVCo laboratory. The number of potential configurations that can be supported depends upon whether the contact kernel was tested for single or multiple configurations.

  31. Is it possible to modify the EMVCo contract?

    EMVCo policy requires all Product Providers interested in EMVCo Type Approval to sign the same standard contract. Contract modifications for individual Product Providers are not possible. However, comments will be forwarded to EMVCo legal representatives for review and possible inclusion in any future contract revision.

  32. What fees does EMVCo assess for the approval process and how are these payments made?

    Registration is free of charge with EMVCo. However, each request for approval is subject to a Type Approval fee.

    EMVCo administrative fee for test result evaluation services depends on the Product submitted (Contact Level 1, Contactless Level 1, Application Contact Kernel or Contactless Product) and if it is an initial approval or a MCK (case of Application Contact Kernel) or a subsequent Submission (case of Contactless Product) or a renewal. Please check the fees structure in each corresponding Administrative Processes document.

    EMVCo will provide you with an invoice when receiving your completed Request For Approval form. Your invoice will contain payment details, such as account number and payment description to be used.

    EMVCo only accepts payments containing the correct payment description, as shown on your invoice.

  33. What does EMVCo require when requesting that the Product Provider identifies the IFM, the PCD or Application Contact Kernel “as tested in”?

    This designation is not part of the IFM or the PCD or Kernel identification. “As Tested In” provides linkage to the marketing name of the product within which the IFM, the PCD or Application Contact Kernel was actually tested. Note that when completing a Request For Approval, or Implementation Conformance Statement (ICS), the product name must not specify a series or range of terminals. If the components can be used in a series of devices, it is the responsibility of the Product Provider to maintain the necessary documentation linking additional devices to a previously approved component.

    It is mandatory that the specific model used during testing be identified on these forms. Not doing so may result in a delay of approval. All laboratories are required to report the specific terminal the IFM or Application Contact Kernel sample was tested in. This information should be presented within the test report, usually noted in Section III - Product Description, before the test case summary.

    Note that for Contactless Products the ‘as tested in’ does not exist as the Contactless Product Type Approval is for a complete Product and not for components within a Product.

  34. How should I assign my IFM, PCD or Application Contact Kernel to an Identifier?

    Product Providers should note that when assigning an ID to an IFM, a PCD or an Application Contact Kernel, characters that imply a range, series, or family of IFMs, PCDs or Application Contact Kernels are not allowed. This also extends to the “Version” description, as well.

    For example:

    Level 1 - IFM and Terminal Identification (EXAMPLE ONLY)
    Commercial Model # and IFM Name: Rocket 2xxx Version 1.x (Not Acceptable)
    Terminal Identification: Cool 1xxx Family (Not Acceptable)
    --------------------------------------------------------------------
    Commercial Model # and IFM Name: Rocket 2100 Version 1.0 (Acceptable)
    Terminal Identification: Cool 1100 (Acceptable)
    Note: Here the Terminal Identification is what will be noted in the “As Tested In” field.
    ==========================================
    Level 2 - EMV Application Contact Kernel Identification (EXAMPLE ONLY)
    Terminal Name and Model Number: Slider 3xxx Series (Not Acceptable)
    Application Name and Version: KillerApp WR** Version 2.x (Not Acceptable)
    --------------------------------------------------------------------
    Terminal Name and Model Number: Slider 3000 (Acceptable)
    Application Name and Version: KillerApp WR1B Version 2.2 (Acceptable)
    Note: Here the Terminal Name and Model Number is what will be noted in the “As Tested In” field.

    Product Providers should ensure that the approval request matches the description in the Implementation Conformance Statement (ICS). When in doubt, the data provided in the ICS is used as the primary source of information for the EMVCo website, and in the Letter of Approval.
  35. Can you clarify the Test Report Validity Policy?

    Test results can be submitted to EMVCo for evaluation up to 90 days from the date they are generated by the laboratory. Please note the first day for this validity period is the completion date of the testing, not when the report is printed by the laboratory, or when the Product Provider receives the report. Test results that exceed the 90-day validity period are considered expired and may not be submitted. Re-testing is required to create a current test report if the validity period is exceeded and EMVCo evaluation is desired.
  36. How do I indicate the Terminal Type Description when submitting an Application Contact Kernel?

    The terminal type description is to be indicated in “Part III-Terminal Resident Data Objects”, in the Level 2 Contact ICS.

    Description: This field should contain only one value, or multiple values, if the application kernel is being tested for multiple configurations. All supported values shall be declared.

    Note that this value should correspond to those details selected in the ICS under Part V - Terminal Details, which describe the type of terminal configuration being tested.

    Valid Terminal Types
      (Operational Control Provided by)
    (Environment)   Financial Institution Merchant Cardholder
    Attended         
      Online only 11 21 --
      Offline with online capabilities 12 22 --
      Offline only 13 23 --
    Unattended        
      Online only 14 24 34
      Offline with online capabilities 15 25 35
      Offline only 16 26 36
  37. How is approval of an IFM, PCD or Application Contact Kernel extended to other terminals not tested by EMVCo?

    EMVCo does not “extend” approvals to other terminals beyond the terminal, the IFM, the PCD or Application Contact Kernel was tested in. Please be advised that EMVCo does not approve contact terminals, but approves IFMs (Level 1) and Application Contact Kernels (Level 2). For Contactless EMVCo approves PCDs as component and Contactless Products (so contactless terminal) as a complete product including Hardware and EMVCo software.
    It is a Product Provider’s responsibility to provide proof to the acquiring community that their approved Application Contact Kernel or IFM or PCD is portable to other terminals. If a Product Provider finds it necessary to complete the approval process, only to list another terminal, they may do so. Please note, that in this case, a new Application Contact Kernel or IFM or PCD ID must be assigned, as EMVCo does not allow the same ID to be used for a subsequent request for approval.

    EMVCo does not list a formal process of how the Product Provider may “extend the usage of an EMVCo approved Kernel” outside of the normal EMVCo approval process.