Issued like a bank record. Accepted like a network. And only a neutral party can complete the set.
Most people who work in payments carry around a clean mental model of the industry: there's an issuing side and an acquiring side. Issuers give cardholders their cards and see one buyer's spend across every merchant. Acquirers sign up merchants and see one seller's revenue across every cardholder. The network sits in the middle and routes the money.
Payment data — the transaction record itself — doesn't sit cleanly on either side. It's a hybrid. Understanding why explains both why a company like ours exists and why the role we play can't easily be filled by anyone else.
Issued
Start with where the data comes from.
A card transaction record is anchored to a card credential and the issuing relationship behind it. That anchoring is not a detail — it's the source of everything that makes the data valuable. Because the record is tied to the credential and rides the authorization stream, it is real-time, it is authoritative, and access to it is permissioned rather than scraped. This is bank-grade provenance.
It's tempting to say the data "belongs to the bank," but ownership is genuinely contested and beside the point. What matters is that the data is issuer-shaped: it describes one cardholder — or one business and its cards — spending across every merchant they touch. That is exactly the shape spend management, expense, and reconciliation products need. They are not trying to understand a merchant's revenue. They are trying to understand a buyer's outflow, as it happens.
This is also the cleanest line between us and the open-banking model. Pulling from the bank account gives you a posted ledger: one institution at a time, a day or more late. Anchoring to the credential on the network gives you the authorization stream: real-time, and — crucially — completable across networks. Same destination, opposite starting point.
Accepted
Now the twist. Issuer-shaped data is only valuable the way acceptance is valuable.
A merchant who accepts only one network isn't really in business. The customer might arrive with any card, so partial acceptance is close to worthless — the merchant needs all of it or none of it matters. Completeness is the entire point. That's why merchants never wanted five separate network integrations and why the acquirers and platforms that collapsed acceptance into a single relationship won.
Payment data behaves identically. A spend platform cannot ship a product that works for Visa cards and silently fails on Mastercard. A data feed with holes in it isn't a partial product; it's not a product. The value lives in completeness, and completeness means every network, delivered through one integration.
So the data is issued in its provenance and accepted in its distribution. Issuer-perspective data, acquirer-style aggregation. That's the hybrid.
The Neutrality Lock
Here is the part that's easy to miss and matters most.
The completeness requirement doesn't merely invite an aggregator. It mandates a neutral one.
Visa will never aggregate Mastercard. Mastercard will never aggregate Amex. No single network will ever complete the set — not because of an integration gap, but by definition. A network exists to advance its own rails, not its competitors'. The "all networks" requirement that makes the data valuable can therefore only be satisfied by a party that sits outside all of them and is aligned with none of them against the others.
That's why an aggregator's neutrality isn't a nice-to-have. It's the mechanism. It's the only structure that can deliver the thing the market actually requires.
It's also why the networks themselves are comfortable participating rather than treating an aggregator as a threat. A neutral data layer extends the utility of their rails to a long tail of developers they'd never serve one by one — and more data utility means more reason to put spend on those rails. The aggregator is accretive to the network, not competitive with it.
Value on More Than One Side
Because the data is a hybrid, the value of aggregating it lands on several sides at once.
The application — the spend platform, the expense tool, the ERP — gets completeness, real-time data, and a single integration in place of a multi-year program of network-by-network builds. The end business gets its spend flowing automatically into the systems it already runs, with controls and reconciliation that work at the speed money actually moves. And the network gets reach and engagement it couldn't economically build for the long tail itself.
The integration cost is paid once, by the aggregator, and amortized across everyone downstream. That's the structural reason the role persists instead of being rebuilt inside every application. It's the same logic that produced acceptance aggregators a layer below — collapse the hard, idiosyncratic, relationship-gated integrations into one, and let everyone build on top.
Where the Analogy Breaks
A useful frame should be honest about its edges, so here's the edge.
We are acquiring-like in aggregation and completeness. We are not acquiring in the sense that matters most to an acquirer: we don't take settlement risk and we don't move money. The data hybrid borrows the shape of acceptance — the completeness requirement, the single-integration economics, the neutrality lock — without inheriting the balance sheet. That's a feature, not a hedge. But anyone reaching for the analogy should know exactly how far it travels.
The Short Version
Payment data is issued in its origins and accepted in its distribution. It needs to be complete to be worth anything, completeness requires neutrality, and neutrality is something no network can offer about its rivals. That gap is not a temporary market inefficiency. It's a structural opening — and it's the one we were built to fill.