Payment Gateway vs Plugin: What Each One Does in Your Shop

A shop owner wrapping a ceramic mug at a packing table beside a closed laptop and shipping boxes.

A payment gateway is a service that authorizes the sale and moves payment data. A plugin is software installed in your shop that connects checkout to that service. You always need a gateway. You need a plugin only when your shop platform has no built-in connection to it. Choose the gateway first, because it decides your fees, your compliance burden and who holds the money.

TL;DR:

  • A payment gateway is a hosted service that authorizes a payment and reports the result. A plugin is code inside your shop that talks to it.
  • A plugin never holds money. It passes an order total to a gateway and listens for approved or declined.
  • Choose the gateway first. It sets your fees, your PCI DSS scope and whether a merchant account is involved.
  • A plugin that collects card numbers on your own pages can become your compliance problem, so prefer hosted or redirect checkout.
  • With self-hosted BTCPay Server, the gateway is software you own, so there is no processor or merchant account.

Table of Contents

Payment Gateway vs Plugin: A Service on One Side, Code on the Other

A payment gateway lives on someone else's servers (or your own, in the bitcoin case). It receives payment details or a payment request, checks it, sends it to the right network, and returns a result. A plugin lives inside your shop. It adds a payment option to checkout, sends the order total to the gateway, and marks the order paid when the gateway says so.

A gateway's purpose is to connect your checkout to the financial network, so your shop never has to speak to banks or card schemes directly. It also keeps sensitive data out of your own database where possible.

The two get confused because a shop's admin panel shows both as one line item, "Add a payment method," and plugin authors often name the plugin after the gateway. You can swap a plugin without changing gateways (a different connector for the same service), and you can swap gateways while keeping the same shop.

A plugin never touches money. It passes an order total to a gateway and listens for a yes or no.

Some platforms skip the plugin step because the connection is built in. Others, like Shopify, have their own rules for how external payment methods attach, which is covered in our guide to Shopify integration for bitcoin. The rest of this article stays on the general distinction.

What a Payment Gateway Does, and How It Differs From a Processor

A gateway handles the conversation. A processor handles the settlement. When a customer clicks pay, the gateway encrypts and forwards the request. The processor routes it to the card network and the issuing bank, gets the authorization, and later moves the funds to your bank.

So that is the answer to "what is the difference between a payment processor and a payment gateway?" The gateway is the front door and messenger. The processor is the back office that moves money between banks.

In practice the lines blur:

  • Bundled providers. Many companies sell gateway, processor and merchant account as one package, so you never see the seams. You sign one agreement and pay one blended rate.
  • Separate providers. Larger merchants often contract a gateway and a processor independently to negotiate rates or to route traffic across several processors.
  • Self-hosted gateways. In the bitcoin case, there is no card network and no bank to settle with. The gateway watches the blockchain, and settlement is the transaction itself.

Fees show why this matters. Take a hypothetical bundled rate of 2.9% plus $0.30 per card sale. A $50 order costs you $1.75. Over 400 orders a month at that size, that is $700, and the plugin you chose has no influence over it. The gateway contract does.

What a Plugin Does, and When It Quietly Becomes the Gateway

A plugin is an extension for a specific platform: WooCommerce, Magento, PrestaShop, Drupal Commerce and so on. It shows the payment option at checkout, creates the payment request, receives the gateway's confirmation (usually through a webhook), and updates the order status. Our WooCommerce setup guide walks through where that sits in a real store, and the Magento 2 plugin buyer's guide covers what to check before installing one there.

The risk is in how the plugin collects payment details. There are three common patterns:

  • Redirect checkout. The customer leaves your shop and pays on the gateway's page. Your shop never sees card data, which keeps you in the lightest PCI category.
  • Embedded fields. The gateway's form is loaded inside your checkout page. Card data goes straight to the gateway, though your page still influences the form.
  • Direct post or native form. The plugin collects card numbers on your own server and forwards them. Now your shop is handling card data.

The PCI Security Standards Council defines self-assessment questionnaires for each pattern. Fully outsourced checkouts generally fall under SAQ A, sites whose pages can affect the payment form under SAQ A-EP, and merchants who handle card data themselves under SAQ D, which is far longer. A plugin marketed as "simple to install" can move you from the first category to the last.

Pro Tip: Before you install any payment plugin, open its checkout in a private browser window and look at the address bar and page source. If the card fields sit on your own domain and not inside an iframe or on a redirected page, you have just learned your PCI scope is larger than the plugin's marketing page suggested.

Merchant Accounts and Merchant Transactions: Where PayPal Fits

A merchant transaction is a sale between you, the merchant, and a customer that is authorized, captured and settled against your business. It starts with an authorization request, ends with funds arriving in your account, and leaves a record you can refund or dispute. In card network language, "merchant-initiated transaction" has a narrower meaning: a charge you start without the customer present, such as a subscription renewal.

A merchant account is a settlement account, held through an acquiring bank, that receives card funds for your business. It is separate from a gateway. The gateway sends the request, and the merchant account is where the approved money lands.

Is PayPal considered a merchant account? No. PayPal works as a payment facilitator: you get a PayPal business account, and your sales settle into that balance rather than into a dedicated merchant account under your own business ID. Onboarding is quick, but you accept the provider's own rules about holds, reserves and account reviews.

Gateway, Plugin, Processor, Merchant Account: Side by Side

Piece What it is Where it lives Who controls it What goes wrong
Payment gateway Service that authorizes and reports payments Provider's servers (or your own) Provider, or you if self-hosted Outages, rate changes, account freezes
Plugin Connector code for your shop platform Inside your shop You and the plugin author Abandoned updates, compatibility breaks, wider PCI scope
Processor Routes and settles card transactions Provider's network Provider Hidden fees, slow settlement
Merchant account Account that receives settled funds Acquiring bank Bank and provider Reserves, holds, termination

Each row can be replaced independently.

Choosing in the Right Order: Gateway First, Plugin Second

Most buyers do it backwards. They search a platform's plugin directory, pick whatever has the most installs, and read the gateway terms afterward. I would choose in this order:

  1. Decide who holds the money. If a third party holds your balance, it can freeze it. If it settles straight to your own wallet or bank, it cannot.
  2. Decide your compliance load. Prefer redirect or embedded checkout unless you have a reason and the staff to handle a larger PCI scope.
  3. Price the whole path. Add gateway fee, processor markup, any platform surcharge for third-party gateways, and refund costs.
  4. Then pick the plugin. Check the last update date, whether it supports your platform version, and whether it is maintained by the gateway itself or a third party.

For a general look at how modules are priced and judged, see our payment module guide. If you are already weighing bitcoin options, the bitcoin payment plugin comparison lists what to check first.

The Bitcoin Exception: When the Gateway Is Software You Run

Hands holding a physical bitcoin coin over an open leather wallet, with a small server box in the background.

BTCPay Server changes the usual picture of a provider-run gateway and a plugin in your shop. BTCPay Server is open-source software that you run yourself. It generates invoices, watches the blockchain for payment, and pays directly to your wallet. The shop plugin, for example the WooCommerce integration, only talks to your own server.

So the gateway is no longer a third party. There is no processor, no merchant account, and no provider holding a balance. The design follows the goal stated in the original Bitcoin paper: electronic payments between two parties without a trusted intermediary.

The trade-offs are real:

  • No chargebacks. Bitcoin payments are final, so refunds are a manual decision on your side.
  • You choose confirmation rules. You decide how many confirmations to wait for before marking an order paid, which is a risk call for larger orders.
  • You carry the uptime. If your server is down, invoices fail. Someone has to patch and monitor it.

That last point is where most merchants get stuck, and it is where hosting comes in.

Get a Self-Custodial Bitcoin Gateway Wired Into Your Shop Without Running a Server

The main problem with the self-hosted route is the sysadmin work: installing BTCPay Server, keeping it synced and updated, and connecting the right plugin to your shop. Myntli does that for you. The hosted option is $29 a month for a BTCPay Server store on Myntli's node. Customers pay straight into your own wallet, with no percentage taken, no custody of your funds, and no KYC on your store. If you want the node on your own machine, a full install on your server costs $449. Integration setup covers WooCommerce, Shopify, Ghost, Magento, PrestaShop, Drupal Commerce, Invoice Ninja and ReplaPay, and we can guide you through wallet setup if you do not have one yet.

This is a bitcoin gateway only and does not take cards, so if your customers expect card checkout you will keep a card gateway alongside it. Bitcoin payments also cannot be reversed. Check each shop's current plugin requirements against your platform version before you commit.

Frequently Asked Questions

What is the purpose of a payment gateway?

A payment gateway securely carries payment details or a payment request from your checkout to the network that approves it, then returns the result to your shop. It keeps your store from talking to banks directly and, in hosted setups, keeps sensitive data off your own servers.

What does "merchant transaction" mean?

A merchant transaction is a sale between a business and a customer that is authorized, captured and settled to the business. In card network terms, a "merchant-initiated transaction" is a narrower case: a charge the merchant starts without the customer present, such as a subscription renewal.

Is PayPal considered a merchant account?

No. PayPal operates as a payment facilitator, so your sales settle into a PayPal business balance and not into a dedicated merchant account tied to your own acquiring bank agreement. Setup is faster, but the provider's holds and reviews apply to that balance.

What is the difference between a payment processor and a payment gateway?

The gateway collects the payment request and passes it along securely, then reports the outcome to your shop. The processor routes the transaction through the card networks and banks and handles settlement of funds to your account.

Do I need both a gateway and a plugin?

You always need a gateway to accept payments. You need a plugin only when your shop platform has no native connection to that gateway, which is common on open platforms such as WooCommerce or Magento.

Sources