# Additional Acceptor and Service Location Data source: https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/trans-enrich-data/add-accep-ser-loc-data/index.md ## Mastercard Data Quality {#mastercard-data-quality} Mastercard Data Quality (MDQ) is a Mastercard initiative to help all the parties in the payment ecosystem have equal access to the clear information needed to support and create valuable products and services for their customers. Merchants can submit more information about the transaction and its location to: * Improve the quality of services offered to cardholders including rewards and offers. * Increase cardholder approval rates. ## Prerequisites {#prerequisites} To comply with the MDQ requirement: * Your merchant profile on the gateway must be enabled for Additional Acceptor and Service Location Data. Warning: This privilege will be displayed under the compliance section of Manage Merchant - Merchant payment details. For more details, refer to the [Enabling for Additional Acceptor and Service Location Data](https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/trans-enrich-data/add-accep-ser-loc-data/index.md#enabling-additional-acceptor-and-service-location-data) section. Your acquirer must support the MDQ initiative by having SUPPORT_ADDITIONAL_ACCEPTOR_AND_SERVICE_LOCATION_DATA capability. If your merchant profile is Aggregator, you must integrate with Mastercard Gateway API version 84 or later. Provide all the required fields as per the merchant type. For more details, refer to [Fields requirement for processing transaction as per MDQ compliance"](https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/trans-enrich-data/add-accep-ser-loc-data/index.md#fields-requirement-for-processing-transaction-as-per-mdq-compliance) section. ## Enabling Additional Acceptor and Service Location Data {#enabling-additional-acceptor-and-service-location-data} To enable for Additional Acceptor and Service Location Data for merchant type standard, Installment Service Provider and Marketplace ensure that the following mandatory fields are present: * Merchant website URL is required if a merchant is configured to process Internet-based transactions. * Phone or escalation number is required if a merchant is configured to process non-internet-based transactions. ## Fields requirement for processing transaction as per MDQ compliance {#fields-requirement-for-processing-transaction-as-per-mdq-compliance} Warning: For merchant type Standard, Installment Service Provider and Marketplace, the required fields will be sourced from the main profile. For merchant type Standard, Installment Service Provider and Marketplace enabled as Dynamic Descriptor the required fields will be sourced from API when provided or from the main profile when not provided. Refer to the following new fields introduced for MDQ compliance to know the new API fields. ### Ecom configured to process Internet-based transaction: {#ecom-configured-to-process-internet-based-transaction} * `order.subMerchant.address.street` * `order.subMerchant.address.city` * `order.subMerchant.address.postcodeZip` * `order.subMerchant.address.stateProvince` * `order.subMerchant.address.country` * `order.subMerchant.websiteUrl` ### Non Ecom configured to process non-internet-based transaction: {#non-ecom-configured-to-process-non-internet-based-transaction} * `order.subMerchant.address.street` * `order.subMerchant.address.city` * `order.subMerchant.address.postcodeZip` * `order.subMerchant.address.stateProvince` * `order.subMerchant.address.country` * `order.subMerchant.phone/order.subMerchant.disputeContactPhone` Warning: Provide `order.subMerchant.identifier` and `order.subMerchant.tradingName` mandatory field for submitting sub merchant details, without these fields transactions will be treated for standard merchant-initiated transaction fetched from merchant profile or dynamic descriptor. ## New fields introduced for MDQ compliance from version 84 {#new-fields-introduced-for-mdq-compliance-from-version-84} The following new fields are introduced for merchant types as a part of the MDQ initiative: * For merchants enabled for Dynamic Descriptors a new field is introduced through API `statementDescriptor.websiteUrl` to update merchant's dynamic descriptor website URL. * For Merchant type such as Payment Facilitator or Sub merchant a new field is introduced through API subMerchant.websiteUrl to update the submerchant's website URL. * PartnerId Code order.merchantPartnerIdCode is an optional field which can be submitted through API to represent a partnership agreement between you and the issuer. * `Transaction.serviceLocation` parameter block is conditional and will be submitted through API when transaction service location is different than your registered business location. When submitting this block all the fields in the block such as `transaction.serviceLocation.city`, `transaction.serviceLocation`, `stateProvinceCode`, `transaction.serviceLocation.country`, and `transaction.serviceLocation.postCodeZip` are expected on the request. ### Service location examples: {#service-location-examples} ![](https://static.developer.mastercard.com/content/mastercard-gateway/uploads/service_location_eg_1.png) ##### Service location example 1 ![](https://static.developer.mastercard.com/content/mastercard-gateway/uploads/service_location_eg_2.png) ##### Service location example 2 Alert: The genuineness of Additional Acceptor and Service Location Data submitted will not be checked. Ensure the accuracy and correctness of the location and service details that you submit. ## Frequently asked questions {#frequently-asked-questions} You must provide all the required fields as per the merchant type. Refer to the [Fields requirement for processing transaction as per MDQ compliance](https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/trans-enrich-data/add-accep-ser-loc-data/index.md#fields-requirement-for-processing-transaction-as-per-mdq-compliance) and have Additional Acceptor and Service Location Data checked. Transaction will not be rejected for not providing the required fields, however, to provide the additional acceptor and service location data, you must be enabled for Additional Acceptor and Service Location Data. Currently, there are varying adoption timelines for different parties in the payments industry.