Payment gateways, processors, acquirers, and PayFacs
Card acceptance combines distinct technology, acquiring, and merchant-distribution roles. One provider can perform several roles without making the roles interchangeable.
A payment gateway is the interface that accepts and transmits payment information from a merchant’s checkout. A payment processor handles transaction messages and processing functions. An acquirer provides the merchant’s acquiring relationship to a card network. A payment facilitator, or PayFac, brings sponsored merchants into an acquiring arrangement.
These are roles. A company can perform several of them under one commercial brand.
The gateway connects checkout to processing
A gateway receives payment information from a website, app, or another acceptance interface and passes it into the processing chain. Its services can include token handling, fraud-tool integration, routing, and connections to more than one processing endpoint.
Providing a checkout interface does not by itself establish that the gateway holds merchant funds or bears the acquirer’s obligations. Those responsibilities come from the provider’s additional roles and contracts.
The processor operates transaction functions
A processor handles functions such as authorization-message routing, transaction records, clearing preparation, and reporting for its clients. A merchant-side processor connects acceptance activity to the acquiring and network environment; issuer processing serves the cardholder-side institution.
Processing an authorization request is distinct from deciding whether the cardholder’s account should fund the purchase. The issuing side makes that decision under its authorization arrangements.
The acquirer supplies the acquiring relationship
The acquirer connects the merchant acceptance business to the card network and takes the acquiring obligations defined by the network and merchant contracts. These include responsibilities for merchant acceptance, settlement arrangements, and exposure arising from disputed or uncollectible transactions.
An acquirer can outsource technical processing. Outsourcing the message-handling work does not make the processor the acquirer for every legal and financial purpose.
A PayFac aggregates sponsored merchants
A PayFac operates under an acquiring relationship and enrolls sponsored merchants within that arrangement. It can combine onboarding, processing access, reporting, and payment distribution into a platform service.
A platform that pays sellers is not automatically a PayFac. The classification depends on its actual acquiring arrangement, network role, and responsibilities, rather than the appearance of its dashboard.
An independent sales organization, or ISO, distributes acquiring or processing services and manages commercial relationships within its agreements. Selling a processing contract does not by itself make an ISO the transaction processor.
Integration changes the number of providers, not the functions
Take a merchant with a separate gateway, processor, and acquiring bank. Moving to one provider that combines those services reduces the number of interfaces and contracts the merchant manages. Authorization messaging, merchant admission, settlement, and dispute handling still require identifiable owners.
The useful classification records the legal entity and contract behind each function. A single brand can simplify purchasing while leaving several institutions in the payment chain.
Questions
- Is a payment processor the same as an acquirer?
- No. Processing is an operational function; acquiring is the merchant-side network and contractual role. One provider can perform both.
- Does every platform that pays sellers operate as a PayFac?
- No. PayFac status depends on the platform’s acquiring and network arrangement, not merely on whether it transfers money to sellers.
- Can one company be a gateway, processor, and acquirer?
- Yes. An integrated provider can combine those roles. Each role still carries a distinct function and set of obligations.