What Is a Payment Processor? How It Works and How to Choose One

A payment processor is the company that moves money between your customer's bank and yours. It authorizes the card at checkout, then settles the funds into your account days later.

Your processor also holds your merchant account, and the card networks count your disputes against it.

Across the merchant accounts on our own platform, that dispute exposure concentrates hard by processor. Every merchant I saw land in a monitoring program had been drifting for months first. A descriptor problem or a processor mismatch sat unread, then tipped past the limit at once.

Here's what a processor does, what it costs, and how your chargeback risk attaches to it.

Key takeaways

What does a payment processor do?

A payment processor is the company or service that facilitates the electronic transaction between your business and your customer's bank. It handles everything from the card swipe or checkout click through to the funds landing in your account.

Per Stripe's own explainer, that single job breaks into four distinct steps on every card sale:

1. Routes the authorization request from your checkout to the card network and the customer's bank.
2. Returns the approve-or-decline answer to your store, usually in about two seconds.
3. Batches the approved sales at the end of the day and submits them for settlement.
4. Funds your merchant account once the money clears from the customer's bank.

Each job hands off to a different company. Only the processor talks to the card network, the issuing bank, and your bank on one sale.

That's why it underwrites you, and why your merchant agreement is with them.

Step 2 on that list is the customer's bank's decision. It checks the cardholder's balance and its own fraud rules, then sends back an approve or a decline. A processor decline is either the bank's answer relayed to you or the processor's own rule firing.

That gap matters the moment a sale turns into a chargeback. The customer's bank approves the charge, and you and your processor pay for the dispute.

How payment processing works, step by step

A card sale completes in six steps across two phases, authorization at checkout and settlement a few days later:

1. Your customer enters card details at checkout and the gateway encrypts them.
2. The processor sends the authorization request to the card network.
3. The card network routes it to the customer's issuing bank.
4. The issuing bank approves or declines, and the answer travels back the same path.
5. At the end of the day, the processor batches your approved sales and submits them.
6. The acquiring bank moves the funds into your merchant account.

The two phases are separate for a reason. Authorization only puts a hold on the cardholder's credit line, so no money has moved yet.

Settlement is the batch that moves it.

So a refund you issue before the batch goes out behaves differently from one you issue after. The first one cancels a hold, and the second sends real money back once the funds have moved from the issuing bank to your merchant account.

The timeline stretches when a processor keeps part of your money under a rolling reserve. You then get paid days after the sale settles.

Payment processor vs. gateway vs. merchant account

The gateway captures the card data, the processor moves the funds, and the merchant account is where those funds land:

Vendors sell all three together behind one dashboard, so people use the words interchangeably. Each part breaks in its own way, and you call a different company each time.

Our full breakdown of payment gateway vs. payment processor covers which one sees a dispute first.

The bank side of the deal comes with its own commitments. Our guide to the merchant account walks through them.

What payment processors charge

Processor pricing comes in three shapes, and the shape matters more than the headline rate:

Every rate above is a flat-rate quote, which is one of three ways a processor can price you:

1. Flat-rate charges one blended number on every card, whatever that card costs the processor.
2. Interchange-plus passes on the true cost of each sale and adds a stated markup, as Helcim's pricing guide describes it.
3. Tiered sorts sales into qualified, mid-qualified, and non-qualified buckets, each priced its own way.

Flat-rate rolls the network's wholesale cost and the processor's markup into one number. Interchange-plus lists them out.

So two processors can quote you a similar rate, and only one of them lets you watch a cost increase happen. Our breakdown of interchange fees covers where that wholesale cost comes from.

The published rates above sit close together. The per-dispute chargeback fee and the reserve terms decide your bill, and you get both numbers from the merchant agreement or the risk team.

Every published rate also assumes a domestic, standard-risk, card-not-present sale. Three things price their own way:

1. Foreign cards, which carry cross-border and currency-conversion costs.
2. High-risk merchant category codes, which price on the category itself.
3. Keyed-in sales, which cost more because the card was never present.

A merchant marked high-risk may never get a flat-rate offer.

Why your payment processor owns your chargeback risk

Your chargebacks are scored against the merchant ID your processor issued you, so the card networks hold the processor accountable for your dispute ratio.

Card networks measure the acquirer across all its merchants at once. Your bad month raises the ratio the network fines the acquirer for.

Per NMI, acquirers set their own ratios and fees to balance the numbers across their portfolio. The number your processor enforces is often stricter than the one Visa's acquirer monitoring program publishes.

Your merchant ID is what a processor reports when it drops you, and that report is the one a merchant can't take back.

It puts them on the MATCH list, where they stay for five years, and every processor they apply to next can see it.

Run your own dispute volume through our ROI calculator to see what a rising ratio costs before your processor acts on it.

In our dataset, alerts concentrate with a few processors. About 80.9% of alerts with a recorded processor came from Stripe, and 16.6% from Shopify. Those shares track our merchant mix.

Our post on when Stripe closes an account covers how that plays out at the largest processor in that chart. The pattern is the same everywhere else.

One setup changes who the ratio belongs to. On a payment facilitator or a shared merchant account, you never get your own merchant ID. Your disputes count toward another company, and its risk tolerance becomes your limit.

How to choose a payment processor

Choose on dispute terms before the headline rate, using the four questions we call the Dispute Exposure Check:

1. Whose merchant ID is my volume under?
2. What dispute ratio does this processor enforce?
3. At that ratio, does a reserve come first or termination?
4. Does this processor pass pre-dispute alerts through?

Each answer changes what the next question means. If the answer to question 2 is the processor's own number, question 3 matters far more. A processor that terminates before it reserves makes dispute alerts worth a lot more.

The two sections below cover the criteria every comparison gives you, then the four questions above in full.

The standard criteria, and what they actually tell you

Pricing model, integration fit, payout speed, and payment methods decide your cost and build time, and all four come off a public pricing page:

1. Pricing model: Flat-rate, interchange-plus, or tiered, per the comparison above.
2. Integration fit: Whether your cart, billing, and accounting tools have a maintained connector.
3. Payout speed: How many days sit between settlement and money in your bank.
4. Supported payment methods: Wallets, local methods, and the card brands your customers carry.

Every processor comparison covers these four, and every one of them stops there.

Which processor closes your account is the question the next section answers.

The chargeback questions nobody asks in a sales demo

Ask these four before you sign, and get the answers in writing:

1. What dispute ratio triggers a review of my account? A good answer names a number and the window it's measured over.
2. Is that threshold the network's or your own? A good answer admits it's the processor's own, which is the common practice.
3. What happens first at that threshold, a reserve or termination? A good answer names a reserve policy with a percentage and a hold period.
4. Do you pass pre-dispute alerts through? A good answer names Ethoca (Mastercard) and Verifi (Visa, which operates RDR and CDRN), directly or through an approved reseller.

Send them to the processor's risk contact and ask for the ratio threshold and the reserve terms in the merchant agreement itself.

Look for a dispute API or webhook too. If the dashboard is the only place a dispute shows up, you won't know about one until someone logs in. Response windows run as short as seven days.

Question four is the one to push hardest on. You enroll in Verifi's RDR and CDRN through your processor or an approved reseller.

Without that support, you can't settle a dispute before it counts against you.

A processor can answer all four well and still close your account. The bank above it acts on its own risk.

Our guide to dispute alerts walks through how one stops a dispute before it reaches your ratio.

Major payment processors

Stripe, Shopify Payments, Square, PayPal, Adyen, and Braintree cover most merchants, split into full-stack and processor-only:

1. Stripe: Full-stack, with its own gateway, processing, and merchant account.
2. Shopify Payments: Full-stack, bundled into the store platform, and covered in our roundup of Shopify payment gateways.
3. Square: Full-stack, strongest where in-person and online sales share one account.
4. PayPal: Full-stack, and often a second checkout button rather than a primary processor.
5. Adyen: Processor and acquirer for larger volumes, with its own merchant accounts.
6. Braintree: Gateway and processing under PayPal, usually paired with a separate acquirer.

The split matters because a full-stack provider puts all three parts under one risk policy. You then get all four Dispute Exposure Check answers from a single vendor.

That works right up until the day that vendor calls your ratio a problem.

High-risk merchants usually need a specialist acquirer instead, because standard-risk providers turn those categories down at underwriting. Our guide to the high-risk merchant account covers who qualifies.

How we sourced our data

The processor-level alert figures here come from anonymized, aggregated alert data across merchants enrolled on the Chargeback.io platform.

We counted total alerts in each category, then reported them as shares of the alerts that carried a recorded processor. The figures describe our own merchant mix.

FAQ

Is Zelle a payment processor?

Zelle is a bank-to-bank transfer network for person-to-person payments, so it sits outside card processing. Those transfers carry no card-network dispute path, so a merchant paid by Zelle can't be charged back either.

Can I create my own payment processor?

You can, but it takes card network registration, a sponsoring bank, and PCI-DSS certification. Most people asking this want the payment facilitator route, which onboards sub-merchants under an existing processor's registration.

Can I switch processors while a dispute is open?

Yes, but the open dispute stays with the merchant account it was filed against and follows that account's clock. Close the old account too early and you can lose your chance to respond, so keep it open until every dispute closes.

Does using two processors lower my chargeback ratio?

Each processor scores only its own merchant ID, so you end up with two separate ratios. Spreading volume on purpose to stay under a threshold is load balancing, which most merchant agreements ban.