Is Your Payment Gateway Costing You More Than You Think?

When businesses set up online payment acceptance, they typically focus on the merchant account—the processing rate, the monthly fees, the funding timeline. The payment gateway, the technology layer that connects their website or software to the processing network, often gets selected based on whatever their developer recommends or whatever requires the least configuration.
That approach is understandable. Gateways do not announce their cost in the same way that processing rates do. Their fees are often smaller per transaction but persistent—they apply to every online transaction regardless of how the underlying processing is priced. For businesses with significant online volume, gateway costs are a meaningful component of total processing expense.
What a Payment Gateway Actually Does
A payment gateway is the technology infrastructure that authorizes online transactions. When a customer enters their card information on your website and clicks purchase, the gateway encrypts that data, routes the authorization request to the card network, receives the approval or decline response, and communicates the result back to your website—all in a few seconds.
Gateways are separate from processors, though some processors bundle both functions under one product. When they are separate, both charge fees. When they are bundled, the combined pricing may or may not be better than sourcing each separately.
Gateway Fee Structures to Understand
Per-transaction gateway fees typically range from $0.05 to $0.30 per transaction. This is separate from the processing fee. A transaction that costs you 2.3% plus $0.10 in processing also costs another $0.15 in gateway fees, bringing the true total to 2.3% plus $0.25. Over high volume, that difference is material.
Monthly gateway fees are common—typically $10 to $50 monthly for access to the gateway infrastructure. Some gateways also charge setup fees, although competitive pressure has largely eliminated these for mainstream options.
Volume-tiered gateway pricing exists at scale. High-volume merchants often negotiate per-transaction gateway fees that are significantly below the standard published rates. If you process more than $100,000 monthly online, it is worth having an explicit conversation about gateway pricing rather than accepting the default rate.
When Your Gateway Is Redundant
Some merchants pay for a standalone gateway while using a processor that includes built-in payment gateway functionality. Their developer integrated the external gateway because it was familiar, without realizing the processor offered the same capability as part of the account.
If you use Stripe, Square, or Braintree for your online processing, you do not need a separate gateway—these platforms combine processing and gateway infrastructure. If you use a traditional merchant account with a regional processor or bank, check whether they include a gateway or whether you are paying for that separately.
Security Features Worth Understanding
3D Secure authentication—the step where customers sometimes receive a verification code from their bank during online checkout—is a gateway-level feature that shifts fraud liability. When a transaction completes with 3D Secure authentication, the liability for fraud chargebacks shifts from the merchant to the card issuer. For categories with elevated online fraud risk, this is a meaningful protection.
Not all gateways implement 3D Secure identically, and the customer experience varies. Poorly implemented 3D Secure creates abandonment—customers who encounter friction in the authentication step leave without completing the purchase. The balance between security and conversion requires attention, and your gateway implementation quality affects both.
Recurring Billing and Subscription Management
Businesses with subscription models or recurring billing have additional gateway requirements. The gateway must handle stored payment credentials compliantly, manage retry logic for failed payments, and support the card network rules for recurring transaction processing.
Gateway platforms vary significantly in how well they support subscription complexity. A simple monthly subscription is straightforward. Variable billing amounts, pause and resume functionality, trial periods, and proration all require more sophisticated handling. If your business model includes any of these, evaluate gateway capabilities explicitly rather than assuming they work correctly.
Conducting Your Own Gateway Audit
Pull your last three months of gateway invoices or look for gateway fees on your processing statements. Calculate the total gateway cost as a percentage of your online processing volume. If you are paying more than 0.4% in gateway fees alone, there is likely room to improve.
Ask your processor whether gateway functionality is included in your account. Ask your developer what gateways they have experience integrating—the answer often reveals that options you did not consider are technically accessible without additional development cost.
The goal is not necessarily to minimize gateway fees at the expense of capability or reliability. It is to ensure you are paying for what you actually need and receiving the value you are paying for.
