Image Source: Pexels
Running a payment facilitator program on general-purpose processing tools is one of the more expensive ways for a software company to collect a share of its customers’ card volume. A sponsor bank relationship alone can require an onboarding fee of $25,000 to $100,000 and annual sponsorship of $50,000 to $250,000, according to the Payments Mastery industry reference. Those amounts are due before the company has hired a compliance analyst or approved a single merchant.
Fixed Costs of a Registered Program
Card network registration adds an approval period of 60 to 120 days and annual fees of $5,000 to $25,000. Mordor Intelligence estimates security compliance at the highest card industry level, which requires an annual on-site audit, at $100,000 to $500,000 before variable monitoring costs. Legal review and state licensing analysis add further expense.
A program earning a net 0.5% on card volume needs $100 million in annual volume to produce $500,000 of gross income, and the fixed costs described here can consume most of that amount. Dedicated platforms convert a portion of those costs into per-transaction fees. The software company pays more per dollar processed and much less before the first dollar arrives, which lowers the break-even point to a volume a smaller company can reach.
Time to First Transaction
A company building its own program has to select a sponsor bank, complete registration, pass an audit, and write the integrations for onboarding and settlement. Each of those steps depends on a party outside the company, so the schedule is difficult to control. Dedicated platforms already hold the sponsor relationships and the audited infrastructure, which leaves product integration as most of the remaining work.
For a company whose competitors already offer payments, each month of delay is a month of sales calls conducted without the feature. A shorter launch also produces real transaction data sooner, and the product team can use that data to decide which merchant features to build next.
Components of a Dedicated System
A payment facilitator platform for PayFacs is built for a company that intends to own the merchant relationship while leaving much of the regulated infrastructure to a specialist. The typical product includes merchant onboarding screens, underwriting tools, tokenized card storage, payout scheduling, and dispute management, all available through an application programming interface.
General gateways are designed around 1 merchant accepting payments. Facilitator systems serve thousands of merchants under 1 program, with fee schedules, reserves, and reporting that can be set for each merchant or group. That structure allows a software company to offer a promotional rate to some customers and a different payout schedule to others without custom code.
Split Funding and Payout Logic
Software companies that collect money on behalf of merchants often need to divide each transaction. A marketplace may keep a 10% commission, and a franchise system may send a royalty to the parent company before the local owner is paid. Building that logic on a general gateway usually means reconciling separate transfers after the fact.
Dedicated systems apply the split at the moment of settlement and record each party’s share. Finance staff then have 1 ledger to audit, and merchants receive a statement that agrees with the amount in their bank accounts, which removes a common source of support calls.
Merchant Onboarding and Dispute Tools
Merchant onboarding is the step a software company’s customers notice first. Dedicated systems supply prebuilt forms that collect the required business and ownership details, along with status messages that tell an applicant what is missing. Building the same flow in-house means writing and maintaining every screen. Those screens also change each time a sponsor bank changes its data requirements.
Card networks set short response windows, and each dispute needs evidence matched to a specific reason code. Platforms gather the transaction data automatically and present the merchant with a single request for whatever remains, which spares a small business owner from learning the network rules.
Staffing and Specialist Knowledge
A self-managed program needs people who have done this work before, including a compliance officer, risk analysts, and staff who can respond to card network inquiries. Those specialists are difficult to recruit into a company with no existing payments team, and a shortage of cybersecurity workers adds to the difficulty on the security side of the program.
Some of that work can be purchased with the platform. The software company keeps responsibility for its own program and needs at least 1 employee who can judge the partner’s performance, since a sponsor bank will hold the company accountable for problems the partner causes.
Audit and Reporting Burden
Sponsor banks require periodic reports on merchant losses and complaints, and card networks can request transaction records with short deadlines. Most of those reports come directly from the platform’s transaction data, and the software company reviews them instead of compiling them from several systems.
Shared Costs Across Many Programs
Platforms serving many software companies spread the cost of audits, network certifications, and risk models across all of them. Those economies of scale are the basis of its pricing, because a single company doing the same work has to recover the full cost from its own volume.
The software company also avoids the opportunity cost of assigning engineers to card network certification. Those hours would otherwise go to the product its customers pay for, and for most vendors the product is the main source of competitive advantage.
Exit Terms and Vendor Risk
Vendor lock-in occurs when the cost of moving to another supplier becomes high enough to keep a customer in place, and in this market the main source of that cost is stored card data. The contract should state that tokens and merchant records can be exported in a usable format at the end of the agreement. Test the export before it is needed.
Volume Thresholds and Later Decisions
The strongest argument for a dedicated platform is also a reason to plan for leaving it. Per-transaction fees grow with volume while the fixed costs of a registered program stay largely flat, so a successful company will eventually reach the point where the platform costs more than the work it replaces. The companies best placed to act on that figure are the ones that negotiated data portability before they signed.