What matters most when picking a payment gateway
A payment gateway is the tool that connects your customer's payment method to your bank account. Choosing one means deciding what transactions you'll accept, how much you'll pay in fees, how fast you get your money, and what happens when something goes wrong. The right choice depends on your business type, transaction volume, and how much technical setup you're willing to handle.
Start by knowing what you actually need to process. Do you take credit cards only, or also digital wallets like Apple Pay and Google Pay? Do you need to bill customers monthly, or handle one-time purchases? Do you sell internationally? The gateway you pick must support those specific payment methods—not every gateway accepts every type of card or wallet, and some charge extra for international transactions.
Then look at the real costs. Gateways charge in three ways: a percentage of each transaction (typically 2.2% to 3.5%), a flat fee per transaction (usually $0.20 to $0.30), or a monthly subscription. Some combine all three. A gateway that looks cheap at 2% might cost you more than one charging 2.9% plus $0.30 if your average transaction is small. Calculate what you'll actually pay on your typical sale before comparing.
Key Takeaways
- Payment gateways charge fees as a percentage of the transaction, a flat per-transaction fee, or a monthly subscription—calculate your actual cost on a typical sale before choosing.
- Settlement time (when money hits your bank account) ranges from same-day to five business days depending on the gateway and your bank, and slower settlement costs you money if you need cash flow.
- Your gateway must support the specific payment methods your customers use—credit cards, debit cards, digital wallets, and ACH transfers are not all available on every platform.
- Fraud protection and dispute handling vary widely; some gateways offer chargeback insurance or machine learning fraud detection, while others leave you to handle disputes alone.
- Integration difficulty ranges from plug-and-play (Shopify, Square) to requiring a developer (Stripe, Authorize.Net), so match the gateway's technical demands to your team's skills.
Settlement speed and when you actually get paid
The time between a customer's payment and the money in your bank account matters more than most people realize. If you're running on thin margins or need cash to restock inventory, waiting five days instead of one day can force you to borrow money or delay operations.
Most gateways offer settlement in one of three windows: same-day (usually for an extra fee), next business day, or two to five business days. Square and PayPal typically settle next business day. Stripe defaults to two business days but offers next-day for a fee. Authorize.Net and traditional merchant processors often settle in three to five days. Your bank also plays a role—some banks hold funds longer than the gateway promises, so confirm with your bank what they'll actually do.
Faster settlement costs money. Same-day settlement usually adds 0.5% to 1% to your transaction fees. If you process $10,000 a month, that's $50 to $100 extra per month. For most small businesses, next-business-day settlement is the practical middle ground. Only choose same-day if you genuinely need the cash that quickly.
Payment methods your customers will actually use
Not every gateway accepts every payment method, and your customers won't use a method you don't support. The big ones are Visa, Mastercard, American Express, and Discover—almost every gateway takes these. But beyond that, support varies.
Digital wallets (Apple Pay, Google Pay, PayPal) are increasingly expected, especially for online sales. Some gateways include them; others charge extra or don't support them at all. ACH transfers (bank-to-bank payments) are common for B2B transactions and subscriptions but rare in retail gateways. International cards and local payment methods (Alipay, WeChat Pay, iDEAL) are available only on gateways that specifically target global merchants.
Make a list of the payment methods your customers ask for or that your competitors accept. Then check each gateway's documentation to confirm support. A gateway that doesn't accept the methods your customers prefer will lose you sales, no matter how cheap it is.
Fraud protection and who handles disputes
When a customer disputes a charge or a fraudulent transaction hits your account, the gateway's tools and policies determine how much money you lose and how much work you do to fight back.
Basic fraud protection is standard: most gateways flag suspicious transactions and can block them before they settle. But beyond that, features diverge. Stripe and Square offer machine learning fraud detection that learns from your transaction patterns. PayPal includes some chargeback protection. Authorize.Net leaves most fraud detection to you or your payment processor. Some gateways offer chargeback insurance (you pay a small fee, they cover losses up to a limit), but this is rare and expensive.
Dispute handling also varies. When a customer claims they didn't authorize a charge, the gateway provides tools to submit evidence (shipping confirmation, email receipt, IP address match). Some gateways make this easy with templates and automated evidence gathering. Others require you to manually upload documents. If you process high volumes or high-value transactions, choose a gateway with strong dispute tools—you'll use them.
Technical setup and integration difficulty
Some gateways work out of the box. Others require a developer to write code. Your choice depends on your technical skills and budget.
Plug-and-play gateways like Shopify Payments, Square, and PayPal are built into their platforms or have simple dashboard setups. You log in, configure your account, and start accepting payments. No coding required. These are ideal if you're not technical or don't have a developer on staff.
Developer-friendly gateways like Stripe, Authorize.Net, and Braintree require integration through code or an API. You (or your developer) write code to connect your website or app to the gateway. This takes longer to set up but gives you more control over the customer experience and what data you collect. If you're building a custom website or app, this is often the better choice.
Check the gateway's documentation and ask whether they offer pre-built plugins for your platform (WordPress, WooCommerce, Shopify, etc.). A gateway with a ready-made plugin for your setup saves weeks of development time.
Monthly volume and pricing tiers
Some gateways charge the same rate whether you process $1,000 or $1 million per month. Others offer tiered pricing—lower rates as your volume grows. A few have monthly minimums or caps.
If you're just starting, tiered pricing doesn't help you yet. But if you're growing, it matters. Stripe and Authorize.Net don't change rates based on volume, so you pay the same percentage forever. Square and PayPal sometimes offer volume discounts if you ask. Some traditional merchant processors build in tiered rates from the start.
Also check for hidden costs: setup fees (usually $0 to $100), monthly minimums (some gateways charge $20 to $50 even if you process nothing), PCI compliance fees, statement fees, or fees for features like recurring billing. Add these to your per-transaction costs to get the real picture.
Customer support and what happens when things break
When a payment fails, a customer can't complete checkout, or you need to dispute a transaction, you need to reach someone who can help. Support quality varies dramatically.
Square and PayPal offer phone support during business hours and email support anytime. Stripe offers email and chat support but no phone line (though they have a community forum). Authorize.Net offers phone support but response times vary. Traditional merchant processors usually have dedicated account managers if you process high volume.
Before choosing, test their support. Email a question and see how long it takes to get an answer. Call their support line and see if you reach a person or a queue. If you process payments that are critical to your business, phone support matters—email support won't help you when a customer's payment is stuck at 2 p.m. on a Friday.
Comparing gateways side by side
| Gateway | Per-Transaction Fee | Settlement Time | Setup Difficulty | Best For |
|---|---|---|---|---|
| Square | 2.6% + $0.10 | Next business day | Plug-and-play | Small retail, restaurants, simple online stores |
| PayPal | 2.2% + $0.30 | 1–2 business days | Plug-and-play | Existing PayPal users, international sales |
| Stripe | 2.9% + $0.30 | 2 business days | Developer required | Custom websites, apps, high volume |
| Authorize.Net | 2.9% + $0.30 | 3–5 business days | Developer required | Recurring billing, B2B, established businesses |
| Shopify Payments | 2.9% + $0.30 | 1–2 business days | Plug-and-play (Shopify only) | Shopify stores only |
Frequently Asked Questions
Can I switch payment gateways without losing my customers?
Yes. Your customers don't know which gateway you use—they only see your checkout page. When you switch, update your website to point to the new gateway and inform customers of any changes to how they pay. Recurring subscriptions may need manual migration depending on the gateways involved, so plan that transition carefully.
What if a gateway doesn't support the payment method I need?
You have two options: choose a different gateway that does support it, or use multiple gateways (one for credit cards, another for ACH transfers, for example). Using multiple gateways adds complexity but is common for businesses with diverse customer bases. Make sure your accounting software can reconcile payments from multiple sources.
Do I need PCI compliance to use a payment gateway?
It depends on how you handle card data. If you use a hosted payment form (the gateway handles the form, not you), you're mostly exempt from PCI requirements. If you build your own form or store card data, you must meet PCI compliance standards, which is expensive and complicated. Always use a hosted form or tokenization to avoid this.
What's the difference between a payment gateway and a payment processor?
A gateway is the tool that captures payment information. A processor is the company that moves the money from the customer's bank to yours. Some companies (like Stripe and Square) do both. Others (like Authorize.Net) are gateways only—they partner with a processor behind the scenes. For your purposes, this distinction rarely matters, but it explains why some gateways have partnerships with specific banks.
How do I know if a gateway is safe?
Look for PCI DSS Level 1 certification (the highest security standard for payment processors). Check whether the gateway uses encryption and tokenization to protect card data. Read their privacy policy to see what data they collect and how long they keep it. Avoid any gateway that stores full card numbers on your server—they should tokenize (replace with a code) immediately.