Appendix
Standardization of transaction data elements mandate
Fields for Standardization of transaction data elements mandate below
| Location/Transaction Type | Acceptor Name | Acceptor Street Address/Postal Code / City/ Country Subdivision / Country | Service Location / City / Postal Code / Coutnry Subdivision / Country |
|---|---|---|---|
| Static Location | Merchant name: The name of the merchant at the store location | Merchant store location: The address of the merchant store location | |
| Variable Location | Merchant name: The name of the merchant business | Business office location: the address of the merchant primary business location | Servicing location at the time of interaction: the location of the physical customer interaction with the merchant |
| Mail or telephone order | Catalog name: the name of the merchant business or catalog name | Business office or processing center location: the address of the merchant primary business location or order processing center location | |
| Ecommerce | Catalog name: the name of the merchant business or catalog name | Business office or processing center location: the address of the merchant primary business location or order processing center location | |
| Ecommerce: electric vehicle charging for fuel purchase | Service name: the name of the merchant business or service name | Business office location: the address of the merchant primary business location | Location of the charging station or refueling station |
| Ecommerce: in-store pickup | Website name: the name of the merchant business or website name | Business office or processing center location: the address of the merchant primary business location or order processing location | Merchant store location: The location of the merchant store |
| Ecommerce: marketplace | Marketplace name: the name of the merchant business or marketplace name | Business office or processing center location: the address of the merchant primary business location or order processing location | |
| Takeout dispatchers | Dispatcher name seller name: The name of the food order service followed by the restaurant name | Business office or processing center location: The address of the food order service primary business location or order processing center location | Seller store location: the location of the restaurant |
| Travel and rental reseller/booking | Website name: The name of the merchant business or website name | Business office or processing center location: The address of the merchant primary business location or order processing center location | Place of service or point of origin: The location where services are consumed or the starting location of transport |
| Ride-hailing | Service name: The name of the merchant business or service name | Business office location: The address of the merchant primary business location | Place of service or point of origin: The location where services are consumed or the starting location of transport |
| Onboard transit | Service name: The name of the merchant business or service name | Business office location: The address of the merchant primary business location | lace of service or point of origin: The location where services are consumed or the starting location of transport |
Mastercard's Standardization for authorization
The following data elements and subfields are impacted by Mastercard's Standardization for authorization:
| Field Name | Where will the data come from | Notes |
|---|---|---|
| Acceptor Name | Masterfile | |
| Acceptor City Name | Masterfile | Now has to have the city. The phone number and URL are now sent in a new field |
| Acceptor Country Code | Masterfile | |
| Version Code | System | Identifies if message is capable of the new data fields and values |
| Acceptor Street Address | Masterfile | |
| Acceptor Country Subdivision Code | Masterfile | State or Province |
| Acceptor URL | Masterfile | |
| Acceptor Customer Service Phone Number | Masterfile | Now will be populated from the Merchant Descriptor phone number field on merchant profile |
| Acceptor Phone Number | Masterfile | Optional - Fiserv will not be created this field |
| Acceptor Additional Contact Information | N/A | Optional - Fiserv will not be created this field |
| Acceptor Tax ID | N/A | Optional - Already sent in clearing. Fiserv will not be sending in authorization |
| Partner ID Code | N/A | Optional - Need a Business Case, otherwise, Fiserv will not be creating this field |
| Service Location City Name | Merchant through new field in the specification | Only needs to be sent if transaction occurred in a State other than the city the merchant location |
| Service Location Subdivision Code | Merchant through new field in the specification | Only needs to be sent if transaction occurred in a State other than the city the merchant location |
| Service Location Country Code | Merchant through new field in the specification | Only needs to be sent if transaction occurred in a Country other than the city the merchant location |
| Service Location Postal Code | Merchant through new field in the specification | Only needs to be sent if transaction occurred in a Postal Code other than the city the merchant location |
Mastercard's Standardization for settlement
The following data elements and subfields are impacted by Mastercard's Standardization for settlement:
| Field Name | Where will the data come from | Notes |
|---|---|---|
| Acceptor Name | Masterfile | |
| Acceptor Street Address | Masterfile | |
| Acceptor City Name | Masterfile | Now has to have the city. The phone number and URL are now sent in a new field |
| Acceptor Postal Code | Masterfile | |
| Acceptor Country Subdivision Code | Masterfile | State or Province |
| Acceptor Country Code | Masterfile | |
| Acceptor Customer Service Phone Number | Masterfile | Now will be populated from the Merchant Descriptor phone number field on merchant profile |
| Acceptor URL | Masterfile | |
| Service Location City Name | Merchant through new field in the specification | Only needs to be sent if transaction occurred in a City other than the city the merchant location |
| Service Location Subdivision Code | Merchant through new field in the specification | Only needs to be sent if transaction occurred in a State other than the city the merchant location |
| Service Location Country Code | Merchant through new field in the specification | Only needs to be sent if transaction occurred in a Country other than the city the merchant location |
| Service Location Postal Code | Merchant through new field in the specification | Only needs to be sent if transaction occurred in a Postal Code other than the city the merchant location |