Merchant, Counterparty, Category: The Words a Bank Feed Gets Wrong

You buy a $6 coffee. Two days later your statement says SQ *BLUE BOTTLE 0412. You order dinner and it says DOORDASH, with no sign of the restaurant. You split rent with a roommate and it says VENMO CASHOUT.

Three charges, three names, and not one of them is the business you actually dealt with. This is not your bank being careless. It is the payment system telling you the truth about who moved the money, which happens to be a different question from who sold you the coffee.

Any app that organizes your money has to pick words for these things, and the words it picks shape what it can and cannot tell you. Below is the vocabulary we settled on, why merchant turned out to be the wrong default, and what changes once you separate who from what for.

The label is not a name

The text on a transaction is called a descriptor, and it is written by whoever submitted the charge to the card network. That party is often not the seller. Square prefixes charges it processes with SQ, Toast uses TST, and both are doing exactly what the rules expect of them.

Descriptors also drift. The same cafe can bill you as SQ *BLUE BOTTLE 0412 from one location and BLUE BOTTLE COFFEE from another, because the store number and the processor prefix are part of the string. To a system that groups charges by their text, those are two different businesses. Your spending by merchant report then shows the same coffee chain twice, splits your totals, and asks you to categorize it twice.

The volume makes this expensive. Consumers made an average of 47 payments a month in 2026, 16 of them on credit cards and 15 on debit cards^[4]. A few hundred charges a quarter, each carrying a name written by a party you did not choose, is enough noise to make a clean report impossible by hand.

What a counterparty is

A counterparty is whoever is on the other side of a transaction. The shop you buy from is one. So is the employer who pays you, the broker that sends a dividend, the bank that credits interest, the friend who reimburses you for tickets.

The word comes from finance, where it has always meant the other party to a deal, with no assumption about direction. That is the whole reason to prefer it. Merchant only ever describes half of your transactions, and only the outgoing half. Call the concept merchant and your employer has to be filed as a kind of vendor, which is how money apps end up with a Vendors page that lists your paycheck.

Direction is a fact about a relationship, not a filter on who gets to have one.

Direction being a property rather than a category matters more than it sounds. A payment processor can bill you fees and pay you out. A bank can charge you a maintenance fee in March and credit you interest in April. A landlord can take rent and return a deposit. Those are single relationships with two directions, and splitting them into a payee and a payer loses the fact that they are the same party.

The five kinds of counterparty

Once you accept that the descriptor names a party rather than the seller, the useful question becomes: which party? Plaid, the bank data provider we use to read transactions, answers that with a list of counterparty types. Its API classifies each party it finds behind a transaction as one of these^[1]:

Read that list as a warning about ambiguity rather than a taxonomy to memorize. A single SQ *BLUE BOTTLE charge has two counterparties: a payment terminal, Square, and a merchant, Blue Bottle. A DoorDash order has a marketplace and, sometimes, no identifiable restaurant at all, because the restaurant never touched your card. A Venmo cashout has a payment app on one side and nothing behind it, since Venmo moved money from its own balance.

This is why the honest answer to what a charge means is sometimes several names. An app that insists on exactly one is going to pick the wrong one some of the time.

Why the card networks need five words too

These five types are not a data vendor’s invention. They map closely onto the ways card network rules allow a company to stand between you and a seller, each with different obligations.

A summary of the Visa Rules by the law firm Venable distinguishes four such models^[3]. A merchant of record is the company that presents itself as the seller, identifies itself to you under its own name, and handles your dispute. A payment facilitator is, in Venable’s words, permitted to “submit the transactions of an identified group of third-party sub-merchants” through its own merchant account. A marketplace brings buyers and sellers together and must receive and distribute settlement funds to the sellers on its platform. A staged digital wallet operator runs two separate transactions: your card funds the wallet, then the wallet pays the merchant without using your card at all.

That last model explains the most frustrating charges you will ever try to categorize. When a wallet pays the merchant in a second transaction that your card never sees, your bank genuinely cannot tell you where the money went. No amount of enrichment recovers information that was never sent.

Visa’s own merchant standards go a step further and reserve a merchant category code for marketplaces, describing them as platforms that bring together cardholders and retailers selling a range of goods that would otherwise qualify for different codes, under a single brand^[2]. The network has a category that means, in effect, “many categories, indistinguishable from here”. And because a payment facilitator is a third party, the manual requires it to assign each sponsored merchant the code that best fits that merchant’s business, not its own^[2].

Who, what for, and neither

The confusion worth clearing up is not between merchant and counterparty. It is between a counterparty and a category, because most apps quietly treat them as the same field.

Keeping them apart pays off immediately. One counterparty can span several categories: a home improvement store sells you lumber and light bulbs, and a warehouse club sells you groceries, tires and a television. If who and what for are the same field, you must choose, and you will be wrong about part of your spending forever.

The transfer column is the one that corrupts totals. Paying your credit card bill is not spending. The purchases were already counted when you made them, and the payment moves money from an asset to a liability. An app that files that payment under a category has just counted the same money twice. We wrote about the structural fix in why double-entry bookkeeping keeps a money app honest.

The rest of the vocabulary

These are the words LumaLedger uses, and what each one is responsible for. The pattern is that every word answers exactly one question.

One deliberate omission: there is no counterparty table in our database. A counterparty is a grouping of your transactions by a stable identity, computed when you look at it. What persists is the rule you wrote and the name or logo you chose. That means a counterparty cannot go stale, and deleting one cannot take a transaction with it.

How LumaLedger uses these words

The practical payoff of the vocabulary is that a decision can be attached to a party rather than to a string.

Charges are grouped onto one counterparty by the stable merchant identity your bank data provides when it has one, and by a normalized version of the description when it does not. Store numbers, reference codes and processor prefixes are stripped, so SQ *BLUE BOTTLE 0412 and BLUE BOTTLE COFFEE land on one page instead of two. On that page you can rename the counterparty, give it a logo, add its website and notes, and see both what you paid it and what it paid you.

Filing it sets a rule. Every future transaction with that counterparty goes to the category you picked, and the ones already on file move with it, except any you categorized by hand. A rule can narrow itself to an amount band, which is how one counterparty carries several: over $200 at the hardware store is home improvement, the rest is shopping. And a rule only ever files one direction, so what a party charges you can never be mistaken for what it pays you.

If a counterparty turns out to be your own money moving, you point it at the account it goes to instead of a category. It stops counting as spending from that moment, backwards as well as forwards.

LumaLedger

Income & spending

Past 6 months

Apr

May

Jun

Jul

Aug

Sep

IncomeSpending

Spending · Sep$6,178

Housing$2,450

Groceries$780

Transportation$610

Dining$540

Shopping$520

Utilities$390

Everything else$888

The same grouping key feeds recurring detection, which is why the subscriptions view and the counterparty view always agree on what counts as the same party. We went into that machinery in how subscription creep goes unnoticed, and into reading the raw descriptors themselves in how to read a credit card statement.

None of this makes a wallet transaction reveal what it bought. Nothing can. What the vocabulary buys you is that the gap shows up as a gap, instead of quietly becoming a category you did not choose.