Skip to content
HIGH-RISK PAYMENT GATEWAY  ·  BUILT FOR iGAMING

Payments built for
the traffic other
gateways refuse.

Local rails, European bank payments and stablecoin settlement for iGaming, betting and sportsbook operators, with pay-out on the same local rail as the pay-in. One counterparty, one integration, one balance.

20
Local markets
49
Local methods
9
European bank-payment markets
USDT·USDC
Settlement, one balance
QRISOVOMayaGrabTouch 'n Go eWalletWavePayPhonePeIMPSEasypaisaPixNequiSEPAPayIDUSD Coin (USDC)
DANAGCashQR PhDuitNow QRKHQRUPIGoogle PayJazzCashTossOXXOM-PesaFaster PaymentsTether (USDT)
Coverage

20 markets. 49 methods. Both directions.

20Local markets
49Local methods
9European bank-payment markets
Coverage

Every market on the rail, both ways.

Scroll to tour the regions. Each market takes pay-ins and sends pay-outs on the same local rail, against one balance.

01 / 07

Southeast Asia

  • IndonesiaQRISDANAOVOVirtual account
    IN · OUT
  • PhilippinesGCashMayaQR PhGrab
    IN · OUT
  • MalaysiaDuitNowFPXTouch 'n GoBoost
    IN · OUT
  • CambodiaKHQRAll-bank pay-out
    IN · OUT
  • MyanmarWavePayBank transfer
    IN · OUT
02 / 07

South & Central Asia

  • IndiaUPIPhonePeGoogle PayIMPS
    IN · OUT
  • PakistanEasypaisaJazzCashQR
    IN · OUT
  • BangladeshbKashNagad
    IN · OUT
  • KazakhstanKaspi QRLocal bank transfer
    IN · OUT
03 / 07

North & East Asia

  • KoreaKakaoPayTossVirtual account
    IN · OUT
  • JapanBank transfer
    IN · OUT
  • TaiwanJKOPayConvenience storeATM
    IN · OUT
04 / 07

Latin America

  • BrazilPix
    IN · OUT
  • MexicoSPEIOXXO
    IN · OUT
  • ColombiaPSENequi
    IN · OUT
  • ArgentinaCVUQRE-wallet
    IN · OUT
  • PeruOnline bankingBank transfer
    IN · OUT
05 / 07

Africa

  • NigeriaPalmPayBank transfer
    IN · OUT
  • KenyaM-Pesa
    IN · OUT
06 / 07

Oceania

  • AustraliaPayID
    IN · OUT
07 / 07

Europe · bank payments

SEPA InstantOpen bankingFaster Payments (UK)IN · OUT
  • Austria
  • Belgium
  • France
  • Ireland
  • Italy
  • Netherlands
  • Portugal
  • Spain
  • United Kingdom
All markets

Every market. Both directions. One balance.

20 local markets and 9 European bank-payment markets, each paying in and paying out on the same rail, settling to one balance with USDT and USDC available.

Every corridor20 local markets · 9 European bank-payment markets
Southeast Asia
IndonesiaID
QRIS · DANA · OVO · Virtual account
IN · OUT
PhilippinesPH
GCash · Maya · QR Ph · Grab
IN · OUT
MalaysiaMY
DuitNow · FPX · Touch 'n Go · Boost
IN · OUT
CambodiaKH
KHQR · All-bank pay-out
IN · OUT
MyanmarMM
WavePay · Bank transfer
IN · OUT
South & Central Asia
IndiaIN
UPI · PhonePe · Google Pay · IMPS
IN · OUT
PakistanPK
Easypaisa · JazzCash · QR
IN · OUT
BangladeshBD
bKash · Nagad
IN · OUT
KazakhstanKZ
Kaspi QR · Local bank transfer
IN · OUT
Africa
NigeriaNG
PalmPay · Bank transfer
IN · OUT
KenyaKE
M-Pesa
IN · OUT
North & East Asia
KoreaKR
KakaoPay · Toss · Virtual account
IN · OUT
JapanJP
Bank transfer
IN · OUT
TaiwanTW
JKOPay · Convenience store · ATM
IN · OUT
Latin America
BrazilBR
Pix
IN · OUT
MexicoMX
SPEI · OXXO
IN · OUT
ColombiaCO
PSE · Nequi
IN · OUT
ArgentinaAR
CVU · QR · E-wallet
IN · OUT
PeruPE
Online banking · Bank transfer
IN · OUT
Oceania
AustraliaAU
PayID
IN · OUT
Europe · bank payments
AustriaAT
SEPA Instant · Open banking
IN · OUT
BelgiumBE
SEPA Instant · Open banking
IN · OUT
FranceFR
SEPA Instant · Open banking
IN · OUT
IrelandIE
SEPA Instant · Open banking
IN · OUT
ItalyIT
SEPA Instant · Open banking
IN · OUT
NetherlandsNL
SEPA Instant · Open banking
IN · OUT
PortugalPT
SEPA Instant · Open banking
IN · OUT
SpainES
SEPA Instant · Open banking
IN · OUT
United KingdomGB
Faster Payments · Open banking
IN · OUT

Methods, limits, currency ranges and settlement terms are confirmed per corridor in writing before launch. The full rate card is issued on request. Flags: flag-icons, MIT licence.

Payment methods

The methods depositors already trust.

Wallets, QR schemes and bank rails as depositors know them at home, across 20 markets, with European bank payments and stablecoin settlement on the same balance. Hover a row to pause it and see each market.

QRISGCashGrabVirtual accountKHQRPhonePeJazzCashPixM-PesaFPXPayIDDANAMayaDuitNow QRWavePayBoostGoogle PayEasypaisaOXXOSEPATether (USDT)bKashOVOQR Ph
JazzCashPixM-PesaNagadPayIDDANAMayaDuitNow QRWavePayKaspi QRGoogle PayEasypaisaOXXOSEPATether (USDT)KakaoPayOVOQR PhTouch 'n Go eWalletUPIIMPSBank transferTossNequi
MayaDuitNow QRWavePayJKOPayGoogle PayEasypaisaOXXOSEPATether (USDT)Convenience storeOVOQR PhTouch 'n Go eWalletUPIIMPSSPEITossNequiFaster PaymentsUSD Coin (USDC)QRISPSEGCashGrab
OXXOSEPATether (USDT)CVUOVOQR PhTouch 'n Go eWalletUPIIMPSQRTossNequiFaster PaymentsUSD Coin (USDC)QRISOnline bankingGCashGrabKHQRPhonePeJazzCashPalmPayPixM-Pesa
Touch 'n Go eWalletUPIIMPSSEPA InstantTossNequiFaster PaymentsUSD Coin (USDC)QRISOpen bankingGCashGrabKHQRPhonePeJazzCashVirtual accountPixM-PesaPayIDDANAMayaFPXDuitNow QRWavePay

Logos are trade marks of their owners, shown to identify the payment methods available; no endorsement is implied. Methods without a usable official logo file are shown by name. Nequi logo: Nequi, CC BY-SA 4.0. Maya logo: Maya Bank, Inc., CC BY 4.0. WavePay logo: Wave Money, CC BY-SA 4.0. All via Wikimedia Commons; sources and licences in LOGOS.md.

Stablecoin

Stablecoin settlement, one balance

For a high-risk operator, stablecoin is not a novelty rail. It is how treasury copes with many collection currencies and a correspondent-banking system that does not want the business.

Settle in USDT or USDC. Take settlement in stablecoin against the same balance as your local rails and European bank payments.
One balance. Pay-ins from every rail land on one balance, so there is one position to watch rather than one per vendor.
One statement. Settlements and withdrawals are recorded in the console against the same transaction references.

Why it matters

Stablecoin settlement can take out the correspondent-banking leg, the FX spread on each repatriation and the float between a local pay-out and a usable balance: the three costs that quietly eat a high-risk operator's margin.

How it works

In on a local rail. Out on the same one.

A depositor pays at your checkout over a local rail, open banking or stablecoin, and the money lands on one balance. When they withdraw, the pay-out goes back over the same rail, from the same balance. Most gateways take the deposit and leave the withdrawal to someone else.

  1. DepositorDeposit
  2. CheckoutYour site or app
  3. The railLocal · open banking · stablecoin
  4. One balanceYour Payee Global account

Pay-out on the same rail

Withdrawals go back over the same local rail the deposit came in on, from the same balance.

Settlement you can see

Collected pay-ins are calculated into your settlement balance every 30 minutes; settlements and withdrawals are recorded in the console.

Stablecoin on one balance

Take settlement in USDT or USDC against the same balance, alongside local fiat and European bank payments.

Bank payments — Europe

Instant open banking

The API starts the payment directly from the depositor's bank account into yours. No card network in the path means no interchange, no issuer decline wall and no chargeback mechanism for friendly fraud to exploit.

97%
Acceptance, up to · open banking rail
89%
Processed via SEPA Instant · open banking rail
9
European markets
0
Chargeback mechanism in the rail

97% and 89% are partner-reported figures for the European open banking rail only. They do not describe any other rail.

Coverage
AustriaBelgiumFranceIreland ItalyNetherlandsPortugalSpain United Kingdom
Rails
SEPA INSTANT  ·  SEPA
SWIFT  ·  TARGET
FPS  ·  CHAPS
Scope of service

What you get

Pay-in across 20 local markets and 49 methods
Pay-out on the same local rail as the pay-in
European bank payments in 9 markets over SEPA Instant and open banking
USDT and USDC settlement on the same balance
A documented merchant API with webhooks and status calls
A merchant console for pay-ins, pay-outs, settlements, API keys and webhooks
Rule-based routing across provider accounts
Two-factor sign-in, roles and permissions, IP allow-listing
Risk controls: block lists and per-account amount limits
The whole stack as a white label, under your brand
White label

Resell the whole stack under your name.

Payee Global is also a white-label payments reseller. Payment companies, platforms and agencies put their own brand on the rails, the back office and the checkout, and sell to their merchants as their own product. One integration gives your merchants every solution we run: local rails in 20 markets, European bank payments and stablecoin settlement. We run the platform behind it and stay out of sight.

  1. Your brand

    Your logo, colours and name across the admin back office, the merchant console and the hosted checkout page your merchants' customers see.

  2. Your domain

    The back office and the merchant console run on a domain you choose, such as console.yourbrand.com, not on ours.

  3. Admin back office

    Run merchants, transactions, pay-outs, settlements, provider accounts and risk rules from one back office, with roles and permissions for your team.

  4. Merchant onboarding

    Open merchant accounts, set their limits and risk rules and issue their API keys. Merchants integrate the API or send customers to the hosted checkout.

  5. Settlement views

    Collected pay-ins are calculated into settlement balances every 30 minutes, and settlements and withdrawals are recorded where you and your merchants can see them.

White label · how it works

From request to your first merchant.

Five steps, delivered in 10 days from kickoff. Kickoff follows the review of your business and signed terms.

  1. 01

    Request

    Tell us your company, the markets you need, your expected volume band and your use case. Apply for several markets at once.

  2. 02

    Review

    We review your business, its ownership and the corridors you asked for, and agree terms in writing.

  3. 03

    Configure

    We set up your brand, your domain and your admin back office, with your team's roles.

  4. 04

    Onboard

    You open merchant accounts. Merchants integrate the API or use the hosted checkout.

  5. 05

    Operate

    You run merchants, pay-outs and settlement from your back office. We run the rails.

The platform

The orchestration layer, behind every rail.

Routing, settlement, webhooks, provider management and reporting, run from the admin back office and the merchant console.

Rule-based routing

Pay-ins are routed across your provider accounts by configured rules, round robin or percentage split.

Settlement engine

Collected pay-ins are calculated into your settlement balance every 30 minutes, with settlements and withdrawals recorded in the console.

Webhook engine

Pay-in and pay-out results are posted to your webhook URL and retried up to three more times. Confirm each with a status call.

Provider management

Add, edit and activate provider connectors and accounts from the back office, and set their limits.

Dashboard analytics

Totals, success and failure counts, balances and last-hour reports, calculated when the page loads.

Admin back office

Operators run merchants, transactions, pay-outs, settlements, providers and risk rules from one back office.

Merchant console

Merchants see pay-ins, pay-outs, settlements, API keys, webhooks and IP allow-list settings in one place.

Hosted checkout

A hosted page with a QR code, UPI app buttons and a countdown.

Developers

Five calls. Documented as they behave.

Create a pay-in, check it, send a pay-out, check it, read your balance. Results arrive by webhook; the docs say plainly where the API is still rough.

One base URL

api.payeeglobal.com, with your API key as a Bearer token on every call.

Encrypted requests

Pay-in and pay-out fields travel AES-256-CBC encrypted under your secret hash.

Webhook, then confirm

Confirm each webhook with a status call before you act on it.

Status in the body

Most answers use HTTP 200. Read status in the body; only authentication failures use 401.

Read the API documentation

POST /v2/upi/status
curl -sS -X POST 'https://api.payeeglobal.com/v2/upi/status' \
  -H 'Authorization: Bearer <API_KEY>' \
  -H 'Content-Type: application/json' \
  -d '{"merchant_order_id":"<merchant_order_id>"}'
Response · HTTP 200
{
  "status": "success",
  "merchant_order_id": "ORDER-10001",
  "transaction_id": "T4K2Q9ZB1790000000000",
  "amount": "100.00",
  "utr": "000000000000"
}
The consoles

One back office. Every screen in your colours.

Dashboard, merchants, transactions, pay-outs, routing, settlement and branding. Drag the ring, or open the clickable demo with sample data.

Dashboard
console.yourbrand.com/dashboard
Dashboard screen of the admin back office, values hidden
console.yourbrand.com/merchants
Merchants screen of the admin back office, values hidden
console.yourbrand.com/transactions
Transactions screen of the admin back office, values hidden
console.yourbrand.com/payouts
Pay-outs screen of the admin back office, values hidden
console.yourbrand.com/routing
Providers & routing screen of the admin back office, values hidden
console.yourbrand.com/settlement
Settlement screen of the admin back office, values hidden
console.yourbrand.com/settings/branding
Settings & branding screen of the admin back office, values hidden
Open the clickable demo Screens use placeholder values. The demo runs on sample data and is not connected to any production system.
Onboarding

One integration, not one per rail

Adding a market later is a configuration change, not a new build.

Step 1

KYB and site review

Operating entity verified, each URL reviewed and approved one by one. High-risk categories are the expected case, not an escalation.

Step 2

Accounts open

Pay-in, pay-out and settlement accounts opened; API key, secret hash and console access issued.

Step 3

API integration

Integrate the documented API or use the hosted checkout. Your developers work from the same docs we publish.

Step 4

Test and launch

Small real transactions on each enabled corridor, then production traffic.

Approved traffic

iGaming, betting, sportsbook and forex are the categories this gateway is built for. Fraud-type merchants are refused outright and terminated on discovery, so your funds are not pooled behind someone else's book.

Site-by-site approval

Every app and URL is reviewed one by one before it takes traffic. If you are an aggregator, the same standard applies to your merchants.

Terms fixed before launch

Reserve, settlement cycle, limits and dispute handling are agreed in writing before the first transaction. No mid-season re-pricing.

Disputes in writing

How a disputed order is evidenced, held and released is part of the terms you sign, not a policy we change later.

A policed book

Fraud-type merchants are refused, and terminated with funds frozen on discovery. That standard is what keeps the rails open for everyone on them.

Security

Controls merchants switch on themselves.

Six controls, in the merchant console and the admin back office.

API keys

Each merchant gets an API key and an encryption key. The API key can be reset from the console at any time.

Two-factor sign-in

Merchants turn on two-factor sign-in with an authenticator app or an emailed code.

Roles and permissions

Back-office users get roles and permissions; merchants add sub-users with their own permissions.

IP allow-listing

Merchants restrict API calls to their own server addresses. Anything else is refused.

Risk controls

Block lists for email, UPI ID and user, with per-transaction and daily amount limits per account.

Encrypted requests

Pay-in and pay-out request fields are encrypted with AES-256-CBC under a key held by the merchant.

Start here

Send us your two
worst-performing
corridors.

Tell us the markets where deposits fail or withdrawals stall. We come back with the corridors we can run for you, the settlement terms and the commercials, before you sign anything.

Reselling payments under your own brand? Request a white label.