SB nº 130: Autorun as Implementation Option (Spec Change)

v1.0 Specification Bulletins
Contactless

Specification Bulletin No. 130 First Edition August 2013 Autorun as Implementation Option This Specification Bulletin proposes a change to the EMV Contactless Specifications, version 2.3, Book A, namely to make the Autorun functionality an implementation option.

Applicability

This Specification Update Bulletin applies to:

  • EMV Contactless Specifications for Payment Systems, Book A: Architecture and General Requirements, version 2.3

Related Documents

  • Other volumes of the EMV Contactless Specifications for Payment Systems, version 2.3

Description

The Autorun parameter is a configuration parameter of the POS System used to determine one of the following behaviours: 1. The field is kept on between transactions. A transaction is started automatically when a card enters the field. (Autorun = “Yes”). 2. The field is off between transactions. Transactions need to be initiated to take place, e.g. the merchant enters the amount (Autorun = “No”). This bulletin makes the support of the Autorun parameter optional for terminal vendors. If the parameter is not supported, The behaviour of the system will be the same as for a setting of

Proposed Specification Change Book A Specification Change Apply the following change to Section 5.6.2:

5.6.2 POS System Configuration for Starting a Transaction The POS System must be configured such that a contactless transaction is either initiated by terminal action or starts automatically after the previous transaction has completed. The configuration parameter is Autorun [No, Yes]. Support for the Autorun parameter is optional. If the Autorun parameter is not supported, then the POS System must function as if the value of Autorun is "No". If the value of Autorun is “No”, then the transaction start is initiated by the merchant, typically by entering the amount. If the value of Autorun is “Yes”, then the transaction start is when a card enters the polling field and responds, indicating its presence. In general “No” is for environments supporting EMV mode transactions, where the terminal needs to know the amount before starting a transaction, the field is off between transactions, and the reader is dependent on and under control of the terminal. “Yes” is generally for environments supporting mag-stripe mode transactions, where the field is on between transactions, and the reader does not depend on the terminal and initiates contactless transactions independently. Depending on the acceptance environment, the Autorun parameter is not constrained as above. For example, environments supporting EMV mode transactions with a fixed amount and field on between transactions could use Autorun “Yes” and environments supporting mag-stripe mode transactions with manual start and field off between transactions could use Autorun