Payment Gateways

Your checkout is only the beginning.

The gateway connects your checkout, payment tools and processing relationships.

We help you evaluate integration fit, stored payments and long-term flexibility.

Editorial illustration of a checkout page connected by a bridge through a marble gateway to a payment processor, card network and issuing bank, with signs for tokens, recurring billing, fraud controls and reporting

Together or separate. The trade-offs matter.

A gateway and processor can come from one provider—or be selected separately.

Bundled Environment

Bundled payment environment: a checkout connects to a single provider building containing both the gateway and processor, illustrated in forest-green marble, cream stone and brass.

One provider. Fewer moving parts.

Potential benefit
Simpler setup and support.
Trade-off
Greater provider dependence.

Separate Gateway + Processor

Separate payment providers: a checkout connects to a standalone green gateway, with brass connections branching to separate cream-stone buildings labeled Processor A and Processor B.

Separate providers. More flexibility.

Potential benefit
More processor choice.
Trade-off
Additional fees and support coordination.

Neither is automatically better. The right structure depends on your business.

Connections depend on gateway compatibility, underwriting and provider agreements.

Explore Payment Orchestration →

Great features mean little if the connection doesn’t fit.

Evaluate the integration before becoming dependent on a gateway. The setup should fit how your customers actually pay.

Editorial illustration of a compatible connection: a cream application block links by brass plug to a green gateway block, with checkout, invoice and virtual terminal panels above and an incompatible triangular plug labeled does not fit below
Platform & development
Confirm platform support, APIs, plugins, SDKs and webhooks.
Checkout experience
Choose hosted or embedded checkout that fits your application.
Beyond the website
Evaluate invoices, payment links and virtual terminals.

Keyed acceptance depends on the business model, underwriting and risk profile.

Tokens & Portability

Can your stored payments move with you?

Changing providers does not automatically transfer stored customer payments. Confirm portability before planning a move.

Ask about export rights, provider cooperation and subscription continuity.

Editorial illustration of a conceptual migration checkpoint: an open vault labeled Current Provider holds stored customer payment cards that travel across a brass bridge labeled Migration Support toward a closed vault labeled New Provider — stored payments do not transfer automatically
Stored payments do not automatically move when you switch.
Export rights
Confirm whether stored credentials can be exported, and in what form.
Provider cooperation
Ask how the current provider supports credential migration.
Subscription continuity
Plan how recurring payments continue if credentials cannot transfer.

Tokenized credentials support future payments; gateway, processor and network tokens can have different provider dependencies.

Tokenization does not remove a merchant's PCI obligations; it changes how those obligations apply.

Token ownership, export rights and migration capabilities vary by provider, contract, technology and card-network rules.

Capabilities that matter to your business.

Editorial illustration of recurring billing: a green marble desk calendar with a renewal cycle symbol, ringed by cream customer profile tiles connected by a brass band

Recurring Payments

Keep repeat payments running.

Evaluate stored payments, billing integrations, card updates and retry support.

Explore Recurring Billing →
Editorial illustration of fraud screening: payment cards travel along a green marble and brass conveyor under a shield gate; a checked card continues while a flagged card is diverted to a side tray

Fraud Controls

Manage risk without blocking good customers.

Match fraud rules, verification tools and 3DS to your risk strategy.

Explore Fraud & Risk →
Editorial illustration of payment reporting: a cream and brass screen on a green marble base shows bar charts, a donut chart and card transaction rows with approval and warning status, with a magnifier alongside

Reporting & Data

See what's happening—and why.

Access transaction records, decline responses and reporting tools.

Explore Approval Rates →

Gateway Costs

The monthly fee is only part of the cost.

Compare the total cost of the services you need, not just the headline gateway fee.

Evaluate the tools, usage charges and additional connections your business requires.

Explore Processing Costs →

Illustrative fee categories. Pricing varies by provider and services used.

Editorial illustration of an itemized gateway cost review on a dark green leather clipboard: line items for monthly and transaction fees, tokenization and account updater, fraud tools, and additional MIDs and platform fees, above a total gateway cost row with a magnifying glass — the categories show no quoted amounts

Should you change your gateway?

You may need an adjustment—not a new gateway.

Switching is not always necessary. The benefits should justify the impact on integrations, stored payments and recurring customers.

Editorial illustration of a conceptual software workbench on a cream countertop: a processor block connected to the current gateway, a brass tuning panel, a second processor block and a replacement gateway standing ready on a marble base

Fraud configuration and reporting also carry over—or need rebuilding—depending on the path chosen.

  • Keep it

    Keep the current gateway.

  • Change processor

    Change only the processor.

  • Tune configuration

    Improve the current setup.

  • Add a processor

    Where compatibility allows.

  • Replace gateway

    When limitations justify migration.

Confirm technical compatibility, provider cooperation and underwriting requirements before making changes.

How Merchant Counselor helps.

Tell us how your checkout, processor and gateway work together today. We'll help determine whether the setup still fits, including contract terms, data access, support responsibilities and migration requirements.

  1. Laptop displaying payment analysis beside a sketched workflow.

    Assess

    Review the gateway, integrations, tokens, reporting, contracts and support.

  2. Three payment option cards arranged for comparison.

    Advise

    Compare options for business fit, compatibility, cost and flexibility.

  3. Payment terminal showing a completed setup check.

    Implement

    Coordinate configuration, connections and migration when appropriate.

  4. Laptop showing payment performance improving over time.

    Optimize

    Monitor approvals, costs, fraud controls and functionality as needs evolve.

Review My Gateway Setup →

Choose the gateway for the architecture—not the other way around.