What Is a Billing Descriptor?
A billing descriptor is the text that appears on your bank or credit card statement to identify a transaction. When you buy a coffee at a cafe, the billing descriptor is the line of text next to the charge amount that tells you where the money went. In a perfect world, it would simply say the name of the business. In practice, it often looks like a garbled abbreviation that bears little resemblance to the store you visited.
Understanding how billing descriptors work demystifies one of the most confusing aspects of personal finance and helps you identify charges without the stress of wondering whether your card was compromised.
How Billing Descriptors Are Assigned
Billing descriptors are not chosen by your bank. They are set by the merchant or, more precisely, by the merchant's payment processor. When a business sets up its payment processing account, it provides a business name and other identifying information. The payment processor uses this to generate the descriptor that ultimately appears on your statement.
The problem is that there are multiple parties in the chain between a purchase and your statement, and each one can modify or truncate the descriptor along the way:
1. The merchant provides a business name to their payment processor
2. The payment processor (Stripe, Square, Adyen, etc.) formats the descriptor according to its own rules
3. The acquiring bank may further modify or append information
4. The card network (Visa, Mastercard, etc.) transmits the descriptor with character limits
5. Your issuing bank displays the descriptor, sometimes reformatting it again
By the time it reaches your statement, the original business name may be shortened, rearranged, or replaced entirely.
Static vs. Dynamic Descriptors
Payment processors typically offer merchants two types of descriptors:
Static descriptors are fixed text that appears the same for every transaction from that merchant. A business called "Downtown Bakery" might set its static descriptor to "DOWNTOWN BAKERY" and every purchase will show that same text. Static descriptors are simple but inflexible. A company with multiple product lines or locations cannot distinguish between them.
Dynamic descriptors change per transaction. They allow the merchant to include specific information about what was purchased or which location handled the sale. For example, a hotel chain might use a dynamic descriptor that includes the city name: "HILTON HOTELS NYC" or "HILTON HOTELS CHI." Online marketplaces use dynamic descriptors to show the specific seller or product category.
Soft vs. Hard Descriptors
There is another distinction that explains why charges sometimes look different when they are pending versus when they post:
Soft descriptors are temporary and appear during the authorization phase, while a charge is still pending. They often contain less information than the final descriptor.
Hard descriptors replace the soft descriptor once the transaction settles, usually within two to five business days. The hard descriptor is the permanent record on your statement. Sometimes the soft descriptor is more recognizable than the hard one, and sometimes it is the other way around.
This is why a pending charge might show the store name clearly, but the posted charge looks like gibberish, or vice versa.
Why Descriptors Don't Match the Store Name
Several specific situations cause a disconnect between the business you paid and the name on your statement:
- Legal name vs. trade name: A business operating as "Sunny Side Cafe" might be legally registered as "SSCAFE Holdings Inc." The billing descriptor often uses the legal name.
- Franchise billing: Individual franchise locations sometimes bill under the corporate parent rather than the local store name.
- Payment aggregators: Services like PayPal, Square, and Stripe process payments on behalf of many merchants. This is why you see "PP*" for PayPal transactions, "SQ *" for Square transactions, and sometimes "STRIPE" followed by the actual merchant name.
- Third-party billing: If you buy something through an app or marketplace, the charge may come from the platform (Apple, Google, Amazon) rather than the individual seller.
How Major Payment Processors Format Descriptors
Different processors have recognizable patterns:
Stripe typically formats descriptors as the business name followed by a location or product detail. Merchants using Stripe can customize their descriptor, but it always starts with the account name.
Square prefixes every descriptor with "SQ *" followed by the business name. If you see "SQ *LOCALCOFFEE" on your statement, it means a Square merchant called "Local Coffee" charged your card.
PayPal uses "PP*" or "PAYPAL *" followed by the merchant name. When you pay through PayPal, the descriptor identifies PayPal as the intermediary and attempts to include the seller name in the remaining characters.
Toast (used by many restaurants) shows as "TST*" followed by the restaurant name. "TST*MARIOS PIZZERIA" means you ate at a restaurant called Mario's Pizzeria that uses Toast for payment processing.
Shopify often appears as "SP *" or "SP * SHOPIFY" followed by the store name for merchants using Shopify Payments.
Character Limits and Truncation
One of the biggest reasons descriptors look confusing is character limits. Card networks impose strict limits on descriptor length:
- Visa allows up to 25 characters
- Mastercard allows up to 22 characters
- American Express allows up to 20 characters for the merchant name
When a business name exceeds these limits, it gets truncated. "Mediterranean Kitchen and Grill" becomes something like "MEDITERRANEANKITCH" which is barely recognizable. Add a payment processor prefix like "SQ *" and you lose even more characters for the actual business name.
Examples of Confusing Descriptors
Here are real-world examples of descriptors that regularly confuse cardholders:
- "AMZN MKTP US" = Amazon Marketplace purchase
- "GOOGLE *SERVICES" = A Google subscription or app purchase
- "APL*APPLE.COM/BILL" = Apple subscription or iTunes purchase
- "SQ *COFFEE SHOP" = A coffee shop using Square
- "TST*THAI PALACE" = A restaurant using Toast POS
- "WPY*FREELANCER" = A payment through a freelance platform
- "IDP*EXAMPLE.COM" = An online service using a specific payment gateway
If you encounter a descriptor you cannot identify, use our [transaction lookup tool](https://transactionlookup.com) to search for it. The database covers thousands of known billing descriptors and maps them back to their actual business names.
How Merchants Can Improve Their Descriptors
For business owners reading this, unclear billing descriptors lead to chargebacks. When customers do not recognize a charge, they dispute it. This costs you money in chargeback fees and lost revenue. Best practices include:
- Use your trade name (the name on your storefront or website), not your legal entity name
- Keep the name short enough to avoid truncation
- Include a customer service phone number or URL when your processor allows it
- Test how your descriptor appears on actual bank statements
- Use dynamic descriptors to include order-specific details when possible
Looking Up a Billing Descriptor
The fastest way to identify a confusing billing descriptor is to search for it. Copy the exact text from your statement and enter it into a search engine or a dedicated lookup tool like [TransactionLookup.com](https://transactionlookup.com). Most common descriptors have been identified and cataloged, so you will get an answer in seconds.