Skip to content

Platform

White Label Payment Gateway API and Integration

A white label gateway connects in three directions at once. Acquirers and payment methods sit on one side, your merchants on the other, and your own back-office systems underneath. Each side has its own integration work, its own owner on your team and its own timeline.

This guide to the white label payment gateway API and integration walks through all three, then lists the technical requirements for white-label payments on each deployment option. The figure to plan around is about 5 business days to a first live payment, on SaaS and with connectors that already exist.

Three sides of white label payments integration

Split the job first. The three parts rarely run on the same schedule, and each one has a different person on your team waiting for it.

Side What connects Who does the work Typical time
Upstream Acquirers, PSPs, local methods, wallets We build or enable connectors Ready connectors at once; a new one in about 14 days
Downstream Your merchants' sites and apps Merchants, with your support Shortest on the hosted page, longest on host-to-host
Internal Your CRM, accounting, KYC tools, data warehouse Your developers, through our APIs and webhooks Depends on your stack

The downstream row is the one that grows with your business, since every new merchant repeats it. That's why the merchant-facing options deserve most of your attention.

Connecting acquirers and payment methods

Upstream integration is mostly our job. The gateway ships with 700+ ready connectors to acquirers, PSPs and payment methods, and enabling one of them is configuration work, not development.

When you bring an acquirer we don't have yet, we build the connector from its documentation in about 14 days, and the speed depends mostly on how complete that documentation is and how quickly the acquirer's technical team answers our questions. Your existing contracts stay yours, since we don't sit in the flow of funds.

How merchants connect to your gateway

Merchants pick the option that fits their skills and their PCI DSS scope. Offering all of them means you don't turn away a merchant because of how its site is built.

  1. The hosted payment page is the fastest. The merchant redirects shoppers to a page on your domain, and card data never touches its servers.
  2. CMS plugins suit merchants on popular e-commerce platforms, who install and configure rather than code.
  3. The JS SDK embeds secure card fields inside the merchant's own checkout, with real-time validation.
  4. iOS and Android SDKs add payments to mobile apps.
  5. Host-to-host gives a merchant full control of its payment page through the white label payment API, and it brings card data into the merchant's own PCI DSS scope.

Most new merchants start on the hosted page, since a white label checkout on your domain needs no development from them, and move to an SDK once their volume justifies the work.

White label payment gateway API and webhooks for your systems

Nobody on your team should export gateway reports by hand. Our APIs expose merchants, transactions, settlements and reports, and webhooks push events to your systems as they happen.

Typical uses are a CRM that updates when a merchant's onboarding status changes, an accounting system that receives settlement figures, and a data warehouse that pulls transactions for your own analytics. KYC and KYB checks run through the provider of your choice, which we integrate on request.

Technical requirements for white-label payments

What you need depends on where the gateway runs. SaaS asks the least of your team, and self-hosting moves infrastructure and its compliance onto your side.

Requirement SaaS Your cloud or servers
Hosting Run by us Your AWS, Azure, Google Cloud or Oracle Cloud account, or your own servers
Setup time About 5 business days with ready connectors About 30 days in a cloud account, about 60 on your own servers
PCI DSS Covered by our Level 1 certification You certify your environment; we support the audit
Domain Your domain for the payment page and admin panel The same, inside your infrastructure
Acquiring Your acquirer contracts, or an acquiring partner we refer The same
Operations Automated monitoring and alerts by us Your team runs the infrastructure; we deploy, configure and support

The table leaves out one requirement on purpose, which is the license. Whether you need one depends on your country and business model, not on the software, and it's worth settling before integration starts.

Testing before go-live

Run test transactions through every connector and integration type you plan to sell, not only the card flow. Refunds, partial captures, 3-D Secure challenges and declined retries tend to show integration gaps that a single successful payment hides.

A dedicated payment team works through these checks with you in the testing step of gateway implementation, before any live merchant pays through the gateway.

Questions

What payment gateway provides the most flexible white-label payment integration?

The most flexible ones offer every merchant option at once: a hosted page, CMS plugins, a JS SDK, mobile SDKs and host-to-host. Ours offers all five, so each merchant can pick the one that fits its team.

Is the white label payment API easy for developers to integrate into a custom web platform?

A custom platform usually starts with the hosted page or the JS SDK, which need only front-end work and keep card data off its servers. Host-to-host needs more development and its own PCI DSS scope.

Can my merchants accept payments inside an iOS app?

Yes, through the iOS SDK, and Android has its own SDK. Apps that sell digital goods inside iOS should check Apple's App Store rules on in-app purchases before choosing a payment flow.

Can I connect a payment provider that isn't on the connector list?

Yes. We build new connectors from the provider's documentation, which takes about 14 days, and you can keep using your existing contracts.

Plan your integration with us

Bring your acquirer list and the merchant types you plan to serve, and we'll map out the integration for each.