Payment gateway vs payment processor: what's the difference?
Payment gateway vs payment processor explained simply: who does what in a card payment, where acquirers and card schemes fit, and what it means for your fees.
- Published
- Reading time
- 6 min read
- By
- CentraPoint Team
On this page
The payment gateway vs payment processor difference is about roles. A payment gateway is the technology that securely captures your customer's payment details and passes them on; a payment processor is the party that moves the transaction through the card networks and banks so it can be authorised and settled. In South Africa, most small businesses sign up with a provider that bundles both, which is why the terms are often used interchangeably.
Understanding the split still matters, because it explains your fees, your settlement times and who to call when a payment fails.
The parties in a card payment
Before comparing the two, it helps to see everyone involved when a customer pays R499.00 by card on your website:
| Party | What it does | South African example of the role |
|---|---|---|
| Customer (cardholder) | Enters card details and approves the payment | Your buyer |
| Merchant | Sells the goods or service | Your business |
| Payment gateway | Captures and encrypts the card data, sends it for authorisation, returns the result | Online gateway or hosted checkout |
| Payment processor | Routes the transaction between the parties and handles authorisation and settlement messaging | Often part of the gateway or the acquirer |
| Acquiring bank (acquirer) | Holds the merchant relationship with the card schemes and settles funds to the merchant side | A bank that acquires card transactions |
| Card scheme | Runs the network and rules | Visa, Mastercard |
| Issuing bank | Issued the customer's card and approves or declines | The customer's bank |
What a payment gateway does
A gateway is the front door. Its jobs include:
- Collecting payment details securely, usually on a hosted page or an embedded form so that raw card data never touches your server.
- Running authentication such as 3-D Secure, where the customer confirms the payment in their banking app or with a one-time PIN.
- Sending the authorisation request onward and returning "approved" or "declined" to your site.
- Notifying your system through a redirect and a server-to-server notification (a webhook).
- Offering extras: saved-card tokens for recurring billing, refunds, payment links and a merchant dashboard.
Online, the gateway is the part you integrate with. If you use a WooCommerce plugin or a checkout link, you are talking to a gateway.
What a payment processor does
The processor does the plumbing between the gateway and the banks:
- Formats and routes the transaction to the right card scheme.
- Carries the authorisation request to the issuing bank and brings the answer back.
- Handles clearing and settlement messages at the end of the day so that funds move from issuer to acquirer.
- Manages chargebacks and other exceptions through the scheme's processes.
Sometimes the processor is a specialist company working for the acquiring bank; sometimes the acquirer processes itself; sometimes the gateway company also acts as processor. That is why the lines blur.
Payment gateway vs payment processor side by side
| Payment gateway | Payment processor | |
|---|---|---|
| Main job | Capture and pass on payment details securely | Move the transaction through networks and banks |
| Who integrates with it | You (website, app, plugin) | Usually only gateways and acquirers |
| Customer sees it? | Yes, the checkout page or form | No |
| Handles 3-D Secure | Typically | Supports the messaging |
| Settlement | Reports it to you | Performs clearing and settlement messaging |
| Typical relationship | Direct contract, or through an aggregator | Behind the scenes |
Aggregators versus direct merchant accounts
In South Africa there are two common models:
Aggregator (payment facilitator). Many providers with quick online sign-up work this way; Payfast, for example, describes its standard offering as an aggregation solution. The provider signs you up under its own acquiring arrangements. Onboarding is quick, pricing is usually a simple percentage plus a fixed fee, and the provider pays out to your bank account. The gateway, processing and acquiring relationship are bundled.
Direct merchant account. Larger businesses may get their own merchant number from an acquiring bank and connect it to a gateway. This can mean lower rates at volume, but more paperwork, and you often pay the gateway and the acquirer separately.
Neither model is better in general. Aggregators suit most SMEs; direct accounts suit high-volume merchants who can negotiate. Our guide to choosing a payment gateway in South Africa goes through the questions to ask.
Why the distinction matters in practice
Fees. Every card payment carries interchange (to the issuer), scheme fees and the acquirer or aggregator's margin. An aggregator folds these into one blended rate. With a direct setup you see more of the parts. See payment gateway fees in South Africa.
Declines. Most declines come from the issuing bank, not from the gateway. The gateway only reports the reason code it receives.
Settlement timing. When funds reach you depends on the acquirer's or aggregator's payout schedule, not on how quickly the gateway approved the payment.
Security scope. Using a gateway's hosted page or iframe greatly reduces how much card data your systems handle, which shrinks your PCI DSS scope. It does not remove your obligations entirely, so check with your provider which self-assessment questionnaire applies to you.
Recurring payments. Saved-card tokens are created by the gateway and usually only work with that gateway. Moving providers can mean asking customers to re-enter card details. Card tokenisation explained covers this.
Where bank payments fit
Not every payment is a card payment. Pay-by-bank (instant EFT) providers, PayShap requests, debit orders and mobile money all use different rails with their own participants. The same idea applies, though: someone captures the payment instruction (the gateway role), and someone moves the money between institutions (the processing and clearing role).
How CentraPoint helps
CentraPoint is neither a gateway nor a processor, and it does not hold your funds. It is a billing and payments layer that connects to the gateways you contract with directly, including PayFast, Paystack, Peach Payments, Ozow, Yoco, PayGate and DPO Pay, plus Netcash for debit orders and M-Pesa and MTN MoMo for mobile money. You get hosted checkout pages, invoices, subscriptions and reconciliation of payouts and fees across all of them. See the supported list on our gateways page.
Frequently asked questions
Is a payment gateway the same as a payment processor?
No. The gateway captures and sends payment details; the processor routes the transaction through the card networks and banks. Many providers bundle both, so small businesses often deal with one company for both roles.
Do I need both a gateway and a processor?
For online card payments, both roles are always involved, but you usually only sign up with one provider that handles or arranges both.
Who decides whether a card payment is declined?
Most declines are decided by the customer's issuing bank. The gateway passes on the response and reason code, and fraud rules at the gateway or acquirer can also block a transaction.
What is an acquiring bank?
An acquiring bank is the bank on the merchant's side of a card transaction. It is a member of the card schemes and ensures funds from card payments are settled to the merchant or to the aggregator that serves the merchant.
- #payment gateways
- #card payments
- #acquiring
- #payments basics