Registered PayFac · sub-merchant model

Payment facilitator services — onboard sub-merchants in days, not months.

The payment facilitator model on topropay pairs a registered PayFac master MID with the platform's vault, routing engine, dispute queue and reconciliation feed. Sub-merchants inherit PCI L1 and scheme-programme posture without their own underwriting marathon.

Book a PayFac review Read the API docs

Key benefits

Why the payment facilitator model collapses time-to-live

Four properties that show up the moment software platforms and PSPs stop pointing their customers at direct-MID underwriting and start onboarding them as sub-merchants.

  1. 01

    Onboard sub-merchants in days, not months

    Direct-MID underwriting can take 4–12 weeks. The payment facilitator model collapses that into a same-week sub-merchant approval against the PayFac's master MID — KYB checks run through topropay's onboarding flow.

  2. 02

    Inherit the PayFac's compliance posture

    Sub-merchants inherit PCI DSS Level 1, scheme-programme posture, sanctions screening and AML monitoring from the registered PayFac. No per-sub-merchant SAQ-D project.

  3. 03

    Smart routing across the acquiring panel

    Even sub-merchants benefit from per-BIN routing. Soft declines cascade across connected acquirers inside the same authorisation, lifting approval without surfacing retries to the buyer.

  4. 04

    One reconciliation feed for sub-merchant settlements

    Settlements split per sub-merchant in one normalised ledger; finance reads one feed for the whole sub-merchant base rather than a per-acquirer reconciliation per sub-merchant.

How the payments facilitator flow runs

From acquirer master MID to per-sub-merchant payout in six steps

What actually happens between an acquirer issuing the master MID to the PayFac and a sub-merchant receiving its first payout.

  1. 01

    Acquirer issues master MID to the PayFac

    A licensed acquiring bank registers topropay (or the merchant's own PayFac entity) as a payment facilitator and issues the master MID under which sub-merchant volume clears.

  2. 02

    PayFac onboards a sub-merchant

    KYB checks, sanctions screening and AML profile assembled per sub-merchant. Onboarding completes in days when documentation is clean; flagged cases queue for manual underwriting review.

  3. 03

    Sub-merchant integrates the API once

    The sub-merchant integrates topropay's unified API once — hosted checkout, embedded fields or SDK. The integration doesn't change as the sub-merchant grows or migrates between acquirers behind the scenes.

  4. 04

    Buyer transacts — routing engine selects an acquirer

    Each authorisation runs through the routing engine; the PayFac's master-MID portfolio of acquirers is ranked per transaction; soft declines cascade inside the same auth.

  5. 05

    PayFac receives funds; splits to sub-merchants

    Acquirers settle to the PayFac; the PayFac's settlement engine splits the funds per sub-merchant per the agreed pricing (interchange-plus or blended), net of platform fees.

  6. 06

    Reconciliation + sub-merchant payouts

    One normalised ledger across every connected acquirer; daily exports tagged per sub-merchant, scheme and currency; sub-merchant payouts on the merchant's preferred cadence.

Main use cases

Where the registered payment facilitator path earns its keep

Six recurring shapes — software platforms, PSPs and ISVs, marketplaces, professional networks, regulated verticals and regional facilitator expansion.

  • Plat

    Software platforms embedding payments

    SaaS platforms (booking, scheduling, marketplace platforms) that want to monetise payments without becoming an acquirer — onboard their customers as sub-merchants and earn on payments volume.

  • PSP

    PSPs and ISVs scaling sub-merchant bases

    Independent software vendors and PSPs operating an electronic payment facilitator role inside their vertical (legal-tech, vet-tech, fitness, education) — fast sub-merchant onboarding and one settlement feed.

  • Mkt

    Marketplaces and multi-seller commerce

    Multi-seller commerce platforms running a PayFac model so sellers don't each need their own MID; the platform takes payments centrally and splits to sellers.

  • Pro

    Professional-services networks

    Networks of agencies, consultancies or franchisees that bill through one PayFac master MID while keeping per-firm reconciliation and per-firm payouts.

  • Reg

    Regulated-vertical PayFacs

    Licensed gaming, regulated subscriptions and other compliance-bound verticals running the PayFac model with scheme-programme posture tuned to the vertical.

  • Geo

    Regional PayFac coverage (EU / UK / APAC / LATAM)

    PayFac entities expanding regionally onboard sub-merchants across multiple markets without re-integrating per region — partner acquirers provide the local licensed acquiring.

Scheme-side rules

Payment facilitator rules to plan against

Five scheme-side rule areas the PayFac model carries — onboarding, sub-merchant volume caps, disclosure, dispute monitoring and funding flow.

Sub-merchant onboarding & KYB
Scheme rules require the PayFac to KYB every sub-merchant before clearing volume — beneficial owners identified, sanctions screened, business legitimacy verified. topropay's onboarding flow captures the standard PayFac evidence pack per scheme.
Per-sub-merchant transaction & volume caps
Visa, Mastercard and Amex set caps on per-sub-merchant annual volume in the standard PayFac model (typically US$1M / EUR equivalent before the sub-merchant must move to its own MID). High-volume sub-merchants graduate to direct-MID over time.
Statement descriptor & disclosure
Scheme rules require the sub-merchant's identity to be clearly disclosed to the cardholder — typically through statement descriptors that name the sub-merchant alongside the PayFac brand.
Dispute, chargeback & ratio monitoring
Scheme dispute monitoring programmes (VDMP / VAMP / ECP) apply at the PayFac and at the sub-merchant levels. topropay surfaces the position per sub-merchant per acquirer; routing weights can rotate around at-risk lanes.
Settlement & funding flow
Funds flow acquirer → PayFac → sub-merchant. The PayFac is responsible for prompt settlement to sub-merchants; topropay's settlement engine handles the per-sub-merchant split and audit log.

Platform features

Capabilities that make the electronic payment facilitator model run

Twelve capabilities the platform ships once and reuses across every sub-merchant under the PayFac master MID.

  • Master MID + sub-merchant onboarding

    KYB, sanctions screening and AML profile per sub-merchant; same-week approval for clean documentation.

  • Unified API for sub-merchants

    One REST contract — hosted, embedded or SDK — that every sub-merchant integrates against.

  • Smart routing across acquirers

    Per-BIN, per-currency and per-country scoring across the connected PayFac acquiring panel.

  • Cascade & retry

    Soft declines cascade to the next ranked acquirer inside the same authorisation; nothing leaks back to the buyer.

  • PCI DSS Level 1 vault

    PAN captures into the vault before any acquirer sees it; sub-merchants inherit the posture.

  • Network tokens & updaters

    VTS / MDES network tokens by default for sub-merchant card-on-file; account updaters keep tokens alive.

  • 3DS2 / SCA orchestration

    Selective EMV 3DS2 challenges per authorisation — PSD2-compliant for European sub-merchants.

  • Per-sub-merchant settlement

    Settlement files split per sub-merchant; payouts on the merchant's preferred cadence.

  • Unified dispute queue

    One dispute queue across acquirers tagged per sub-merchant; evidence-pack templates per vertical.

  • Scheme-programme posture per sub-merchant

    VDMP / VAMP / ECP positions tracked per sub-merchant per acquirer; routing weights respond to at-risk positions.

  • Signed webhook & accounting events

    Auth, capture, settlement, dispute events per sub-merchant; ERP and accounting connectors push receipts into the merchant's books.

  • One reconciliation feed

    Settlements, fees, refunds and chargebacks across every sub-merchant in one normalised ledger.

Trust & compliance

Compliance posture inherited by every sub-merchant

One audited environment for the orchestration layer plus PayFac registration via partner facilitator entities where applicable. Sub-merchants inherit the relevant posture without carrying separate certifications themselves.

PCI DSS Level 1
Annual on-site assessment plus quarterly ASV scans; sub-merchants inherit the posture across every connected acquirer.
Scheme PayFac registration
Where topropay or its partner facilitator entity sits as the registered PayFac, scheme registration (Visa / Mastercard / Amex / Discover) is the platform's responsibility — sub-merchants don't carry it.
Scheme programme posture
VDMP / VAMP / VFMP / ECP / EFMP positions surfaced per acquirer and per sub-merchant; routing weights respond to at-risk lanes.
SCA & PSD2
Selective 3DS2 on the authorisation path keeps approval high in Europe without skipping the SCA bar.
Sanctions & AML alignment
Sanctions screening at onboarding for every sub-merchant; AML monitoring tuned per merchant vertical, volume and counterparty pattern.
Licensed verticals only
Licensed gaming, regulated financial services and other compliance-bound verticals supported only where current operating licences exist. Grey and black-market verticals are out of scope regardless of PayFac shape.

Ready to onboard sub-merchants

Run the payment facilitator model on one platform.

A 30-minute PayFac review covers the master-MID and acquirer panel relevant to your geographies, sub-merchant onboarding flow, scheme-programme posture per sub-merchant, and a sandbox you can test against before any commercial commitment.

Book a PayFac review Read the API docs

Frequently asked

Buyer questions about the payment facilitator model on topropay

Definitions, PayFac-vs-ISO comparison, sub-merchant onboarding mechanics, scheme rule areas and the practicalities of running a PayFac path with one orchestration layer underneath.

  1. 01

    What does payment facilitator mean on topropay?

    A payment facilitator (PayFac) is an entity registered with the card schemes (Visa / Mastercard / Amex) that holds a master MID with a licensed acquirer and onboards downstream sub-merchants under that MID. topropay's platform provides either the registered-PayFac role itself (via partner facilitator entities) or the orchestration layer underneath a customer's own PayFac entity — depending on the contract shape the merchant wants.

  2. 02

    How does the payment facilitator model differ from the ISO model?

    The payment facilitator model puts the PayFac on the acquirer's master MID and gives the PayFac end-to-end control over sub-merchant onboarding, settlement and dispute handling. The ISO (Independent Sales Organisation) model is referral-only — the ISO refers merchants to an acquirer for direct-MID onboarding and the acquirer carries the relationship. PayFac is faster to onboard sub-merchants but carries scheme-side compliance obligations the ISO doesn't.

  3. 03

    Is topropay an electronic payment facilitator?

    topropay operates as an orchestration platform that can fill the electronic payment facilitator role through partner facilitator entities holding the scheme PayFac registration, or sit underneath a customer's own registered PayFac as the technology layer. The same platform supports both contract shapes.

  4. 04

    Which payment facilitator companies sit inside the connected provider panel?

    The connected provider panel includes payment facilitator companies and acquirers across EU, UK, APAC and LATAM. The specific list is shared under NDA during onboarding — publishing it isn't useful because the panel evolves as new partners are added and weights rotated based on real-time performance.

  5. 05

    Where does topropay sit if I'm already running my own payments facilitator setup?

    If the merchant is already running their own payments facilitator setup, topropay's orchestration layer sits behind the merchant's PayFac entity — unified API, smart routing, vault, dispute queue and reconciliation across the merchant's acquirer panel. The merchant keeps the PayFac contract; topropay supplies the technology.

  6. 06

    Do you publish a payment facilitator list publicly?

    topropay doesn't publish a public payment facilitator list. The composition of the connected panel changes as new facilitator-eligible acquirers join and as performance shifts; what stakeholders care about — geographic coverage, scheme support, scheme-programme posture per acquirer — is shared in writing during underwriting.

  7. 07

    Does the platform work with a registered payment facilitator entity I already have?

    Yes. If the merchant has its own registered payment facilitator entity with the schemes, topropay's platform sits underneath that registration — providing the technical capabilities (vault, routing, sub-merchant onboarding flow, reconciliation) the PayFac entity needs to run.

  8. 08

    Is the platform available as a payment facilitator uk option?

    Yes — payment facilitator uk coverage is part of topropay's EU + UK base. Sub-merchants located in the UK clear through licensed UK acquirers connected to the PayFac master MID; settlement files normalise into the same reconciliation feed as EU and APAC sub-merchants.

  9. 09

    Does the platform support ach payment facilitator workflows?

    Yes. ach payment facilitator workflows are supported through partner ACH processors — NACHA mandate handling, R-code-aware retries and same-day ACH where supported. Sub-merchants accepting US ACH ride the same PayFac master arrangement as card volume; reconciliation merges card and ACH into one feed.

  10. 10

    What are the most important payment facilitator rules to plan around?

    Payment facilitator rules to plan around include scheme-set per-sub-merchant volume caps (typically US$1M / annum before graduating to direct-MID), KYB and sanctions screening per sub-merchant, statement-descriptor disclosure of the sub-merchant identity, scheme dispute monitoring programmes at both PayFac and sub-merchant levels, and prompt settlement obligations from PayFac to sub-merchants.

  11. 11

    How quickly can a sub-merchant go live?

    Most sub-merchants go from KYB submission to first payment in 2–5 business days under the PayFac model — meaningfully faster than direct-MID underwriting (which often runs 4–12 weeks for licensed verticals). Clean documentation and low-risk verticals accelerate the timeline.

  12. 12

    What happens when a sub-merchant outgrows the PayFac model?

    Scheme rules cap per-sub-merchant volume under the PayFac model. When a sub-merchant approaches the cap, the platform flags it and the migration to direct-MID begins — typically the sub-merchant retains its topropay integration unchanged because topropay supports both sub-merchant and direct-MID contract shapes.

  13. 13

    Does the platform handle dispute and chargeback flows per sub-merchant?

    Yes. The unified dispute queue tags every chargeback to its originating sub-merchant; evidence-pack templates per vertical can be configured at the sub-merchant level. Scheme dispute-monitoring positions surface per sub-merchant so the PayFac can intervene before a sub-merchant crosses programme thresholds.

  14. 14

    Can payouts to sub-merchants run on different cadences?

    Yes. Payout cadence (daily, T+1, weekly, monthly) is configurable per sub-merchant. The settlement engine respects the cadence while keeping a single reconciliation feed at the PayFac level.

  15. 15

    What kinds of businesses are NOT a good fit for the PayFac path?

    Businesses operating in adult content, unlicensed gambling, grey-market goods or other compliance-bound verticals without the relevant operating licences aren't a good fit for the PayFac path on topropay. The platform's underwriting filters these out at onboarding rather than letting volume start and then face a sudden termination from the scheme side.

Related

Related on the topropay platform