PCI Watch

Tracking changes across the Payment Card Industry

SB nº 118: Clarification on the Definition of Payment System (Spec Change)

v1.0 Specification Bulletins
Contact

Specification Bulletin No. 118 First Edition December 2012 Clarification on the Definition of Payment System This Specification Bulletin clarifies the meaning of “Payment System” within the context of Payment System specific range of tags in the EMV Specifications.

Applicability

This Specification Update Bulletin applies to:

  • EMV Integrated Circuit Card Specifications for Payment Systems Version 4.3

Related Documents

None

Description

This Specification Bulletin clarifies the meaning of “Payment System” within the context of Payment System specific range of tags in the EMV Specifications. Specification Change In EMV 4.3 Book 3, modify the last five bullets in section B1 prior to section B2 from:

  • The coding of primitive context-specific class data objects in the range '9F50' to '9F7F' is reserved for the payment systems.
  • The coding of tag 'BF0C' and constructed context-specific class data objects in the range 'BF20' to 'BF4F' is reserved for this specification.
  • The coding of constructed context-specific class data objects in the ranges 'BF10' to 'BF1F' and 'BF50' to 'BF6F' is reserved for the payment systems.
  • The coding of constructed context-specific class data objects in the ranges 'BF01' to 'BF0B', 'BF0D' to 'BF0F', and 'BF70' to 'BF7F' is left to the discretion of the issuer.
  • The coding of primitive and constructed private class data objects is left to the discretion of the issuer. to:
  • The coding of primitive context-specific class data objects in the range '9F50' to '9F7F' is reserved for the payment systems. Payment system-specific tags are interpreted within the context of the application RID.
  • The coding of tag 'BF0C' and constructed context-specific class data objects in the range 'BF20' to 'BF4F' is reserved for this specification.
  • The coding of constructed context-specific class data objects in the ranges 'BF10' to 'BF1F' and 'BF50' to 'BF6F' is reserved for the payment systems. Payment system-specific tags are interpreted within the context of the application RID.
  • The coding of constructed context-specific class data objects in the ranges 'BF01' to 'BF0B', 'BF0D' to 'BF0F', and 'BF70' to 'BF7F' is left to the discretion of the issuer. Issuer-specific tags are interpreted within the context of the Issuer Identification Number (as defined in ISO/IEC 7812-1). Additionally, to satisfy business requirements such as proprietary domestic processing, multiple issuers may agree on the definition of a private class tag. Such tags may be interpreted in the context of other data such as Issuer Country Code.
  • The coding of primitive and constructed private class data objects is left to the discretion of the issuer. Issuer-specific tags are interpreted within the context of the Issuer Identification Number (as defined in ISO/IEC 7812-1). Additionally, to satisfy business requirements such as proprietary domestic processing, multiple issuers may agree on the definition of a private class tag. Such tags may be interpreted in the context of other data such as Issuer Country Code.