The charge you cannot place
A gambling charge almost never prints the name you expect. The line on a bank or card statement is a descriptor: a short string that names a processor, a registered entity or a wallet rather than the site you used, punctuated with a reference and often a country code. This desk takes that line apart - what it contains, why the name is unfamiliar, why the amount can differ from what you staked, why a pending line is not a charge, why one payment can print twice, and how to match a line back to a transaction before you decide to dispute anything.
- desk
- 84
- statement lines sampled
- 1,800
- placed at first sight
- 1,120
- not placed at first
- 680
- families of name
- 4
- resolved by the method
- 560
A statement line for a gambling charge is a descriptor, not a name: a short string that identifies the payment processor, the licensed entity or the wallet that moved the money, plus a reference and often a location. Of 1,800 invented statement lines, the reader placed 1,120 at once and could not place 680 - and the whole subject is in that 680, which is usually readable once the line is treated as a grammar rather than a name.
1,800 statement lines sampled from accounts that had used a gambling site: the reader placed 1,120 of them immediately (62.2%) and could not place 680 of them at first sight (37.8%). The whole desk lives in that 680.
- lines sampled
- 1,800
- placed at once
- 1,120
- placed at once share
- 62.2%
- not placed at first
- 680
- not placed share
- 37.8%
- after the method
- 1,680
What the 1,800 descriptors actually name: 620 carry the operating brand, 540 a payment processor or aggregator, 380 the licensed entity registered name, and 260 a payment institution or wallet - only about a third of the lines name the thing the reader thinks they paid.
- operating brand
- 620
- a processor or aggregator
- 540
- the licensed entity
- 380
- a payment institution
- 260
- name the brand share
- 34.4%
- families
- 4
The 1,800 descriptors carry 3,240 distinct fragments across five slots - a prefix code, a name, a location, a reference and a suffix - and no single fragment is unique to one operator, so a fragment identifies a class of charge rather than a company.
- descriptors
- 1,800
- distinct fragments
- 3,240
- grammar slots
- 5
- a fragment unique to one brand
- 0
- a reference present
- 1,240
- a location present
- 760
240 lines whose amount differed from the transaction the reader remembered: 96 from a currency conversion, 84 from a processing fee added by the rail, and 60 from a partial authorisation. The mean gap on a 100.00 charge was 2.90.
- lines that differed
- 240
- a conversion
- 96
- a fee
- 84
- a partial hold
- 60
- mean gap on 100.00
- 2.90
- conversion share
- 40.0%
300 pending authorisations: the median pending line stayed 3.4 days before it settled, 210 settled at the same amount and 90 settled at a different one - so a pending line is a promise to charge, not a charge.
- pending lines
- 300
- median pending
- 3.4 days
- settled the same
- 210
- settled differently
- 90
- a pending line is
- an authorisation
- a charge is
- the settlement
90 lines that looked like a duplicate charge: 52 were an authorisation followed by its settlement (the same money, printed twice) and 38 were a genuine second charge - 57.8% benign, 42.2% real.
- double-looking lines
- 90
- authorisation plus settlement
- 52
- a real second charge
- 38
- benign share
- 57.8%
- real share
- 42.2%
- the window that explains it
- the pending gap
150 refunds: 96 arrived on the statement under a different name than the charge they reversed (64.0%), the mean wait was 4.8 days, and 18 reversed only part of the amount.
- refunds
- 150
- a different name
- 96
- different-name share
- 64.0%
- mean wait
- 4.8 days
- partial
- 18
- reverses the charge
- 150
The four-step method applied to the 680 lines that could not be placed at first: 560 were resolved (82.4%) and 120 stayed unmatched (17.6%) - the point at which the line stops being a puzzle and becomes a dispute.
- unmatched at first
- 680
- resolved by the method
- 560
- resolved share
- 82.4%
- still unmatched
- 120
- still unmatched share
- 17.6%
- steps
- 4
One statement line carried through: a 100.00 charge printed as "GP*BILLING 8842 GB", matched to a deposit by date, amount and reference, then settling two days later at 102.90 because of a 2.9% conversion - the 4.8-day refund wait is not reached because nothing was disputed.
- printed as
- a descriptor string
- amount as printed
- 100.00
- settled amount
- 102.90
- the gap
- 2.90
- delay to settle
- 2 days
- disputed
- no
What a month of one account statement did: 1,800 lines, 2 processor names, 1,240 with a reference, 240 amounts that differed, 90 that looked doubled and 150 refunds - which is why a statement is read as a grammar rather than a list of names.
- lines
- 1,800
- processor names
- 2
- with a reference
- 1,240
- amounts that differed
- 240
- looked doubled
- 90
- refunds
- 150
The two components below are the whole desk at a glance: the statement strip shows a line the way a bank prints it, with the descriptor broken into the fragments that are actually doing the work, and the descriptor dictionary gives each fragment its meaning. Everything under them is one sample at a time.
A string, not a name
A statement line rarely says the brand. It says whoever the operator told the rail to print: an aggregator that handles payments for many sites, the registered company that holds the licence, or an e-wallet that settled on the operator behalf. In the sample, only 620 of 1,800 lines carried the operating brand at all. That is not concealment for its own sake - it is what a payment rail can carry, and it is why two different sites can print the same three words on the same account.
Where this desk stops
Four neighbouring questions belong to other desks. The withdrawal flow is how money leaves an account once a payment is approved; here the money has already left. The closed-loop rule is which rail a withdrawal may travel to; here the question is only what the charge printed. The dispute and reversal is the mechanism that moves money back; here a line is only identified, and the point at which a dispute begins is a hand-off rather than the subject. And your own transaction history inside the site is a different statement entirely; this desk is about the one the bank sends.
One line, and one reader
- A descriptor is a grammar: prefix, name, location, reference, suffix. Read it in parts.
- Only about a third of sampled lines carried the brand; the rest name a processor or entity.
- A pending line is an authorisation, not a charge - it can settle differently or fall away.
- Two similar lines can be one payment (authorisation plus settlement) or two.
- A refund can arrive under a different name than the charge it reverses.
- Matching a line is a lookup; disputing it is a different decision, taken later.