□The Unmatched Line statement line Open the partner account
paid
Affiliate disclosure. The partner link in the masthead and in the band beside the copy on this page is a sponsored link to a partner operator, and this site may be paid if you open an account through it, at no extra cost to you. It carries rel="sponsored noopener" and opens in a new tab. A desk about the line a charge prints should not leave its own funding unsaid: one link funds the site, no bank, operator, processor or person is named, rated or recommended anywhere on it, and it prints no real descriptor.
The Unmatched Line / what a line hides
what a descriptor cannot tell you

What a statement line cannot tell you

A descriptor is a payment routing string, and it is worth being exact about what it is not. It cannot tell a third party what you bought, which game you played or whether you won, and it cannot be read as a profile. The line is thin on purpose: it carries only what the rail needs to move money and, if required, to reverse it.

Desk spec
what it carries
routing and reversal
what it names
the carrier, not the product
what it omits
the game and the outcome
who can read it
the account holder and their bank
a profile of the reader
no
reversible
yes, by the reference
what the line isA descriptor, not a name: a routing string of up to five fragments. The reference is the only one that is yours.
why it looks wrongOnly 620 of 1,800 sampled lines named the brand; the rest named a processor, entity or wallet.
what decides a disputeThe money that actually left the account. 560 of 680 unplaceable lines were placed by reading, not disputing.
Direct answer

A statement descriptor is a routing string: it exists so the rail can move money and the bank can reverse it, and it carries only what those two need. It does not name the product, the game or the outcome, it is not a profile of the reader, and the same three words can sit on the statements of thousands of unrelated payments.

What the string is for

A descriptor has two jobs and only two: route a payment to the right merchant account, and allow the bank, on the holder instruction, to find and reverse it. Everything in the string serves one of those two jobs - a prefix that says how it was taken, a name that routes it, a location and a reference that let it be found again. It is not a summary of the transaction, and it is not shared between banks as one.

What the line carries, and what it does not carries the kind of charge a prefix the carrier a name where it settled a location how to find it again a reference does not carry the product or game no the amount won or lost no the account login no any other reader no so the line is enough to move and reverse money, and too thin to describe the person who paid it
Reading a line with the right expectations
  • It is a routing string, not a receipt: the product is not on it.
  • It is thin: the same words sit on unrelated statements.
  • It is reversible by the reference, which is why the reference exists.
  • It is read by the holder and their bank, and is not a public profile.
  • It is not evidence of a win or a loss; only the amount that moved is shown.
This desk describes the general shape of a payment descriptor and prints invented strings. It makes no claim about any real bank, processor or operator policy, and it is not advice about data rights - which are a different subject belonging to another desk.
When nothing matcheswhere the lookup becomes a disputeThe linethe four fields a statement printsQuestionsthe desk answered in full