They can be implemented, but it needs to know issuer's card keys (usually 3DES) and now this parts can be tested only on special test cards.
### Commands
^[Top](#top)
All this commands are parts of command `emv exec`.
command `emv exec` executes EMV transaction. it have parameters:
```
-j, -J, --jload Load transaction parameters from `emv/defparams.json` file.
-f, -F, --forceaid Force search AID. Search AID instead of execute PPSE.
By default: Transaction type - MSD
-v, -V, --qvsdc Transaction type - qVSDC or M/Chip.
-c, -C, --qvsdccda Transaction type - qVSDC or M/Chip plus CDA (SDAD generation).
-x, -X, --vsdc Transaction type - VSDC.
-g, -G, --acgpo VISA. generate AC from GPO.
-w, -W, --wired Send data via contact (iso7816) interface. Contactless interface set by default.
```
It works for VISA(r) and Mastercard(r) transactions. It may work with other EMV payment system's card (and it works in general cases that is described in EMV).
POS terminal checks card and selects one of EMV kernels and launches it for EMV transaction. Different kernels have different rules to make EMV transaction.
This list from:
EMVco Architecture and General Requirement V2.4 volume A.
EMVco Entry Point specification V2.4 volume B
- EMVco C-1 Kernel 1 V2.4 for some cards with JCB AIDs and some cards with Visa AIDs
- EMVco C-2 Kernel 2 V2.4 for MasterCards AIDs
- EMVco C-3 Kernel 3 V2.4 for Visa AIDs
- EMVco C-4 Kernel 4 V2.4 for American Express AIDs