Payment gateway
- Single connection to one acquirer or processor
- Captures and authorises card transactions
- Console and reporting per provider
- Typically requires its own merchant account
- Adds a new gateway each time you add a market
Payment aggregator
Payment aggregator: many connections in, one settlement out.
topropay is the payment aggregator that puts every connected acquirer, PSP and method behind one integration. Smart routing picks the best route for each payment. Cascading retries keep approval rates high. And one ledger brings settlement together across every provider you use — card, mobile, in-app and card-not-present.
- 300+
- methods
- 50+
- acquirers
- 40+
- markets
- 1
- ledger
The short version
What a third party payment aggregator does, in practice
Most teams start with one payment provider. Then they hit the limits the hard way: a method they cannot offer, a market where approval rates sag, a renewal that fails in silence, or a new region that needs its own acquirer and merchant account. Each fix adds another contract, another dashboard and another file to reconcile. In time, the "payment provider" is a stack of half-joined services with no single source of truth.
A payment aggregator turns that around. Instead of holding a merchant account per acquirer, you use the aggregator's relationships through one sub-merchant integration. It handles approval, routing, tokenisation, settlement and reconciliation underneath. On top, your team gets one API, one dashboard and one ledger. New methods and markets become switches. Provider outages become routing decisions.
Gateway vs aggregator
Payment gateway and payment aggregator — what is actually different?
The terms get used interchangeably, but they describe different jobs. A quick side-by-side shows where each lives in the stack and which one fits the shape of your business.
Payment aggregator
- One integration in front of many acquirers, PSPs and methods
- Smart routing and cascading across providers per transaction
- Unified portal and reconciliation across every connection
- Sub-merchant model — merchants ride the aggregator's MIDs
- New markets and rails are configuration, not engineering
Key benefits
What teams gain from one aggregator layer
Three outcomes show up first when a unified aggregator replaces a stack of partly-integrated providers.
Reach without re-integration
A single payment aggregator integration replaces a backlog of separate provider builds. Hundreds of methods, dozens of acquirers and every supported PSP appear behind the same unified API, so new geographies and rails ship as configuration rather than fresh code.
Smart routing per authorisation
Per-transaction scoring picks the route most likely to clear at the lowest cost for that scheme, currency and market. Soft declines cascade to the next ranked provider in the same request, so the buyer sees a single clean result and the sale survives an outage at any one acquirer.
Settlement and reporting, normalised
Every settlement, fee, refund and chargeback across every acquirer reconciles into one normalised ledger that exports straight to your ERP. The finance close stops being a file-per-provider merge and becomes a single source-of-truth export.
How it works
From first integration to live operations
Three lanes describe the lifecycle of a topropay deployment. The cards inside each lane are the actual jobs the platform takes off your plate.
Connect
- One integration
Drop in the unified API or a prebuilt checkout. SDKs cover web, mobile and server-to-server flows.
- Reuse contracts
Bring your existing acquirers and PSPs; the aggregator sits in front of them, not in their place.
- Vault by default
Cards capture into our PCI DSS vault; your origin only ever handles network-aware tokens.
Configure
- Routing policy
Optimise for approval, cost, currency or risk — change the policy from the dashboard, not a release.
- Method mix
Switch on the methods relevant for each market, including mobile payment aggregator flows like wallets and QR.
- Risk rules
3DS2, SCA and step-up logic per transaction; selective challenges keep approvals high without breaking compliance.
Operate
- Live operations
One portal for authorisations, refunds, disputes and chargebacks across every connected provider.
- Unified reconciliation
Settlements normalise into one ledger keyed off vault tokens for finance and audit.
- Continuous improvement
Adjust routing weights, switch methods on or off, add a new acquirer — all without re-integration.
Where it fits
Where best payment aggregator setups earn their keep
Different shapes of business stress different parts of the aggregator. These are the patterns the platform sees most often.
- DTC
Direct-to-consumer commerce
One aggregator for cards, wallets and account-to-account at the checkout; routing keeps approvals high across every market the brand sells in.
- Subs
Subscriptions and SaaS
Recurring billing on vault tokens, smart retry policies and account updaters — renewal recovery as a configuration choice instead of per-gateway scripts.
- Market
Marketplaces and platforms
Split payments and seller payouts orchestrated through one aggregator connection; reporting keeps every party's ledger straight.
- Mobile
Mobile-first and in-app
A native mobile payment aggregator flow with tokenised pay sheets, Apple Pay and Google Pay surfaced inside the same unified API.
- PSP
PSPs and ISVs
Resell aggregated capacity downstream. Your merchants inherit the routing, reconciliation and reporting; you keep the relationship and pricing.
- Travel
Travel and high-ticket
Staged captures, partial refunds and multi-currency capture run end-to-end so a complex booking can be investigated from one timeline.
Capabilities
Capabilities of a payment gateway aggregator, grouped by job
Three categories cover the lifecycle of a transaction: how it gets in, how it is processed, and how it gets accounted for.
- Unified API
- One REST integration plus SDKs that act as a single payment gateway aggregator across every connected acquirer, PSP and method.
- Hosted checkout
- A prebuilt checkout you can drop in, or hosted fields if you want full control of the surface around the payment form.
- Webhooks
- Signed, normalised event stream into your SIEM, warehouse or in-house tooling.
- Smart routing
- Per-transaction scoring picks the route most likely to approve at the lowest cost; cascading retries fail soft declines over mid-request.
- Tokenisation vault
- PCI DSS Level 1 vault keeps card data out of your systems; refunds, retries and recurring run on tokens.
- 3DS2 & SCA
- Selective authentication per transaction, applied only where the market and risk profile call for it.
- Unified ledger
- Settlements, fees, refunds and chargebacks normalise into one ledger across every connected acquirer.
- ERP-ready exports
- CSV, Parquet and signed event feeds keyed off vault tokens so finance never needs a PAN to investigate.
- Multi-currency settlement
- Settlement currency is a policy choice; payouts group by currency and acquirer for clean reconciliation.
Industry relevance
Industries running on the platform
The same aggregator serves a single-storefront DTC brand and a multi-market PSP. These are the sectors we work with most often.
- 01Retail & DTC
- Storefronts and headless commerce
- 02Subscriptions
- Vault-token recurring billing
- 03Marketplaces
- Split payments and multi-seller payouts
- 04Travel & hospitality
- Staged captures, multi-currency
- 05Ticketing & events
- Peak-load checkout resilience
- 06Financial services
- Wallets, top-ups and payouts
- 07Gaming & entertainment
- Licensed operators across permitted markets
- 08PSPs & ISVs
- Aggregated capacity resold downstream
One thing stays the same across every sector: the shape of the work. Take the payment, route it to the best acquirer, clear it through the rails and account for it cleanly. Solve that once, and a new product line or a new country becomes a config change, not a project. For a deeper look at one part, see merchant acquiring or the PCI compliance posture.
Trust & compliance
What the aggregator carries so your team does not
The licences, attestations and resilience work sit with the platform. Your team inherits the controls rather than rebuilding them.
- Compliance carried
PCI DSS Level 1 service-provider posture, annual on-site assessment, quarterly ASV scans — done on the platform's cycle, inherited by you.
- Authenticated by default
3DS2 and SCA wired into the authorisation path; selective challenges keep approvals high without breaking PSD2 in Europe.
- Data, where it should be
Regional data-residency options for merchants who need them; signed event logs available from the dashboard for audit.
- Resilient by design
Redundant acquiring zones and automatic failover keep authorisation available through outages and seasonal peaks.
Common questions
Frequently asked questions about payment aggregators
What is a payment aggregator, and how is topropay one?
A payment aggregator is a service that lets many merchants accept payments through the aggregator's own acquiring relationships — instead of each merchant setting up its own merchant accounts, they ride a shared infrastructure with smart routing, tokenisation and unified reporting on top. topropay operates that aggregator pattern at platform scale: one integration reaches every connected acquirer and method, every transaction is routed in milliseconds, and one ledger reports across every provider.
What is the difference between a payment gateway and payment aggregator?
A payment gateway is a single connection that authorises and clears card transactions; the merchant typically holds its own MID with the acquirer behind that gateway. A payment aggregator sits one level higher: a single sub-merchant relationship lets you ride the aggregator's MIDs across many acquirers, with one settlement and one ledger out. Some platforms only do one or the other; topropay combines the orchestration of a gateway aggregator with the operational shape of a unified aggregator.
Is topropay a payment gateway aggregator or just a gateway?
It is both, functionally. The platform exposes a unified payment gateway API and aggregates many providers behind it, so from your code it looks like one gateway and from your business it behaves like a payment gateway aggregator across every method and market you operate in.
Do I need a payment aggregator license to use the platform?
Generally not. The licensing requirement sits with the aggregator, not with you as a merchant. topropay operates under the licences relevant to its supported regions, so merchants integrate as sub-merchants and inherit the platform's regulatory standing rather than holding a payment aggregator license themselves.
Does topropay hold a payment aggregator license rbi for India?
The payment aggregator license rbi framework — the Reserve Bank of India's authorisation regime for online payment aggregators — applies to entities aggregating payments to merchants in India. topropay's current licences cover EU, UK, APAC and LATAM operations rather than the RBI regime, and any India connectivity is delivered through licensed partner relationships rather than a direct RBI payment aggregator license held by topropay. We are transparent about this during onboarding so you can pick the right structure for the markets you serve.
How do payment aggregator companies typically compare?
Payment aggregator companies differ on three axes that matter most: the breadth of methods and acquirers they reach, the quality of their routing and cascading, and how cleanly their reconciliation rolls everything up for finance. Headline rate cards are usually a poor comparison — the cheapest sticker price often comes with the narrowest method set or the weakest routing, so total cost of ownership tells a different story. We recommend comparing on real authorisation traffic rather than spec sheets.
Which is the best payment aggregator for international merchants?
The best payment aggregator depends on your geographies, methods and growth shape. For merchants and PSPs operating across Europe, the UK, APAC and LATAM with a mix of cards, wallets and account-to-account rails, topropay's unified API, smart routing and centralised reconciliation are designed for that exact problem. For a single-country, single-method merchant, a simpler local provider may be enough.
Is topropay a third party payment aggregator in the sense regulators use the term?
Yes — a third party payment aggregator (TPAP) is the regulatory term for a non-bank entity that aggregates payments and settles them to merchants. topropay fits that description in the markets it operates in, with the licences and PCI DSS posture that come with it. The day-to-day shape from a merchant view is the same: one integration, many providers, one settlement story.
How does mobile payment aggregator support work?
Native iOS and Android SDKs plug into the same unified API the web checkout uses, so a mobile payment aggregator flow is one tokenised pay sheet on top of the same routing, vault and reconciliation engine. Apple Pay and Google Pay surface as routes inside the unified payment view, and authorisations from mobile roll up into the same ledger as web cards.
Can a gambling payment aggregator setup work with topropay?
We work with licensed and regulated operators only. A gambling payment aggregator flow is supported where the operator holds a current licence in a permitted jurisdiction and runs full KYC, AML and responsible-gaming controls. Unlicensed gambling, grey-market betting and similar verticals are out of scope regardless of integration shape.
How long does adopting an aggregator usually take?
Most merchants reach a live integration in days rather than quarters. The integration is one API; existing acquirer contracts can stay in place; the dashboard, routing rules and reconciliation feed light up as soon as the first transaction posts. Finance and operations teams usually onboard inside a single training session because they learn one tool, not one per provider.
Talk to payments engineers
Put every provider behind one aggregator.
Book an aggregator review. We map your current providers, score where approvals and settlements leak today, and scope a single-integration rollout across your markets — without renegotiating your existing acquirer or PSP contracts.
Continue reading