Comparison · Payment processing
Payment gateway versus merchant account: what each does and when you need both
Last updated 25 October 2026 · 2 sources listed · Reading time about 3 minutes
Short answer
A merchant account is the arrangement that lets you receive card funds into a bank account; a payment gateway is the software link that securely passes card details from checkout to the processor. Bundled providers hide the split, while unbundled setups give you more control and more paperwork. The right structure depends on volume, technical ability and how much you want to negotiate separately.
Who this is for: A merchant setting up online or phone sales who is confused by providers that sell the two components separately or bundle them.
What to evaluate
Who underwrites you
Whoever holds the merchant account makes the risk decision and sets hold policies.
How to check: Ask whether you will have your own merchant identifier or share a pooled one.
Gateway flexibility
A standalone gateway can route to several processors, which matters if you want redundancy or to change acquirers without rebuilding checkout.
How to check: Ask which acquirers the gateway supports and whether routing rules can be configured.
Checkout customization
Hosted pages protect you from handling card data but limit branding, while direct integration gives control with higher compliance burden.
How to check: Compare hosted, embedded and API-based options and their effect on your compliance questionnaire.
Recurring and stored payments
Subscriptions require tokenization and retry logic that not every gateway handles well.
How to check: Check whether retry schedules, card updater services and failed payment notifications are included.
Fraud screening
Online sales carry more fraud exposure than counter sales and the gateway is where screening often lives.
How to check: Ask which screening rules are built in, who tunes them, and how declines of good customers are reviewed.
Fee layering
Separate vendors mean separate fee schedules for the gateway and the processor, which can be harder to compare.
How to check: Request both schedules and add them together for a typical month of your own transactions.
Support accountability
When a payment fails, two vendors may each blame the other.
How to check: Ask who owns first-line support and how escalation between gateway and acquirer works.
Comparison
| Approach | Good when | Watch out for |
|---|---|---|
| Bundled provider | You want one contract, one dashboard and quick launch | Less leverage to negotiate and harder to switch one part |
| Standalone gateway plus merchant account | You need routing choice or custom checkout flows | Two agreements, two support lines and reconciliation across both |
| Gateway offered by your e-commerce platform | You run a hosted storefront and want little setup | Limited processor choice and platform-driven pricing |
| Gateway from your bank | You want settlement into an existing business bank account | Feature gaps in subscriptions or international payment methods |
| Direct API with acquirer | You have engineering resources and high volume | Larger compliance scope and maintenance burden |
Decision worksheet
Rate up to three options against this guide’s own criteria. It runs in your browser and saves only on this device. It is a thinking aid, not a recommendation.
1. Have you checked each criterion?
0 of 7 criteria checked.
2. Compare options (0 = fails or unknown, 3 = meets it well)
| Criterion | |||
|---|---|---|---|
| Who underwrites you | |||
| Gateway flexibility | |||
| Checkout customization | |||
| Recurring and stored payments | |||
| Fraud screening | |||
| Fee layering | |||
| Support accountability | |||
| Total (max 21) | 0 | 0 | 0 |
Questions to ask before you commit
- Is the gateway certified with my acquirer, and who maintains that certification?
- Can I move to a different acquirer without rebuilding the checkout?
- What currencies and local payment methods are supported?
- How are failed recurring payments retried and reported?
- What is the uptime commitment and how are outages communicated?
- Does the gateway tokenize cards in a way I can port?
- Who handles disputes, the gateway or the acquirer?
- Are there per-transaction fees for declined or voided attempts?
Typical trade-offs
Bundle everything with one vendor
- Upside
- Faster setup, single point of contact and simpler invoicing.
- Downside
- Switching one component means switching all of them.
Hosted payment page versus embedded fields
- Upside
- Hosted pages minimise exposure to card data and compliance effort.
- Downside
- Embedded fields offer smoother branding and conversion but need more care in implementation.
Multiple acquirers behind one gateway
- Upside
- Resilience and potential approval-rate gains through routing.
- Downside
- More operational complexity and more contracts to maintain.
Common mistakes
- Believing a gateway alone lets you collect money; without a merchant account or facilitator relationship, funds have nowhere to settle.
- Buying a gateway based on its plugin list without checking acquirer compatibility in your country.
- Skipping a sandbox test of refunds, voids and partial captures before launch.
- Assuming tokens are portable and discovering at exit that they are not.
- Ignoring the combined fee view and judging each vendor in isolation.
Related questions
Do I always need a separate gateway and merchant account?
No. Facilitator-style providers and many platform-embedded systems combine both behind a single onboarding. You only face the split when you choose an unbundled path, typically for control over acquirer choice, routing or underwriting terms. If you sell low volume through a mainstream shop platform, bundling is normally simpler. The split earns its keep at larger scale, in unusual sectors or with cross-border operations.
What does a gateway actually do during a payment?
It encrypts the card details captured at checkout, sends an authorisation request to the processor and card networks, receives an approve or decline response, and returns the outcome to your site. It also typically handles capture, void and refund instructions, and can store tokens for repeat use. It does not move money itself; settlement occurs through the acquirer and merchant account later.
Why do some gateways require a merchant account from a specific acquirer?
Each gateway must be technically certified with an acquirer's processing platform. Where certification exists, integration is smooth; where it does not, you either cannot connect or face custom work. This is why gateway marketing pages list supported processors. Before choosing either component, confirm that the pair is explicitly supported in your region, and who is responsible when an upgrade breaks the connection.
Does a hosted checkout hurt conversion?
It can, if the hosted page looks disconnected from your brand or sends customers to an unfamiliar domain, but modern hosted options are usually customizable and mobile friendly. The compliance saving is real, so the usual approach is to test both: run hosted first, then move to embedded fields only if you can demonstrate a measurable gain and have the capacity to maintain it.
How do I compare two quotes when one bundles and one splits?
Build a single sheet of your actual monthly activity: number of transactions, typical ticket, card types, refunds and disputes. Apply each quote's fixed and variable charges, including gateway, processor, statement and compliance fees. Compare the totals and then the qualitative items such as holds and exit terms. A lower total with harsher exit terms is not necessarily the better offer.
Sources and further reading
These pages were reachable when we last checked. They informed definitions and rules referred to above; they do not endorse this guide. Where rules differ by country, check the authority for your location.
- PCI Security Standards Council — PCI Security Standards Council, retrieved 27 October 2026
- Business Guidance — US Federal Trade Commission, retrieved 27 October 2026
Related guides
How to choose · Payment processing
How to choose a payment processor for a small business
Start with how you sell: in person, online, by phone or through invoices. Then compare pricing structure, settlement speed, reserve and hold policies, dispute handling, contract exit terms and how well the gateway connects to your accounting and ordering systems. Pricing is rarely the only difference; a cheap headline structure can hide holds, minimums and early termination clauses. This page covers how to evaluate, not which provider to pick.
Problems & fixes · Payment processing
Hidden costs and problem clauses in payment processing contracts
Processing contracts often look simple on the first page and shift cost into minimums, statement and compliance fees, early termination charges, equipment leases and rate-change rights buried later. Review the schedule of fees, auto-renewal, liability for chargebacks and the provider's right to alter terms. Ask for everything in writing and have a professional adviser read the agreement before you commit.
Requirements · Payment processing
Card data security requirements for merchants
Any business accepting cards must protect cardholder data under the card network security standard, validated through a questionnaire or assessment that depends on how you take payments. The less card data touches your own systems, the lighter the effort. Hosted checkout, encrypted terminals and tokenization shrink scope. Your acquirer or processor tells you which validation applies.
Requirements · Banking and personal finance
What to expect when switching your current account to another provider
Switching is mostly an exercise in moving recurring payments and income without a gap. Where an official switching service exists, the new provider coordinates the transfer; elsewhere you move payments manually. Prepare by listing every incoming and outgoing payment, keep the old account open during a overlap period, and check closure terms. Rules and guarantees differ by country, so confirm with your regulator.
Comparison · Business banking
Traditional bank versus fintech account for a business
Traditional banks usually offer broader services, direct deposit protection, cash handling and lending relationships, at the cost of slower onboarding and clunkier digital tools. Fintech providers offer speed, integrations and spending controls, but may rely on partner banks, have narrower product sets and different protection arrangements. Many businesses use both for different jobs.
Comparison · Procurement and suppliers
Competitive tender versus framework agreements versus spot buying
Tenders suit large, complex or high-value purchases where transparency and competition matter. Framework agreements pre-qualify suppliers and agree terms so individual orders are quicker. Spot buying suits low-value or urgent needs but can lack leverage and control. Choose by value, complexity, frequency, legal rules and the need for supplier relationships, and keep records for accountability.
Requirements · Business banking
What you need to open a business bank account
Banks typically need proof of the business's legal existence, identification and address for owners and controllers, a description of activity and expected transactions, and tax registration details. Requirements vary by country, structure and risk level. Gather formation documents, ownership information and a clear business explanation in advance, and ask the bank for its exact checklist.