Payment Facilitator
Introduction
Payment facilitators (PFAC) take the role of a service provider, and are merchants registered by an acquirer to facilitate transactions on behalf of sub-merchants. The provider of the goods/services becomes the sub-merchant instead of the merchant. When the cardholder makes a purchase, the sub-merchant routes the transaction data to the payment facilitator. The payment facilitator incorporates all necessary transaction and merchant identification data and sends this to the acquirer.
There are 2 most commonly used PFAC models - Single-MID and Multi-MID model.
Single-MID model also known as Aggregator does not provide a separate merchant ID (MID) to their sub-merchants, they use aggregator’s own MID, simplifying the process for businesses that handle very low volumes of transactions.
Multi-MID model provides MID for each of the sub-merchants, that sign on under them. This model works great for medium sized businesses who don’t want to deal with the hassle involved in the traditional model.
The way how PFAC transactions are processed and flagged in the authorization message depends mainly on your boarding requirement, if you wish to get all your sub-merchants boarded in the Gateway or you would rather prefer to avoid boarding all your sub-merchants and initiate all transactions from your master-store (PFAC merchant).
Payment API Integration
REST API solution specifics can be found here: REST API PFAC Integration
SOAP API Integration
SOAP API solution specifics can be found here: SOAP API PFAC Integration
Updated 2 months ago