Choosing between a payment facilitator, an acquiring bank arrangement, and your own merchant account affects onboarding, pricing, payouts, risk controls, and how much control your business has over payment operations. This guide explains the payment facilitator vs merchant account decision, what to compare, which metrics to review each month or quarter, and when a growing company should reassess its model.
Overview
A payment facilitator, often called a PayFac, enables businesses to accept card payments through a master arrangement with an acquiring bank. The business typically signs up as a sub-merchant, completes the facilitator’s onboarding process, and uses the facilitator’s payment gateway, reporting, and payout tools. This model can make it relatively straightforward to start online payment processing without negotiating a separate acquiring relationship.
With a traditional merchant account, the business has a direct processing relationship with an acquirer or an acquiring partner. The business is generally underwritten as its own merchant, receives its own merchant account credentials, and may have more influence over configuration, reporting, pricing, and risk arrangements. A payment gateway may still be involved, but the gateway and the merchant account are separate concepts: the gateway transmits payment information, while the merchant account supports the acquiring and settlement relationship.
Neither model is automatically better. A PayFac can suit a business that values faster setup, consolidated tools, and operational simplicity. A direct merchant account may be more appropriate for a company with substantial or predictable volume, specialized risk requirements, multiple entities, international plans, or a need for greater control over payment data and commercial terms. The right choice depends on the business’s risk profile, transaction pattern, technical requirements, and expected growth.
When comparing providers, do not focus only on the advertised processing rate. Review the complete payment processor comparison: onboarding requirements, pricing structure, payout timing, reserves, chargeback handling, account ownership, data portability, support, and contract terms.
What to track
1. Onboarding and underwriting
Record how long approval takes, which documents are requested, whether additional review occurs after launch, and what business activities are restricted. A PayFac usually manages initial onboarding for sub-merchants, while a direct merchant account may involve more detailed underwriting before activation. In both cases, provide accurate information about products, fulfillment, countries served, average order value, refund practices, and expected transaction volume.
Track whether the provider’s assumptions still match your business. A material change in product mix, sales channel, geography, or transaction size can prompt a new review. Ask how updates are handled before making a change that could affect risk assessment.
2. Pricing and total cost
Build a monthly cost view rather than comparing one headline rate. Depending on the arrangement, costs may include a percentage fee, a per-transaction fee, gateway charges, monthly or account fees, currency conversion costs, dispute fees, refund-related charges, and contract or termination fees. Also distinguish between blended pricing, tiered pricing, interchange-plus pricing, and other structures; labels can vary by provider, so request a written explanation of how each transaction is calculated.
Compare effective cost by dividing total payment-related fees by the processed payment volume for the same period. Keep card-present, card-not-present, ACH, international, and other payment methods separate where possible. This makes it easier to see whether a lower quoted rate is offset by other charges or by a change in payment mix.
3. Payouts, reserves, and cash flow
Track the time between a successful payment and the funds arriving in your operating account. Note weekends, holidays, cutoff times, rolling schedules, payout delays, and any differences between payment methods or countries. A provider may also establish a reserve, delay selected funds, or adjust payout conditions when its risk assessment changes. Review the reserve percentage or amount, release conditions, review process, and notice provisions in the agreement.
Cash-flow planning should use the provider’s actual settlement behavior rather than an assumed next-day schedule. If delayed funds would affect payroll, inventory, refunds, or supplier payments, model that exposure before selecting a payment facilitator or merchant account.
4. Chargebacks and fraud controls
Measure dispute count, dispute rate, recovered amounts, response time, and the operational effort required for evidence submission. Clarify who receives dispute notifications, who is responsible for responding, and whether the provider offers tools such as alerting, rules, tokenization, or 3D Secure flows. These tools can support fraud protection payments, but they do not eliminate the need for accurate order records, clear policies, delivery evidence, and customer service.
Also review responsibility for unauthorized transactions, account takeover, refunds, and suspected fraud. The contract and operating procedures should make clear which decisions remain with your business and which are controlled by the provider.
5. Ownership, portability, and support
Ask who owns the merchant account or sub-merchant relationship, who controls customer and transaction records, and how data can be exported if you change providers. Confirm whether payment tokens, recurring billing records, dispute history, and reconciliation data can be migrated. A move may require customer reauthorization if stored payment credentials cannot be transferred.
Evaluate support by channel, hours, escalation path, and expertise. For a business accepting payments continuously, support quality is part of operational resilience—not merely a convenience.
Cadence and checkpoints
Use a simple review calendar so the decision remains based on current operating conditions.
- Monthly: reconcile processed volume, fees, refunds, disputes, payout timing, reserves, failed payments, and unexplained adjustments. Compare the provider statement with your order and accounting records.
- Quarterly: review effective cost by payment method, approval and decline patterns, chargeback trends, support tickets, payout reliability, and changes in your customer or geographic mix. Check whether the current model still fits your forecast.
- Before a major launch: confirm underwriting approval, supported currencies and countries, settlement accounts, fraud settings, subscription requirements, refund workflows, and technical capacity. Test webhooks, retries, reconciliation, and failure handling before directing significant volume to a new flow.
- Annually: read the full contract again, including renewal, pricing-change, reserve, termination, data-access, and dispute provisions. Request a written fee schedule and compare alternatives using your actual transaction profile rather than a generic quote.
A useful evaluation worksheet has one row for each provider and columns for onboarding time, required documents, payment methods, supported markets, pricing model, effective cost, payout schedule, reserve terms, chargeback process, account ownership, data export, integration options, support escalation, contract term, and exit requirements. Mark each item as confirmed, estimated, or unanswered. Unanswered items should become questions before approval.
How to interpret changes
A rise in fees does not always mean the provider changed its base rate. It may reflect a different card mix, more cross-border transactions, higher refunds, new payment methods, or additional service charges. Compare like-for-like periods and separate volume changes from price changes.
Longer payout times or a new reserve may indicate that the provider’s risk assessment has changed, but the practical response is to ask for the applicable terms and review the effect on working capital. Do not assume that moving to a direct merchant account will remove all reserves or underwriting; risk controls can exist under either structure.
Higher declines can result from fraud rules, authentication settings, issuer decisions, integration errors, or incomplete customer information. Review decline codes, checkout changes, and geographic patterns before changing providers. If disputes increase, examine fulfillment, product descriptions, cancellation instructions, customer support, and evidence quality alongside fraud controls.
Consider a PayFac-to-merchant-account transition when volume is becoming predictable, payment costs are material, the business needs customized underwriting, or reporting and account control are limiting operations. Consider staying with a PayFac when its consolidated tools, support, and flexible onboarding continue to meet requirements and the total cost remains acceptable. A hybrid setup may also be possible, but it can add reconciliation, integration, and compliance work.
When to revisit
Revisit the payment facilitator vs merchant account decision whenever the business changes its risk or cash-flow profile. Common triggers include a sustained increase in transaction volume, larger average orders, a new subscription product, international expansion, a new sales channel, a significant rise in disputes, repeated payout holds, or the need to support additional payment methods or currencies.
Begin with the last three to twelve months of actual payment data, depending on how stable your business is. List the operational problems first, then test whether they arise from the provider model, the contract, the integration, or internal processes. Request written answers on pricing, reserves, settlement, account ownership, data portability, and chargeback responsibility. Avoid switching solely because another provider advertises a lower rate; migration costs, customer reauthorization, engineering work, and temporary disruption can change the total economics.
Before signing or migrating, complete a controlled test of authorization, capture, refund, partial refund, dispute notification, webhook retry, reconciliation, and payout reporting. Update your PCI compliance process, access controls, incident procedures, and customer communications as needed. Keep the review worksheet and monthly metrics so the next evaluation starts with evidence rather than memory. That recurring discipline helps a growing company choose a payment model that remains practical as its volume, markets, and risk exposure evolve.