How Much Volume You Actually Need Before PayFac-as-a-Service Pencils Out · Midcore Operations
Midcore Operations
Payments & Fintech Advisory

How Much Volume You Actually Need Before PayFac-as-a-Service Pencils Out

The fixed diligence and reporting costs behind a PayFac-as-a-Service program do not shrink with volume. That is where the real breakeven comes from.

Published
8 November 2026
Reading time
9 min read
Author
Payments & Fintech Advisory practice
Topic
Payments & Fintech Advisory
Key takeaways
  • Visa's own Payment Facilitator and Marketplace Risk Guide requires an acquirer to complete an onsite inspection of a prospective payment facilitator's operations before registering it. That diligence cost applies whether the program processes 5 million dollars a year or 500 million.
  • Visa Core Rules Section 10.2.2.4 requires an annual due diligence review of a registered Third Party Agent, and Section 10.2.2.6 lets Visa demand a detailed quarterly activity report with a 30 calendar day deadline. Both are recurring compliance obligations that do not shrink just because volume is low.
  • A PayFac-as-a-Service program earns a share of per-transaction margin, which scales directly with volume. The compliance, underwriting, and program-management overhead behind it does not scale down the same way. That mismatch is the actual math behind Midcore's own stated 25 million to 50 million dollar threshold.
  • Below that volume, the revenue share a program captures usually does not clear the fixed cost of standing up and maintaining it, which is why a referral or ISO model, not a PayFac-as-a-Service program, is usually the right call until volume or a credible path to it exists.

How much volume you actually need before PayFac-as-a-Service pencils out comes down to a mismatch between two kinds of cost. A program’s revenue scales directly with transaction volume. The compliance and diligence obligations sitting underneath it do not scale down the same way, because a card network’s registration and review requirements apply at close to the same intensity whether a program processes a modest volume or a large one. That mismatch, not a round marketing number, is where a real volume floor actually comes from.

The diligence cost that does not shrink with volume

Visa’s own Payment Facilitator and Marketplace Risk Guide requires an acquirer to complete a due diligence review before it may contract with and register a prospective payment facilitator. That review explicitly includes an onsite inspection of the prospective payment facilitator’s business operations and its operational risk policies, procedures, and controls, covering underwriting, risk monitoring, and data security specifically. This is not a lighter-touch review for a smaller program. The guide does not scale the inspection’s depth to the applicant’s projected volume. A payment facilitator processing a modest volume still has to pass the same onsite inspection a much larger one does.

That single requirement already explains a meaningful share of why a small program struggles to make the structure work. An onsite inspection, and the operational documentation it requires a platform to have ready, is a real cost in time and preparation regardless of how many transactions the resulting program will actually process. A platform spreading that fixed cost across a small transaction volume is absorbing a much higher cost per dollar processed than one spreading it across a large one.

The recurring obligations that follow registration

The fixed-cost problem does not end once a payment facilitator program is approved and live. Visa Core Rules Section 10.2.2.4 requires the sponsoring Member to perform an annual due diligence review of each registered Third Party Agent, a category that covers a payment facilitator, to confirm it still complies with applicable regional due diligence standards. That review happens every year, for every registered program, independent of how much volume moved through it that year.

Section 10.2.2.6 adds a second recurring obligation with real consequences attached. Upon Visa’s request, the Member must submit a detailed quarterly report, signed by an authorized officer, covering the activities and services of each Third Party Agent doing business on its behalf. Visa may assess a non-compliance charge if that report is not delivered within 30 calendar days from the end of the quarter. Producing that report accurately requires the underlying activity records to already exist in good order. A smaller program still has to maintain those records and still faces the same 30 day deadline and the same non-compliance exposure if it cannot meet it, even though the revenue behind that program is proportionally much smaller than a larger one facing the identical obligation.

Why the revenue side scales and the cost side mostly does not

A PayFac-as-a-Service program earns its revenue as a share of the per-transaction margin on every sub-merchant’s processing volume. Double the volume moving through the program, and the revenue roughly doubles alongside it, assuming pricing stays consistent. The onsite inspection described above does not become twice as expensive because volume doubled. The annual due diligence review does not take twice as long. The quarterly reporting obligation does not get materially harder to satisfy at a higher volume, since the underlying recordkeeping discipline needed to produce an accurate report is largely the same discipline whether the numbers in that report are small or large.

This is the actual mechanism behind a volume threshold. At low volume, the revenue the program’s margin share generates is thin relative to the fixed cost of standing up and maintaining the compliance structure underneath it. As volume grows, that same fixed cost gets spread across a larger and larger revenue base, and at some point the economics flip from a program that is a net drag to one that is genuinely profitable. Where exactly that crossover happens depends on a program’s specific pricing, revenue share, and cost structure. That is why Midcore states a range rather than a single number. Twenty five million to fifty million dollars in annual volume is where most programs Midcore has structured actually cross that line, not a figure derived from any published card network standard.

What actually sits inside the fixed side of the ledger

The fixed costs behind a payment facilitator program are not limited to the two Visa obligations described above. They also include the PFaaS provider’s own underwriting of the platform itself. That review does not get materially lighter for a smaller applicant, because the provider has to perform it before extending the infrastructure and sponsorship that makes the program possible in the first place. They also include the platform’s own internal operational readiness: a documented sub-merchant underwriting process, and a risk monitoring function capable of watching for the fraud and dispute patterns Visa’s own acquirer monitoring program tracks. They include a team that can actually produce accurate records when the quarterly report request described above arrives.

None of this is a one-time setup cost that disappears once the program launches. The annual due diligence review and the possibility of a quarterly report repeat on their own schedule for as long as the program exists, which means the fixed-cost side of the ledger is not a number a platform pays once and amortizes away. It is a standing, recurring commitment that has to be staffed and maintained every year the program runs, regardless of whether that year’s volume grew, stayed flat, or shrank.

This is also why volume alone, without the cost structure behind it, is an incomplete way to evaluate the decision. A platform that has built strong internal operational discipline for other reasons faces a lower effective fixed cost than one starting that discipline from nothing specifically for this program. A mature compliance function already tracking fraud and dispute data closely, already maintaining clean records an auditor could review on short notice, has most of the hard part done before the program even begins. The same volume threshold does not apply identically to every platform, because the actual cost side of the equation is not identical either.

A concrete example: two platforms considering the same structure

Picture two vertical SaaS platforms, each evaluating a PayFac-as-a-Service program with a similar PFaaS partner and similar pricing. The first platform processes 8 million dollars a year across its merchant base, growing steadily but not dramatically. The second processes 40 million dollars a year and is still growing quickly.

For the first platform, the revenue share captured on 8 million dollars of volume has to absorb the same onsite inspection, the same annual review cycle, and the same quarterly reporting discipline the second platform faces on five times the volume. The margin generated rarely covers that fixed overhead plus the platform’s own cost of maintaining the program, which usually means a referral or ISO arrangement captures less revenue per dollar processed but avoids the compliance structure entirely, and comes out ahead on a net basis. For the second platform, the same fixed diligence and reporting costs are being spread across a revenue base large enough to absorb them comfortably, which is exactly the scenario where PayFac-as-a-Service economics genuinely work in the platform’s favor.

What to actually calculate before assuming the structure is right

The volume figure alone does not answer the question completely. A platform below the typical threshold with a clear, credible trajectory toward it within a year or two has a legitimate case for building the program early. That means accepting a period where the fixed costs outweigh the revenue share, in exchange for having the structure in place when volume catches up. A platform at or above the threshold with flat or declining volume does not automatically clear the bar just because the number looks right today.

The actual calculation has to weigh the specific revenue share a given PFaaS partner’s pricing offers, against the platform’s own cost of maintaining the operational readiness a due diligence review and ongoing reporting actually require, measured against current volume and a realistic growth trajectory rather than an optimistic one. A platform that has not run this calculation with its own real numbers is making a structural decision based on a rule of thumb rather than its own actual economics.

Running that calculation accurately, against a specific platform’s real volume, pricing, and growth trajectory rather than a generic threshold, is exactly the work behind Midcore’s PayFac-as-a-Service consulting engagements. Where the better fit turns out to be a different banking relationship structure entirely, banking-as-a-service consulting is where that broader question gets worked through. And because a card program carries a similar fixed-cost-versus-volume dynamic of its own, card-as-a-service consulting is where that parallel calculation gets run for a platform considering both paths at once.

Frequently Asked Questions

Is the 25 million to 50 million dollar volume threshold an official Visa or card network rule?

No. It is Midcore’s own stated position, built from structuring these programs directly, not a published card network threshold. Visa’s own rules do not set a minimum volume for a payment facilitator program. What Visa’s rules do set are fixed diligence and reporting obligations, an onsite inspection before registration and recurring annual and quarterly reviews afterward, that apply regardless of volume. Those fixed costs are what actually produces a real-world volume floor.

Why does a PayFac-as-a-Service program’s economics depend so much on registration and reporting rules rather than technology costs?

Because the technology, the onboarding flow, the sub-merchant portal, is a build cost that a platform controls directly and can usually manage within a fixed budget. The compliance obligations behind the underlying payment facilitator registration are different. Onsite due diligence before approval, and ongoing annual and quarterly review afterward, are set by the card network and the sponsor relationship, not by the platform. They apply at essentially the same intensity regardless of how much volume the program processes.

What should a platform below the volume threshold do instead of PayFac-as-a-Service?

Usually a referral arrangement or a standard ISO relationship with a processor, which gives up PayFac-level revenue share and onboarding control in exchange for avoiding the fixed diligence and reporting overhead a payment facilitator program carries regardless of volume. The right structure depends on the platform’s actual volume trajectory, not just its volume today, since a credible path to the threshold can justify building the program ahead of the revenue that will eventually support it.

Sources: Visa Payment Facilitator and Marketplace Risk Guide and Visa Core Rules and Visa Product and Service Rules, Sections 10.2.2.4 and 10.2.2.6.

Payments & Fintech Advisory practiceMidcore Operations · 8 November 2026
All insights
Free consultation

Get your free Assess

Tell us what is happening. We reply within one business day with a US-based practice lead, not a salesperson.

  1. 01Within 1 business dayA US-based practice lead replies and books a 30 minute call.
  2. 02On the callWe map the problem, the volume, the partners, and the constraints.
  3. 03After the callYou get a written read of one to three pages, yours to keep.
  • Handled under NDA
  • Written, not a slide deck
  • No obligation to continue

No obligation. We will tell you if you do not need us.

Before you go

Take the written read with you

Every engagement opens with an Assess: a written read of what is happening, what it costs, and what to do about it. It is quoted on its own and you can stop after it.

+1 (786) 619-0152