By clicking “Accept ”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Cookies Policy for more information.
Blog
Información del producto

In-house vs. Third-party Solutions for Mastercard AN4569 Compliance: Making the right choice

Por
Ondřej Slivka
4
min de lectura

When it comes to compliance with Mastercard AN4569 and the implementation of tools for payment data enhancement, businesses often find themselves at a crossroads — whether to develop an in-house solution or leverage third-party expertise. While the allure of internal development might be tempting, practical considerations and industry insights often favour the efficiency and effectiveness of external solutions.

The pitfalls of in-house development

Developing an in-house payment data enhancement tool involves creating a comprehensive merchant knowledge base. While this may sound like a viable option at first, the practicalities tell a different story. The process is inherently time-consuming, diverting valuable resources away from core business activities. Furthermore, it's a more expensive endeavor compared to the cost-effective alternative of opting for external solutions.

Maintenance and updates become an ongoing challenge with an in-house solution. Tasks such as adding new entries, removing outdated ones, and implementing changes demand significant manpower. This continuous effort to ensure data correctness can lead to a drain on resources that could be better allocated elsewhere within the organisation.

The reality of data correctness

Maintaining data correctness is a critical aspect of compliance with Mastercard AN4569. Notably, the fact that most businesses rebrand every 7-10 years and 8% of logos change yearly underscores the dynamic nature of merchant information. An in-house solution might struggle to keep up with these changes, potentially compromising the accuracy and completeness of payment data.

Below you can see an example of the data correctness process put in place.

example of the TapiX data validation and correctness process
Correctness of enhanced data should be priority. Without the correct inputs there can be no quality outputs.

Speed and efficiency at the center

With digital transactions, timing is an absolute key factor. Building an in-house solution could take months, consuming precious time and delaying compliance efforts. In contrast, deploying an external solution, such as partnering with a third-party provider, usually requires just a few weeks. This speed is crucial for businesses seeking swift compliance with Mastercard AN4569 while minimising disruption to their operations.

Example of a TapiX API implementation that regularly takes 2-3 months to go live for a typical bank in the market
Example of a Tapix API implementation that regularly takes 2-3 months to go live for a typical bank in the market

Why collaborating with a third-party is the way to go

For most companies, the favoured approach for enhancing payment data and complying with Mastercard AN4569 is collaborating with a third-party solution provider. External solutions bring specialised expertise, efficiency, and cost-effectiveness to the table. With a dedicated focus on payment data enhancement, third-party providers can navigate the complexities of compliance more effectively than businesses attempting to manage it internally.  

In conclusion, the decision between in-house and third-party solutions for Mastercard AN4569 compliance is vital. While the idea of internal development may be appealing, the practicalities often tip the scales in favor of external solutions, ensuring businesses can navigate the intricacies of enhancing payment data with speed, accuracy, and efficiency.

Appendix A: Details of scheme compliance requirements 

Sourced from AN4569 Revised Standards for Mastercard Rules (published 4 April 2023) 

Enhanced Merchant Data. Effective 14 October 2023, an Issuer in Albania, Andorra, Austria, Belgium, Bosnia, Bulgaria, Channel Islands, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Gibraltar, Greece, Hungary, Iceland, Ireland, Isle of Man,  

Italy, Kosovo, Latvia, Liechtenstein, Lithuania, Luxembourg, Macedonia, Malta, Moldova, Monaco, Montenegro, Netherlands, Norway, Poland, Portugal, Romania, San Marino, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Ukraine, United Kingdom or Vatican City must provide to a Cardholder enhanced Merchant data, when available, to help the Cardholder recognize a Transaction when it is queried by the Cardholder. Such enhanced Merchant data includes, when available, without limitation, the Merchant’s public facing or ‘doing business as’ name, location, contact details and logo. The Issuer must provide the enhanced Merchant data via the Issuer’s banking application, mobile wallet, Internet banking interface, or other digital means that provides at least equivalent ease and accessibility for the Cardholder. 

Acerca del autor

Ondřej Slivka, un entusiasta del marketing, le encanta compartir conocimientos en el mundo de la banca digital y la tecnología financiera.

Ondřej Slivka

Senior insider

Un experimentado entusiasta del marketing B2B con más de 5 años de experiencia compartiendo conocimientos en el mundo de la banca digital y la tecnología financiera. Mi pasión radica en la elaboración de estrategias innovadoras y el compromiso con un contenido capaz de ofrecer los resultados deseados.

Tabla de contenido