Start an application
Payment gateway

One connection to all of your acquirers.

You integrate with us once. Behind that we connect your merchant accounts, whichever banks they sit with, and add new ones later without you changing a line of code. Cards are tokenised on our side, so any of those acquirers can charge them.

Start an applicationRead the docs
What you get

What the gateway takes care of

01

One API, many acquirers

Add or remove merchant accounts behind the gateway without touching your integration.

02

Gateway tokens

Cards are tokenised with us, not with an acquirer, so a stored card keeps working when you change banks.

03

3DS2 built in

Authentication is requested only when the issuer needs it. Exemptions are applied where the rules allow.

How it works

What happens when you send us a payment

You send a request. We run 3DS if the issuer wants it, pick the acquirer and send the answer back, usually in under 200 ms.

  1. STEP 01

    Create a payment

    One request with amount, currency and either card details from our hosted fields or a stored token.

  2. STEP 02

    We authenticate and route

    3DS2 runs if the issuer asks for it. The payment is then sent to the acquirer chosen by your routing rules.

  3. STEP 03

    You get the result

    A synchronous response plus a signed webhook. Settlement reports follow on the cycle in your offer.

Specifications

Technical details

If something you need is missing here, ask your analyst or check the docs.

Integration
REST API, hosted checkout, hosted fields, server-side SDKs
Card schemes
Visa, Mastercard, Maestro, American Express, JCB, UnionPay
Authentication
3DS 2.2 with exemption handling
Tokenisation
Gateway tokens; network tokens where the scheme supports them
Currencies
134 settlement currencies, 180+ presentment
Compliance
PCI DSS Level 1 service provider
Get started

Ready to apply? Send the short form and an analyst will get back to you within a working day.

Start an application