Payment terminals submit raw 25-character merchant descriptors and 4-digit ISO 18245 MCC codes via Visa Clearing Record 10 or Mastercard IPM clearing messages. Modern banking apps use data enrichment APIs (like Plaid or MX) to normalize these strings into clean merchant names and logos.
- Card terminals pass transaction data formatted as: 25-character Merchant Descriptor + 13-character City + 2-character State + 4-digit MCC
- The acquirer (e.g. Stripe, Square, Fiserv) assigns the MCC at terminal onboarding; merchants with mixed lines of business often miscode
- Fintech data enrichment APIs clean raw terminal strings (e.g., 'SQ *BLUE BOTTLE SOMA') into verified brand logos and reward category tags
- Merchant acquirers configure statement descriptor strings and ISO MCCs during terminal onboarding
The Technical Architecture of a Card Transaction String
When you tap your card at a merchant terminal, the Point of Sale (POS) generates a financial authorization message governed by the ISO 8583 / ISO 20022 payment specifications.
Under Visa Clearing Record 10 (CR10) and Mastercard Integrated Processing Network (IPM) standards, the merchant terminal transmits a standardized payload to the payment gateway and merchant acquiring bank:
[4-Digit MCC] + [25-Character Descriptor] + [13-Character City] + [2-Character State/Country]
Example: 5814 SQ *BLUE BOTTLE COFFEE SAN FRANCISCO CA
Key Elements of the Clearing Record
- Merchant Category Code (Field 18 / ISO 18245): A four-digit numeric identifier assigned by the acquiring bank (e.g., Fiserv, Chase Paymentech, Stripe) based on the merchant’s primary source of revenue.
- Merchant Name / Descriptor (25 Characters):
A fixed-length string identifying the business. Square terminals prefix
SQ *, Stripe prefixesSTK*or the configured statement descriptor, and PayPal usesPAYPAL *. - Card Acceptor Location (City & State): City (13 characters) and State/Province (2 characters).
How Modern Banking Apps Clean the Data
When you open Chase, Capital One, or Amex mobile apps, you don’t see SQ *BLUE BOTTLE COFFEE 101 SOMA CA.
Financial institutions route raw clearing strings through Fintech Data Enrichment Engines (such as Plaid, MX, Yodlee, or Snowdrop):
- String Normalization: Regular expressions strip terminal IDs, store numbers (
#10423), and payment processor prefixes (SQ *,TST*). - Logo & Website Mapping: The cleaned string
Blue Bottle Coffeematches an internal entity database, attaching the official high-resolution SVG logo and corporate domain (bluebottlecoffee.com). - Reward Multiplier Validation: The issuing bank’s rewards logic evaluates the raw 4-digit MCC against its contractual category rules to assign 1x, 3x, or 4x points.