These codes are present in the de022 field (POS entry mode) in some Authorization Events API webhooks and the Create Simulated Card Authorization endpoint. The de022 field must be enabled by request in the Events API webhooks and in the RDFs.
Positions 1–2
In the RDFs these codes are in the POS ENTRY MODE field.
| Code | Description |
|---|---|
| 00 | Unspecified |
| 01 | Manual |
| 02 | Contactless transaction originated using a mobile device emulating a magnetic-stripe read (magnetic-stripe emulation). Transaction may or may not be tokenized. |
| 03 | Bar code |
| 04 | OCR |
| 05 | Contact-chip transaction originated using chip-data rules. |
| 06 | Manual (key-entered) |
| 07 | Contactless chip transaction originated using chip-data rules. Transaction may or may not be tokenized. |
| 08 | Reserved for ISO use |
| 09 | PAN entry via electronic commerce, including remote chip (for chip-secured remote-payment transactions). |
| 10 | Credentials on file |
| 11–60 | Reserved for ISO use |
| 61–78 | Reserved for national use |
| 79 | Chip card or chip-capable terminal was unable to process the transaction using the data on the chip or magnetic stripe; the PAN was entered manually or the acquirer is not certified to process the value 80. |
| 80 | Chip card or chip-capable terminal was unable to process the transaction using the data on the chip; the PAN was entered via magnetic stripe. The full track data was read from the data encoded on the card and transmitted within the authorization request on Track 2 data (DE035) or Track 1 data (DE045) without alteration or truncation. |
| 81 | Manual PAN entry via electronic commerce. |
| 82 | Auto PAN entry via server (issuer, acquirer, or third-party vendor system). |
| 83–89 | Reserved for private use |
| 90 | Full magnetic stripe read and exact content of Track 1 and Track 2 is included (CVV check is possible). The Common AID must be present on the chip, which may reside in a mobile device or a card, and full chip data will be present in the transaction. Transaction may or may not be tokenized. |
| 91 | Contactless chip transaction originated using magnetic stripe data (MSD). Transaction may or may not be tokenized. |
| 92–94 | Reserved for private use |
| 95 | Integrated circuit card, CVV data may be unreliable due to absence of track data or failure to meet other requirements. |
| 96 | Stored value from pre-registered checkout service |
| 97–99 | Reserved for private use. |
Position 3
In the RDFs this code is in the PIN ENTRY CAPABILITY field.
| Code | Description |
|---|---|
| 0 | Unspecified |
| 1 | PIN entry capability |
| 2 | No PIN entry capability |
| 6 | PIN pad inoperative |
| 8 | Terminal has PIN entry capability but PIN pad is out of service |
| 9 | PIN verified by terminal device |