Skip to content

Merchant acquirer vs payment processor vs payment gateway vs PSP: what each one does

An acquirer holds the merchant account, a processor runs the transaction, a gateway captures card data and a PSP bundles them. See which you need.

An acquirer holds the merchant account and settles funds with the card networks. A processor handles the technical transaction flow for the acquirer or PSP. A gateway captures and secures card data and routes it onward. A payment service provider (PSP) bundles some or all of these into one contract.

This guide explains each role, how they fit together in one payment and which contract you need, as of November 2026. BlindPay publishes this guide.

Key takeaways

  • Only the acquirer is a licensed financial institution that stands behind the merchant with the card networks. Processors and gateways are technology and service layers.
  • Visa states that the acquirer remains responsible for sellers and for any entities operating between the acquirer and the seller.
  • One provider can fill every role. Stripe's own explainer says it acts as both processor and acquirer, with an integrated gateway, so no separate merchant account is needed.
  • A payment facilitator (a type of PSP) signs sellers up on an acquirer's behalf and receives their settlement. Visa requires the facilitator to partner with an acquirer, and a seller that grows past a volume threshold must be added to the acquirer's agreement.
  • Which setup you need depends on volume, channel (online or in person) and how much control over pricing and risk you want. Most businesses start with a PSP.

What does a merchant acquirer do?

A merchant acquirer holds your merchant account, sends your card transactions to the card networks and settles the money to you. It also carries the financial risk if a transaction is later reversed, which is why it underwrites each merchant before approving it.

Stripe's explainer describes the acquirer as a financial institution that partners with businesses to process card transactions, maintains merchant accounts and handles settlement with issuing banks, and it assigns the risk of chargebacks, fraud and disputes to the acquirer (Stripe, "Payment processor vs merchant acquirer", last updated April 25, 2025). The pillar guide to merchant acquiring covers the full flow.

For Visa and Mastercard, a Federal Reserve Bank of Philadelphia paper defines the acquirer as the member financial institution responsible for its merchant customers' transactions with the network (Philadelphia Fed, October 2007). That paper is old, but the structure it describes still holds.

What does a payment processor do?

A payment processor handles the technical side of a transaction: it passes authorization requests and responses between the merchant side and the acquirer or network, and it handles the data for clearing and funding. Think of it as the plumbing, not the licence.

Visa's guidance describes third-party servicers that acquirers hire for payment or gateway processing, host and data center management, back-office reconciliation and fraud monitoring. These firms may handle Visa transaction data, but under Visa's rules they do not take on the acquirer's responsibilities. The acquirer keeps the responsibility (Visa, "Beyond the Acquirer", February 15, 2024).

Because processors often work for the acquirer, many merchants never contract with one directly. The Philadelphia Fed paper adds that some third-party firms offer such a broad scope of services that people call them acquirers, but the network member institution remains ultimately responsible.

What does a payment gateway do?

A payment gateway captures card details at checkout, encrypts them and forwards the transaction for authorization. It is the online counterpart of the card terminal on a shop counter.

Stripe's explainer describes its integrated gateway as the component that securely captures transaction details and sends them on to its processing infrastructure. Visa lists payment gateway processing among the services sellers can buy from third-party agents, separately from their acquirer, and says sellers must tell their acquirer about those providers.

A gateway does not hold funds, settle with networks or carry chargeback risk. If your question is how a gateway differs from a payment orchestration layer, see payment orchestration vs payment gateway.

What is a payment service provider (PSP)?

A PSP is a company that offers merchants a bundle of payment services under one contract, typically a gateway, processing and a way to get paid, without the merchant needing its own acquirer contract. A payment facilitator is a PSP that formally signs sellers on behalf of an acquirer.

Visa's definition is precise: a payment facilitator, also called a master merchant or merchant aggregator, is a third-party agent that can sign a merchant acceptance agreement with a seller on behalf of an acquirer and receive settlement proceeds from the acquirer on behalf of the seller. Sellers under it are sub-merchants. Visa adds that facilitators must partner with an acquirer that meets its minimum equity requirements, and that Visa's requirements apply equally to a sponsored merchant as if it contracted directly with an acquirer.

Stripe's payfac guide says the same thing in plain terms: if a sub-merchant exceeds a certain threshold of transaction volume, it must sign a direct merchant agreement with the acquiring bank (Stripe, "Payment facilitators", undated). For the merchant side of that decision, read merchant account vs payment facilitator.

How do the four work together in one transaction?

The customer pays through the PSP's checkout, the gateway sends the data to the processor, the processor takes it to the acquirer, the acquirer routes it through the card network to the issuer, and the approval returns along the same path.

Here is the path of one online sale:

  1. Customer to merchant. The customer enters card details on the checkout page.
  2. Gateway. The gateway encrypts the card data and sends an authorization request.
  3. Processor. The processor formats and forwards the request to the acquirer or network.
  4. Acquirer and network. The acquirer routes the request through the card network to the issuer, the cardholder's bank.
  5. Issuer. The issuer approves or declines, and the answer travels back to the checkout in seconds.
  6. Settlement later. The acquirer settles funds with the network and pays the merchant, or pays the PSP, which pays the merchant.

When one provider plays all four roles, steps 2 to 4 happen inside the same company, but the functions are still distinct. How the money then moves is explained in how a card payment works: authorization, clearing and settlement.

RoleWhat it doesWho holds the riskWhen you contract with it directly
AcquirerHolds the merchant account, settles with the networksCarries financial and chargeback risk toward the networksWhen you have a direct merchant account, usually at higher volume
ProcessorRuns the technical transaction flowOperational risk of the service; the acquirer keeps the financial responsibilityRarely on its own; often chosen by the acquirer or sold inside a bundle
GatewayCaptures and encrypts card data, routes itNone for funds or chargebacksWhen you build your own checkout or want a gateway separate from your acquirer
PSP or payment facilitatorBundles gateway, processing and often acquiring accessTakes on sub-merchant risk toward its acquirer and usually passes it on to youMost small and mid-size online businesses

Do I need all four, or can one provider cover them?

You do not need to sign four contracts. One provider can cover all four roles, and many do. Large merchants sometimes unbundle them to negotiate each layer separately.

Stripe's explainer says it acts as both a payment processor and an acquirer, with a built-in gateway, so a business does not need a separate acquirer or merchant account. Visa notes that a single service provider may play the role of multiple entities in its ecosystem, as long as it meets the obligations of each role.

Unbundling can lower cost or add control: you can pick an acquirer for rates, a gateway for features and a processor for routing. But you take on integration, reconciliation and contract management. The trade-off between a bundled PSP and separate components is part of how to choose a merchant acquirer.

Who carries chargeback and fraud risk?

The acquirer carries the financial risk toward the card networks. If you use a PSP, your contract usually makes you responsible to the PSP, which covers the acquirer.

Visa says the acquirer remains responsible for the acts and obligations of sellers and of any other entities operating between the acquirer and the seller. Stripe's explainer assigns the risk of chargebacks, fraud and disputes to the acquirer. In a facilitator model, the sub-merchant owns the customer relationship, including refunds and disputes. Visa's document describes the merchant as the party that handles refunds and disputes with the customer.

Read your agreement for who repays a disputed amount, what fees apply per dispute and whether the provider may hold funds. Those terms vary and are not set by one rule. For the network ratios that trigger penalties, see the series guide on chargebacks, ratios, VAMP and ECM.

Does the setup change for online versus in-person payments?

The roles stay the same, but the technology changes. Online, a gateway or hosted checkout captures the card data. In person, a terminal reads the card and connects to a processor or acquirer host, and the terminal vendor often acts as the gateway.

Visa's document notes that payment facilitators may also provide point of sale infrastructure and process transactions through a gateway link between the acquirer and the seller. That is why one vendor can sell you a terminal, a checkout, processing and a merchant account in one agreement.

A card-not-present payment, meaning the physical card is not read, usually costs more in interchange than a card-present one. Visa's table effective October 24, 2026 lists 1.43% + $0.10 for a basic consumer credit card in person and 1.89% + $0.10 online (Visa USA interchange table). That difference does not depend on which of the four providers you use.

How do I pick the right setup?

Match the setup to your volume, channels and need for control. Use this decision list:

  • If you are starting out or selling online with modest volume, you probably need a PSP or payment facilitator. It gives you gateway, processing and a merchant relationship in one contract. See merchant account vs payment facilitator.
  • If you have large, steady card volume, you probably need a direct acquirer relationship. Ask for an interchange-plus quote and compare it with your PSP's all-in rate.
  • If you sell in several countries, you probably need local acquiring or more than one provider. Authorization and costs vary by market.
  • If you need custom checkout or routing, you probably need a standalone gateway or an orchestration layer. The gateway captures the data and routes it to the acquirers you choose.
  • If you run a platform that pays out sellers, you probably need a facilitator model or a partner that offers one, plus a way to pay out across borders.

BlindPay is none of the four: it is the cross-border payout, collection and stablecoin settlement layer that works alongside your acquirer or PSP.

For the same roles told from the processor side, see payment processor vs payment gateway and issuer, acquirer, card network, processor, gateway and PSP roles.

Methodology and sources

All sources were read in November 2026.

What to do next

Read merchant account vs payment facilitator to decide which contract fits your business, then how to choose a merchant acquirer for the questions to ask.

This article is general information, not legal, tax, or financial advice.

FAQ

One API.
Multiple payment rails.

Blind Pay, Inc. (“BlindPay”) is a United States-based financial technology and payments infrastructure company, incorporated in the State of Delaware on May 2, 2024. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000277566153. BlindPay is not a state-licensed money transmitter and does not, in its own capacity, engage in regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial institution partners. BlindPay's role is limited to providing financial technology, virtual account management, payment processing, and related payments infrastructure services that facilitate payment flows and account functionalities. These services are provided in coordination with its licensed partners and in compliance with applicable federal MSB requirements and relevant state regulatory frameworks.

Blind Pay, LLC (“BlindPay”) is a Delaware limited liability company formed on June 24, 2025. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000318334247 and is listed in the Nationwide Multistate Licensing System (“NMLS”) under NMLS ID #2745309.

BLIND PAY SOCIEDADE PRESTADORA DE SERVIÇOS DE ATIVOS VIRTUAIS LTDA. (“BlindPay”) is a Virtual Asset Service Provider (“VASP”) operating in Brazil. The company is presently completing the regulatory adaptation process required of Virtual Asset Service Provider Companies (SPSAV) under Central Bank of Brazil Resolution No. 520/2025, and remains subject to the transitional regime set forth in Article 88 of that Resolution. Registered address: Avenida Princesa Isabel, nº 15, Sala 1405, Edifício Martinho de Freitas, Centro, Vitória/ES, 29010-361.

BlindPay is a stablecoin API that enables individuals and businesses to move money worldwide.