Additional Acceptor and Service Location Data
Mastercard Data Quality (MDQ)
MDQ is 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
To comply with MDQ requirement:
- Your merchant profile on the gateway must be enabled for Additional Acceptor and Service Location Data.
This privilege will be displayed under compliance section of Manage Merchant - Merchant payment details. For more details refer to “Enabling for Additional Acceptor and Service Location Data" section.
- Your acquirer must support MDQ initiative by having SUPPORT_ADDITIONAL_ACCEPTOR_AND_SERVICE_LOCATION_DATA capability.
- If your merchant profile is Aggegator, you must integrate with DirectAPI version 84 or later.
- You must provide all the required fields as per the merchant type. For more details refer to “Fields requirement for processing transaction as per MDQ compliance” section.
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 ensures that 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
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:
-
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:
-
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
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
Following new fields are introduced for merchant types as a part of MDQ initiative:
- For merchants enabled for Dynamic Descriptors a new field is introduced through API
statementDescriptor.websiteUrlto 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 submerchant's website URL.
- PartnerId Code
order.merchantPartnerIdCodeis an optional field can be submitted through API to represent a partnership agreement between you and the issuer. Transaction.serviceLocationparameter 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, andtransaction.serviceLocation.postCodeZipare expected on the request.Service location examples:
Figure: Service location example 1
Figure: Service location example 2
Frequently asked questions
What is required to make a transaction AN6022 compliant?
You must provide all the required fields as per the merchant type. Refer to the “Fields requirement for processing transaction as per MDQ compliance” and have Additional Acceptor and Service Location Data checked.
Will the transaction be rejected if required fields are not provided?
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.
When will the MDQ mandate be effective?
Currently, there are varying adoption timelines for different parties in the payments industry.