Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
4.7.4.1 Transaction Data<br />
The “Fare Transaction” UD record is generated by card reader devices and can be<br />
considered the equivalent <strong>of</strong> the “Farecard Usage Transaction” as proposed by the<br />
WG4. Different subtypes <strong>of</strong> the Fare Transaction record are defined as follows:<br />
• Single-tag fare payment, ride destination unknown<br />
• Dual-tag entry transaction,<br />
maximum fare deducted (purse debit)<br />
• Dual-tag exit transaction,<br />
fare adjustment (purse rebate)<br />
• Dual-tag entry transaction, no fare deduction<br />
• Dual-tag exit transaction, fare payment<br />
• Single-tag fare payment, known ride destination<br />
Two record subtypes are defined for a single-tag system. One subtype is generated<br />
when<br />
the reader does not know the destination, and the other subtype is generated<br />
when the reader device obtains the destination location from either the driver console<br />
or the patron.<br />
Using<br />
a card in a dual-tag system results in two Fare Transaction UD records being<br />
genera ted. A dual-tag entry transaction (maximum fare deducted) record is generated<br />
at the start <strong>of</strong> a ride on an open two-tag system, with a matching dual-tag exit<br />
transaction (fare adjustment) record being generated at then end <strong>of</strong> the ride. Similarly, a<br />
dual-tag entry transaction (no fare deduction) record will be generated at the start <strong>of</strong> a<br />
ride on a closed-barrier two-tag system, matched by a dual-tag exit transaction (fare<br />
payment) record at the end <strong>of</strong> the ride.<br />
An “Add Value Transaction” UD record, the equivalent <strong>of</strong> WG4 proposed Add Value<br />
Transaction Data message, is generated by all devices that add value to TransLink<br />
cards. The following record subtypes reflect the variances in the payment method:<br />
• Cash payment at a Ticket Office Terminal (TOT) or Add Value Machine (AVM)<br />
• Check payment at a TOT<br />
• Credit card payment at a TOT or AVM<br />
• Debit card payment at a TOT or AVM<br />
• Periodic Autoload at a reader device<br />
• ThresholdAutoload at a reader device<br />
• Remote re-load at a reader device<br />
• Remote load <strong>of</strong> a new pass or ride book at a reader device<br />
Tra L udit register snapshots. Audit<br />
gisters are non-resettable counters and accumulators used within the TransLink ®<br />
ns ink<br />
it<br />
® also provides a separate message type for a<br />
re<br />
system to give an independent method <strong>of</strong> verifying UD <strong>com</strong>pleteness. Different aud<br />
register snapshot subtypes are defined as follows:<br />
• CID audit registers<br />
Page 53
Change language