About BeamPay
We are making SME merchants discoverable, bookable, and payable by AI agents.
London-based. Pre-seed. Founded by payments operators with thirty-seven combined years of experience. First merchant pilots live August 2026.
Our thesis
Aggregator at entry by design. Acquirer by destination.
Agent commerce is happening. The platforms building AI agents that need to transact — OpenAI, Anthropic, Google, the next wave behind them — are converging on a small number of payment protocols. None of the legacy payment infrastructure was built for it. Most of what exists today is orchestration glue routing between existing processors. That is not enough.
We believe two things about how this market develops. The first is that the wedge into agent commerce will be application-layer, not infrastructure-layer. Merchants want a complete pipeline they can switch on without rebuilding their existing systems. The second is that the durable position underneath the wedge is a fully owned payments stack. Without the depth, the wedge becomes a fragile orchestration layer that gets squeezed by the processors it depends on.
BeamPay is built around both. Merchant Enablement is the wedge — the flagship product that opens AI agent commerce to merchants. The infrastructure underneath — Processing, Acceptance, Hardware — is the moat. We land via the flagship. We grow into the infrastructure relationship as merchants and platforms commit deeper.
The architecture
One flagship on top of three foundational products.
Application layer
Merchant Enablement
the flagship product
Processing
our own ISO 8583 message switch
Acceptance
payment application, SDK, TMS, and remote key infrastructure
Hardware
payment terminals, certified and configured
The application layer is what is new — Merchant Enablement, the agent commerce pipeline, the catalogue and interaction architecture. The three layers underneath have five years of development behind them and historical production deployment at significant scale. We are not building infrastructure in stealth. We are building the application layer on top of infrastructure that already works.
The story
Built on infrastructure that already works at scale.
BeamPay is not a clean-room startup. Our co-founders spent five years at a previous company building the payments stack that BeamPay now owns. It scaled to over a million merchants and deployed at thirty thousand-plus terminals in production. The infrastructure is real. It has been through scheme certifications, regulatory audits, and the operational fires that come with running payments at scale.
What is new at BeamPay is Merchant Enablement on top of that infrastructure — a flagship product designed for a moment that did not exist at the time the stack was built. The combination is unusual at our stage: a pre-seed company with technology depth that normally appears only at Series B and later.
Status
Pre-seed. First merchant pilots live August 2026.
We are currently pre-revenue, in active build-up. Our minimum viable product is targeted for September 2026. First merchant pilots run from August 2026 — a hotel group and a beauty salon testing the full pipeline from catalogue to booking to checkout.
Active conversations are underway with European acquirers, neobanks, and vertical SaaS platforms covering more than 134,000 SMEs across the Benelux, DACH, and Iberian markets. We are engaged with Mastercard and Visa on merchant data access and ecosystem participation.
Broader rollout planned across the United Kingdom, Spain, Portugal, and Central Europe through 2026 and 2027.
Our acquiring relationship is with a licensed European acquirer partner. Our hardware partnership is with a tier-one terminal manufacturer. We will name partners publicly once formal announcements are agreed.
Our current certifications are GDPR; PCI DSS is in progress; SOC 2 and ISO 27001 on the roadmap.
Want to work with us?
We talk with prospective partners, customers, and investors regularly. The earliest conversations shape what BeamPay becomes.