PROTOCOL_RFCARD_TYPE_A, PROTOCOL_RFCARD_TYPE_B, PROTOCOL_T_0, PROTOCOL_T_1, PROTOCOL_UNKNOWN, STATUS_ABSENT, STATUS_CONNECTED, STATUS_DISCONNECTED
Modifier and Type | Method and Description |
---|---|
ATR |
connect()
connect to the card and return the ATR information.
|
void |
disconnect()
disconnect the card.
|
byte[] |
transmit(byte[] apdu)
Sends a data buffer to the card reader.
|
byte[] |
transmit(byte[] apdu,
int operation)
Transmit command of level 3 and get the response.
|
getCardStatus, getID, getProtocol
ATR connect() throws DeviceException
DeviceException
- for the standard reasons that are documented in DeviceException
.void disconnect() throws DeviceException
DeviceException
- for the standard reasons that are documented in DeviceException
.byte[] transmit(byte[] apdu) throws DeviceException
In the context of standard EMV or ISO T=0/T=1 asynchronous cpu cards,
the format of the data in buffer
must respect the APDU
format defined by the ISO 7816-4 and EMV specifications. If the data
cannot be processed because it does not respect the standard APDU
formats
ISO 7816-4 case 4 APDUs used with T=0 cpu cards are automatically
converted into an appropriate sequence of TPDUs, consistent with the
current operating mode (EMV or ISO).
All the response data, resulting from a given
APDU command that was transmitted to the card, are automatically
entirely retrieved, stored and made accessible to the application
thru the resulting completion event (sequence of "get-response" card
command is automatically processed when applicable).
apdu
- data buffer to be transmittedDeviceException
- for the standard reasons that are documented in
DeviceException
and also:
ON
byte[] transmit(byte[] apdu, int operation) throws DeviceException
apdu
- data buffer to be transmitted.operation
- reserved for future, must be set to zero.DeviceException
- for the standard reasons that are documented in
DeviceException
and also:
ON