Payment Gateway Fees: Setup, Monthly and Per-Transaction Costs
Payment gateway fees explained: setup, monthly, per-transaction and add-on costs, plus how to compare bundled and standalone pricing at three volumes.

Photo: Pixabay
On this page 6 sections
- What a Payment Gateway Charges You For
- The Four Payment Gateway Fees: Setup, Monthly, Per-Transaction and Add-Ons
- Bundled vs. Standalone Payment Gateway Pricing
- Add-Ons That Raise the Bill: Fraud Tools, Vault, Recurring and Level 3
- Total Payment Gateway Cost at Three Monthly Volumes
- Questions to Ask Before Signing a Gateway Agreement
Key takeaways
- Gateways that bill every request also charge for declines, voids and renewal retries, so base your model on request counts, not approved sales.
- A bundled quote hides the gateway inside a percentage markup, so its cost grows with dollar volume instead of transaction count.
- To find a bundled quote's implied gateway cost, subtract a processing-only quote at the same volume from the bundled total.
- Low-ticket sellers should model per-request fees before assuming a standalone gateway is cheaper.
Payment gateway fees come in four parts: a one-time setup fee, a flat monthly fee, a per-transaction fee, and charges for add-ons such as fraud screening or card storage. All four sit on top of what you pay to process the card. Standalone gateway providers bill each fee on its own line. Bundled providers fold the gateway into the processing rate, where you can't see it. To compare the two formats, pull the gateway cost back out of the bundled quote. The worked example below shows the arithmetic at three sales volumes.
What a Payment Gateway Charges You For
A gateway is the software between your checkout and your processor. It captures card details from a web checkout or a virtual terminal for keyed payments and passes an encrypted authorization request to the processor. Subscription billing platforms send their renewals through it as well. For the full route a payment takes, see how a payment gateway routes online approvals. The gateway doesn't settle funds and has no say over network pricing.
That division shapes your bill. Interchange is set by the card networks and paid to the cardholder's bank. The networks also charge assessment fees of their own. Your processor then adds its markup. The gateway fee is a separate layer, priced commercially by whoever provides the gateway. No Visa or Mastercard rule sets it or caps it, which is why it swings so widely between quotes. The interchange fees card networks set work the other way, and you can't negotiate them.
Card-not-present sales already carry higher interchange than cards tapped or dipped in a store. The reasons are in why online and keyed transactions cost more to process. Next to interchange, the gateway is the smaller cost. It is also the cost that hides inside bundled rates and the one that gets billed twice when two companies both invoice for it.
The Four Payment Gateway Fees: Setup, Monthly, Per-Transaction and Add-Ons
| Fee type | How it's billed | What to check |
|---|---|---|
| Setup | One time, at activation | Whether it's waived, and whether you get it back if underwriting declines you |
| Monthly | Flat, regardless of volume | Whether it's really a gateway fee or a merchant account fee |
| Per-transaction | Flat cents per request | What counts as a "transaction" |
| Add-ons | Monthly, per use, or both | Which features are included and which cost extra |
Setup fees also appear as activation or onboarding fees. Monthly fees look simple, but on a statement they sit next to merchant account charges such as PCI compliance fees. Those belong to the processor, not the gateway, so ask which company bills each line.
The gateway transaction fee needs the closest read, because its definition matters more than its price. Gateway agreements spell out what counts as a billable transaction, and a common definition is any request that passes through the gateway. Under that wording you pay for declines, voids, refunds and separate capture requests, not only approved sales.
Declines are the expensive surprise. Each one costs a gateway fee, and if your processor also charges an authorization fee on declined transactions, you pay that too. Subscription businesses pay again for every retry of a failed renewal. Card testing is the worst case: bots push stolen card numbers through small authorization attempts and can run up a flood of billable requests overnight. Get the definition in writing before you model any costs.
Bundled vs. Standalone Payment Gateway Pricing
With standalone pricing, you hold a merchant account with a processor and a separate gateway account, even when one reseller sets up both. Each gateway charge appears on its own line. A standalone gateway that connects to multiple processors lets you change processors without rebuilding your checkout. Your saved cards move with you only if the gateway lets you export stored tokens, so settle that before you sign. MannyPay offers payment gateways including Authorize.net and NMI, along with integrations for carts such as Shopify and WooCommerce.
Bundled pricing puts the gateway inside the processing rate, in one of two forms. Flat-rate pricing charges one percentage plus a per-transaction amount that covers everything. Our breakdown of Stripe fees beyond the headline rate shows how that model adds up. Bundled interchange-plus passes network costs through at cost and charges a higher markup, and the extra markup pays for the gateway.
One bill and one company to call are real advantages. You still pay for the gateway, though, and the cost grows differently. A standalone gateway gets more expensive as your transaction count rises. A bundled gateway sits inside a percentage markup, so its cost tracks dollar volume, and a bigger month costs more for the same service.
To compare the two on equal terms, work out the implied gateway cost of the bundled quote. Take everything the bundled quote charges in markup and fees, then subtract what a processing-only quote charges at the same volume. The difference is your gateway bill, whatever the statement calls it.
Add-Ons That Raise the Bill: Fraud Tools, Vault, Recurring and Level 3
Add-ons are where gateway quotes that look identical stop being identical. These are the ones to price line by line:
- Fraud screening. Rules filters, velocity limits, IP blocking and AVS/CVV rules, priced as a flat monthly fee or per screened transaction. Our guide to handling AVS and CVV mismatches covers how to set those rules. Ask whether 3-D Secure authentication is part of the fraud package or priced on its own.
- Customer vault. Tokenized card storage for repeat buyers and card-on-file billing, charged either as a monthly fee or per stored profile.
- Recurring billing. The scheduling engine behind subscriptions and memberships. Account updater services refresh expired or reissued cards and carry their own charge, commonly billed per successful update. See how Account Updater keeps saved cards current.
- Level 2 and Level 3 data. Sending extra detail such as sales tax and line items qualifies eligible commercial card transactions for lower interchange categories. The card networks set those qualification rules. Check whether the gateway charges to turn the feature on.
- eCheck or ACH. Bank payments through the gateway come with a fee schedule separate from cards.
Which add-ons matter depends on how you sell. E-commerce stores lean hardest on cart integration and fraud screening, because card testing and stolen-card orders arrive through the checkout.
Subscription and membership businesses run every renewal through the recurring engine and the vault. Their per-request and per-update charges repeat each billing cycle, retries included, so a small unit fee becomes a large monthly line.
Professional services firms key a modest number of large invoices. Per-transaction cents barely register for them, and the monthly fees dominate. When the clients are businesses paying with corporate cards, Level 2 and Level 3 support can pay for itself in lower interchange.
Total Payment Gateway Cost at Three Monthly Volumes
The figures in this section are illustrative. They are not any provider's actual pricing, MannyPay's included. They exist to show the method so you can rerun it with your own quotes.
Interchange and network fees are identical under both quotes, so the totals leave them out and show only the costs that differ. To get a full monthly bill, add your own pass-through costs to both columns. The example treats every request as an approved sale and ignores one-time setup fees.
| Illustrative assumption | Standalone quote | Bundled interchange-plus quote |
|---|---|---|
| Average sale | $100 | $100 |
| Processor markup | 0.25% + $0.10 per sale | 0.35% + $0.15 per sale |
| Monthly account fee | $10 | $15 |
| Gateway monthly fee, add-ons included | $35 | Included in markup |
| Gateway per-transaction fee | $0.07 | Included in markup |
| Monthly sales | Transactions | Standalone total | Bundled total | Standalone gateway | Bundled gateway (implied) |
|---|---|---|---|---|---|
| $10,000 | 100 | $87 | $65 | $42 | $20 |
| $50,000 | 500 | $255 | $265 | $70 | $80 |
| $250,000 | 2,500 | $1,095 | $1,265 | $210 | $380 |
The implied bundled gateway cost is the bundled total minus the standalone quote's processing charges, meaning its markup and account fee. At the lowest volume the bundled quote wins, because the standalone gateway's fixed monthly fee is spread across very few sales. In the middle the two quotes land close together, with standalone slightly ahead. At the top volume standalone is clearly cheaper. Its gateway charges only per request, while the bundled gateway's cost keeps climbing with every dollar sold.
Ticket size moves the crossover. A lower average ticket means more transactions at the same dollar volume. That inflates the standalone gateway's per-request charges and barely touches the bundled markup. If you sell mostly small-ticket items, model the per-transaction fee before you assume standalone is cheaper.
Flat-rate quotes need one extra step, because they already include interchange and network fees. Pull your actual pass-through cost from a recent statement and add it to both columns before you compare. Your card mix decides whether a flat rate comes out ahead, so build the model from your own statements rather than a vendor's averages.
Questions to Ask Before Signing a Gateway Agreement
- Billable transactions. Get the full list in writing, covering declines, voids, refunds and renewal retries.
- Included features. For every add-on outside the base price, get both the monthly charge and the per-use charge.
- Who bills what. The gateway fee belongs on either your processing statement or a separate gateway invoice. When it shows up on both, you're paying twice.
- Vault portability. Find out whether stored card tokens can move to a new processor and what the transfer costs.
- Contract terms. Ask for the term length and the early termination fee. Monthly minimums go into your total cost too, even if you expect to clear them.
- Card-testing defaults. Velocity limits and CAPTCHA protection switched on from day one keep a bot attack from turning into an expensive first month.
- Integration fit. Confirm the gateway supports your cart and billing software, plus Level 2 and Level 3 data if you bill businesses. An integration you have to build yourself carries a cost the fee sheet leaves out.
For the rest of the evaluation, use our guides on comparing merchant processing quotes side by side and choosing a payment gateway provider.
Start with last month's statements. Count every gateway request, not only approved sales, and plug the real figures into the model above. To test a standalone or bundled quote against it, request a free processing quote, and a MannyPay specialist will respond within one business day.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


