How to choose the right payment facilitator technology provider

Business

You run a software company with 4,000 gym owners on your product, and your finance team has noticed that the card fees on their memberships go to someone else. Bringing those payments inside the product could add a new revenue line, and the provider you select decides how much of that revenue you keep and how much risk comes with it. A poor choice tends to appear late, in a funding delay or a failed audit, after hundreds of merchants already depend on the system.

Registration Models

A payment facilitator accepts card payments on behalf of many smaller companies, called sub-merchants, through a relationship with a sponsor bank. Card network rules require a registered facilitator to onboard and monitor those sub-merchants, and responsibility for their conduct falls on the facilitator and its acquiring bank.

Under full registration, a software company holds its own status with the card networks, writes its own underwriting policy, and absorbs losses when a sub-merchant fails. Under a managed model, the provider holds the registration and the software company receives a share of the revenue in exchange for less liability. Annual volume and the availability of compliance staff decide this, and a provider should be able to show you the point at which moving from one model to the other makes financial sense.

Ask also what happens when a sub-merchant grows. A 2014 Mastercard bulletin raised to $1 million the annual volume at which a sub-merchant must hold its own merchant account. A large gym chain on your product could pass a figure of that size. Network thresholds change, so your provider should state the current figure and describe the transfer process in writing.

Sub-Merchant Onboarding

The first measurement to request is the median time from application to first live transaction, broken out by merchant category. A provider’s headline approval speed often describes the easiest applicants. You want the share of applications that go to manual review, the average time those reviews take, and the rate at which legitimate businesses in your category are rejected.

Identity checks on business owners and sanctions screening are baseline requirements, so a provider gains little credit for having them. Compare providers on how much of the application your software can fill in from data it already holds. Gym owners who have given you a legal name and a bank account should not type those details a second time.

Funds Routing

Onboarding, split funding, ledgering, and reporting are usually bundled behind one set of programming interfaces. When you evaluate a payment facilitator platform for PayFacs, test each of those functions separately. Split funding determines how a single transaction is divided between the sub-merchant and your company. If a configuration cannot represent your commission structure, your staff will reconcile by hand at the end of every month.

Run a test transaction with a partial refund and a chargeback against it, then read the resulting reports. If the sub-merchant’s statement and your revenue report do not agree with the bank deposit to the cent, the provider has shown you a problem that will grow with volume.

Integration Effort

Ask your engineers to build a test integration against the provider’s sandbox before the contract is final. The sandbox should simulate declines and delayed settlements, because those are the events that produce support tickets after launch. Webhooks deserve particular scrutiny, since your software learns about a failed payout through them, and a provider should document its retry policy and its event ordering guarantees. Retiring an interface on 90 days’ notice would interrupt your roadmap, so the contract should state a minimum support period for each version.

Ledger Accuracy

When middleware provider Synapse filed for bankruptcy in April 2024, more than 100,000 consumers lost access to about $265 million in deposits. The Consumer Financial Protection Bureau later alleged that the company failed to keep adequate records and match them with its partner banks. The bureau described the resulting missing customer funds as an unrecovered loss of $60 million to $90 million.

Synapse served banking apps, and the same questions apply to card settlement. Ask who holds merchant funds between authorization and payout, how often balances are reconciled against bank statements, and how quickly you can obtain a ledger export at the level of each sub-merchant.

Compliance Ownership

TD Bank agreed in October 2024 to pay about $3 billion in a money-laundering settlement with the US Justice Department, after prosecutors described deficiencies in its anti-laundering program that lasted 9 years. That case involved a bank of far greater size than most software companies, and transaction monitoring was at its center.

Your contract should name the party responsible for transaction monitoring and suspicious activity escalation, and it should state who completes the annual security assessment. A provider that answers “we take care of that” without naming a report or a responsible team has not answered.

Availability Records

A single vendor failure can stop card acceptance at thousands of locations at once. The AWS outage of October 20, 2025 knocked some of the world’s largest sites offline for hours, and the companies that depended on a single cloud region had few options until service returned.

Request monthly uptime figures for the past 24 months, the regions in which the provider operates, and the results of its last failover exercise. Service credits in a contract offer modest compensation, since a credit of a few hundred dollars does not cover a Saturday morning in which none of your gyms can sell a membership.

Merchant Support Coverage

When a gym owner’s payout is late, the call comes to your company, because your name is on the product. Establish who resolves it, within what time, and through which channel. Some providers offer branded support lines staffed by their own agents, while others supply only a portal for your staff to open tickets, and the difference affects how many support employees you must hire in the first year  Ask for median resolution times on payout inquiries specifically, since a general ticket average also includes password resets and billing questions.

Contract Economics

Pricing is usually quoted as a margin above interchange, plus fees per sub-merchant and per transaction. Model those fees against your actual mix of small and large merchants, because a low per-transaction rate paired with a monthly fee on every sub-merchant is costly for a product with many small accounts. Check as well if your revenue share is calculated before or after chargebacks and refunds.

Card tokens are the main cause of vendor lock-in in this market. TechTarget describes the condition as one in which a customer cannot easily transition to a competitor’s product or service, and a vendor that controls your customers’ stored cards is in a position to create it. Require a clause that obliges the provider to transfer tokens to a successor within a stated number of days and at a stated fee, and agree on those terms before the first merchant goes live.

The Friday Shutdown Test

Before signing, put one question to each finalist and ask for the answer in writing. If your provider stopped operating on a Friday afternoon, who would pay your merchants on Monday morning, from which bank account, and using whose records?