Data Dictionary
Purpose
The Data Dictionary serves as the definitive single source of truth for all terminology used within Harmonize Analytics. It documents field lineage, tracing the origin and transformation of data, and provides clear mappings between various data points. Its primary function is to standardize definitions across our platforms, ensuring a unified understanding of data elements. Furthermore, it clarifies complex grouping logic and thoroughly documents the transitions of fields as they evolve from Harmonize 1.0/2.0 → Harmonize 3.0
This documentation is helpful for ensuring that all clients consistently understand the meaning and context of various fields when they are analyzing payments data within the Harmonize platform. It eliminates ambiguity and promotes accurate interpretation of financial information.
Auth
Harmonize 3.0 Name | Definition | Data Example | Legacy Field Name |
|---|---|---|---|
Acquirer Response Code | Code from the acquiring bank that indicates the result of the authorization request. | 100 | — |
Acquirer Response Description | Text description from the acquiring bank explaining the authorization result. | Approved | Auth Response / Reason |
Acquirer Response Description & Code | Combined field that concatenates the acquirer response code and its description. | Expired Card (522) | — |
Attempt # | Sequential number of the authorization attempt for the same transaction. | 2 | — |
Auth Type | Specifies the category of authorization applied. | Conditional Deposit, Authorization, Refund Authorization | — |
AVS Response Code | Code returned by the Address Verification System indicating whether the billing address matched what was on file with the issuer. | 22 | — |
CVV Response Code | Code returned by the card network indicating whether the CVV/CVV2 matched. | M | — |
Day of Month | Numeric day of the month (1–31) when the transaction was authorized. | 15 | — |
Day of Week | Name of the day when the authorization occurred. | Wed | — |
Initial Network Response Code | Response code from the card network on the very first authorization attempt. | Transaction Not Allowed | — |
Initial Network Response Description | Response code from the network for the first authorization attempt. | 6P | — |
Initial Response Description | Text description from the acquirer for the first authorization attempt. | Call Issuer | — |
MCC | Merchant Category Code sourced directly from the acquirer authorization data | 1234 | — |
MOTO Indicator | Codes indicating if the transaction was Mail Order or Telephone Order. | 5 | — |
MOTO Indicator Description | A description of the MOTO indicator code. | Non-Authentication E-Comm | — |
Network Advice Code | Code provided by the network suggesting additional action; currently used by Stripe. | 03 | — |
Network Response Code | Code from the card network indicating the result of the authorization. | 122 | — |
Network Response Description | Text description from the card network describing the response. | 3DS Authentication Error | — |
Network Response Description & Code | Combined field that concatenates the network response code and its description. | 3DS Authentication Error-122 | — |
OP Response Description | Internal normalized description of the authorization result, grouped for reporting. | Cvd/Cvv2/Cvc2 Failure | Decline Reasons / Auth Response Group / Reject Reason Group / Reason Group |
POS Entry Mode | How the card data was entered (e.g., chip, swipe, manual entry, contactless). | Contactless Chip | — |
Presenter | Name of presenter or merchant system that sent the authorization. | worldpay | Presenter |
Token Indicator | Indicates whether a transaction was processed using a network token. | Network Token | — |
Wallet Type | Identifies the digital wallet used in the authorization attempt | Apple Pay, Google Pay | — |
BIN
Harmonize 3.0 Name | Definition | Data Example | Legacy Field Name |
|---|---|---|---|
Card Classification | OP Combined field of Card Type and Card Funding Source. | Corporate - Prepaid | Card Type-Class |
Card Funding Source | Identifies how the card is funded, such as Credit, Debit, or Prepaid. | Credit | Card Type |
Card Product Type | Specifies the card category, such as Consumer, Commercial, or Corporate. | Large Market Enterprise | — |
Card Regulated | Indicates whether the card is subject to interchange regulation (e.g., Durbin Amendment in the U.S.). | — | — |
Credit Debit | Indicates whether the card is credit or debit. | Credit, Debit | — |
Debit Regulated Indicator | Indicates whether the card is regulated or non-regulated debit. | Regulated with Fraud, Unregulated | Card Issuer Regulated |
Debit Routing Eligible | Shows if a debit card can be processed through multiple debit networks. | Y | — |
Detailed Funding Source | OP combined field of Card Reloadability and Card Funding Source. | Prepaid - Non Reloadable | Funding Source |
Issuer Country | The country where the card issuer is located. | United States of America | Country of Issuance |
Issuer Group | The banking group or brand family the issuer belongs to (e.g., Chase, Bank of America). | JP Morgan Chase | Bank Group |
Issuer Name | The official name of the issuing bank. | Jpmorgan Chase Bank N.A. | — |
Prepaid Type | Defines the type of prepaid card, such as reloadable or non-reloadable. | Reloadable | — |
Card
Harmonize 3.0 Name | Definition | Data Example | Legacy Field Name |
|---|---|---|---|
BIN6 | The first six digits of the card number (Bank Identification Number), used to identify the issuing bank and card type. | 411111 | Bin |
BIN8 | The first eight digits of the card number (Bank Identification Number), used to identify the issuing bank and card type. | 41111111 | — |
Brand | The card’s payment network brand. | Visa, Mastercard, Amex, Discover | — |
MOP Name | The specific method of payment name that combines the card brand and funding type. | Visa Debit, Amex Credit, Star, Accel, NYCE | Method of Payment |
MOP Network Name | The network provider that processes the transaction. | Visa, Mastercard, PayPal | MOP Group |
MOP Type | The broader category of the method of payment. | Visa, Mastercard, PayPal Account | — |
OP MOP Category | Optimized Payments’ internal classification of payment method type. | Card Based, PIN/PINless Debit | Type of Payment |
Currency
Harmonize 3.0 Name | Definition | Data Example | Legacy Field Name |
|---|---|---|---|
Presentment | Currency in which the transaction was presented to the customer at the point of sale. | USD, CAD, MXN | Presentment Currency |
Reporting | Currency used for internal reporting; defaults to USD across all clients. | USD, CAD, MXN | — |
Settlement | Currency in which the transaction was settled between acquirer and merchant. | USD, CAD, MXN | — |
Disputes
Harmonize 3.0 Name | Definition | Data Example | Legacy Field Name |
|---|---|---|---|
Category | Category of dispute. | Fraud, Processing Errors, Authorization | Dispute Category |
CB Reason Code | Chargeback reason code assigned by the acquirers. | 10.4 | — |
CB Reason Code Name | Chargeback reason description provided by the acquirers. | Other Fraud-Card Absent Environment | Reason Group |
CB Reason Description & Code | Combined field that includes both description and code for the chargeback reason. | Other Fraud-Card Absent Environment (10.4) | — |
Current Position | Current status of the dispute process. | Win, Loss | — |
Dispute Type | Type of dispute. | Chargeback, RDR | — |
Financial Impact | Financial impact of the dispute on the merchant. | Credit, Debit, No Impact | — |
Network CB Reason Code | Chargeback reason code as defined by the network. | 4853 | Reason |
Network CB Reason Description | Text description of the network chargeback reason | Cardholder Dispute | — |
Network CB Reason Description & Code | Combined code and description of the network chargeback reason. | Cardholder Dispute (4853) | — |
Fees
Harmonize 3.0 Name | Definition | Data Example | Legacy Field Name |
|---|---|---|---|
Fee Category | Different categories of fees. | Interchange, Network, Acquirer | KPI Response Subcategory / Fee Category |
Fee Code | Code assigned to the fee by the network or acquirer. | MC Consumer Standard Prepaid | — |
Fee Name | Name of the fee. | MC Consumer Merit 1 | Fee Name |
Fee Note | Description or note clarifying the fee type. | ChargebackReversed, PayPal Rates | — |
Fee Rate % | Fee expressed as a percentage of the transaction amount. | 0.017341 | — |
Fee Rate PI | Fixed fee charged per transaction. | 0.200000 | — |
Fee Sub-Category | Sub-classification of the fee for more detailed grouping. | Processing Fees | Fee Sub Category |
Fee Sub-Category 2 | Additional sub-classification of the fee. | Visa Prepaid International | Fee Sub Category 2 |
Txn Type | Transaction type associated with the fee. | Sales, Refund | — |
MID
Harmonize 3.0 Name | Definition | Data Example | Legacy Field Name |
|---|---|---|---|
Acquirer | The name of the acquiring bank or processor that authorizes and settles transactions. | Chase, Vantiv | Processor |
Business | The merchant’s business name used for identification and reporting. | Retail | — |
Business Type | Classification of the merchant’s line of business or industry. | Resort, Business | — |
Card Environment | The environment in which the transaction took place. | Ecomm | — |
Chain | The chain identifier associated with the merchant. | 154739 | — |
DBA Country | The country where the merchant’s Doing Business As (DBA) entity is registered or operates. | USA, Canada | — |
DBA Name | The Doing Business As (DBA) name of the merchant, typically the customer-facing brand. | Donut_Shop | MID Name |
DBA State | The state where the merchant’s DBA operates. | NC, GA, CO, OH | — |
Descriptor | The text that appears on the cardholder’s bank statement for a transaction. | Mobile | — |
District | The district identifier assigned to organize the merchant within its organization. | Greater Atlanta | — |
Division | The division of the merchant’s organization responsible for a location or group of locations. | IN INS OH Utility | — |
Industry | The industry category or vertical classification of the merchant. | Government, Retail | — |
Legal Name | The legal, registered entity name of the merchant. | Donut Shop LLC | — |
Location Name | The descriptive name assigned to a specific merchant location. | BMW Atlanta | — |
Location Number | The internal numeric identifier for a merchant location. | 2345 | — |
MCC | The four-digit Merchant Category Code assigned by card networks to classify merchant type. | 1234 | MCC |
Merchant Account | The company or account name used by the merchant. | DonutShop-Chase | Merchant Account |
OP Reporting MID Name | A combined field of the merchant’s MID and DBA name, used for reporting. | Digital-12345 | Division Name |
Parent | The parent company or corporate entity that owns or oversees the merchant. | Wells Fargo | — |
POS Type | The type of point-of-sale system or channel used for transactions. | Gift Cards, Kiosk | — |
Region | The geographic region where the merchant operates. | Southeast | — |
Reporting Group | A Vantiv-specific grouping field that consolidate multiple merchant accounts under a common reporting name | Donut in Atlanta | Reporting Group / SubGroup |
Rollup1 | The first custom grouping used for reporting purposes. | Donuts - Chase | Group Name / Reporting Group Name |
Rollup2 | The second custom grouping used for reporting purposes. | Demo Chase | Harmonize Group |
Tax ID | The tax identification number assigned to the merchant for compliance and reporting. | 11-1234567 | — |
TXN
Harmonize 3.0 Name | Definition | Data Example | Legacy Field Name |
|---|---|---|---|
AVS Response Code | The Address Verification System code returned for the transaction, indicating whether the billing address matched. | 81 | — |
Country | The country where the transaction originated. | United States, Canada | — |
Currency Pair | Pair of presentment and settlement currency. | Presentment Currency (HKD) - Settlement Currency (USD) | |
CVV Response Code | The Card Verification Value code returned for the transaction, indicating CVV match status. | S, U | — |
Downgrade Code | The code assigned when a transaction is downgraded by the processor. | 226 | — |
Downgrade Reason | The descriptive reason explaining why a transaction was downgraded. | No CVV Data present on Track Data | — |
Downgrade Reason & Code | A combined field showing both the downgrade reason and its associated code. | No CVV Data present on Track Data (226) | — |
Funding Method | Indicates if the transaction was conveyed and settled. | Conveyed, Settled | — |
IC Code | The interchange category code applied to the transaction. | 274253 | — |
IC Code Description | A description of the interchange category code. | MC Business Level 1 Standard | — |
MCC | The Merchant Category Code passed from the PSP for the transaction. | 1234 | — |
MID | The Merchant ID tied to the transaction. | 123456789 | SE Number |
MOTO Indicator | Codes indicating if the transaction was Mail Order or Telephone Order. | 5 | — |
MOTO Indicator Description | A description of the MOTO indicator code. | Non-Authentication E-Comm | — |
POS Entry Mode | The method by which card data was entered at the point of sale. | 108 | — |
POS Entry Mode Description | A description of the POS entry mode used for the transaction. | Manual, EMV-enabled Device, No Track II | — |
Presenter Name | The name of the entity (merchant system or processor) that presented the transaction. | worldpay | — |
PSP Data Source | The Payment Service Provider that supplied the transaction data. | CLE_SETTLEMENT (Fiserv), Vantiv Debit | — |
Settled Day of Month | The numeric day of the month when the transaction was settled. | 15 | — |
Settled Day of Week | The day of the week when the transaction was settled. | TUES | — |
Sub-Category | The transaction sub-type or classification. | RDR, Sale, Refund | — |
Sub-Merchant ID | Identifier used to track the sub-merchant associated with the transaction. | 123456 | — |
Token Indicator | Indicates whether a transaction was processed using a network token. | Network Token | — |
Wallet Type | Identifies the digital wallet used in the transaction | Apple Pay, Google Pay | — |