MTA Bulletin nº 37: Mobile L1 Process Update

2024-02-28T00:00:00+00:00 v8.0 Type Approval Bulletins

ContactlessMobile NFC Consumer Device

EMV® Mobile Type Approval Bulletin No. 37 Eighth Edition, February 2024 Mobile L1 Process Update This bulletin informs of updates made to the Mobile L1 Type Approval Process

Applicability

This Bulletin applies to the Mobile L1 Type Approval process

Effective Date

March 1, 2024

Description

The Mobile L1 Approval process has been updated to introduce the testing against EMV Level 1 Specifications for Payment Systems

EMV Contactless Interface Specification Version 3.2. Other process updates have been introduced as well. As a reminder, the introduction of the Analogue and Digital Test Cases v3.2a has already been made in the Card Type Approval Bulletin No. 39 published in January 2024. The introduction of the Mobile L1 Test Guidelines version 3.2a has been made in the previous version of this Approval Bulletin also published in January 2024. The following documents available on the EMVCo website are impacted by this testing update: Mobile L1 Administrative Process v2.7: This document was updated to:
Update the version of applicable EMVCo documents,
To formally require that by default, an active mobile product shall support both Type A and Type B. Passive mobile product may support only one Protocol Type
To remove the Performance Testing requirement per Approval Bulletin 43
To clarify the use case where multiple Laboratories are involved in an approval,
To clarify the validity of an ICS and the maximum time to complete an approval,
To let the Product Provider choose the Initial Execution Environment (Initial EE) on which analogue and interoperability testing will be performed,
To clarify the test requirements in case of major change made to a product.
To remove the card profile A1’, B1’ and AB’ in the Analogue and Digital UICC kit. Mobile L1 Test Application Requirements v2.0.2: This document was updated to remove the card profile A1’, B1’ and AB’ and to update the GET DATA Response. Implementation Conformance Statement v3.2a: This document was updated to:
To reference the new specification version
To clarify the form when the product is a non-card L1 form factor
To introduce the selection of the initial EE by the Product Provider
To introduce minor editorial updates.
To remove the card profile A1’, B1’ and AB’ in the Analogue and Digital UICC kit. Mobile L1
Validation and Interoperability Testing Requirements v1.6: This document was updated to:
Add references to the initial EE selected by the Product Provider,
To add eUICC Execution Environment,
To document the case where the Reference Mark is not on the Presentation Plane,
To provide instruction for non-card L1 form factors. Test activation planning: Testing against the new EMV Level 1 Specifications for Payment Systems
EMV Contactless Interface Specification Version 3.2 will be activated on March 1, 2024, and will become mandatory on September 1, 2024 as announced in the latest version of Card and Mobile Type Approval Bulletin No. 031. For additional information, please contact EMVCo CATA Secretariat at card_approval@emvco.com.

Legal Notice

This document summarizes EMVCo’s present plans for evaluation services and related policies and is subject to change by EMVCo at any time. This document does not create any binding obligations upon EMVCo or any third party regarding the subject matter of this document, which obligations will exist, if at all, only to the extent set forth in separate written agreements executed by EMVCo or such third parties. In the absence of such a written agreement, no product provider, test laboratory or any other third party should rely on this document, and EMVCo shall not be liable for any such reliance. No product provider, test laboratory or other third party may refer to a product, service or facility as EMVCo approved, in form or in substance, nor otherwise state or imply that EMVCo (or any agent of EMVCo) has in whole or part approved a product provider, test laboratory or other third party or its products, services, or facilities, except to the extent and subject to the terms, conditions and restrictions expressly set forth in a written agreement with EMVCo, or in an approval letter, compliance certificate or similar document issued by EMVCo. All other references to EMVCo approval are strictly prohibited by EMVCo. Under no circumstances should EMVCo approvals, when granted, be construed to imply any endorsement or warranty regarding the security, functionality, quality, or performance of any particular product or service, and no party shall state or imply anything to the contrary. EMVCo specifically disclaims any and all representations and warranties with respect to products that have received evaluations or approvals, and to the evaluation process generally, including, without limitation, any implied warranties of merchantability, fitness for purpose or non-infringement. All warranties, rights and remedies relating to products and services that have undergone evaluation by EMVCo are provided solely by the parties selling or otherwise providing such products or services, and not by EMVCo, and EMVCo will have no liability whatsoever in connection with such products and services. This document is provided "AS IS" without warranties of any kind, and EMVCo neither assumes nor accepts any liability for any errors or omissions contained in this document. 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. EMVCo makes no representations or warranties with respect to intellectual property rights of any third parties in or in relation to this document. EMVCo undertakes no responsibility to determine whether any implementation of this document may violate, infringe, or otherwise exercise the patent, copyright, trademark, trade secret, know-how, or other intellectual property rights of third parties, and thus any person who implements any part of this document should consult an intellectual property attorney before any such implementation. Without limiting the foregoing, this document may provide for the use of public key encryption and other technology, which may be the subject matter of patents in several countries. Any party seeking to implement this document is solely responsible for determining whether its activities require a license to any such technology, including for patents on public key encryption technology. EMVCo shall not be liable under any theory for any party's infringement of any intellectual property rights in connection with this document.

Applicability

Related Documents

Effective Date

Description

Legal Notice