It is a self-serve merchant deduplication engine designed for banks. Banks face issues carrying out any analysis using merchant data. Merchant descriptions are all over the place and analysis done on such data is inaccurate. The Merchant Match team built a self-serve engine that would deduplicate AND clean a bank’s merchant data. Allowing banks to conduct merchant-centric analysis, that is both accurate and actionable.

Merchant deduplication is a process that identifies, deduplicates and matches multiple merchant descriptions to one entity. Merchant Match uses its algorithms to deduplicate merchant descriptions while matching them with a global merchant repository which the team curates on a continuous basis.

Merchant-centric analysis must feed off of a clean, unified merchant dataset. Unclean data leads to inaccurate analysis. Merchant Match allows banks to have a strong foundation to carry out analysis centred around their merchant data.

Merchant Match takes about 2 hours to deduplicate and clean 1 million rows of merchant data. Doing the same manually or with a team would take banks anywhere between 6 to 12 months. It’s a no-brainer!

Immediately after sign up. Banks can sign up and test the engine before they pay for it.

Absolutely! The aim is to prove the power of Merchant Match before it costs anything. Test Drive now!

Merchant Match currently works in countries where the merchant data is in English.

Merchant Match is the only deduplication engine for banks.
It is the fastest and most accurate out there.
It is the easiest engine to use, with zero manual intervention.
At a never before value.

If a bank operates in India, payment is through netbanking.
Any other bank can pay through either Paypal or netbanking.
Reach out to yuwa@crayondata.com for more information on payments.

Once banks have tried out the product, the Merchant Match team will reach out to them regarding an annual contract. The billing will only allow for annual contracts.

An auto renewal clause will be available at the end of the 11th month.

Merchant Match can be run only 12 times in a year.

Banks will be able to access their cleaned data only through the duration of the contract.

Yes. But remember, each account will be limited to 12 runs in a year.

Not to fret. If the team detects that the process ended unexpectedly, they will provide an additional run.

Data is stored in a highly secure cloud storage environment on AWS (S3 storage).

Merchant Match works well with any quantum of merchant data. It is recommended to feed as much data as possible to finetune the output that the engine provides. Merchant Match has seen a much higher accuracy when the quantum of data is greater than 500,000 rows.

Merchant Match was designed with the goal of addressing a core problem in banks - unclean merchant data.

No. Merchant Match currently only works with merchant data pertaining to banks.

The engine is currently able to process CSV files only. Subsequent updates of Merchant Match will be compatible with other input file formats.

The downloadable output file will be in a CSV format. Subsequent updates of Merchant Match will offer other output file formats.