A payment gateway is the technology that captures card details at checkout, encrypts them and sends them on for approval. A payment processor is the company that moves the transaction between your acquiring bank and the card networks, returns the approve or decline, and handles clearing and settlement. The gateway is the front door. The processor is the plumbing behind it.
For a high-risk business the difference matters: the gateway shapes your PCI workload, fraud controls and recurring billing, while the processor and bank decide whether you get approved at all. Apply free with Paymotile to be matched with processors and banks that accept your industry.
What is a payment gateway?
A payment gateway is software that sits between your checkout (website, app, virtual terminal or card reader) and your processor. It collects the card data, encrypts it, formats the authorization request, sends it to the processor and returns the answer to your checkout in a few seconds. Many gateways also store cards as tokens for repeat billing.
Common gateway functions include:
- Hosted payment pages, embedded fields (iframes) or an API.
- Tokenization, which swaps the card number for a reference value you can store and charge later.
- Recurring billing, retries and card updates.
- Fraud filters such as AVS, CVV and velocity rules.
- 3-D Secure authentication requests to the card issuer.
Card network rules do not treat a gateway as a bank. A gateway provider usually falls under what Visa’s rules call a Third Party Agent: an entity that provides payment-related services, directly or indirectly, to a member bank or its merchants, and that the bank generally must register with Visa (Visa Core Rules).
What is a payment processor?
A payment processor is the company that routes your card transactions to the card networks and the issuing bank, carries back the approval or decline, and handles the clearing and settlement that put money in your bank account. The processor works for, or on behalf of, an acquiring bank, which is the bank that legally sponsors your merchant account.
Federal Reserve Regulation II gives a plain legal definition. A processor is “a person that processes or routes electronic debit transactions for issuers, acquirers, or merchants.” The same rule separates the processor from the acquirer: an acquirer contracts with the merchant to provide settlement, and “does not include a person that acts only as a processor” (12 CFR 235.2). The rule covers debit transactions, but it shows how the legal roles are separated.
The processor is usually the company on your merchant statement: it underwrites with the bank, prices your account, holds any reserve and pays you. Our guide to what a merchant account is explains the bank side.
What is the difference between a payment gateway and a payment processor?
The gateway captures and transmits payment data. The processor moves the transaction through the card networks and settles the funds. You can change gateways without changing banks, but you cannot accept cards without a processor and acquiring bank. Gateway choice mostly affects checkout, fraud tools and PCI scope. Processor choice affects approval, pricing, reserves and payouts.
| Question | Payment gateway | Payment processor |
|---|---|---|
| Main role | Captures, encrypts and transmits card data from your checkout | Routes transactions to the networks and issuer, then clears and settles funds |
| Who you contract with | The gateway company (sometimes bundled with the processor) | The processor and its sponsoring acquiring bank, under a merchant agreement |
| What it touches | Raw card data at checkout, tokens, authorization requests | Authorization messages, clearing records, settlement funds, disputes |
| Typical fees | Monthly gateway fee and a per-transaction fee, set by the gateway | A percentage of each sale plus per-item and account fees, plus any reserve |
| PCI DSS scope | Hosted pages and tokenization can shrink your scope a lot | The processor is in scope for its own systems; your bank sets how you validate |
| Decides if you are approved? | Can refuse your industry under its own terms | Yes, together with the acquiring bank’s underwriting |
For a full breakdown of processor and bank pricing, see our guide to merchant account fees.
How does a card payment flow through the gateway, processor, network, acquirer and issuer?
A card payment moves in four stages: authentication (optional, through 3-D Secure), authorization, clearing and settlement. The gateway sends the request, the processor and acquirer pass it to the card network, the network routes it to the cardholder’s issuing bank, and the issuer approves or declines. Later, funds move from the issuer to the acquirer and then to you.
- Checkout. The customer enters card details on a page or form served by your gateway.
- Authentication (if used). The gateway can start a 3-D Secure check. Visa describes the issuer using an access control server to assess risk and authenticate the cardholder (Visa).
- Authorization and response. The gateway sends the request to your processor, which passes it into the card network for your acquiring bank; the answer comes back the same way. Visa defines authorization as the process where the issuer, its processor, or Visa’s stand-in processing approves a transaction (Visa Core Rules).
- Clearing. Your processor submits the approved sales in a batch. Visa describes clearing as the stage where payment details are exchanged between the acquirer, issuer and card network (Visa).
- Settlement. Funds move from the issuer to the acquirer, and the acquirer (through the processor) pays you, minus fees and any reserve.
| Party | Who it works for | Job in the transaction |
|---|---|---|
| Payment gateway | The merchant | Captures and sends card data, returns the response |
| Payment processor | The acquiring bank and merchant | Routes authorizations, submits clearing, delivers deposits |
| Acquiring bank (acquirer) | The merchant | Signs the merchant and enters its transactions into the network |
| Card network (Visa, Mastercard) | Its member banks | Sets the rules and routes data between acquirer and issuer |
| Issuing bank (issuer) | The cardholder | Authenticates the cardholder, approves or declines, pays the acquirer |
Visa defines the acquirer as the member that “signs a Merchant or Payment Facilitator” and enters its transactions into interchange (Visa Core Rules).
What is a third-party payment processor or payment facilitator?
A third-party payment processor, often called a payment facilitator, signs up many small merchants under its own master merchant account instead of giving each one its own account. Visa calls these merchants Sponsored Merchants. Setup is fast, but the facilitator controls your funds and can close you quickly. In bank supervision, the term means something slightly different.
Visa defines a Payment Facilitator as an entity that contracts with an acquirer to deposit transactions or receive settlement on behalf of a Sponsored Merchant. Under the current Visa rules (October 2026 edition), the acquirer must sign a direct merchant agreement with a sponsored merchant that exceeds USD 1 million in annual transaction volume (existing sponsored merchants get up to 2 years), subject to limited exceptions. If a facilitator is considered high-integrity risk, its acquirer must register it with Visa as a High-Integrity Risk Payment Facilitator (Visa Core Rules).
Bank regulators use “third-party payment processor” more broadly. The FDIC’s Guidance on Payment Processor Relationships, last amended February 3, 2026, describes processors as bank deposit customers that process payments for merchant clients, often by originating ACH debits or remotely created checks. Banks are told to review a processor’s merchant onboarding, check whether it resells through sales organizations or gateway arrangements, verify its merchants and watch for high return or chargeback rates (FDIC). The February 2026 amendment removed references to reputation risk.
If an aggregator already closed your account, read what to do when Stripe, PayPal or Square closes your account.
How does gateway choice affect PCI DSS scope?
PCI DSS v4.0.1 is the current card data security standard. The less card data your own systems touch, the smaller your compliance job. A redirect to a hosted payment page, or an embedded payment form served by a PCI DSS compliant provider, can qualify an e-commerce merchant for SAQ A, the shortest self-assessment questionnaire.
The PCI Security Standards Council lists v4.0.1 as the current PCI DSS version in its document library (PCI SSC). In February 2025 the Council explained a new SAQ A eligibility criterion: the merchant must confirm its site “is not susceptible to attacks from scripts.” The criterion applies only to merchants whose page embeds a provider’s payment form (for example, an iframe). It does not apply when the page redirects customers to the provider. Merchants can confirm it with script controls like those in Requirements 6.4.3 and 11.6.1, or with written confirmation from a PCI DSS compliant provider that its embedded form includes script-attack protection (PCI SSC).
What to look for in a gateway:
- Hosted payment page or hosted fields, so card numbers never hit your server.
- Tokenization, so you store a token for rebills instead of the card number.
- Written confirmation of the provider’s PCI DSS compliance and of any script protection on embedded forms.
Your acquiring bank decides which questionnaire you file, so confirm it with the bank.
What do high-risk merchants need from a payment gateway?
High-risk merchants need a gateway that the acquiring bank supports and that brings strong recurring billing, control over the billing descriptor, 3-D Secure, configurable fraud filters and, where the bank approves it, separate merchant IDs (MIDs) for each product line. Fraud tools and 3-D Secure cut chargebacks, and bank-approved MIDs keep each product line on the right account.
| Gateway feature | Why it matters for high-risk |
|---|---|
| Recurring billing and card updater | Subscriptions, memberships and auto-ship need clean rebills, retries and clear cancellation handling |
| Billing descriptor control | Visa requires the merchant name used in receipts, authorizations and clearing records to match the name customers know you by (Visa Core Rules); an unfamiliar descriptor invites “I don’t recognize this” disputes |
| 3-D Secure (EMV 3DS) | Issuer authentication can shift liability for authenticated or attempted-authentication transactions (Visa) |
| Fraud filters | AVS, CVV, velocity, BIN and geography rules cut card testing and stolen-card sales |
| Separate MIDs by product line | Lets you keep each product line on its own merchant account, where your bank approves it. MIDs are not a way to spread disputes across accounts: Visa can disqualify high-integrity risk merchants that try to get around its programs (Visa Core Rules) |
Fraud and dispute counts are measured against your merchant account. Since April 1, 2026, Visa labels a US merchant “Excessive” at a VAMP ratio of 1.5% with at least 1,500 fraud reports and disputes in a month (Visa). Our VAMP guide and chargeback prevention page cover how to stay under it. Subscription sellers can see our subscription merchant account guide, and adult merchants the adult payment gateway section.
Why do some payment gateways refuse high-risk industries?
Gateways and facilitators restrict high-risk industries because they carry the risk their merchants create. Card network rules add monitoring, registration and possible disqualification for high-integrity risk merchants. Banks are expected to vet the processors and merchants they serve. Many all-in-one platforms simply choose not to take on that work, so they ban whole categories.
Visa’s rules show the extra load. For a High-Integrity Risk Merchant, the acquirer must track daily sales volume, average ticket, receipts and disputes, compare activity to normal levels at least daily, and hand Visa the original underwriting package within 7 calendar days on request. Visa may also impose extra security or authentication requirements and can disqualify a merchant that reaches a critical level of disputes (Visa Core Rules). Bank regulators also expect banks to watch the payment processors they serve for high return and chargeback rates (FDIC), which adds to the caution many platforms show.
Gateways that work with high-risk acquiring banks accept these categories because the bank has already underwritten the merchant. So get approved for a merchant account first, then connect a gateway your bank supports.
How do I get a gateway and processor for a high-risk business?
Apply for a high-risk merchant account first, because the acquiring bank’s approval decides which gateways you can use. With Paymotile, the process is a website review, a written offer, then gateway setup. Typical approval takes about 5 to 10 business days once your application is complete, and applying is free.
- Prepare your website. Clear pricing, refund and cancellation terms, and contact details.
- Apply. Submit the free application or call (888) 542-4147. Paymotile reviews your site and matches you with processors and banks that accept your industry.
- Review the written offer. Typical high-risk rates run 3.25% to 3.99%, and rolling reserves are often 5% to 10%, held about 90 to 180 days. Our reserve guide explains how holds work.
- Set up the gateway. Connect a gateway your bank supports, turn on tokenization, 3-D Secure and fraud filters, and set your descriptor.
- Go live. Run test transactions, confirm deposits and monitor disputes from day one.
For more on comparing offers, see how to choose a high-risk merchant account provider or start at our high-risk credit card processing hub.
Payment gateway vs payment processor FAQ
Do I need both a payment gateway and a payment processor?
To take cards online, yes. The gateway captures and sends the card data, and the processor with its acquiring bank authorizes, clears and settles the sale. Some companies bundle both.
Is Stripe or PayPal a payment gateway or a payment processor?
Platforms such as Stripe and PayPal bundle the gateway and the processing in one account, so you do not choose them separately. Their own terms decide whether your industry is allowed.
Can I switch payment gateways without changing my merchant account?
Often, yes, if your processor supports the new gateway. Ask both sides how saved card tokens move before you switch.
Who handles chargebacks, the gateway or the processor?
The processor and acquiring bank. Disputes come from the issuer through the card network to your acquirer, and your processor notifies you and takes the response. Gateway fraud tools help prevent them. See what a chargeback is.
What is a third-party payment processor in banking?
In FDIC guidance, it is a bank customer that processes payments for other merchants, often through ACH debits or remotely created checks. FDIC guidance expects banks to vet these processors and watch their merchants’ return and chargeback rates.
Ready to set up processing? Apply free with Paymotile or call (888) 542-4147.
Sources
Statistics and legal references in this guide come from the sources below. We review them regularly and update the page when newer data is published.
- Visa, Visa Core Rules and Visa Product and Service Rules (October 24, 2026).
- Visa, Visa Acquirer Monitoring Program Overview (May 2025).
- Visa, 3D Secure: Your Guide to Safer Transactions (updated November 2025 or later, accessed November 2026).
- Board of Governors of the Federal Reserve System, Regulation II, 12 CFR 235.2 Definitions (current eCFR text).
- Federal Deposit Insurance Corporation, Guidance on Payment Processor Relationships (FIL-127-2008, revised July 2014 and February 2026) (February 3, 2026).
- PCI Security Standards Council, FAQ Clarifies New SAQ A Eligibility Criteria for E-Commerce Merchants (February 28, 2025).
- PCI Security Standards Council, Document Library: PCI DSS v4.0.1 (accessed November 2026).