Skip to content

Payment processor vs payment gateway vs acquirer vs PSP: what is the difference?

A gateway carries card data, a processor moves messages, an acquirer settles funds, and a PSP bundles them. See who does what and which setup fits.

A payment gateway carries card details from checkout to the payment system. A payment processor moves the authorization, clearing and settlement messages. An acquirer is the licensed institution that accepts the card payment for you and settles funds. A payment service provider (PSP) bundles several of these behind one contract.

This guide is current as of November 2026. Vendors bundle roles and use the words inconsistently, so it ends with five questions that show what a vendor really covers. Start with the pillar, what is a payment processor, if the basics are new.

Key takeaways

  • Roles and companies are different things. One company can be gateway, processor and acquirer at once.
  • The issuer, not the gateway or processor, approves or declines the payment.
  • A PSP is a bundle. A payment facilitator lets you accept cards without your own merchant account.
  • Start with a PSP, add a direct acquirer when card volume in one market is large enough to negotiate, and use more than one provider when an outage would stop sales.
  • Five vendor questions reveal who holds your funds, who is liable and who you actually contract with.

Quick comparison table

This table shows the main job of each role and who you usually contract with. Licensing differs by country, so the licence column describes the common pattern, not a rule.

RoleMain jobHolds a licence to settle fundsWho you contract with
Payment gatewaySecurely carries payment data from checkout to the processor or acquirerUsually noA PSP, or a standalone gateway vendor
Payment processorRelays authorization, clearing and settlement messagesUsually no, unless it is also the acquirerAn acquirer, a PSP, or directly in large setups
AcquirerAccepts card payments for the merchant and settles fundsYes, as a bank or licensed institutionYou, or a PSP on your behalf
IssuerIssues cards and approves or declines each paymentYes, as a bank or licensed institutionThe cardholder
PSPBundles gateway, processing, risk tools and settlementVaries: some hold licences, others buy acquiringYou
Payment facilitatorOnboards you as a sub-merchant under its master merchant accountVaries by market, it relies on an acquirerYou
Payment orchestration platformRoutes payments across several providersUsually noYou
Merchant accountThe account that receives your card proceedsNot a licence, an account typeAn acquirer or a facilitator

What does a payment gateway do?

A payment gateway is the technology that securely sends transaction data between the customer and the acquirer. Adyen's knowledge hub describes it as a component of a PSP (Adyen). Global Payments' developer docs say the same: a technology service that simplifies sending payments between a merchant and an acquirer (Global Payments developer docs).

Think of it as the card reader of the internet. It encrypts details, forwards the request and returns the answer. It does not decide anything. Many gateways also host the payment form, which keeps raw card data off your servers.

What does a payment processor do?

A payment processor relays authorization and clearing messages between the acquirer, the card network and the issuer. PaymentBrief says "processor" is one of the most overloaded words in payments because contracts blur it with the acquirer or the PSP (PaymentBrief).

Follow one illustrative $50 sale. The customer pays, the gateway passes the request on, and the processor carries it through the card network to the issuer. When the merchant captures the sale, the processor sends the clearing details. Later it passes the settlement instructions so funds move to the merchant. See a card payment step by step, with fees and declines for the timing of each stage.

What does an acquirer do?

An acquirer is the bank or licensed institution that accepts card payments for a merchant and settles the funds to it. Adyen describes the acquirer as the financial institution that holds the merchant's bank account and processes card payments, and notes that some modern PSPs can also act as acquirers (Adyen).

In the same $50 walk-through, the acquirer receives the money from the card network and pays the merchant, net of fees. Acquiring is a regulated activity. In the European Union, the revised Payment Services Directive (PSD2) lists acquiring of payment transactions among the regulated payment services, so the institution needs authorization (Directive (EU) 2015/2366). Rules differ by country, so check the licence of whoever settles your funds.

What is a PSP and how is it different?

A payment service provider (PSP) bundles a gateway, payment processing and usually settlement and risk tools into one offering with one contract. Adyen describes a PSP as an all-in-one partner that helps businesses accept electronic payments. PaymentBrief describes the bundle as gateway, processing and acquiring access under one contract.

The difference from a gateway or processor is scope. Those are single roles. A PSP is a package. A related model is the payment facilitator, which Global Payments describes as a provider that lets merchants operate as sub-merchants under a master account. The next post in this cluster compares that model with a merchant of record: merchant of record vs payment facilitator.

Do you need a merchant account?

You need some way to receive card proceeds, but you do not always need your own merchant account. A merchant account is the account that holds card payments before they reach your bank. Under a payment facilitator you accept cards as a sub-merchant, so you skip your own account and its underwriting.

Dedicated merchant accounts come with their own underwriting. They suit larger volume, custom pricing or special risk profiles. A PSP that uses aggregated accounts is faster to start, while a dedicated account gives you more control over terms. Choose the lighter route first, and move to a dedicated account when volume justifies the negotiation.

The trade-off shows up in three places:

  1. Onboarding time. A sub-merchant account under an aggregated PSP can often go live after a short application. A dedicated account goes through full underwriting, which reviews your business model, processing history and financials before approval.
  2. Holds and reserves. Aggregated accounts are underwritten as a pool, so the provider may hold funds or pause payouts when your activity looks unusual. A dedicated account sets reserve terms in the contract, which you can read and negotiate up front.
  3. Pricing. Aggregated accounts usually come with a blended rate. A dedicated account is where interchange-plus pricing and volume discounts become possible.

Which setup fits which business?

The right setup depends on volume, markets and tolerance for downtime. Use this decision list.

  1. Start with a PSP. One contract, one integration, fast onboarding. This fits most new merchants.
  2. Add a direct acquirer when card volume in one market is large enough to negotiate your own rates and terms.
  3. Use more than one provider when an outage would stop sales. Routing across providers is called payment orchestration, and payment orchestration vs payment gateway explains how it differs from a gateway.
  4. Keep non-card flows separate. Bank transfers and cross-border payouts run on other rails and need other providers.

Five questions to ask any vendor

Five questions reveal what a vendor covers, whatever it calls itself.

  1. Who is the acquirer on my transactions, and who holds the licence?
  2. Who do I sign the contract with, and who is liable if funds go missing?
  3. Do funds sit in my account or in a master account, and for how long?
  4. Who handles chargebacks, fraud screening and the card scheme monitoring programs?
  5. Which parts can I replace without rebuilding the integration?

Write the answers down. Two vendors that both say "processor" can answer these very differently. Keep a copy with the contract. If a vendor cannot answer in writing, treat the gap as a risk, because disputes and settlement problems are settled by the contract, not by the label on the sales page.

Where BlindPay fits

BlindPay is none of the card roles above. It is not a gateway, acquirer or PSP for card acceptance. It is payments infrastructure for cross-border payouts and collections over bank rails, turning USDC and USDT into local-currency payouts over Pix, SPEI, ACH, RTP, SEPA and SWIFT (POBO/COBO), and collecting local currency into stablecoins. Teams use it beside any card stack to pay sellers, contractors and suppliers abroad. BlindPay also offers card payins, a USD card charge delivered as stablecoins, which keeps card entry in an isolated frame; see the card payin docs.

Methodology and sources

Checked in November 2026. Definitions paraphrase the sources below. No fee or rate figures are used on this page.

This article is for general information only and is not legal, tax, or compliance 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.