Payment Facilitator (PayFac)

Overview

How it works and why it matters

In card acceptance, a PayFac operates under a relationship with an acquiring institution to help sponsored submerchants accept payments. It typically handles onboarding and risk management under acquirer and card-network requirements. The precise obligations depend on contractual and network rules.

Important technical and operational details

A PayFac typically performs merchant onboarding, due diligence, transaction aggregation, risk monitoring, reporting, and operational support under card-network and acquirer rules. Its purpose is to let multiple sponsored merchants access payment acceptance through a managed acquiring and operating framework.

Operational implementation normally requires acquirer sponsorship, submerchant onboarding, merchant identifiers and reporting, transaction monitoring, and funding and reserve controls. Program records should connect the PayFac, acquirer, sponsored merchant, merchant identifiers, underwriting evidence, transactions, reserves, funding, disputes, and monitoring decisions.

Useful measures include active submerchant count, onboarding approval rate, fraud and dispute rate, funding timeliness, and merchant concentration.

The principal risks include weak merchant due diligence, fraud concentration, misclassification of merchant activity, settlement liability, and program noncompliance.

Practical decision points

The PayFac model usually combines card-network and acquiring-bank responsibilities that do not exist in the same form in a direct blockchain transfer. A sponsored submerchant may not have its own direct merchant acquiring relationship, so the program must define underwriting, risk thresholds, dispute obligations and how funding is attributed. PayFac revenue can include transaction fees or software-service charges, but reserve, chargeback and fraud exposures still need documented allocation. During due diligence, merchants should distinguish the platform's technical checkout offering from its legal role in the card scheme. The presence of many submerchants on one website is not proof of a PayFac relationship.

Related concepts

Payment Capability

Further reading

• bis.org documentation