What Pagos actually is
Pagos is a measurement company. It connects to the processors and gateways a merchant already uses, normalizes the data those systems emit into one comparable dataset, enriches it with its own card-BIN database, and reports on what is happening: approval rates, declines and their reasons, retry outcomes, fees, interchange, and how it all compares against benchmarks.
It is not in the payment. Pagos does not acquire, authorize, route, settle, hold funds or carry chargeback risk, and holds no acquiring registration or money transmission licensing because it never touches money. CEO Klas Bäck has described it as turning disparate payments data into actionable insight without requiring customers to change their payment processors — the strategy in one line: Pagos sells to merchants who are not ready to switch anything.
The clearest way to place Pagos is against the orchestration platforms it gets listed beside. An orchestrator sits in the authorization path and executes a routing decision; Pagos sits outside it and reports what the decisions produced. It does sell Decision Signals — recommendations about retry and routing behavior — but the merchant, or its orchestration layer, has to act on them. That is the whole risk profile: Pagos cannot take your checkout down, and cannot fix a decline either.
How Pagos works and where it sits in the stack
The product divides into three layers, as Pagos itself describes it.
- The foundation layer ingests and harmonizes data. Processors emit transaction records in incompatible schemas, with incompatible decline taxonomies and fee reporting. Pagos normalizes them into one dataset exposed through a Data Ingestion API, an Enrichment API, warehouse export and, since 2025, a Model Context Protocol server.
- The intelligence layer is what most buyers think they are buying: payments monitoring, insights, cost optimization and Decision Signals.
- Credential management behaves least like analytics and most like a service — BIN data, account updater and network tokenization, sold as usage-priced APIs.
The credential-management products attack a different problem from the analytics. Account updater refreshes stored card details when an issuer reissues a card; network tokenization replaces the card number with a token that survives reissue. Both exist to stop recurring revenue leaking through expired cards, a subscription merchant can buy them without the analytics, and the revenue they recover is directly measurable — the easiest part of the line to justify to a finance team.
None of this changes the merchant's contractual position. Acquirers stay acquirers, gateways stay gateways, chargeback liability stays where it was, and Pagos's fees are software fees on top of what the processors already charge.
How Pagos prices
Pagos publishes more pricing than almost anyone else in payments, which is a genuine differentiator. As of July 2026 the public page shows a free tier with capped processor connections and a monthly transaction allowance, a mid-market tier at a published monthly price, and a custom enterprise tier. Add-on API products are priced per transaction or per query.
Two structural features shape the real bill. Add-ons carry per-product monthly minimums, so light usage pays the minimum rather than the usage; and each tier includes a transaction allowance and charges overage above it. The free tier is unusually useful, letting a merchant find out whether the harmonized view tells it anything new before procurement is involved.
Higher-volume API and enterprise pricing is quoted by sales, and contract length, termination terms, service levels and data-deletion commitments are not published at all. Pagos publishes no standard customer agreement — the /company and /terms-of-service URLs both returned errors in July 2026 — so everything contractual must be negotiated. For a vendor whose product is custody and analysis of a merchant's transaction data, that is the gap a security review lands on first.
Where Pagos is genuinely strong
Independent comparison across processors. This is why the company exists. A merchant running two or more acquirers is otherwise reading several sets of reporting, each produced by a party with an interest in how it reads. Pagos produces one view from the merchant's own raw data that can be used to challenge a processor's account of its own performance at renewal. That is a different thing from a better dashboard.
The API and data-delivery surface. Pagos is API-first and, unusually, does not insist on being where you look at the data. Ingestion and Enrichment APIs, BIN and account-updater APIs, warehouse export and an MCP server deliver payments data into systems the merchant already runs, rather than into a vendor portal.
It requires nothing to be switched. Instrumenting payments before changing providers is the right order of operations, and Pagos is adopted without touching production payment flow — an integration risk close to nil.
Where Pagos falls short
It replaces nothing, so it is pure additional cost, and its fee must be justified entirely out of decisions made better — achievable at scale, hard to prove below it. That is why single-processor merchants should think carefully: the value comes from normalizing across providers and from statistically meaningful volume, and a merchant on one processor can usually get most of this from that processor's own reporting at no extra cost.
Decision Signals stop short of doing anything. Pagos recommends retry and routing behavior; something else must implement it. A merchant without an orchestration layer or engineering capacity to act will find recommendations accumulating unactioned — a common and expensive way for analytics purchases to fail. The add-ons compound this: each carries a monthly minimum, so modest usage pays as though it were heavy.
The scale claims do not reconcile, and Pagos does not define them. The website cites benchmarking against more than $2 trillion in network volume and 100 billion-plus events monitored; the March 2026 press release cites more than 16 billion transaction events ingested and more than $1.3 trillion in volume processed. Those sets measure different things and neither is defined publicly. Treat every Pagos scale figure as company-stated and undefined.
It carries no risk on your behalf, and its security posture is thinly evidenced. Pagos cannot stand behind an acceptance or settlement outcome, or help a merchant no processor will approve. It states PCI DSS and SOC 2 Type I and Type II compliance and AWS hosting, but publishes no attestation reports, no PCI DSS level, no ISO 27001 certification and no GDPR statement.
Ownership, funding and the vendor-viability question
Pagos Solutions, Inc. was founded in 2021 by Klas Bäck, Albert Drouart and Daniel Blomberg, several of them former Braintree, Venmo and PayPal leaders. It raised a $10M seed round in October 2021 co-led by Underscore VC and Point72 Ventures. An oversubscribed $34M Series A led by Arbor Ventures followed in February 2023, at which point the company reported roughly 41 employees and over a billion annualized transactions. Since then the public record is product news rather than financing news: the first payments-intelligence MCP server in 2025, an expanded conversational version in February 2026, and an AI-ready payments data platform in March 2026.
Pagos also attracts little independent scrutiny: no Wikipedia entry, and little trade-press coverage beyond funding announcements and its own releases, so most of what can be said comes from Pagos. Headquarters is a small example — 2026 press releases carry a Los Angeles dateline, but the company was described as remote-first at launch and publishes no address. Named customers including Adobe, Eventbrite, GoFundMe, StubHub, Ultra Mobile and Warner Bros. Discovery are the strongest external evidence available. No controversies or litigation were found.
How to evaluate Pagos before you buy
This is a low-integration-risk purchase, so diligence should concentrate on two questions: will the insight change a decision, and will the vendor be here in three years.
- Use the free tier as the evaluation. Connect one or two processors, run it for a full billing cycle, and write down every decision you would have made differently. If that list is short, paid tiers will not lengthen it.
- Establish who acts on the output. Analytics nobody owns produce nothing. Name the person, and confirm there is an orchestration layer or engineering allocation capable of implementing a retry or routing change once Pagos recommends one.
- Price the add-ons against real volume, including the minimums — BIN data, account updater, network tokenization and Decision Signals each carry a monthly floor — and ask for the definitions behind the scale claims: what counts as a transaction event, what counts as volume processed, and what the benchmark cohort consists of. Benchmarks are useful only if you know who you are compared against.
- Get contract terms in writing, because none are published — term, notice, service levels, price-change rights, data retention, deletion on termination and export format — then ask what happens to your ingested transaction history when you leave. Request the PCI DSS Attestation of Compliance and level, the SOC 2 Type II report and the subprocessor list.
- Do vendor-viability diligence properly. Ask directly about funding since February 2023, current headcount, runway and customer count. A small vendor holding a copy of your payments data is a concentration risk worth sizing, and the answers are not available elsewhere.
- Compare against the two honest alternatives: your processors' native optimization tooling, bundled and adequate if you are concentrated on one provider; and building the normalization in your own warehouse, which many large merchants do, trading engineering time and a self-sourced BIN database for no recurring software fee.
Capability assessment
Every company profiled on this site is assessed against the same eighteen dimensions, so the profiles can be read against one another. Each rating carries one sentence of evidence. There is no score out of ten, because a score is not defensible and a sentence is.
Core strength means a primary, differentiating capability. Supported means genuinely offered and documented, but not a differentiator. Limited means partial, geographically restricted, gated behind an enterprise tier, or delivered through a third party. Not offered means what it says. Unclear means the company markets the capability but does not document it well enough to judge — which is itself a finding.
Who Pagos suits
- Large merchants running two or more processors or acquirers who cannot get a single comparable view of approval rates, declines, fees and interchange across them.
- Payments teams inside enterprises who need to justify or challenge processor performance with independent data, rather than relying on each processor's own reporting.
- Recurring and subscription merchants whose revenue leaks through expired or reissued cards, where account updater, network tokenisation and BIN-level intelligence attach directly to recovered revenue.
- Companies that want payments data delivered into their own warehouse or into an AI assistant, rather than consumed only through a vendor dashboard.
- Merchants who want to instrument payments before they change providers, since Pagos explicitly does not require switching processors.
Who Pagos is a poor fit for
- Merchants looking for a processor, gateway or orchestration layer — Pagos does not authorise, route or settle transactions, so it is an addition to the payment stack, not a replacement for any part of it.
- Single-processor and low-volume merchants: the product's value comes from normalising and comparing across providers and from statistically meaningful volume, and a merchant on one processor can usually get most of this from that processor's own reporting at no extra cost.
- Buyers who require vendor-viability assurance. Pagos is a small company: 41 employees were reported at the time of its $34M Series A in February 2023, and no subsequent funding round has been publicly announced as of July 2026, which is an unusually long gap for a venture-backed company at that stage. Valuation, revenue and current headcount are all unpublished.
- Organisations that need published contractual terms before buying — Pagos publishes tier and add-on pricing but no standard customer agreement, so contract length, SLA, termination and data-deletion terms are not verifiable in advance.
- Merchants whose add-on needs are small: the credential-management and decision products carry per-product monthly minimums, so light usage is charged at the minimum rather than at usage.
- Buyers who need the vendor to carry payments risk or hold regulatory permissions — Pagos holds no acquiring registration or money transmission licensing because it never touches funds, so it cannot stand behind acceptance or settlement outcomes.
Competitors and alternatives
| Company | Why a business would choose it instead |
|---|---|
| Chargebee (inai) | Chargebee acquired payments-intelligence company inai in September 2025 and now bundles AI-driven payment recovery and settlement/fee intelligence with its billing platform. |
| Spreedly | Overlaps on network tokenisation, account updater and optimisation analytics, but also executes routing — a merchant wanting one vendor for both intelligence and orchestration would look here. |
| Primer / Gr4vy | Orchestration platforms that bundle analytics with routing; chosen by merchants who want the insight and the action in one layer. |
| BR-DGE / Payoneer-class orchestrators | Alternative routes to multi-processor visibility for merchants who are already planning to add an orchestration layer. |
| In-house data warehouse plus processor reporting | The realistic alternative for many large merchants — build the normalisation internally and avoid a per-transaction software fee. |
| Stripe Radar / Adyen RevenueAccelerate | Processor-native optimisation, free or bundled, which is sufficient for merchants concentrated on one provider. |
Pagos — frequently asked questions
Is Pagos a payment processor?
No. Pagos does not authorize, route or settle transactions, holds no acquiring registration and holds no money transmission licensing, because it never touches funds. It ingests and normalizes data from the processors and gateways a merchant already uses and reports on performance, cost and declines. CEO Klas Bäck has described the platform as turning disparate payments data into actionable insight without requiring customers to change their payment processors.
What is the difference between Pagos and a payments orchestration platform?
An orchestration platform sits in the authorization path and executes routing, failover and retry decisions on live transactions. Pagos sits outside that path: it reads the data those decisions produce and reports on it, and its Decision Signals product recommends retry and routing behavior that the merchant or its orchestration layer must then implement. Pagos cannot take a checkout down, and it also cannot change the outcome of a transaction on its own.
Does Pagos publish its pricing?
Yes, more than most payments vendors. As of July 2026 the pricing page shows a free tier with a capped number of no-code processor connections and a monthly transaction allowance, a mid-market tier at a published monthly price, and a custom enterprise tier. Add-on API products — BIN data, account updater, network tokenization and Decision Signals — are priced per transaction or per query and carry their own monthly minimums. Enterprise and very high volume pricing is quoted by sales.
What does Pagos actually sell?
Three groups of products, as described on its own site. A foundation layer covering data harmonization, benchmarking, Pagos AI and an MCP data pipeline; an intelligence layer covering payments monitoring, insights and opportunities, cost optimization and Decision Signals; and credential management covering BIN data, account updater and network tokenization. The credential-management products are the ones that attach directly to recovered subscription revenue.
Who owns Pagos and how much has it raised?
Pagos Solutions, Inc. is private and venture-backed. It raised a $10M seed round in October 2021 co-led by Underscore VC and Point72 Ventures, and a $34M Series A led by Arbor Ventures announced in February 2023, taking total disclosed funding to about $44M. Its 2026 press boilerplate also names Tarsadia and Infinity Ventures as backers. No funding round has been publicly announced since February 2023 as of July 2026, and valuation and revenue are unpublished.
How big is Pagos?
Pagos reported about 41 employees at the time of its February 2023 Series A and describes a global team spanning ten countries in its 2026 boilerplate; no current headcount is published. It states more than 16 billion transaction events ingested and more than $1.3 trillion in transaction volume processed as of March 2026, while its website separately cites benchmarking against more than $2 trillion in network volume — figures that measure different and undefined things. Named customers include Adobe, Eventbrite, GoFundMe, StubHub, Ultra Mobile and Warner Bros. Discovery.
Does Pagos work for a merchant using only one payment processor?
It works technically, but the economics are weaker. Most of the value comes from normalizing and comparing data across multiple providers, and a merchant on a single processor can usually obtain comparable reporting from that processor at no extra cost, often alongside bundled optimization tooling. The credential-management products — account updater, network tokenization and BIN data — can still pay for themselves for a single-processor subscription merchant, but the analytics layer generally will not.
Sources
This profile was built from the following primary and secondary sources. Where sources disagreed, the disagreement is stated in the text rather than resolved silently.
- https://www.pagos.ai/
- https://www.pagos.ai/pricing
- https://www.pagos.ai/privacy-policy
- https://techcrunch.com/2021/10/15/founded-by-former-braintree-and-paypal-execs-pagos-raises-10m-in-seed-fundin
- https://techcrunch.com/2023/02/27/pagos-raises-34m-as-the-demand-for-payment-intelligence-rises/
- https://www.prnewswire.com/news-releases/pagos-raises-10m-to-scale-platform-helping-companies-understand-and-o
- https://pagos.ai/blog/pagos-new-heights
- https://www.prnewswire.com/news-releases/pagos-expands-mcp-server-to-enable-conversational-access-to-harmonize
- https://www.prnewswire.com/news-releases/pagos-transforms-payments-data-from-harmonized-to-ai-ready-302703312.
- https://www.prnewswire.com/news-releases/pagos-launches-first-mcp-server-to-bring-payments-intelligence-to-ai-
- https://www.finextra.com/newsarticle/41872/payments-intelligence-firm-pagos-raises-34m
- https://www.pagos.ai/security
- Headquarters: Los Angeles is taken from the dateline on Pagos's own 2026 press releases. Pagos publishes no address on its website or in its privacy policy, and at launch was described as remote-first, so the LA dateline may reflect the CEO's location rather than a formal HQ.
- Employee count: the only sourced figure is 41 as of February 2023 (TechCrunch). Current headcount is not published. Do not present the 2023 figure as current.
- Founding month and exact incorporation date: TechCrunch reported the company started 'earlier in 2021' but no precise date is published.
- Daniel Blomberg's current role: he was described as CTO and co-founder in 2021; Albert Drouart is described as CPTO (Chief Product and Technology Officer) in 2026 materials, so Blomberg's present involvement is unconfirmed.
- Funding since February 2023: no round has been publicly announced. Tarsadia appears as a backer in the 2026 boilerplate but was not named in the Series A coverage, which implies an unannounced round or a secondary purchase — this could not be confirmed.
- Valuation, revenue and customer count: none are published.
- Contract terms, SLA, termination, data-deletion and data-retention commitments: Pagos publishes no standard customer agreement, so none could be verified. The URLs /company and /terms-of-service both returned 404 in July 2026.
- The scale figures on the Pagos website ($2T+ network volume benchmarked, 100B+ events monitored, 30M+ records added daily) do not reconcile cleanly with the March 2026 press release figures (16B+ transaction events ingested, $1.3T+ transaction volume processed) — the two sets appear to measure different things, and Pagos does not define either. Treat all Pagos scale claims as company-stated and undefined.
- No Wikipedia article exists for Pagos, and there is very little independent trade-press coverage beyond funding announcements and its own press releases.
- Pagos states PCI DSS and SOC 2 Type I/II compliance on its security page but does not publish the attestation reports, a PCI DSS level, an ISO 27001 certification or a GDPR statement there.