As Mercury scaled, transactions became a core input to accounting, categorization, and other downstream financial workflows. Standard transaction data wasn’t reliable enough to support those processes until Mercury integrated Spade.
Impact at a glance
- Minimized manual cleanup and customer frustration caused by inconsistent merchant data
- Turned transactions into reliable inputs for accounting and financial automation
- Supported a best-in-class corporate card experience built on consistent transaction context
Together, this foundation supports a company operating at significant scale with over 200,000 customers, one in three U.S. startups on the platform, and $650M in annualized revenue.
The Opportunity
Mercury provides banking and financial tools for startups and small businesses that want clarity and control over their finances. For many customers, Mercury functions as a financial operating system, where transactions flow directly into accounting, expense management, and financial automation.
At Mercury’s scale, transaction data isn’t just displayed in a feed — it’s consumed by downstream systems that depend on accuracy and consistency. Merchant names, categories, and identities need to hold up not only for user visibility, but when passed directly into accounting workflows and automated processes.
Before Spade
Like most fintechs, Mercury relied on Merchant Category Codes and raw transaction descriptors. In practice, this data was often inconsistent. The same merchant could appear under multiple names, categories were too broad to be useful, and edge cases required manual intervention.
These gaps initially became evident in accounting processes. Inaccurate merchant data forced customers to reclassify transactions and reconcile records by hand, introducing friction into workflows that were meant to feel automated and reliable.
With Spade
The Mercury team responsible for accounting workflows was the first to integrate Spade’s API. Instead of parsing descriptors or relying on MCCs, each transaction could be tied to a stable business entity with reliable metadata. This improved accounting accuracy and reduced manual cleanup.
As Mercury recognized that other parts of their platform could benefit from the same enriched transaction data, Spade became shared infrastructure across the business — including the corporate card experience, where consistent transaction context supports clearer categorization and more predictable behavior.
Applications Beyond Mercury
Mercury’s experience highlights a broader pattern for fintechs building products where transactions feed downstream systems. As companies scale, transactions stop being an endpoint and become an input — powering accounting, automation, and customer-facing workflows.
When transaction data is unreliable at the source, inconsistency compounds downstream. Investing in accurate, structured transaction enrichment as core infrastructure allows fintechs to reduce operational overhead, maintain data integrity across products, and scale without introducing additional complexity.