Ordering.coOrdering.co
ESTalk to Ordering.coTalk to usBook a demo
Menu

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.

Explore payment gatewaysDiscuss payment setup

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
Read the payment setup guidesRead the API reference

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.

Answers for choosing your payment flow

  • Embedded checkout or a hosted payment page?

    An iframe embeds provider-hosted fields or a payment page inside your site; a redirect-based hosted checkout takes the customer to the provider and returns them afterward. Embedded products do not all use the same approach: Checkout.com documents Flow as an embedded interface, alongside Hosted Payments Pages and Payment Links. Confirm the selected product, browser/app behavior, authentication, callbacks, and order confirmation instead of assuming every gateway supports every route.

  • Can I add payment plans or recurring charges?

    Installments, buy now pay later, and recurring billing are different flows. Ordering.co supports Stripe Connect recurring payments; that does not establish installment support for every gateway or account. Review the provider, country, currency, customer authorization, schedule, cancellations, refunds, and failed-payment handling for the specific service you intend to sell.

  • Are payment links the same as invoices?

    A payment link opens a payment flow; an invoice records what is billed. Checkout.com documents links to its hosted payment page, created through its Dashboard or API. A provider’s link feature does not establish a native Ordering.co link or invoice connector. Agree how the paid amount and reference match an order or invoice, and how partial payments, expiry, and refunds are reconciled. Review fiscal-invoice requirements separately.

  • How should I compare Checkout.com with other gateways?

    Compare supported merchant countries and currencies, API and checkout interfaces, authentication, refunds, settlement, support, and a written quote against your order journey. Checkout.com publishes tailored pricing with flat-rate and interchange++ structures. Verify the current product and connector scope for each candidate; a provider’s API documentation alone does not prove its connection is ready for your Ordering.co project.

  • What goes into enterprise and third-party payment costs?

    Separate Ordering.co subscription or agreed enterprise scope from gateway processing, settlement/currency conversion, disputes, provider licenses, implementation, and ongoing support where applicable. Ask each party to identify its charges, billing unit, taxes, contract term, and responsibilities. Request a quote when no applicable tariff is public; missing pricing is not zero.

  • Is a third-party integration a payment method?

    A gateway processes payments; cards, wallets, transfers, or cash are customer payment methods; a POS or middleware connector moves operational data. These are distinct layers. A mention of Plug&Pay, Zuppler, Foodkit, iATS, or Bolt does not establish a particular Ordering.co integration. For an online checkout, card terminal, and payment-link requirement, verify each flow with the provider, account, country, currency, and actual connector. There is no single universal method list for every food-delivery business.

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.

Discuss payment setupSee pricing

What are you building?

Tell us and we’ll take you to the right next step.