Ambimat GroupAmbimatAmbiSecureSIMAuthAmbiAutomationEngineering BlogAhmedabad · India · Est. 1982
HISTORICAL ARCHIVE · Originally published August 28, 2020
Archive

Understanding EMV certification In Public Transportation

A practical look at EMV certification in public transport — which certifications apply, the roles of acquirer, scheme, terminal vendor, and transit authority, and the typical timeline from prototype to revenue service.

This is an earlier piece from the AmbiSecure engineering archive. Where the field has moved on, the link above points to current coverage of the same topic.

EMV Certification

EMV in transit is not a single certification. The scope depends on which acceptance model the operator picks, which schemes are accepted, and where the merchant boundary sits. This article walks through the applicable certifications, the roles of acquirer / scheme / terminal vendor / transit authority, and the realistic timelines from prototype to revenue service.

"EMV is designed to significantly improve the security for consumer card payments by providing enabling features for reducing fraudulent payment."

Four Key EMV Features

  1. Authentication of chip cards to prevent counterfeit fraud
  2. Risk management parameters defining conditions for chip card usage
  3. Digital signing of payment data for transaction integrity
  4. Enhanced cardholder verification against loss and theft

The Evolution of the EMV Specifications

The specifications began in 1994 through collaboration between Europay, MasterCard, and Visa. JCB joined in 2004, and American Express in 2009. Version EMV '96 was released in 1996, with production version 3.1.1 in 1998. The current version is 4.2 from 2008.

Three levels of EMV certification

  • Level 1 — Hardware: "The physical terminal, logic, and transmission of payments are tested."
  • Level 2 — Software Kernel: "The software written to facilitate the transfer of payment information is tested."
  • Level 3 — Application: "Each card brand is tested against the entire processing solution."

EMVCo, composed of six member organizations, manages specifications and certifies Levels 1 and 2 only.

Who is Ambimat Electronics?

Close to 4 decades of design experience as a solution provider for payment products and IoT development across smartwatches, smart homes, medical devices, robotics, retail, and security.

Looking for the current take?

This archive piece reflects thinking from August 28, 2020. For a current-generation treatment of the same topic, see our modern coverage.

Read the current article

Frequently asked questions

Is EMV certification in transit a single certification?

No. EMV in transit is not one certification — the scope depends on which acceptance model the operator picks, which card schemes are accepted, and where the merchant boundary sits.

Who is involved in an EMV transit certification?

Four parties share the work: the acquirer, the card scheme, the terminal vendor, and the transit authority. The split between them determines the timeline from prototype to revenue service.

How does open-loop EMV sit alongside closed-loop transit cards today?

The EMV Contactless Transit Specification has matured, and most major networks now accept open-loop EMV alongside their closed-loop DESFire systems rather than replacing them.

What are the four key features EMV brings to card acceptance?

Authentication of the chip card to prevent counterfeit fraud, risk-management parameters defining the conditions under which the chip may be used, digital signing of payment data, and the broader security features that reduce fraudulent payment.

What drives the certification timeline from prototype to revenue service?

Where the merchant boundary sits and how many schemes are in scope. Each additional acceptance model and scheme adds its own test scope across the acquirer, the terminal vendor and the transit authority.

Browse more historical AmbiSecure writing.

The full archive lists everything we have published, with the modern-equivalent counterpart linked wherever one exists.

Open archive