...
This section explains how to can create and modify application identifiers (AIDs) and associate them with TLV Groups in the reader's memory for specific types of transaction handling. Detailed descriptions of the configurable application identifier (CONAID) commands are also included.
Each AID uniquely identifies a payment application. The reader has default AIDs that are preconfigured to support common payment applications. These AIDs are called System AIDs and they can be modified or disabled, but not deleted. Readers also support up to eight user-defined AIDs called User AIDs.
Each AID must be associated with a TLV Group that defines transaction processing for that payment application. The System AIDs are initially associated with a default TLV Group (called Group 0), which can be modified but not deleted. User AIDs can be associated to with the default TLV Group or any of seven other user-defined TLV Groups.
With the implementation of M/Chip 3.0, an additional default TLV Group (Group 80 for NEO II or Group 1 for NEO product) has been added. M/Chip 3.0 does not use the Reader Default Group (Group 0).
All AIDs must be unique. The reader's default configuration is based on System AIDs and two default groups. All of the System AIDs (except PayPass AIDs, as noted above) initially refer to the default TLV Group 0. The diagram below shows the default reader AID configuration.
The configurable application identifiers feature of the ViVOpay readers allows users to create and customize AIDs and the TLV Groups associated with them. Each AID may have characteristics that are unique and different from the reader's default System AIDs and TLV Group configuration.
To create a new configurable AID, send to the reader both:
...