All Classes and Interfaces
Class
Description
The balance of blocks 8 and 9, in thousandths of a euro.
Everything a dump of one card holds.
A date as the card packs it into two bytes: 7 bits of year since 2000, 4 bits
of month and 5 bits of day.
A
CardDate followed by a time of day, five bytes in total: the packed
date, then hour, minute and second as plain binary.Thrown when a block does not hold what the card specification says it should:
a wrong length, a checksum that does not match, a field outside its range or
a value no known product uses.
The card id printed on the plastic, which block 2 holds as two letters and
one decimal digit per nibble, such as
BE322743.The products these cards come as, which bytes 0 to 2 of block 1 tell apart.
A MIFARE Classic variant one of these cards is built on.
Direction of a journey along its route, byte 8 of a transaction: the operator
GTFS
direction_id plus one.The blocks of a card, one after another, as MIFARE Classic Tool or a Proxmark
writes them.
Fills the blocks of a dump one at a time, leaving the untouched ones zeroed.
A structure the card stores as bytes.
Block 10 of a top up card, which the card rewrites on every journey and
leaves alone on a top up.
When the last paid journey happened, which the card records to the minute.
A route and the direction travelled along it.
A six byte MIFARE Classic sector key.
One subscription product of a personal card, which lives in a sector of its
own.
Route id of the operator's GTFS feed, byte 7 of a transaction.
The two keys of one sector.
Where a transaction happened, bytes 5 and 6 of a transaction.
A stop of an operator other than the urban buses and the tram.
A tram stop, whose number the card stores multiplied by one hundred.
An urban bus stop, which the operator numbers internally.
Block 13 or 17 of a personal card, which the card copies into block 14 or 18.
Block 12 or 16 of a personal card, which describes one subscription product
the card carries.
One record of the transaction log: a journey or a top up, with where and when
it happened.
Collects the fields of a
Transaction one at a time, which reads
better than a constructor of ten arguments and cannot mix up the counters
that sit next to each other.What a transaction record stands for, which byte 8 tells: a journey or a top
up.
A ride, paid out of the balance or free as a transfer.
Money added to the balance.
The ring of six blocks a card keeps its last transactions in: block 5 holds
the newest record, and the five before it live in the archive blocks, each in
the slot its sequence byte picks.
The UID of block 0, whose length depends on the chip the card is built on.