Payment Ecosystem
- Most card transactions involve four parties: your customer, your business, the issuer (the customer's bank) and the acquirer (the bank behind your processor), connected by a card network. Amex and Discover can run three-party, when they're both the customer's bank and yours
- On a four-party sale, your acquirer pays interchange to the issuer. Networks set it, not your processor. Amex and Discover can work differently, through a merchant discount or an OptBlue arrangement. In the site's assumed example, a flat-rate processor's gross share comes out about the same size as interchange
- Your processor (Stripe, Square, Adyen) is your acquirer or sits in front of one. When you call support, you're calling the processor, not Visa
- The four-party model explains why you can't negotiate interchange directly and why different card types cost different amounts to accept
Before you can optimize payments, you need to know who's taking a cut and why.
The payment industry has a lot of players with confusing titles. This page maps the territory.
The Four-Party Model
Most card transactions involve four parties, plus the networks that connect them. Amex and Discover can run three-party, when they're both the customer's bank and yours. The four-party flow:
The Four Parties
| Party | What They Do | Examples |
|---|---|---|
| Cardholder | The customer paying with a card | You, your customers |
| Issuer | Bank that issues the card and extends credit/debit | Chase, Capital One, your local bank |
| Acquirer | Bank that provides your merchant account | Wells Fargo Merchant Services, Elavon |
| Merchant | Business accepting the payment | You |
The Networks
Card networks (Visa, Mastercard, Discover, Amex) connect issuers and acquirers. They:
- Set the rules for transactions
- Route authorization requests
- Facilitate settlement between banks
- Set interchange rates
Amex and Discover are different: They're both network AND issuer for most of their cards. This is the "three-party model" (they play two roles).
Where All the Other Players Fit
The four-party model is clean, but real life is messy. Here's where the other players fit:
That's the path a transaction takes. A PayFac or an ISO is a commercial relationship around it, not a stop every payment has to pass through, and one company can play several of these roles (Stripe on how the roles combine, accessed 3 November 2026).
Processor
What they do: Route transactions between you and the acquirer.
Key points:
- Connects to card networks on acquirer's behalf
- Provides the technology layer (APIs, SDKs, dashboards)
- May or may not be the same company as your acquirer
Examples: First Data (Fiserv), TSYS (Global Payments), Worldpay, Adyen
Gateway
What they do: Securely transmit payment data from your website/app to the processor.
Key points:
- Handles the technical integration (JavaScript libraries, APIs)
- Encrypts and tokenizes card data
- Often bundled with processing (Stripe, Square)
- Sometimes separate (Authorize.net with separate processor)
Examples: Stripe (bundled), Authorize.net, Braintree, NMI
ISO (Independent Sales Organization)
What they do: Resell processing services from acquirers/processors.
Key points:
- Sales and support layer
- May mark up pricing
- Wide variation in quality and pricing
- Your contract is often with the ISO, not the acquirer directly
Examples: Many local payment companies, "merchant services" providers
PayFac (Payment Facilitator)
What they do: Let you start processing quickly by putting you under their merchant account.
Key points:
- You're a "sub-merchant" under their master account
- Ask how long onboarding takes, and what verification can hold it up
- Pricing depends on the provider and plan
- They take on part of the compliance work. Your own PCI duties don't go away, even if you outsource all card handling (PCI SSC FAQ 1092, June 2025)
- Termination alone doesn't put you on the MATCH list. Listing has its own conditions
Examples: Stripe, Square, PayPal, Shopify Payments
The Key Distinction: PayFac vs. Direct Processor
| Factor | PayFac | Direct Processor |
|---|---|---|
| Your merchant ID | Sub-merchant under theirs | Your own MID |
| Who you contract with | The PayFac | The processor or acquirer |
| PCI work | They do part of it. Your duties stay with you | You manage more of it, and your duties stay with you |
Everything else is a question, not a given. Onboarding time, price, contract length, support and termination risk vary by provider and plan, not by the label. Stripe and Square publish standard rates and offer custom pricing, and Helcim publishes its own cancellation terms (accessed 3 November 2026). Ask each provider for all five in writing.
The tradeoff: simplicity against control.
How Money Flows
Authorization Flow (Real-time)
When a customer swipes/taps/enters their card:
Time: Usually a few seconds
Settlement Flow
After transactions are captured:
Time: Settlement moves money between the banks. Your deposit then follows your processor's payout schedule. Track both clocks separately
Fee Flow
Everyone takes a cut. Here's who gets what:
In this example, on a flat rate, your processor's gross share comes out about the same as the issuer's. That surprises people. It's an assumed US example, not an observed typical split. At 2.9% + 30c, a $75 order costs you $2.48. Assumed interchange of 1.36% + $0.152 is $1.17, and unverified assessments of 0.14% + $0.02 are about $0.13. That leaves $1.18 gross, which isn't profit: it has to cover processing, acquiring and other costs. Where those inputs come from.
Fee Breakdown
| Fee Type | Goes To | What to use |
|---|---|---|
| Interchange | Issuer | Your actual charges. The site's model assumes about 0.9% in person and 1.4% online, blended. For US domestic sales, card-specific examples include regulated debit at 0.05% + $0.21 (plus $0.01 for eligible issuers), Visa Business Non-Qualified at 3.15% + $0.20, and Mastercard small business Standard, Level 5 at 3.30% + $0.10 |
| Assessment | Network | Your actual charges. The US model assumes 0.14% + $0.02, which is unverified. Canadian network schedules are public, but they don't verify it |
| Acquirer/Processor markup | Your processor | Set by your provider and plan. This is the negotiable part |
Interchange rates are from Visa's US schedule of 18 April 2026 and Mastercard's of 17 April 2026, both verified 2 August 2026. The blend weights them by Federal Reserve transaction counts, which don't establish the full card, reward or channel mix. Treat it as the site's model.
Why This Matters
-
Interchange is a cost you don't control, and the networks set it. You can't negotiate it directly, but you can qualify for lower tiers (see Interchange Optimization). Your own statement shows how big it is. In the example above, the processor's gross share is about the same size, and that part you can negotiate.
-
Processor markup is negotiable for higher volume. If you're paying 2.9% + $0.30 and doing $1M+/year, price an interchange-plus quote against it on your actual card mix.
-
Bundled pricing hides the breakdown. Flat-rate pricing (2.9% + $0.30) is simple but doesn't let you see where money goes.
Understanding Your Stack
Who Am I Actually Working With?
Many merchants don't know who their acquirer is. Here's how to figure it out:
| Clue | What It Tells You |
|---|---|
| Who signed your contract? | Might be ISO, PayFac, or processor |
| Who deposits your money? | Usually the processor or acquirer |
| Who handles disputes? | Processor or acquirer |
| What's on your statement? | May show acquirer name |
Common Stack Configurations
| Configuration | Example | Who's Involved |
|---|---|---|
| PayFac (all-in-one) | Stripe | You → Stripe (combined roles) → the acquiring bank your agreement names |
| Traditional | Restaurant with Elavon | You → POS system → Elavon (Acquirer + Processor) |
| Split | Enterprise e-commerce | You → Custom Gateway → Processor → Bank acquirer |
| ISO layer | Local payment provider | You → ISO (reseller) → Processor → Acquirer |
Why This Matters for You
For Negotiations
Knowing the layers helps you negotiate:
- Can you go direct to the processor instead of through an ISO?
- Are you paying PayFac simplicity fees when you've outgrown them?
- Is your interchange actually what you're being charged?
For Troubleshooting
When things break, knowing who does what helps:
- Transaction declined? Check the status and code first. An issuer refusal, a provider or network block and an integration error are different problems (Stripe's decline categories, accessed 3 November 2026).
- Payout late? Find which stage is delayed before you decide who owns it.
- Dispute? Processor routes it, network rules apply.
For Compliance
Different players have different requirements:
- PCI compliance flows up the chain
- Network rules apply to everyone
- A PayFac can handle part of it. Your own duty to protect card data and validate PCI compliance stays with you
For Risk
Understanding relationships affects your risk:
- PayFac termination doesn't list you by itself. MATCH listing has its own conditions
- Direct processor = more control, more responsibility
- ISO in between = another layer that can change or fail
Glossary Cheat Sheet
| Term | Meaning |
|---|---|
| Acquirer | Bank that provides your merchant account and settles funds |
| Issuer | Bank that issued the customer's card |
| Processor | Company that routes transactions between you and acquirer |
| Gateway | Technology that transmits payment data to processor |
| ISO | Reseller of processing services |
| PayFac | Payment facilitator (you're under their merchant account) |
| Network | Visa, Mastercard, Amex, Discover |
| Interchange | Fee the acquirer pays the issuer on a four-party sale |
| Assessment | Fee paid to network on each transaction |
| MID | Merchant ID (your account number with acquirer) |
Test to Run
Map your payment stack:
- Who provides your gateway? (The JavaScript/API you integrate with)
- Who is your processor? (Who shows up in your dashboard)
- Who is your acquirer? (Who actually holds your merchant account)
- Are you on a PayFac or direct? (Check if you have your own MID)
If you can't answer these, ask your account rep or check your contract.
Scale Callout
| Volume | Where to Focus |
|---|---|
| Under $100k/mo | PayFac is fine. Don't over-optimize. |
| $100k-$500k/mo | Consider your own merchant account (direct processing). Run the numbers on interchange-plus pricing: card costs passed through at cost, plus a separate processor markup. |
| $500k-$2M/mo | Definitely evaluate direct. Negotiate rates. Consider multiple processors. |
| Over $2M/mo | Optimize everything. Multi-processor. Dedicated support. Custom pricing. |
Where This Breaks
-
PayFac termination. If your PayFac terminates you over chargebacks or fraud, check whether the termination also meets a MATCH listing condition. A listing makes finding a new processor harder, and the next provider still decides whether your business fits its policies. Termination by itself isn't a listing.
-
ISO instability. ISOs come and go. If your ISO goes out of business, your processing may be interrupted.
-
Acquirer compliance. If your acquirer decides your business is too risky, they can hold funds or terminate you, even if you're technically compliant.
Next Steps
Just starting out?
- Pick a PayFac → Buying Payments
- Understand your fees → Reading Your Statement
- Learn the basics → Authorization & Capture
Scaling up?
- Evaluate direct processing → Processor Comparison
- Negotiate rates → See Buying Payments
- Optimize interchange → Interchange Optimization
Troubleshooting?
- Map your stack → Use the questions above
- Know who to call → Different issues go to different parties
- Understand the layers → Each has their own rules and timelines
See Also
- Accept Payments: The payments hub
- Card Networks: Visa, Mastercard, Amex, Discover rules and programs
- Buying Payments: Choosing a processor
- Gateway Basics: What gateways do
- Provider Types: Gateway vs ISO vs PayFac vs MoR
- Authorization & Capture: Transaction mechanics
- Settlement & Reconciliation: Money movement
- Interchange Optimization: Reducing fees
- Processor Comparison: Comparing options
- Reading Your Statement: Understanding fees
- Processor Management: Working with processors
- MATCH / TMF List: What happens if you're terminated