Choose the payment model
that matches your ambition.
PSP-first, PayFac, and Merchant of Record are not simply integration choices. Each model changes who controls the merchant relationship, who owns payment economics, and who carries the operational burden.
What are the three payment business models?
PSP-first delegates most payment operations to a provider. A PayFac manages sub-merchants under a sponsored acquiring structure and owns more of the merchant and payment operations. A Merchant of Record becomes the seller of record for the end-customer transaction and assumes the broadest commercial and operational role.
Three ways to own payments
The difference is not just technology. Each model changes who is the seller, who controls merchant operations, and how much financial responsibility your platform takes on.
Your business sells. The PSP processes the payment.
Your platform onboards sub-merchants and controls more of the payment experience.
The MoR takes the broadest commercial role in the customer sale.
One journey. Three levels of ownership.
Use the profiles below as a strategic starting point. The exact allocation of responsibility varies by provider, sponsor bank, geography, product design, and legal structure.
PSP-First
Use an established payment provider to launch quickly while your business remains the seller and keeps the operating model simple.
- Best for
- Speed and simplicity
- Control
- Low–Medium
- Responsibility
- Low–Medium
Payment Facilitator
Onboard sub-merchants and make payments part of your platform, gaining more control over pricing, operations, and payment economics.
- Best for
- Control + economics
- Control
- High
- Responsibility
- High
Merchant of Record
Become the seller for the end-customer transaction and take on the broadest commercial and financial operating role.
- Best for
- Maximum ownership
- Control
- Very High
- Responsibility
- Very High
Compare the operating profile
These are directional profiles, not legal definitions. A specific implementation can shift depending on contractual, regulatory, acquiring, and geographic arrangements.
| Decision factor | PSP-First | PayFac | Merchant of Record |
|---|---|---|---|
| Control | Provider-led payment layer | Merchant + payment operations | End-to-end commercial ownership |
| Speed to market | Typically fastest starting model | More setup and sponsorship | Broadest operational setup |
| Merchant ownership | PSP owns much of the payment relationship | Platform manages sub-merchants | MOR is seller of record |
| Payment economics | Limited margin control | Pricing and payment margin become strategic | Broad commercial economics, broad costs |
| Operational responsibility | Much is delegated to PSP | Merchant, risk, finance, payout operations | Broadest commercial and financial role |
| Reconciliation complexity | Fewer internal financial events | Fees, balances, reserves, settlements, payouts | Customer-to-provider financial truth must align |
From delegated processing to commercial ownership
This spectrum is illustrative. Real-world responsibility depends on contracts, acquiring setup, licensing, geography, risk allocation, and the exact product design.
Start with the operating model, not the payment API.
The technical integration is only one part of the decision. Leadership should first decide which responsibilities the business actually wants to own.
Merchant relationship. Who owns onboarding, pricing, support, risk controls, and lifecycle management?
Payment economics. Is payment acceptance a cost center, a product feature, or a strategic source of margin?
Financial operations. Who must explain fees, settlements, balances, reserves, refunds, disputes, and payouts?
Operating maturity. Can finance, risk, compliance, and support teams absorb the additional responsibility?
More payment ownership requires stronger reconciliation.
As a platform moves toward PayFac or MOR, it must reconcile more than processor deposits. It must connect transaction events to fees, routing, settlements, reserves, adjustments, merchant balances, refunds, chargebacks, and payouts. That makes a unified ledger and automated payment reconciliation a core operating requirement rather than a back-office convenience.
One control layer across all three models.
Centralize merchant operations, payment orchestration, routing, unified ledger, reconciliation, and payouts while preserving flexibility across underlying providers.
Questions decision-makers ask
Which payment business model is fastest to launch?
A PSP-first model is typically the fastest starting point because payment acceptance is largely delegated to a payment service provider. The exact timeline depends on product scope, geography, integrations, and compliance requirements.
Which payment model gives a platform the most control?
PayFac and Merchant of Record models generally provide the greatest control over merchant experience and payment economics, but they also bring substantially greater operational, risk, finance, reconciliation, and compliance responsibility.
Can a platform move from PSP-first to PayFac later?
Yes. A platform can start PSP-first, centralize merchant and transaction operations, add orchestration and a unified ledger, then move toward PayFac as volume and operational maturity justify the change.
Why does reconciliation become more complex as payment control increases?
Greater payment control creates more financial events to explain: fees, routing decisions, split settlements, reserves, adjustments, chargebacks, balances, and payouts. A unified ledger and automated reconciliation become increasingly important as the operating model grows more complex.
Design the payment model you can scale.
Amaryllis provides a modular control layer for PSP-first, PayFac, and MOR-ready operations — without hard-wiring your future to one provider.
