Mastercard's new data quality controls for Card Payouts are designed to enforce data quality requirements at a network level. Mastercard will gradually roll out these controls from July 15, 2026 onwards.
To prepare, you should ensure that your API requests are following Mastercard's validation rules to avoid potential declines once these changes take effect. To help you assess your integration's compliance with these requirements, we've listed the relevant API fields and requirements below.
Merchant name
If you use a dynamic billing descriptor to provide a dynamic merchant name in your payout requests using billing_descriptor.name:
- The merchant name must not be blank
- The merchant name must not contain all spaces, zeroes, or unsupported special characters (underscores, hyphens, commas, etc.)
Merchant city
If you use a dynamic billing descriptor to provide a dynamic city in your payout requests using billing_descriptor.city:
- The merchant city must not be blank
- The merchant name must not contain all spaces, zeroes, or unsupported special characters (underscores, hyphens, commas, etc.)
- The merchant city must not contain a phone number
- The merchant city must not be an invalid value such as 'Internet', your website name, your country name, or street address
Sender city
For the sender.address.city:
- The sender city must not be blank
- The sender city must not contain all spaces, zeros, or unsupported special characters (underscores, hyphens, commas, etc.)
- The sender city must match the sender state (sender.address.state) or the sender country (sender.address.country)
Sender country
For the sender.address.country:
- The sender country must not be blank
Transaction purpose
If you send a purpose of payment in instruction.purpose, this must be a valid value.