Can a PayFac work with more than one acquirer?

Yes. Many PayFacs add a second acquirer to cover new countries, add local schemes or keep a fallback. Each acquirer has its own onboarding requirements and settlement files, which is why the platform underneath needs to handle several acquirers in onboarding, routing and reconciliation.

Common, and often necessary

A PayFac starts with one sponsor acquirer, but a second one soon follows: to enter a country where the first does not acquire, to add a local scheme, to cover a merchant category the first refuses, or simply to have a fallback. Each acquirer sponsors the PayFac under its own agreement.

What multiplies

• Onboarding: each acquirer has its own sub-merchant requirements and data formats.
• Routing: transactions must be sent to the acquirer that sponsors the merchant for that market or method.
• Settlement: each acquirer sends its own files, with its own fees and timing.
• Compliance: each acquirer audits the PayFac's program on its own terms.

What the platform must do

Handle several acquirers in onboarding, so one merchant file can be submitted to the right sponsor or to two in parallel. Route per merchant, market and method. Reconcile all settlement files into one transaction record and one merchant statement. Report compliance status per acquirer. A PayFac whose platform was built for one acquirer discovers this at the second, usually as a set of spreadsheets. Infrastructure designed for multi-acquiring makes the second acquirer an activation rather than a rebuild.