Card payment gateway options include a processor’s built-in checkout, a hosted payment page, an embedded or API-based checkout, and a payment facilitator that bundles gateway and processing services. The right fit depends on how you sell, the checkout experience you need, your technical resources, and the provider’s fees and supported payment methods.
What a card payment gateway does
A gateway securely transmits card-payment information between a checkout and the payment services that request authorization. It is one part of a broader payment chain: a customer submits card details, the gateway passes transaction data to a processor or acquiring bank, and the card network routes an authorization request to the card issuer. The issuer approves or declines it; approval is not the same as final settlement into the merchant’s account.
Some companies offer several parts of this chain together, while others specialize in one part. As a result, the term “gateway” is often used loosely to describe a complete online payment service. Before comparing products, check which services are included: gateway access, processing, merchant account or payment-facilitator services, fraud tools, recurring billing, and settlement reporting.
Main gateway options
- Hosted payment page: Customers are sent to a provider-hosted page to enter payment details. The provider handles much of the payment form and its security. This can reduce development work, but the merchant has less control over the page and the transition may feel less integrated.
- Embedded checkout: A provider’s payment fields or checkout components appear within the merchant’s site. This can offer a more continuous experience while keeping sensitive card entry within provider-managed components. The exact security responsibilities depend on the integration.
- API-based gateway: Developers build a more customized checkout using the gateway’s programming interface. This allows greater control over payment flows and can support complex platforms, but requires more development, testing, maintenance, and careful security work.
- Payment facilitator or all-in-one service: A provider may combine checkout, gateway, processing, and merchant onboarding under one service. Setup can be simpler than arranging separate vendors, although account structure, fees, support, and control over payment operations vary by provider.
- Gateway integrated with a merchant account: A business may pair a standalone gateway with a separate acquiring relationship or processor. This can suit existing payment setups or specialized needs, but the merchant must coordinate vendors and confirm that the systems work together.
In-person businesses may also need a gateway or payment platform that connects online payments with card terminals and point-of-sale software. A gateway intended for web checkout is not automatically a complete in-person payment solution.
How to compare providers
Start with the sales channels and payment flows you actually need. A small online shop with straightforward one-time purchases has different requirements from a marketplace that pays sellers, a subscription service that bills repeatedly, or a business taking payments both online and at a counter.
- Payment methods and coverage: Check which card types, digital wallets, currencies, and customer countries are supported for your business. Availability can depend on the provider, account, and location.
- Integration and compatibility: Confirm support for your website platform, shopping cart, accounting tools, subscription system, and point-of-sale setup. Review available plugins, APIs, documentation, and migration requirements.
- Checkout control: Compare hosted, embedded, and custom options. Consider mobile usability, accessibility, localization, and whether customers can complete payment without unnecessary redirects.
- Payment operations: Look for the functions you need, such as refunds, recurring charges, saved payment credentials, authorization and capture, partial payments, or consolidated reporting. Verify the conditions and any extra charges.
- Support and reliability: Review support channels and hours, incident communication, service documentation, and how disputes or failed transactions are handled. Ask what support is included in the proposed plan.
- Data portability: Understand what transaction and customer-payment data you can export, and what happens if you switch providers. Stored card credentials may not transfer automatically.
Ask providers for a complete written price schedule rather than comparing one advertised percentage. Costs may include per-transaction charges, monthly or setup fees, chargeback fees, currency conversion, international-card charges, refunds, and optional products. Pricing depends on the agreement and transaction details; obtain the actual terms directly from each provider.
Security and compliance responsibilities
Using a hosted checkout or provider-managed payment fields can reduce how much sensitive card data passes through a merchant’s own systems. It does not mean every security or compliance obligation disappears. The applicable requirements depend on how the checkout is implemented, which systems handle card data, and the merchant’s role. Confirm responsibilities with the provider and the relevant payment-security standards; do not assume that a particular integration automatically makes a business compliant.
Use secure account access, restrict staff permissions, protect administrator accounts, and keep website software and payment integrations maintained. Review fraud controls such as transaction monitoring, address or security-code checks where supported, and rules for reviewing unusual orders. Fraud controls can reduce some risks but may also reject legitimate customers, so check how decisions and exceptions are managed.
For a custom integration, never place secret API credentials in public website code or logs. Use the provider’s current integration guidance, protect credentials, and test payment, refund, cancellation, and error scenarios before launch. Avoid collecting or storing card data yourself unless your organization has the expertise and compliant systems to do so.
Common problems and practical checks
A payment marked “authorized” may still need to be captured and settled, depending on the setup. A declined authorization can reflect an issuer decision, incorrect details, fraud controls, or a technical issue; the gateway may not reveal the issuer’s full reason. A successful screen on the website also does not, by itself, prove that the funds have settled.
- Check that the website’s currency, payment methods, and checkout settings match the provider account.
- Test successful payments, declines, refunds, duplicate submissions, and interrupted checkouts in the provider’s test environment.
- Use transaction identifiers and provider reports to reconcile orders, refunds, and settlement records.
- Make sure the integration handles delayed or repeated notifications safely, so a customer is not charged twice for one order.
- Before changing gateways, plan for recurring payments, saved credentials, refunds, reporting history, and any period when both systems may need to be monitored.
A gateway can route a payment request, but it cannot guarantee approval, prevent all fraud, or ensure immediate access to funds. Those outcomes depend on other participants and the terms of the payment service.
Frequently Asked Questions
What is the difference between a payment gateway and a payment processor?
A gateway securely passes payment data from checkout into the payment system. A processor handles transaction processing between relevant financial institutions and networks. Providers sometimes bundle these functions, so compare the services in the contract rather than relying on the label.
Do I need a separate merchant account?
It depends on the provider’s model. Some services provide a bundled arrangement or payment-facilitator setup; other gateways connect to a separate merchant account or acquiring service. Ask who holds the account relationship and how settlement works.
Is a hosted checkout more secure?
A hosted page can keep card entry on provider-managed systems and reduce the merchant’s direct handling of card data. Security depends on the entire setup, including the website, account access, and configuration. Hosted checkout does not remove every security responsibility.
Can one gateway handle online and in-person payments?
Some payment platforms support both, but capabilities vary. Confirm that the provider supports your terminals, point-of-sale system, reporting needs, and the online payment methods you use.
Can I change gateways later?
Usually a business can migrate, but it may need to rebuild the checkout integration and arrange for recurring payments or stored credentials to move. Data transfer, customer consent, and migration support depend on the providers and the applicable arrangements, so clarify them before signing.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this section
- Avalanche Game Schedule: Dates, Times and Where to Check
- Avalanche Hockey Schedule: Games, Dates and TV
- Avalanche Debt Payoff Tracker Calculator
- Avalanche Debt Repayment Calculator and Payoff Plan
- Avalanche Debt Payoff Calculator and Spreadsheet
- Avalanche Debt Payoff Calculator: Free Estimate