This guide provides a comprehensive overview of key factors that influence the performance of Genify's APIs, including how transaction data is matched with merchants, and how real-time data expansion improves coverage. It also explains the latency differences between transactions that have been processed before versus new transactions.
Real-Time Merchant Expansion
We continuously expand our merchant coverage in real-time, leveraging ever-growing third-party sources of information. This dynamic growth ensures that more transactions are accurately matched with merchants over time. Additionally, we maintain a constant review process to ensure the highest accuracy, providing our users with the most up-to-date and precise data available.
Understanding Matches vs. Non-Matches
In this section, we explain the difference between Matches and Non-Matches in Genify's transaction enrichment process:
- Matches: These are transactions where we are highly confident that the merchant has been formally identified by our system. Matches occur when a transaction description has been enriched before or when the extracted merchant from the transaction description is one that our system recognizes. Since these merchants have been identified multiple times, we guarantee the top accuracy of the merchant details provided. These include both transactions that have been retrieved and previously enriched, as well as those where the merchant extracted from the description is recognized as a formally identified merchant.
- Non-Matches: Non-matches represent newer or less commonly seen merchants in our system. These merchants are typically the result of our growing integration with third-party services and are often enriched through their online presence. While we continue to expand our coverage, the accuracy of non-matches depends more on the merchant's online footprint, making these less certain than our matches.
Latency for Seen vs. Unseen Transactions
Latency varies significantly depending on whether a transaction description has been seen before by our system:
- Seen Transactions: When a transaction description has been processed previously, the latency is at its lowest, typically around 1 second. This efficiency is due to our system's familiarity with the merchant and the associated details, allowing for quick retrieval and enrichment of the data.
- Unseen Transactions: Conversely, if the transaction description is new and has not been encountered before, the latency increases to approximately 2 to 4 seconds. This higher latency occurs as our system needs to analyze and enrich the transaction details based on the merchant's online presence, which may require additional time for processing and data collection.