Payment Processing

10 min read

Payment Facilitator Compliance Requirements: The 2026 Checklist

Payment facilitator compliance requirements in one checklist: card network registration, sponsor bank oversight, sub-merchant KYC and OFAC screening, monitoring, PCI DSS, money transmission and reporting, plus what payfac compliance never covers.

Quick answer: To operate as a payment facilitator you need a sponsoring acquirer (sponsor bank) and registration with each card network through it. You need a written underwriting and KYC program for every sub-merchant, including OFAC and sanctions screening. You need ongoing transaction and chargeback monitoring, PCI DSS compliance (typically Level 1 at payfac scale), and a funds-flow structure that either fits under your sponsor bank or carries money transmitter licences. You also file tax reporting for sub-merchants (Form 1099-K in the US). None of that covers your sub-merchants' sales tax or VAT, which stays with them.

That's the short version. The long version is a year or more of work, which is why most software companies that look into becoming a payfac end up using PayFac-as-a-Service instead. Here's what's on the list, grouped by who is asking.

This is an operator's overview, not legal advice. Rules differ by card network, region and sponsor bank, so confirm the specifics with your sponsor and counsel.

The payment facilitator compliance checklist

Requirement Who requires it What it involves
Sponsor bank agreement Acquirer Contract, due diligence on your company, capital and reserves
Network registration Visa, Mastercard (via sponsor) Registration as a payfac, annual renewals, fees set by sponsor and network
Sub-merchant agreements Networks Every sub-merchant signs terms that meet network rules
KYC/KYB and underwriting Networks, sponsor, AML law Verify identity and business, check beneficial owners, screen against prohibited lists
OFAC and sanctions screening US Treasury (and local equivalents) Screen sub-merchants and owners at onboarding and on an ongoing basis
Transaction monitoring Networks, sponsor Detect fraud, laundering, prohibited goods, chargeback spikes
Chargeback and fraud thresholds Networks Keep sub-merchants under dispute and fraud ratios; remediate or terminate
Large sub-merchant rules Visa Sub-merchants above roughly $1M annual Visa volume need a direct agreement with the acquirer
PCI DSS PCI SSC, networks Validated compliance, typically Level 1 for a payfac's volume
Money transmission State and federal regulators Licences or a bank-held funds structure, depending on how money flows
Tax information reporting IRS (US) Collect TINs, file Form 1099-K for sub-merchants
Audits and reporting Sponsor, networks Regular reviews, sub-merchant data reporting, policy documentation

Some of these are one-time projects. Monitoring, screening and reporting are permanent headcount.

Nothing starts without a sponsor. The acquirer takes on responsibility to Visa and Mastercard for everything you do, so it will diligence your company the way a lender would: ownership, financials, the risk team's experience, the verticals you plan to serve, and how much loss you can absorb. Expect to post a reserve.

Your sponsor then registers you with each network. Visa's payment facilitator and marketplace risk guide lays out what it expects the acquirer to check, and Mastercard runs its own registration and review program. In some regions, such as Visa's CEMEA region, the payfac also signs an agreement with Visa directly and goes through certification. Registration fees and timelines aren't public in a useful way, because the sponsor passes them through along with its own costs.

A "registered payment facilitator" is simply a payfac that has completed this process. Anyone else is reselling someone else's registration.

Sub-merchant onboarding, KYC and sanctions screening

Person reviewing a credit card authorization form in an office
Person reviewing a credit card authorization form in an office

This is the bulk of the daily work. For every sub-merchant you have to:

  1. Verify the business exists and who owns it, including beneficial owners above the ownership threshold that applies to you.
  2. Screen the business and its owners against OFAC's sanctions lists and any other lists your sponsor requires.
  3. Check the business against prohibited and restricted categories (your sponsor will have a list, and it's longer than you expect).
  4. Assign a merchant category code that matches what it actually sells.
  5. Decide limits and reserves based on risk.
  6. Get the sub-merchant to sign an agreement that meets network requirements.

Doing all of that in under five minutes, which is what users expect after Stripe, takes automated identity checks and a risk engine with sensible rules. It also takes a manual review queue for the cases that don't pass cleanly. That queue never goes away.

Monitoring, chargebacks and the $1M line

After onboarding, you watch. The networks run dispute and fraud monitoring programs. If a sub-merchant's chargeback ratio climbs past the program thresholds, you're expected to fix it or shut it down, and fines can land on your sponsor, which will pass them to you. Monitoring also has to catch transaction laundering (a sub-merchant processing for an undisclosed business) and sudden changes in what's being sold.

Growth creates its own obligation. Under Visa's rules, once a sub-merchant processes more than about $1 million a year in Visa volume, the acquirer needs a direct merchant agreement with it. The sub-merchant can usually still be served through the payfac, but the program has to plan for that extra agreement as its best customers grow.

PCI DSS and data security

Server racks with blue lighting in a secure data center
Server racks with blue lighting in a secure data center

A payfac stores, processes or transmits cardholder data for every sub-merchant, so it has to validate PCI DSS compliance. At payfac volumes that's almost always Level 1, which means an annual on-site assessment by a Qualified Security Assessor. Using a processor's hosted fields or tokenization reduces scope a lot, and most new payfacs build that way on purpose. Your sub-merchants still have their own PCI obligations, usually a short self-assessment questionnaire.

Money transmission and funds flow

In the US, holding and paying out other businesses' money can count as money transmission, and most states license it separately. Payfacs generally avoid needing licences in every state by structuring the flow so funds settle into accounts controlled by the sponsor bank and pay out from there under the bank's oversight. Whether your structure qualifies is a legal question with a state-by-state answer, and it's one of the most common reasons payfac projects stall. Venable's overview is a good primer on how lawyers frame it.

Reporting obligations

In the US, the payfac is the payment settlement entity for its sub-merchants, so it collects tax identification numbers and files Form 1099-K. That means TIN validation at onboarding, backup withholding when a TIN can't be validated, and a yearly filing run. Your sponsor and the networks will also want regular reporting on sub-merchant counts, volumes, risk events and terminations.

Fee transparency belongs here too. Sub-merchants expect statements showing what they processed, what they paid and what was held. Building good statements is one of those jobs that looks small and isn't.

What payfac compliance doesn't cover

All of the above is about accepting payments safely. None of it is about the sale itself. A payfac's sub-merchants remain the legal sellers, so they're still responsible for sales tax, VAT, GST, invoicing and consumer-law obligations in every market they sell into. Being a payfac doesn't change your own tax obligations either.

That's the line between a payfac and a merchant of record. An MoR becomes the seller and takes the tax side too. We cover the difference in merchant of record vs. payment facilitator.

Do you actually need to become a payfac?

For most software companies, no. A full payfac program makes sense when you have large payment volume across many merchants, a team that can run risk and compliance permanently, and payments revenue big enough to justify both. For a vertical SaaS platform below that scale, PayFac-as-a-Service gives you the embedded experience and most of the revenue share while the provider holds the registration and the compliance burden. PayFac vs. ISV walks through that decision, and payfac companies lists the providers.

If you're a software company selling your own product (not enabling other merchants), you don't need any of this. You need someone to handle payments and tax for your own sales, which is a merchant of record's job.

Frequently Asked Questions

What are the compliance requirements for a payment facilitator?

A payfac needs a sponsor bank and card network registration, a KYC and underwriting program for sub-merchants with OFAC and sanctions screening, ongoing transaction and chargeback monitoring, PCI DSS compliance, a compliant funds-flow structure or money transmitter licences, and tax reporting such as Form 1099-K in the US.

What is a registered payment facilitator?

A registered payment facilitator is a company that a sponsoring acquirer has registered with Visa, Mastercard and other networks as a payfac. Registration lets it onboard sub-merchants under its own master merchant account, subject to network rules and the sponsor's oversight.

Does a payment facilitator need a money transmitter license?

It depends on how funds flow. Payfacs that hold and disburse sub-merchant funds themselves may need state money transmitter licences in the US. Many structure the flow so funds stay in accounts controlled by the sponsor bank, which can reduce or remove that requirement. This is a legal question, so get counsel.

What PCI level does a payment facilitator need?

Most payfacs validate at PCI DSS Level 1 because of their transaction volume, which requires an annual assessment by a Qualified Security Assessor. Using tokenization or a processor's hosted payment fields reduces the scope of that assessment.

Is there a payment facilitator compliance checklist?

Yes. The core checklist covers the sponsor bank agreement, network registration, sub-merchant agreements, KYC and underwriting, sanctions screening, transaction monitoring, chargeback thresholds, large sub-merchant rules, PCI DSS, money transmission, 1099-K reporting, and regular audits. Your sponsor bank will have its own version on top of the card network rules.

Does payfac compliance cover sales tax?

No. Payfac compliance covers payment acceptance. Sub-merchants stay the legal sellers and remain responsible for sales tax, VAT and GST. Only a merchant of record takes on tax obligations, because it becomes the seller of record.

The bottom line

Becoming a payment facilitator is a compliance program with a payments product attached, not the other way round. If that's the business you want to build, start with the sponsor conversation and the funds-flow question, because those decide everything else. If what you actually want is to sell your own software globally without owning payments, tax and chargeback risk, Comecero acts as your merchant of record for verified customers, after review, at published rates.

Ready when you are

Grow in every market, on every model.

See how Comecero fits your billing, your processors and the markets you sell in. Book a demo with the team, or start free.

Your revenue review

Sample

Revenue slipping away each month

$22,700

Declined at checkout$12,400
Failed renewals$6,900
Fraud losses$2,100
Chargebacks lost$1,300

Each line comes with the fix that wins it back.