CHECKOUT CHRONICLE . ISSUE 01 FEE TABLES REBUILT FROM STATEMENTS . NO AFFILIATE LINKS . CHECKOUTCHRONICLE.COM
CCCheckout ChronicleWhere online store money actually goes
Due diligence

Payment Facilitator vs ISO: The Contract Decides Who Holds Funds

A payfac signs the store and pays it out. An ISO sells a bank's contract. Visa and Mastercard rules show who can hold a store's money under each model.

CCBY the statements desk.10 MIN.21 OCT 2026

The choice in payment facilitator vs ISO usually arrives as a pricing question, and the card scheme rules show it is really a question about who signs the store. Visa describes a payment facilitator as a third-party agent that “Signs a merchant acceptance contract with a sponsored merchant on behalf of an acquirer.” Mastercard's rulebook gives an ISO a sales role instead.

That signature also decides who controls the payouts.

Visa's risk guide for these firms says a payment facilitator “may temporarily suspend a seller’s settlement proceeds when it has reason to believe that funding the seller may result in loss exposure.”

Stores with one to forty million in yearly sales feel this most.

The model behind the checkout settles the party that can pause payouts, the party that holds a reserve, and the moment the bank starts asking for a direct contract.

We read the April 2026 edition of the Visa Core Rules, the June 2026 Mastercard Rules and the payfac terms that Shopify publishes for stores in the UK and the EU. Do not sign on the strength of the rate card alone. The clauses that move cash sit elsewhere in the contract.

What is the real difference in payment facilitator vs ISO?

The difference sits in the name on the merchant agreement and in the account the money passes through. Visa's glossary defines a Merchant Agreement as “A direct contract between a Merchant and an Acquirer or between a Sponsored Merchant and a Payment Facilitator”, and an ISO is missing from that sentence.

Mastercard's rulebook spells out what an ISO does instead.

Its list of ISO services opens with a firm that “Provides Cardholder, Merchant, and/or Account Holder Solicitation, including application processing”, then adds statement preparation, merchant training and terminal deployment. Customer service is allowed too, without access to account data.

In the ISO model the store signs with the acquiring bank, and the bank pays the store. Mastercard's rule 5.4.1 puts that payment duty on the acquirer. The duty ends only when the merchant receives the money.

A payfac sits between the two, yet the bank stays. Visa's rules treat a sponsored merchant as a merchant of its payfac's acquirer, and they hold that acquirer liable for the payfac's acts. Shopify's payfac agreement says it in its opening lines: “We are acting on behalf of and as agents of the Acquirer.”

Cutting a store off stays in the bank's hands as well. Visa requires every payfac agreement to give the acquirer the right to terminate a sponsored merchant immediately for good cause, for fraud or at Visa's request.

The payfac's own status adds a second exit door. Mastercard requires each sponsored merchant agreement to end automatically and immediately if Mastercard de-registers the payfac or if the payfac's acquirer stops being a Mastercard customer for any reason.

So a store on a payfac answers to two risk teams, and a friendlier dashboard does not remove the second one.

Who can freeze a store's payouts under each model?

Under a payfac, the payfac pauses payouts and the acquirer holds any reserve the payfac asks a store to fund.

Under an ISO, the acquiring bank does both jobs.

The pause itself is described in plain words in Visa's guide. A payfac that investigates an alert must release the held funds if the investigation ends well, and if it ends badly the settlement money may move into a reserve account under the contract and the Visa Rules.

The triggers for an alert are spelled out too. The guide tells payfacs to watch sellers that sit dormant for a long time and then show a sudden surge in volume, with an exception for sellers known to run a seasonal business.

Websites are watched as well, since the guide requires payfacs to monitor their sellers' e-commerce sites on an ongoing basis for illegal activity, transaction laundering and deceptive marketing.

That reserve has a fixed home under Visa's guidance. The guide states that “Visa prohibits payment facilitators from holding and controlling merchant reserves”, and it adds that the funds must be held and controlled by the acquirer.

Mastercard gives the payfac and the bank the same contractual tool. Its rule on payments to sponsored merchants reads “A Sponsored Merchant Agreement may provide for a Payment Facilitator to withhold amounts for chargeback reserves or similar purposes.” Rule 5.4.1 hands an acquirer the same right against its own merchants, written into the merchant agreement.

Shopify's payfac terms show the right in a signed contract. They say “Shopify may impose a Reserve and may set off amounts you owe”. Payouts can also wait until identity and KYC checks are passed, and a store that fails them may see funds refunded to customers.

Sellers most likely to meet a reserve are named in Visa's guide: businesses with delayed delivery, such as travel, event ticketing and annual memberships. A merchant in ticketing is on that list by name, and a store taking pre-orders sits close to it.

Read the suspension and reserve clauses before the fee table. In a bad month those lines decide the cash flow, and a store should know in advance which party can trigger each of them.

How does the payfac model treat a store past one million dollars?

The payfac model has a ceiling, and on Visa it sits at one million dollars of yearly volume per store. Rule 5.3.1.4 says an acquirer working with a payfac “must enter into a direct Merchant Agreement with a Sponsored Merchant that exceeds USD 1 million in annual Transaction volume”.

Timing depends on the store's history with the payfac.

A new store over the line needs the direct agreement before the payfac processes its first transaction.

Existing stores get two years after they cross the line.

Signing directly with the bank does not end the payfac relationship. Visa adds that the payfac may keep providing payment services, settlement included, to a store that has signed directly with the acquirer.

A way around the rule rewards stores that stay put. The acquirer can skip the direct contract if the payfac has held the store for at least two years with the same acquirer, reports volume, disputes and fraud to it, and the acquirer keeps overseeing both.

That exemption also carries a clean record condition. A footnote says the acquirer, payfac and sponsored merchant must not appear in Visa risk programs, or have excessive violations, in the three years before the agreement.

A second exemption works by category code and covers sectors such as utilities, healthcare, schools, fines and tax payments.

Online retail does not appear on that list.

Mastercard draws its line ten times higher, at ten million dollars. A sponsored merchant above that volume must sign directly with a Customer, the Mastercard word for an approved financial institution, unless the acquirer and payfac meet a set of threshold conditions.

Those conditions include registering the payfac as a Network Enablement Partner, read-only access for the acquirer to the payfac's systems, and a monthly review of at least five per cent of newly onboarded sellers.

For a store at our readers' size, the Visa line arrives first. A request from a payfac to sign a new agreement naming its bank may be this rule at work.

What does an ISO do if it never touches the money?

An ISO finds the store, prepares the application and keeps in touch afterwards, from statements to terminals.

The acquiring bank signs the contract and pays the store.

Card schemes still track which ISO stands behind each sale. Mastercard's rule 7.6.6 requires an acquirer that uses an ISO to fill a dedicated ISO field with the ISO's identifier in its transaction records.

Payfacs get the same treatment in Visa's transaction data. The acquirer obtains a unique payfac identifier from Visa, and every authorization record must carry both that identifier and the sponsored merchant's own identifier.

Visa counts an ISO among its third party agents, and every such agent goes on a register kept by Visa. The rule is short: “A Member must register a Third Party Agent with Visa.” Visa may also reject a registration at any time, with or without cause, and registration must come before any services start.

Termination leaves the same trace under both models. Visa requires an acquirer to add a terminated merchant, sponsored merchant or third party agent, an ISO included, to its Merchant Screening Service when the listing criteria are met.

Only the hand on the button changes, and the record of a termination stays either way.

With an ISO, a store reads one contract. Its counterparty is a bank registered with the card schemes. Visa itself pitches payment facilitation at merchants without a traditional acquiring relationship, so the direct route is aimed at stores that already look like bank customers.

Which model costs a store less per transaction?

Neither model comes with a fixed price, and the pricing format does not reveal which contract sits underneath. Stripe's UK price page, for one, lists a standard blended rate of one and a half per cent plus twenty pence for standard UK cards. EU cards cost two and a half per cent plus twenty pence.

The same page also offers custom IC+ pricing for large payment volumes.

Visa's own fee page explains what sits underneath. It describes interchange as a transfer fee between acquiring and issuing banks, says merchants do not pay it, and adds that a merchant negotiates a merchant discount with its financial institution, typically as a percentage per transaction.

Take an invented example to see the stakes: a store in London with two million pounds a year on standard UK cards and an average basket of fifty pounds. At Stripe's standard rate of one and a half per cent, that is thirty thousand pounds in percentage fees. Fixed fees on forty thousand payments add eight thousand more.

Whether an acquiring bank would beat thirty-eight thousand pounds for that store is a question no public page answers.

Price follows the contract model in one more way. A payfac answers to its bank for every seller's disputes, since Visa requires its agreement to say the payfac “Is responsible and financially liable for each Transaction processed on behalf of the Sponsored Merchant”. In our reading, part of a payfac's price pays for that exposure, even though Shopify's terms, for one, make the store solely responsible for its own chargebacks.

Should a growing retailer become a payfac?

A single store has no business case to become a payfac, because the role exists only for firms that sign other merchants. Visa pitches it to firms adding payment capability to merchant software, websites and inventory tools.

Liability then lands on the payfac under Visa's rules. Its agreement must make the payfac liable for the acts, omissions and cardholder disputes of its sponsored merchants. The payfac must also make its sellers comply with PCI DSS.

Nesting one payfac inside another is ruled out as well. Visa bars a payfac from sponsoring another payfac, and Mastercard says a payfac may not be a sponsored merchant of any other payfac.

The paperwork is heavy even before the first sale. In Visa's CEMEA region a payfac signs its own agreement with Visa, and the certification package asks for local regulatory licences, a PCI DSS attestation, the beneficial owners and AML policies.

Certification also costs money whatever the outcome, and the regional guide says so plainly: “Each Certification submission attempt is subject to a fee; if the screening is unsuccessful, the fee will still apply.”

A rejected application costs a payfac time as well. The firm must tell its acquirers and suspend operations within sixty calendar days, and it can reapply only twelve months after the rejection.

Building the machinery costs more than the fees. Stripe sells platforms its own embedded payments product, and its payfac guide estimates initial fees of five thousand dollars each for Visa and Mastercard. The same guide puts Level 1 PCI DSS validation at fifty thousand to five hundred thousand dollars.

UK law adds a licensing question of its own. The Payment Services Regulations 2017 list “issuing payment instruments or acquiring payment transactions” among regulated payment services, and a business planning to handle other merchants' card money needs legal advice on authorisation before it signs anything.

Seen from a store, the payfac question is narrower. It asks about the payfac, the acquirer behind it, and the plan for the day the store passes one million dollars on Visa.

What do the card scheme rules leave unanswered?

The rules describe rights, not how often they are used. No scheme document we read publishes how many stores have payouts suspended in a year, how long a typical reserve lasts, or how many sponsored merchants are asked to sign a direct agreement with the bank.

The two schemes also give different answers here.

Visa sets the direct contract line at one million dollars and Mastercard at ten million, so one store can sit over the first line and under the second.

Payfac fees are missing from the public record too. Visa's certification guide points to the Visa Fee Schedule for the amounts and tells firms without access to ask their sponsoring acquirer.

Guidance and rules also run on different clocks. The risk guide dates from April 2021, and rule 5.3.1.4 was last updated in October 2025.

A payments lawyer can confirm how these rules apply to a given contract, an accountant can model what a reserve does to cash flow, and the acquiring bank itself can say whether a direct agreement is due.

Where do we expect payfac contracts to go next?

Our view on payment facilitator vs ISO is that the bank behind the checkout matters more to a growing store than the label on the provider. A payfac suits stores that value speed and one dashboard. An ISO suits a store that wants to negotiate a rate and read a single contract.

Scheme oversight of these intermediaries is tightening in public. From 24 October 2026, Visa requires its US and Canadian members to disclose the numeric identifiers, acquiring identifiers and BINs used by each of their third party agents.

We expect that visibility to reach merchant contracts too. More stores will ask which acquirer stands behind their payfac before they sign, rather than after a payout stops. Shopify already names Adyen as the acquirer for its UK and EU payfac business, and its terms let it move a store to a different acquirer without further approval.

The next renewal is the cheapest moment to ask that question, and the answer belongs in the file next to the rate card.

Sources

  1. Visa Payment Facilitator Model usa.visa.com.
  2. Visa Payment Facilitator and Marketplace Risk Guide usa.visa.com.
  3. Visa Core Rules and Visa Product and Service Rules, 18 April 2026 usa.visa.com.
  4. Mastercard Rules, 2 June 2026 mastercard.com.
  5. Shopify Payments Facilitator Terms (Merchant Agreement) shopify.com.
  6. Stripe pricing, United Kingdom stripe.com.
  7. Visa: Credit Card Processing Fees and Interchange Rates usa.visa.com.
  8. Visa Payment Facilitator Certification Guide, CEMEA km.visamiddleeast.com.
  9. The Payment Services Regulations 2017, Schedule 1 legislation.gov.uk.
  10. Stripe: Payfacs, a guide to payment facilitation stripe.com.