The Name Mismatch Problem
You buy lunch at a place called "The Corner Deli." You check your bank statement and see a charge from "TCDFOODSERVICE LLC." Same transaction, completely different name. This disconnect between where you spend money and what your bank statement says is one of the most common causes of confusion and unnecessary fraud reports in consumer banking.
The mismatch is not a bug. It is an inevitable side effect of how payment processing works. Understanding the system reveals why the names change and how you can decode them.
How a Payment Travels from Store to Statement
When you tap, insert, or swipe your card at a store, the payment passes through a chain of intermediaries before it appears on your statement. Each link in the chain can modify the merchant name:
Step 1 - The Merchant: The store sends the transaction to its payment terminal or online checkout system. At this point, the merchant knows its own name perfectly well.
Step 2 - The Payment Processor: The merchant's payment processor (companies like Stripe, Square, Adyen, Fiserv, or Worldpay) receives the transaction. The processor formats the billing descriptor according to the merchant's account setup and the processor's own naming conventions. This is where prefixes like "SQ *" or "TST*" get added.
Step 3 - The Acquiring Bank: The payment processor routes the transaction through an acquiring bank (also called the merchant's bank). The acquirer may modify or supplement the descriptor with additional reference information.
Step 4 - The Card Network: The transaction passes through the card network (Visa, Mastercard, American Express, Discover). The network imposes character limits on the descriptor, which can cause truncation. Visa allows 25 characters for the merchant name. Mastercard allows 22. American Express allows 20.
Step 5 - Your Issuing Bank: Finally, your bank (the card issuer) receives the transaction and displays it on your statement. Some banks reformat the descriptor again, adding transaction type labels like "POS PURCHASE" or "CHECKCARD" before the merchant name, which further reduces the space available for the actual business name.
By the time the charge reaches your eyes, the original "The Corner Deli" has been processed, prefixed, truncated, and reformatted into something barely recognizable.
DBA Names vs. Legal Entity Names
One of the most common reasons for name mismatches is the difference between a business's DBA (Doing Business As) name and its legal entity name.
The sign on the door says "Joe's Pizza." But when Joe registered his business, he incorporated it as "JPZ Holdings LLC" or "Giuseppe's Food Services Inc." When he set up his merchant account, the payment processor may have used the legal entity name rather than the trade name.
This happens frequently with:
- Small businesses that incorporated under a name different from their storefront
- Franchise operations where individual locations bill under the franchise owner's company name
- Multi-brand businesses where one company operates several restaurant or retail concepts under different names
A single restaurant group might operate "Sushi Palace," "Taco Town," and "Burger Barn," but all three bill under "ABC Restaurant Group LLC."
Third-Party Payment Processors
The rise of third-party payment processors has made billing descriptors more confusing than ever. When small businesses use platforms like Square, Toast, or Shopify to process payments, the platform's prefix becomes part of every transaction:
- Square: Adds "SQ *" before the merchant name. "SQ *SUNRISE BAKERY" is a purchase at Sunrise Bakery.
- Toast: Adds "TST*" for restaurant transactions. "TST*THAI GARDEN" is a meal at Thai Garden.
- Shopify: Adds "SP *" for online purchases. "SP *HANDMADE GOODS" is an order from an online store.
- Clover: May add "CLV*" or show the business name with Clover-specific formatting.
- PayPal: Adds "PP*" or "PAYPAL *" for transactions processed through PayPal.
These prefixes eat into the character limit, so a business with a long name gets truncated even more severely. "SQ *MEDITERRANEAN KITCHEN" might become "SQ *MEDITERRANEANK" on your statement.
Parent Company and Corporate Billing
Large corporations often process payments under their parent company name rather than the individual brand:
- Yum! Brands owns Taco Bell, KFC, and Pizza Hut. A charge might appear as "YUM BRANDS" rather than the specific restaurant.
- Darden Restaurants owns Olive Garden, LongHorn Steakhouse, and Cheddar's. Charges may appear under "DARDEN" or similar.
- Marriott International operates Marriott, Sheraton, Westin, W Hotels, and others. Your hotel stay may bill under "MARRIOTT" regardless of which brand you stayed at.
This is particularly confusing when the parent company name is not well known to consumers.
Aggregator Billing
Payment aggregators process transactions on behalf of many small merchants under a single merchant account. When you pay a merchant that uses an aggregator, the charge may show the aggregator's name rather than (or in addition to) the merchant's name:
- PayPal: Shows "PAYPAL *MERCHANT NAME" because PayPal is the merchant of record
- Stripe: May show "STRIPE" in some configurations, though most Stripe merchants set up their own descriptors
- Google Pay / Apple Pay: Transactions through these services still show the underlying merchant's descriptor in most cases, but occasionally the platform name appears instead
International Transactions
Charges from international merchants add another layer of confusion:
- The merchant name may appear in a different language or alphabet
- A currency conversion note may be appended to the descriptor
- The merchant's country code (GB, DE, JP, etc.) may be included
- Your bank may add a separate line for the foreign transaction fee (typically 1-3% of the charge)
A purchase from a British online store might appear as "EXAMPLE SHOP LONDON GB" with a separate "FOREIGN TRANSACTION FEE" line item, making one purchase look like two charges.
Character Limits and Truncation
Character limits are one of the biggest contributors to confusing descriptors. When a business name exceeds the card network's limit, the result is often an unrecognizable fragment:
| Original Name | After Truncation |
|---|---|
| Mediterranean Kitchen & Grill | MEDITERRANEANKITCH |
| Johnson's Family Auto Repair | JOHNSONSFAMILYAUTO |
| Dr. Smith's Dental Practice | DRSMITHSDENTALPR |
| The Neighborhood Coffee Shop | THENEIGHBORHOODCO |
Add a payment processor prefix, and the truncation gets worse:
| With Processor | After Truncation |
|---|---|
| SQ *Mediterranean Kitchen | SQ *MEDITERRANEANK |
| TST*Johnson's Auto Repair | TST*JOHNSONSAUTORE |
How to Match Confusing Charges to Real Merchants
When you encounter a charge that does not match any business you remember visiting:
1. Search the exact descriptor at [TransactionLookup.com](https://transactionlookup.com). Our database maps thousands of confusing billing descriptors to their actual business names.
2. Look for processor prefixes and strip them. If the charge says "SQ *SUNRISEBAKE," you are looking for a business called something like "Sunrise Bakery" that uses Square.
3. Check the location if your bank provides one. A city and state can narrow down which local business charged you.
4. Match the date and amount against your receipts, email confirmations, and calendar. If you visited a restaurant on Tuesday and see a charge from that Tuesday for roughly what you would expect to pay, the confusing descriptor is likely that restaurant.
5. Search for the truncated name in a search engine. Even a partial name like "MEDITERRANEANK" plus the city name often leads to the right business.
6. Check the MCC (Merchant Category Code) if your bank shows it. The MCC tells you the type of business (restaurant, grocery, gas station, etc.) which can help narrow your search.
What Merchants Can Do About This
If you are a business owner, your customers are probably confused by your billing descriptor right now. To minimize chargebacks and support calls:
- Set your billing descriptor to your trade name (what the sign on your door says), not your legal entity name
- Keep it short to avoid truncation
- Test how your descriptor appears on actual bank statements from different issuers
- Include your city or a recognizable abbreviation when possible
- Ask your payment processor about dynamic descriptors that can include order-specific details
Clearer descriptors mean fewer confused customers, fewer support calls, and fewer costly chargebacks. Everyone wins when the name on the statement matches the name on the store.