# Payment Ecosystem
Source: https://paymentsandrisk.com/docs/payments/payment-ecosystem

Last updated 4 November 2026.

TL;DR

-   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](https://paymentsandrisk.com/docs/payments/payment-ecosystem/#fee-flow), 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:

```mermaid
flowchart LR
    subgraph Left["Buyer Side"]
        CH[Cardholder<br/>👤 Customer]
        IS[Issuer<br/>🏦 Their Bank]
    end
    subgraph Middle["Networks"]
        N[Card Networks<br/>Visa, MC, Amex]
    end
    subgraph Right["Seller Side"]
        M[Merchant<br/>🏪 You]
        AC[Acquirer<br/>🏦 Your Bank]
    end

    CH <-->|Uses card| IS
    IS <-->|Routes through| N
    N <-->|Routes to| AC
    AC <-->|Provides account| M

    style CH fill:#3d5a80,color:#fff
    style M fill:#1f6f4a,color:#fff
```

### 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:

```mermaid
flowchart TD
    subgraph Merchant["Your Stack"]
        M[Your Business]
        G[Gateway]
        P[Processor]
    end
    subgraph Acquiring["Acquiring Side"]
        AC[Acquirer]
    end
    subgraph Networks["Networks"]
        N[Visa / Mastercard]
    end
    subgraph Issuing["Issuing Side"]
        IS[Issuer]
        CH[Cardholder]
    end

    M --> G
    G --> P
    P --> AC
    AC --> N
    N --> IS
    IS --> CH

    style M fill:#1f6f4a,color:#fff
    style AC fill:#3d5a80,color:#fff
```

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](https://stripe.com/resources/more/payment-processor-vs-merchant-acquirer), 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](https://www.pcisecuritystandards.org/faqs/1092/), June 2025)
-   Termination alone doesn't put you on the MATCH list. [Listing has its own conditions](https://paymentsandrisk.com/docs/chargebacks/match-tmf/)

**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](https://stripe.com/us/pricing) and [Square](https://squareup.com/us/en/payments/our-fees) publish standard rates and offer custom pricing, and [Helcim](https://www.helcim.com/pricing/) 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:

```mermaid
sequenceDiagram
    participant C as Customer
    participant M as Merchant
    participant G as Gateway
    participant P as Processor
    participant N as Network
    participant I as Issuer

    C->>M: Pays with card
    M->>G: Send card data
    G->>P: Authorization request
    P->>N: Route to network
    N->>I: Check funds/fraud
    I->>N: Approve/decline
    N->>P: Response
    P->>G: Response
    G->>M: Response
    M->>C: Approved!
```

**Time:** Usually a few seconds

### Settlement Flow

After transactions are captured:

```mermaid
sequenceDiagram
    participant M as Merchant
    participant AC as Acquirer
    participant N as Network
    participant I as Issuer

    M->>AC: Batch of transactions
    AC->>N: Submit for settlement
    N->>I: Present the sales
    I->>N: Sale amount, less interchange
    N->>AC: Net funds
    AC->>M: Payout under your provider agreement
```

**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:

```mermaid
pie title Assumed example, a 75 dollar US online order at 2.9% + 30c
    "Interchange (Issuer)" : 47
    "Network (Visa/MC)" : 5
    "Processor, gross" : 48
```

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](https://paymentsandrisk.com/docs/payments/reference/cost-model-assumptions/).

### 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

1.  **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](https://paymentsandrisk.com/docs/payments/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.

2.  **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.

3.  **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](https://docs.stripe.com/declines), 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](https://paymentsandrisk.com/docs/chargebacks/match-tmf/)
-   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:**

1.  Who provides your gateway? (The JavaScript/API you integrate with)
2.  Who is your processor? (Who shows up in your dashboard)
3.  Who is your acquirer? (Who actually holds your merchant account)
4.  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

1.  **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.

2.  **ISO instability.** ISOs come and go. If your ISO goes out of business, your processing may be interrupted.

3.  **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?**

1.  Pick a PayFac → [Buying Payments](https://paymentsandrisk.com/docs/payments/buying-payments/)
2.  Understand your fees → [Reading Your Statement](https://paymentsandrisk.com/docs/operations/reading-statements/)
3.  Learn the basics → [Authorization & Capture](https://paymentsandrisk.com/docs/payments/auth-and-capture/)

**Scaling up?**

1.  Evaluate direct processing → [Processor Comparison](https://paymentsandrisk.com/docs/payments/processor-comparison/)
2.  Negotiate rates → See [Buying Payments](https://paymentsandrisk.com/docs/payments/buying-payments/)
3.  Optimize interchange → [Interchange Optimization](https://paymentsandrisk.com/docs/payments/interchange-optimization/)

**Troubleshooting?**

1.  Map your stack → Use the questions above
2.  Know who to call → Different issues go to different parties
3.  Understand the layers → Each has their own rules and timelines

* * *

## See Also

-   [Accept Payments](https://paymentsandrisk.com/docs/payments/): The payments hub
-   [Card Networks](https://paymentsandrisk.com/docs/reference/card-networks/): Visa, Mastercard, Amex, Discover rules and programs
-   [Buying Payments](https://paymentsandrisk.com/docs/payments/buying-payments/): Choosing a processor
-   [Gateway Basics](https://paymentsandrisk.com/docs/payments/reference/gateway-basics/): What gateways do
-   [Provider Types](https://paymentsandrisk.com/docs/payments/reference/provider-types/): Gateway vs ISO vs PayFac vs MoR
-   [Authorization & Capture](https://paymentsandrisk.com/docs/payments/auth-and-capture/): Transaction mechanics
-   [Settlement & Reconciliation](https://paymentsandrisk.com/docs/payments/settlement/): Money movement
-   [Interchange Optimization](https://paymentsandrisk.com/docs/payments/interchange-optimization/): Reducing fees
-   [Processor Comparison](https://paymentsandrisk.com/docs/payments/processor-comparison/): Comparing options
-   [Reading Your Statement](https://paymentsandrisk.com/docs/operations/reading-statements/): Understanding fees
-   [Processor Management](https://paymentsandrisk.com/docs/operations/processor-management/): Working with processors
-   [MATCH / TMF List](https://paymentsandrisk.com/docs/chargebacks/match-tmf/): What happens if you're terminated
