← back
entry no. 02 · the longer version

how it actually works

reading the bill

the photo is shrunk on your phone before it goes anywhere — long side 1,400 pixels, which is enough to read thermal print and a tenth of the cost of sending the raw camera file. it goes to a vision model once, comes back as lines, and is thrown away. nothing keeps the image.

then hissa makes you look at it. the model is good, not perfect, and one wrong digit becomes a real argument at the table. correcting three fields is cheap; disputing a settled bill is not.

when the lines don't add up to the printed subtotal, hissa says so instead of pretending.


claiming by portion

a line for seven wraps at 6,790 tapped by seven people is 970 each. tapped by two people where one had two wraps, it's split by portions, not heads.

rounding always resolves: the last claimer on a line absorbs the remainder, so the parts add back to exactly what was printed. a group can't accidentally under-cover a line, whoever tapped it.


tax, discount, tip

gst applies to the subtotal. discount and tip both apply after gst. your own number is your share of the subtotal, scaled up to the final total — so everything rides along in proportion to what you ordered.


who you are

your name, lowercased and trimmed. Faraz, faraz and  FARAZ  are one person, which is what makes rejoining from a second phone or after a refresh free.

the catch is honest and visible: two real people called faraz at the same table will land on one record, and you'll see it happen rather than find out later.


what the code can and can't do

let anyone at the table open the split and claim their own items.

keep out someone who has the code. treat it like the bill itself — it's on the table, not in a safe.

twenty-four hours, then the code stops working and the bill is gone.

once a split is open the bill can't be edited. a forgotten item means a second split.

split a bill →