Knowledge base — Definition
Payment Gateway
What a payment gateway is, how it authorizes and settles online card payments, and what Canadian stores should compare before choosing one.
What Is a Payment Gateway?
A payment gateway is the service that securely captures a customer's payment details on your website and passes them to the card networks and banks for approval, then returns the result to your store. It is the online equivalent of the card terminal at a shop counter.
Three roles are involved in every online card payment: the gateway (the technology that collects and transmits the payment), the payment processor (which routes the transaction through the card networks) and the merchant account (where funds land before they reach your business bank account). Providers such as Stripe, Square and PayPal bundle all three into one account, while traditional setups, such as a bank's merchant services paired with a separate gateway, split them across companies.
Why a Payment Gateway Matters
Your gateway choice affects far more than the fee line on your statement.
- Checkout experience: Whether customers pay on your site, in an embedded form or on a redirect page is set by what the gateway supports.
- Security and PCI scope: Gateways that offer hosted fields or tokenization keep card numbers off your server, which dramatically reduces your PCI compliance workload.
- Payment methods: Wallets such as Apple Pay and Google Pay, buy-now-pay-later options and Canadian methods depend entirely on the provider.
- Cash flow: Payout schedules, reserves and how disputes are handled vary between providers and affect working capital.
- Platform fit: The quality of the WooCommerce or platform integration determines how reliably refunds, subscriptions and order statuses sync.
How a Payment Gateway Works
- Capture: The customer enters card details into fields served by the gateway, often an iframe inside your checkout, so the data goes directly to the provider.
- Tokenization: The gateway replaces the card number with a token your store can use for this order, refunds or saved cards, without ever holding the real number.
- Authentication: For riskier transactions, the issuing bank may ask the customer to verify through 3-D Secure, such as a banking app approval or a one-time code.
- Authorization: The request travels through the processor and card network to the customer's bank, which approves or declines it and places a hold on the funds.
- Capture and settlement: The authorized amount is captured, either immediately or when you ship, then settled into your merchant account and paid out on the provider's schedule, minus fees.
- Notifications: The gateway sends webhooks back to your store to confirm payments, refunds and disputes, which keep order statuses accurate.
Common Payment Gateway Mistakes
- Choosing on headline rate alone: Ignoring cross-border card fees, currency conversion, dispute fees and monthly minimums that change the real cost.
- Ignoring webhooks: Failed or unconfigured webhooks leave orders stuck as "pending" even though the customer was charged.
- Sending customers off-site without warning: A sudden redirect to an unfamiliar domain looks suspicious and interrupts the checkout process.
- Not testing declines: Testing only successful payments, so error messages for declined cards, expired cards and failed 3-D Secure are confusing or missing.
- Forgetting currency and tax setup: Charging in US dollars by default, or mismatching store currency and settlement currency, confuses Canadian buyers.
Best Practices for Payment Gateways
- Compare total cost: Ask each provider for the full fee schedule, including international cards, currency conversion, refunds, chargebacks and payout timing.
- Prefer embedded, tokenized fields: Keep customers on your site while keeping card data off your server.
- Offer the wallets your customers use: Apple Pay and Google Pay shorten mobile checkout considerably; confirm Canadian-specific options such as Interac support with each provider, since availability varies.
- Test in sandbox mode: Run every scenario with the provider's test cards before going live, including refunds, partial refunds and subscription renewals.
- Plan for disputes: Keep clear order records, shipping confirmations and a visible refund policy to support you when a customer files a chargeback.
Payment Gateways at PerfectPixels
We help clients choose a gateway based on their products, volume and customers, then integrate it into WooCommerce or a custom platform with tokenized fields, digital wallets, correct webhook handling and thorough sandbox testing. When an off-the-shelf integration falls short, we build custom payment logic as part of our eCommerce and custom plugin work.
Frequently Asked Questions
What is the difference between a payment gateway and a payment processor?
The gateway collects and securely transmits the payment details from your website, while the processor moves the transaction through the card networks and banks. Many modern providers handle both, so for most small stores the distinction matters mainly when comparing quotes.
Which payment gateways work well for Canadian businesses?
Stripe, Square, PayPal, Moneris, Helcim and Global Payments are all used by Canadian merchants and integrate with WooCommerce. The right choice depends on your volume, whether you also sell in person, the payment methods your customers expect and the fees for your mix of domestic and international cards.
Can I offer more than one payment gateway?
Yes. Many stores pair a card gateway with PayPal or a buy-now-pay-later option. Keep the choices clear and limited at checkout, and make sure each one is tested and reconciled in your accounting.
Related Resources
Further reading: Payments documentation — Stripe Docs.