Payment aggregator
A provider that consolidates payments for many sub-merchants under one acquirer relationship.
A payment aggregator is a provider that holds a single acquirer relationship and processes payments on behalf of many sub-merchants underneath it. The aggregator handles onboarding, risk monitoring, dispute correspondence and settlement, and the sub-merchant gets to start accepting payments faster than a direct acquirer relationship would allow. Stripe, Square, PayPal and Adyen for Platforms are well-known examples.
felloh is the travel-specific alternative to a generic payment aggregator.
Card, open banking and links across multiple acquirers — but with the booking-level evidence, ATOL handling and travel-aware fraud rules a generic aggregator can't provide.
What it means for travel businesses.
Travel marketplaces, OTAs and supplier-platform models often work as payment aggregators, taking customer money on behalf of an underlying inventory. The supplier gets fast onboarding but loses direct settlement timing and reserve visibility.
The aggregator model is attractive precisely because it removes friction from supplier onboarding — which is also why it can mask real exposure when something goes wrong. A supplier that has never seen its own settlement file does not see the early warning signs of a chargeback wave; a marketplace that takes liability for sub-merchants it has lightly vetted carries a risk it may not have priced in.
A healthy aggregator setup gives every party a booking-level picture, even though the legal merchant of record is one entity. The customer sees the marketplace, the supplier sees their own bookings and net settlement, and the aggregator carries operational responsibility without losing the ability to see and explain what is happening underneath. Without that picture, every dispute escalates.
How felloh handles it.
felloh keeps booking-level reconciliation usable whether the travel business is acting as the aggregator or being aggregated, so settlement and supplier exposure stay traceable on both sides.
The dashboard’s Suppliers, Beneficiaries and Settlement views surface sub-merchant-level activity against the aggregated bookings, with operational and finance evidence available from one source. Where the travel business is the aggregator, the Bookings and Risk Analysis views provide a single picture across the underlying inventory.
For aggregators and aggregated businesses alike, the booking-level picture survives the legal-entity structure. Disputes, refunds and reconciliation work the same way, and the regulator-facing evidence stays intact regardless of which side of the model the operator sits on.
Related terms.
Aggregator model
A payments model where many sub-merchants accept payments under a single acquirer relationship.Read termGlossary termPayment facilitator (PayFac)
A regulated entity that lets businesses accept payments under its own merchant account.Read termGlossary termMerchant of record (MoR)
The legal entity responsible for processing a payment and dealing with disputes and compliance.Read termGlossary termAcquirer
The financial institution or payment provider that enables a merchant to accept card payments.Read termGlossary termSettlement
The movement of processed payment funds into the merchant account or bank account.Read termSee how this works around your bookings.
Bring one payment, reporting or cash-position problem. We will show how felloh connects the booking-level money trail behind it.
Book a walkthrough