N NoBullshit.wiki 中文

Tobacco & liquor store cashier - large-payment confirmation SOP - bills through the detector twice, wire transfers honored only on bank credit entries, QR payments verified on the arrival screen against amount and payer, and "we overpaid, refund the difference" refused on the spot and escalated; the definition of "money arrived" gets nailed down

Works with:Claude / GPT-4 classCategories:Tobacco & Liquor StoreLevel:Beginner Updated

You are a cashier trainer for a tobacco & liquor
store. Write an archivable "Large-Payment
Confirmation SOP" for counter staff to execute as
written. Context: tickets of several thousand are
routine, and the minutes spent taking payment
concentrate the risk - counterfeits, faked
transfer slips, delayed-settlement reversals,
third-party payment games. All of them hunt big
tickets.

Trigger: any single ticket above the
[large-payment line] - cash, wire, or QR. Below
the line, routine handling applies; no extra
burden on ordinary sales.

1. Cash
- Bills through the counterfeit detector twice,
  once per side (premium counterfeits often
  beat single-sided detection)
- Any discrepancy between the two passes -
  count mismatch or a rejection: pull that
  note, ask for another or switch to transfer.
  No on-the-spot argument about authenticity;
  the line is "this one won't pass the
  machine, please swap it"
- Hand-check the large denominations: intaglio
  texture, watermark against light - machine
  plus fingers, both barriers
- State the amount aloud as received:
  "That's X received, Y change" - one slipped
  digit in change on a large ticket is
  hundreds

2. Wire transfer (the main anti-fake-arrival
front)
- Payment exists only as: a bank credit entry,
  or the payment platform's own arrival
  notification. None of the following count:
  a transfer screenshot (forgeable), a
  "transfer successful" page (reversible on
  delayed-settlement channels), an SMS alert
  (styles can be faked)
- Customer shows a screenshot and urges
  release: "We go by cleared funds - usually
  minutes. Have a seat." Goods stay packed,
  nobody steps off, delivered in the same even
  tone you'd use for the weather
- Ten minutes, nothing arrived: "Networks run
  slow today - the moment it lands we'll hold
  your stock. Go take care of things." No
  accusation, and the ticket stays un-paid
- A small sign at the register - "This store
  releases goods on cleared funds only" - lets
  the rule exist before any dispute does

3. QR payment
- The arrival screen is mandatory: amount,
  time, payer name - all three checked before
  the ticket counts. The notification chime
  alone is not payment (chimes can be faked by
  spoofed apps)
- Payer name differs from the buyer: someone
  running an errand for family will say so
  unprompted; vague answers under questioning
  mean escalate before release - the cashier
  does not clear it

4. Funds flowing backward: always refused, no
exceptions
- Any shape of "we overpaid / front this for
us / refund the difference to the driver or
the finance person / send it back as a test" -
however reasonable the story, the action is
one word: decline
- The line: "Ask them to reverse the excess at
the source - we only accept the invoice
amount, and we can't move other people's
money"
- Pressure after the refusal: escalate to the
manager, ticket suspended. Cashiers hold no
release authority over reverse flows - this
is fixed, not negotiable

5. After payment
- Large-payment log: time, amount, method,
  payer, handler - one line per ticket
- Cash above the [seal threshold] goes into
  the safe as it accumulates; it never pools
  across shifts or sits overnight

Red lines:
- "The money's not here yet but they look in
  a hurry" is not a release reason - hurry is
  practically the standard equipment of
  large-ticket fraud
- The cashier never operates a
  pay-first-refund-later money movement, for
  any reason
- Two detector passes are never cut to one -
  rushing, a pressing customer, and closing
  time are all not reasons

Why it is written this way

The whole SOP defines exactly one thing: what "the money arrived" means. Nailing that definition to bank credit entries and official platform notifications automatically demotes everything else - screenshots, "success" pages, chimes, SMS - from payment to theater. Every large-ticket script aimed at this trade is built on blurring that definition: each "looks paid" moment the con manufactures is an invitation for the cashier to treat a display as a payment. The SOP doesn't ask the cashier to spot fake screenshots (impossible); it asks them to recognize one form of proof (possible). Swapping an unverifiable task for a verifiable one is the only way a front-line standard actually holds.

The backward-flow ban is written as absolute because it guards the only scam family where the store immediately loses real money: in overpay-and-refund plays, the incoming transfer is reversible or dirty, and the refunded difference is gone for good. The stories are always reasonable - finance slipped a digit, the driver is waiting, just a test - so the defense cannot rest on judging stories; it rests on an action ban. Cashiers aren't authentication experts, and a ban outperforms expertise every time. "Looks in a hurry" is inverted into a red line for the same reason: hurry is essentially the only stable emotional signature of large-ticket fraud - genuine buyers of expensive bottles comparison-shop, hesitate, and come back tomorrow; only someone spending fake money fears the long night.

Two-pass screening and three-point arrival checks are deliberately confined to tickets above the line - a payment SOP most often dies of being applied to everything. If every coffee-money sale needs double screening, staff will skip it under pressure and the standard collapses wholesale. Loading the cost onto the transactions that actually carry the risk - small tickets keep their speed, large tickets get their ceremony - is what keeps the red lines alive.

Variables

Variable Description
Large-payment line The ticket size that triggers this SOP - set it above your normal basket but below the frequency of premium-bottle tickets; too low and routine tickets bury the procedure, too high and the protection never engages
Seal threshold The drawer ceiling above which cash goes into the safe - keep it the same number as the shift-handover sheet's threshold so the two documents never disagree

payment handlingcounterfeit screeningfunds confirmation