Integrations

Payment gateway integrations

Connect checkout to the payment gateways and local methods your customers use. Explore providers by country, then plan the account, channels, and payment flow for your operation.

Payment gateways

Explore payment integrations.

Country filtering uses each provider’s documented business markets, not the countries your customers can order from. Providers without a published country list appear when no country is selected.

32 payment integrations

Choose based on the operating context

A payment gateway connects checkout to the payment methods your project chooses. Start with the merchant account, where you sell, and the channels customers will use before selecting a gateway.

Choose the methods customers need—cards, wallets, bank transfers, local methods, or cash and pay on delivery—then review the provider account and the operational work each method requires.

Beyond the gateway

A gateway is not the only way customers pay. Gift cards let customers redeem a stored-value balance at checkout, and the customer payment wallet lets a customer save a card once and pay in one click on a later order, an optional setting.

Payment setup

Pick a gateway, connect it, and go live.

  1. 01
    Choose your gateway

    Pick the gateway that fits the countries, currencies, and payment methods your customers use.

  2. 02
    Connect your account

    Connect your gateway account to Ordering.co and enable it for the businesses and checkout channels that should offer it.

  3. 03
    Test, then go live

    Place test orders, check successful and declined payments, then switch to live payments.

Payment method implementation guarantee

Missing a payment method in your country? We’ll implement it at no cost.

Tell us the payment method you need and the country where your business operates. Ordering.co will implement the missing payment method at no implementation cost.

Talk to Ordering.co

Payment method map

Compare methods by the decision they change.

Account and provider

The gateway owns its account, onboarding, and settlement requirements.

Merchant account
Account owner and settlement terms
Gateway credentials
Keys, environment, and provider checks
Country and currency
Provider-supported operating context
Provider policy
Verification, refunds, and compliance

Customer checkout

Choose methods that make sense for the customer and the channel.

Cards
Card acceptance and authorization flow
Wallets
Device and provider eligibility
Bank and local methods
Regional payment preferences, such as Bancontact, Alipay, or Giropay through Stripe Redirect
Cash or pay on delivery
Operational handling and reconciliation

Payment methods, commercial terms, and provider requirements depend on your gateway account and are confirmed during setup.

What to decide

A payment method is a customer choice and an operating responsibility.

Checkout surface

Document whether a method appears on web, app, kiosk, or another customer surface.

Method eligibility

Confirm which methods the selected provider supports for the account, country, currency, and customer device.

Order lifecycle

Agree how authorization, capture, cancellation, refund, tip, and receipt events should be handled.

Reconciliation

Make clear who reviews settlement reports and how payment records are matched to orders.

For marketplace projects

Map the movement of money before choosing a provider flow.

Marketplace payment design usually involves more than one party. Decide who is charged, who receives each amount, and which provider requirements apply before the project is configured.

Ordering.co uses Stripe Connect to split payments automatically between platform and business. Driver payment splits are available to clients.

Explore Stripe Connect
  • Customer paymentOrder total
  • Platform + businessAutomatic payment split with Stripe Connect
  • Delivery partnerDriver payment splits available to clients

Technical handoff

Give the payment team a clear configuration brief.

Bring the gateway documentation, account owner, channel requirements, and the order events that need to be tested. Those inputs make the payment setup concrete.

  • Selected gateway and its documentation
  • Account owner and provider requirements
  • Currency, countries, and checkout channels
  • Payment methods and order events to test

Questions

Prepare the right payment conversation.

Are all the gateways in this directory available with Ordering.co?

Yes. Every gateway listed here is an Ordering.co integration. The payment methods your customers see depend on your gateway account, country, and currency, and we confirm them with you during setup.

What should we bring to a payment setup discussion?

Bring the provider, business, country, currency, merchant account owner, and the checkout channels that need to be tested.

What does the payment method implementation guarantee cover?

If a payment method you need in your country is missing, Ordering.co will implement it at no implementation cost. Tell us your country and the payment method you need.

Do the country filters describe where my customers can pay from?

The filters describe documented provider markets for business or connected accounts, not every country where a customer can place an order. Check each provider’s country notes and account requirements.

How does Stripe differ from Stripe Connect?

Stripe collects payments into your own Stripe account and is enabled business by business. Stripe Connect splits each payment automatically between the platform and its businesses, and driver payment splits are available.

Take payments the way your customers want to pay.

Tell us your countries, currencies, and checkout channels, and we will help you choose and set up the right gateway.