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
Product insights

What is vital for a perfect PoC and how to set the right expectations

By
Michal Maliarov
3
min read

Every project in the digital banking market begins with a solution capability check. A concept that helps financial companies find the best solution for a specific use case while cooperating with the data enrichment provider that is most suitable for their needs. This initial exploration, known as Proof of Concept (PoC), is a cornerstone for any successful and enduring business. Let's learn more about all the vital aspects of the perfect PoC that sets the right expectations for the partnership.

Why is PoC so important?

Regardless of the product, understanding its potential is crucial. In digital banking, it's essential to see how your data can work for you and how to present it to users effectively. It doesn't matter how good the features or analytical models are if the core use case data does not meet the quality requirements. In other words, data is king.  

To determine whether the enrichment provider gets the highest quality data, a Proof of Concept is created. This PoC in banking aims to answer the most critical questions: Can it offer sufficient data coverage for the bank’s needs? Is the accuracy high enough, with a low error rate?

POC in banking shows high-quality data input yields accurate results, poor data causes bias.

How to build a working PoC

Step 1: Pick a goal according to usecase and set realistic expectations

Specify the goal the PoC needs to achieve and the use case it's intended for. Determine the criteria and expectations for this assessment. Is the PoC focused solely on bank card transactions, or does it include regular bank account transfers and open banking data? The type and amount of data to enrich depend on this decision. When selecting data for your PoC, it’s essential to use a random and representative sample without filtering or deduplication. This approach provides a realistic benchmark for results, helping to avoid inflated expectations.

Additionally, providing all vendors with an identical data sample promotes fairness, making it easier to compare outcomes accurately. We recommend selecting a substantial sample size - such as one to two days’ worth of transactional data (at least one million transactions) - to avoid artificial enhancement and ensure the PoC results mirror real-world conditions.

Step 2: Choose the right data sample according to your goals

As mentioned above, you need a sample that accurately represents real data. This means:

  • No filtering (leaving out big merchants, transactions from some countries or e-commerce)
  • No unique transactions or terminals. Data sample needs to be from a specific time period
  • Data sample needs to be the right size (1-10k as a small sample, 100k and more as a big sample)

Additionally, provide correct input parameters in a correct format.  

They differ for card and bank transactions, so it's crucial to provide as many parameters as possible. Key parameters for data enrichment include:

  • Merchant ID: key parameter for determining the specific business branch  
  • Merchant description (name, logo, category): key parameters for determining the merchant and specific branch
  • MCC code: key parameter for categorizing merchants
  • Country: key parameter for categorizing merchants and recognizing branches  
  • PoS ID: key parameter for differentiating merchants in the same region (f.ex. same city)
To learn what input data is required, and its ideal structure used to enrich the card payment data – refer to this link.

Step 3: Define the length of the POC in advance

The PoC length needs a proper connection to the goals and resources the company wants to invest in during the testing period. To maintain fairness, all participating vendors should have identical timelines, with clear start and submission dates communicated well in advance. Additionally, setting a relatively short duration for the PoC, such as two to three days, can reduce the likelihood of manual data boosting, ensuring a true reflection of each vendor’s capabilities.

Step 4: Data enrichment and final evaluation

To unlock the full potential of each solution, supply vendors with all possible input parameters for the PoC. This includes sharing a structured data sample in advance for vendor feedback, allowing each provider to prepare effectively. Also, consider that transaction types - like card transactions versus account-to-account (A2A) transfers - require different data input parameters. Accounting for these variations ensures a comprehensive test of each vendor’s solution.

To obtain the most specific and helpful results, address the three crucial aspects of data quality: Coverage, Accuracy, and Information richness. The best approach is to compare data samples from different vendors, take into account approximately 100 transactions and identify differences in the provided information. Subsequently, evaluate the accuracy and richness of data from each provider. For more information, read our article about why data quality matters.

Key factors to evaluate include:

  • Brand Name Recognition: Verify the correctness of recognised brands (e.g., distinguishing between a Tesco supermarket and a flower shop inside a Tesco location).
  • Logo Quality: Assess the clarity and appropriateness of displayed logos.
  • Categorisation Consistency: Ensure categories are applied consistently, with minimal use of overly generic categories like “Other.” Note that models based primarily on MCC codes may lead to less accurate categorisation.
  • GPS Precision: For physical locations, ensure the accuracy of GPS data, distinguishing between headquarters and individual store locations.
  • Clean Merchant Names: Confirm that merchant names are presented clearly and consistently across instances for ease of understanding.

How to approach PoC according to size

Small PoC (1 - 10k of trx)

Simple sample sharing with a duration of ~1 week, minimal effort on the bank's side. 

Typical goals: Direct comparison of multiple solutions (including internal). Data richness insight (e.g. categorisation granularity, GPS accuracy).

Advantages: Possibility of partially testing data accuracy and richness. Relatively short time frame and low costs. Manual sample boost with high impact on results.  

Disadvantages: Not possible to test real coverage, the sample is not representative of typical operations.

Large PoC (100k - milions of trx)

‍‍Simple sample sharing with a duration of ~1 week, minimal effort on the bank's side (e.g. 1-2 days worth of data from standard operation).

Typical goals: Have realistic understanding of the service quality in terms of Coverage, Accuracy and Data richness (e.g. categorisation granularity, GPS accuracy).

Advantages: Realistically set expectations while knowing what the solution is capable of delivering. Testing of real life coverages alongside accuracy and richness. Avoiding buying a “pig in a poke” which is not possible with a smaller POC due to its limitations.

Disadvantages: Evaluation of such a big sample is a resource needy task (e.g. this is not a comparison of 2 numbers anymore).

Custom PoC

Custom PoC are usually project-managed with significant resources invested, using large data sample and longer time frame to complete (usually 1-3 months).

Typical goals:
Feasibility study (e.g. Friends and Family) and business case validation (e.g. impact evaluation on default loan rate).

Advantages: Opportunity to thoroughly test service and build strong business case. Longer period offers a chance for data enrichment service to focus on most relevant data to improve on it gradually.

Disadvantages: Resource heavy on both vendor and bank side => costs need to be considered. 

Conclusion

The journey from exploration to market-ready solutions is not simple, but a well-built PoC serves as your compass, helping you understand the capabilities of different solutions. Picking the right PoC for your needs is a crucial step for achieving the expected results and avoiding mistakes that can occur in the process. Such mistakes include a lack of alignment with your data enrichment provider, insufficient specific data, or a simple lack of time due to an incorrect PoC model choice. Your time invested in a well thought out Proof of Concept today is the cornerstone for tomorrow's success story.

About author

Michal Maliarov, an enthusiastic writer who loves to talk about fintech, AI and the mobile tech market.

Michal Maliarov

Senior insider

A creative enthusiast who has spent half of his life in the technology industry. Passionate about fintech, AI, and the mobile tech market. Navigating the thin line between the worlds of media and advertising for over 10 years, where he feels most at home.

Table of contents