Skip to content
DescriptorAPI
Get API key

Reading statements

What a card descriptor is, and who writes it

The short line on a card statement is not written by your bank. Who writes it, why it looks the way it does, and what each part tells you.

Written for: Everyone 4 min read Updated

Open any card statement and each purchase has a short line of capital letters next to it. That line is the descriptor, sometimes called the billing descriptor or statement descriptor. Most people assume their bank writes it. It does not. The bank prints what it was sent, and what it was sent was decided long before you paid, by the shop and the company that processes its card payments.

Knowing who writes the line explains almost everything strange about it: the cut-off names, the codes you have never seen, and why the same coffee shop can look different from one month to the next.

Who writes the line

Four parties touch a card payment before it reaches your statement:

  1. The merchant chooses the name it wants customers to see, or leaves its legal name as the default.
  2. The acquirer or payment provider, the company that accepts card payments for that merchant, stores that name and adds its own details: a city, a country, sometimes its own brand in front.
  3. The card network (Visa, Mastercard and the others) carries the message between the merchant's side and your bank, in fixed-length fields.
  4. Your bank receives the message, may add a word or two of its own, such as POS or PURCHASE, and prints it.

Each step can shorten, prefix or reformat the text. By the time it reaches you, the line has been edited by three companies, none of whom was thinking about how it reads to you.

What a descriptor is made of

Most lines follow the same order, even when parts are missing:

POS 4417 SQ *BLUE BOTTLE COF SAN FRANCISCO CA

POS 4417
Added by the bank: a point-of-sale purchase on the card ending 4417. Says how you paid, not who you paid.
SQ *
The payment provider, here Square. The asterisk separates its name from the merchant's.
BLUE BOTTLE COF
The merchant, cut off at the field limit. "COF" was "COFFEE".
SAN FRANCISCO CA
Where the payment was taken: city and state, or city and country outside the US.
A typical in-store purchase, read part by part. The colours match the ones our playground uses.

Online purchases often swap the city for a website or a phone number, because there is no shop to locate. Bank-written lines (fees, interest, transfers) skip the merchant part entirely.

Why it rarely matches the shop sign

The name on the door and the name on file are often different. A restaurant group runs five brands under one company. A franchise trades under a famous brand but bills under the franchisee's name. A new owner keeps the old card terminal for a year. In each case the descriptor is accurate from the merchant's point of view and puzzling from yours.

Field note

When a line stumps someone, the cause is usually not fraud or a typo. It is one of three things: a legal name instead of a brand, a payment provider's name in front of the shop's, or a branch name that looks like part of the shop's name. "CARREFOUR MOE" is Carrefour at Mall of the Emirates, not a shop called Carrefour Moe.

Why the line can change after a few days

A card payment happens in two steps. When you pay, the shop asks your bank to authorise the amount, and your banking app shows a pending line straight away. Days later the shop settles, sending the final amount and details. The two messages do not always carry identical text, so the pending "UBER *TRIP" can become a posted "UBER *TRIP HELP.UBER.COM", and a restaurant's pending amount can grow once the tip is added. If a line changed, it is usually the same purchase.

What one line can, and cannot, tell you

From a single descriptor you can usually work out the merchant, the payment provider and roughly where the payment was taken. You cannot see what was bought, and the location is where the payment was processed, which for online shops can be a different country from the one you were in.

That is the problem we work on. DescriptorAPI reads lines like these and returns the merchant, its category, website and logo, the location and the payment provider, with a confidence score so apps know how sure to sound. If you have a line in front of you right now, the playground will read it for you.

Next

Read next