Get Receipt
Sign up

Format spec

Taxi and rideshare trip receipt template

Origin and destination with timestamps, distance, duration, and an itemised surcharge stack.

This is a generic industry format — the printing convention, not any company’s trade dress. You supply your own business identity; Get Receipt supplies the grid it prints on.

Open this format in the makerEvery format

Physical spec

Paper
58 mm thermal roll
Roll or sheet width
57.5 mm
Printable width
48 mm
Horizontal dots
384
Head density
203 dpi (8 dots/mm)
Characters per line
32 (ESC/POS Font A)

The character grid is the printer’s, not an approximation: at 203 dpi a Font A cell is 12 × 24 dots, so 384 dots of printable width is exactly 32 characters. Anything you render has to land on integer dot multiples or the edges blur.

Ordered field list

Top of the document to the bottom. This is the order a reader expects and the order a scanner, a bookkeeper or a returns desk looks for.

  1. 1.Operator or driver name
  2. 2.Medallion or vehicle identifier
  3. 3.Trip identifier
  4. 4.Pickup address and time
  5. 5.Dropoff address and time
  6. 6.Distance
  7. 7.Duration
  8. 8.Base fare
  9. 9.Distance charge
  10. 10.Time charge
  11. 11.Booking fee
  12. 12.Airport surcharge
  13. 13.Tolls
  14. 14.Congestion surcharge
  15. 15.Subtotal
  16. 16.Local taxes and fees
  17. 17.Tip
  18. 18.Total
  19. 19.Masked payment method

Alignment

Label-and-value pairs, values right-flush.

Tax convention

Local taxes and fees after the fare subtotal. Tolls passed through at cost are typically not a taxable fare component.

Tender

Card or wallet, with the last four digits.

Machine-readable code

None on tape; the document version may carry a route map instead.

How to recognise it

  • Origin and destination pair with timestamps
  • Distance and duration together
  • Itemised surcharge stack
  • Tip after the tax line

Get Receipt renders this as Taxi / rideshare trip receipt

In-car printer format: fare, time-and-distance and fees broken out, trip QR at the foot. Every total is recomputed by the engine from the line items, so the printed lines always sum to the printed total — the one thing generated receipts most often get wrong.