Tools Beta

Contactless Entry Point Simulator

Enter the reader's combinations and the card's PPSE response to see, step by step, how Entry Point pre-processes the transaction, builds the candidate list, selects the candidate and activates a kernel. Every decision is linked to its requirement in EMV Contactless Book B v2.11.

Why this simulator splits Start C in two

In this simulator, Combination Selection (Start C of EMV Contactless Book B) is split into two sub-steps:

  • Build the candidate list: SELECT PPSE and building the candidate list.
  • Select the candidate: final combination selection.

This approach gives more flexibility during the selection process, in particular for markets such as the European Economic Area. An EMV Level 3 implementation should be able to opt out of certain applications, or map a specific AID to a specific Kernel ID, between these steps of the selection process.

Unfortunately, this need is not specified by nexo FAST, and EMVCo defines no formal API for Entry Point to guide its design. Implementers may only discover it late, when they integrate an EMV Level 2 library into their payment application. Book B itself only notes that, where business agreements allow, specific applications may be eliminated from consideration either during or after building the candidate list. See also Why APIs Matter in EMV.

Olivier Chauvineau, from field experience with EMV Level 2 and Level 3 integrations.

Scenario

In currency units, for example 25.00.
How a missing or 0 priority ranks against F. The Visa and Amex rule applies to Visa and Amex AIDs only.
Reader combinations {AID – Kernel ID} with their Entry Point configuration Leave a limit or the TTQ empty when it is not configured: Book B treats "not present" differently from zero.
The data field returned by the card, starting with 6F. Open it in the TLV parser.

About this simulator

What it covers

The Entry Point decisions of EMV Contactless Book B v2.11: Pre-Processing (Start A), Combination Selection split into building the candidate list and selecting the candidate (Start C), and Kernel Activation (Start D), with the Try Another Interface and End Application outcomes. It does not run the kernel itself.

Simulated card responses

The card answers to SELECT (AID) are simulated: for each candidate you can choose a successful response or an error status word. For a Visa AID on Kernel 3 only, you can also choose a PDOL that does not request the TTQ (9F66), the case covered by requirement 3.3.3.6. This lets you see how Entry Point removes a candidate and returns to Start C.

Priority 0 or absent

Book B v2.11 treats an Application Priority Indicator of 0, of F, or no indicator at all as the same lowest priority, and the earliest PPSE entry breaks the tie. In practice, Visa and American Express rank 0 or no priority below F for their own applications. Choose the rule in the scenario to see the difference; the preset "Visa with no priority vs Mastercard with F" shows it.

What it assumes

Payment systems are recognised from the RID of the reader AID, for the default kernel of Table 3-6. If the card asks for terminal information (9F3E or 9F3F), the SEND POI INFORMATION step is not simulated and the PPSE list is used as is. Issuer responses at Start B and Start D are out of scope.

Your data

Everything runs in your browser. Nothing you enter is sent anywhere. Use test data.