Payment facilitator (PayFac)_

A travel platform that acts as PayFac for its underlying operators can simplify onboarding and dispute handling but takes on serious compliance and risk responsibilities in return. Choosing or being a PayFac is a strategic decision, not just a technical one.

The PayFac decision is one of the most consequential a travel platform makes. Being a PayFac speeds onboarding for sub-merchants and gives the platform deeper control of the experience, but it also means accepting full responsibility for KYC, risk monitoring and dispute handling. The compliance and operational cost is significant and recurring.

The travel platforms that operate well as PayFacs invest deeply in the underlying compliance, risk and operational infrastructure before the model pays back. The platforms that go PayFac without that investment carry risk they have not priced in and discover the gaps when a sub-merchant gets into trouble.

felloh keeps booking-level evidence intact in PayFac and aggregator models alike, so settlement, dispute and reserve picture stays available even when the underlying entity model is complex.

The dashboard’s Suppliers, Beneficiaries, Audit and Settlement views surface PayFac-side activity alongside underlying sub-merchant bookings. KYC evidence sits against the supplier record so onboarding diligence is auditable, and dispute correspondence is captured against the booking that drove it.

For travel platforms running as PayFacs, the operational infrastructure that the model demands — KYC, dispute handling, settlement reconciliation, risk monitoring — is unified in one dashboard. The compliance and operational cost of being a PayFac becomes manageable, and the underlying sub-merchants get a service that actually works.