Payment gateway for international payments — direct acquiring with global card reach.
BazPay is a regional payment gateway that authorises internationally issued cards on one direct acquiring contract. Present prices in more than twenty currencies at checkout, authorise on our regional licence and settle to your local settlement account. One MID, one integration, one dashboard for global card traffic.
Built for regional-domiciled merchants selling internationally: e-commerce sellers, subscription software firms and professional-services businesses. No per-market PSP to stitch together and no aggregated MID sitting between you and the card networks.
Why regional acquiring works for international card acceptance
Global card networks paired with a single regional acquiring contract solve the two problems merchants selling across borders trip over first: fragmented MIDs and per-region gateway integrations.
-
One regional MID reaches every card network globally
Visa, Mastercard, Cartes Bancaires and eftpos are global networks. Because BazPay clears traffic on a regional acquiring licence, a card issued outside the region authorises on the same contract as a domestically issued card — and settles into the same balance you pay out from.
-
Multi-currency presentment on one integration
Present prices to shoppers in their own currency at checkout and settle back in EUR into your local settlement account. No per-market gateway, no separate contract per presentment currency.
-
Cross-border 3-D Secure 2.2 already handled
Authentication is applied to regional-issued cards; foreign issuers run through their own equivalent step-up when they require it. The exemption engine picks the right path per issuer, so friction only lands where a network requires it.
-
One dashboard for global card traffic
Approvals, declines, disputes and settlement per card scheme visible in real time — filtered by BIN country, issuer bank or presentment currency. Reconciliation stays uniform across markets.
Coverage across networks, wallets and presentment currencies
Four coverage groups sit under one merchant contract. The card networks reach globally; the local payment methods sit alongside for regional markets; presentment currencies span the major FX corridors most regional sellers actually use.
-
Networks
Global card network reach on one regional MID
Visa and Mastercard authorise cards issued anywhere in the world. Cartes Bancaires, eftpos and Interac Debit cover their respective footprints. All three sit on your named regional merchant identifier — no per-market MIDs to stitch together.
- Visa
- Mastercard
- Cartes Bancaires
- eftpos
-
Wallets
Tokenised device wallets
Apple Pay and Google Pay ride the same card rails through wallet-supplied network tokens. Popular with cross-border mobile checkouts because the wallet resolves the currency and country automatically.
- Apple Pay
- Google Pay
-
Local APMs
Local alternative payment methods
For regional-issued shoppers, local payment methods sit alongside card acceptance under the same contract. Turn each on from the dashboard per market you serve.
- iDEAL
- Bancontact
- BLIK
- Pay by bank
- PayTo
- Interac
-
Currencies
Multi-currency presentment
Authorise in the shopper's currency and settle in EUR by default; named settlement currencies are available for approved corridors. Reporting keeps the presentment currency and the settled amount as separate fields on every charge.
- EUR
- EUR
- EUR
- AUD
- CAD
- GBP
- 20+ more
The wider international topic on international payment. Method-by-method depth on card and APM processing.
The life of a cross-border card charge
Six stages describe how a shopper's card, issued outside your home market, becomes a settled dollar on your bank account. Every stage is visible in the dashboard and each stage change fires a signed webhook.
-
Present
Checkout renders in the shopper's currency and language. The charge request records both the presentment currency and the amount.
-
Route
The processor identifies the issuer country from the BIN and picks the routing path with the best recent approval history for that range.
-
Authenticate
3-D Secure 2.2 runs on regional-issued cards where PSD2 requires it; foreign issuers step up only when their own rules ask for it.
-
Authorise
The tokenised charge posts to the card scheme with the authentication result bound to it. Non-regional issuers see the same request shape as regional issuers.
-
Capture
Capture at once or later. Partial captures and partial refunds both post cleanly in the presentment currency.
-
Settle
Funds reconcile per scheme cycle and land in your local settlement account in EUR by default. Presentment vs settlement is kept explicit on every line.
One regional acquirer vs stitching a PSP per region
The alternative to a single regional acquirer with global card reach is one PSP per region, each with its own MID, its own reporting shape and its own dashboard. The comparison below shows where the trade-off lands after go-live.
| Dimension | BazPay (one regional acquirer) | Per-region PSP stack |
|---|---|---|
| Card reach | Global (Visa/Mastercard network-wide) | Region-locked, per-PSP |
| MID structure | One named regional MID for all traffic | One MID per market |
| Presentment currency | 20+ currencies, one integration | Per-region gateway to add each |
| Settlement | EUR into your local settlement account, per scheme cycle | Multi-currency balances to manage |
| Reporting | One dashboard, per-BIN filter | One dashboard per PSP |
| 3-D Secure | 3-D Secure 2.2 with exemption logic | Varies per PSP |
| Underwriting | Merchants across the EU, UK, Australia, Canada and New Zealand, one contract | Broad, per-region contracts |
Rate structure on the pricing page. Boarding on merchant acquiring. Network platform view on network payment gateway.
Features engineered for cross-border acceptance
Every capability below ships on the standard integration. No premium tier gates BIN filtering, network tokens or interchange++ reporting — the primitives cross-border merchants need are default.
-
BIN-country awareness
The BIN tells the gateway which country the card was issued in. Reporting, fraud rules and 3-D Secure logic all get the issuer country as a first-class field.
-
Presentment currency
Charge in the currency the shopper expects. The charge object stores presentment and settlement amounts side by side for finance reconciliation.
-
3-D Secure 2.2 engine
Frictionless flow first, challenge only when the issuer or your rules require it. Exemption logic runs automatically on domestic cards.
-
Network tokens
Visa and Mastercard network tokens refresh automatically after card reissue, keeping subscription renewals alive across borders.
-
Hosted fields
Card, expiry and CVC inputs served from our PCI environment inside your checkout — merchant SAQ A regardless of the shopper's country.
-
Signed webhooks
HMAC-signed, replay-protected events for every state change; delivery retries handle cross-region network hiccups.
-
Interchange++ reporting
Interchange, scheme fees and gateway margin appear on every settled charge, so cross-border interchange stays transparent per BIN region.
-
Multi-currency payouts
Settlement in EUR to your nominated IBAN by default; named settlement currencies and SEPA Instant available on approved corridors.
A cross-border charge in the same API shape as a domestic one
The charge object is currency-aware. Send the presentment currency the shopper sees, and the response returns the settled amount alongside. Non-regional issuer? Same request; the gateway resolves 3-D Secure and the interchange bucket per BIN.
POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
"amount": 6900,
"currency": "EUR",
"settlement_currency": "EUR",
"payment_method": "card",
"capture": "auto",
"three_d_secure": "required_if_needed",
"metadata": { "order_id": "ORD-10842", "ship_country": "JP" }
}The response returns a canonical charge object with the authorisation code, the network it landed on, the BIN country and the exemption applied. Full schema in the API reference.
Who runs cross-border payments through BazPay
The four merchant profiles below already accept international card traffic on BazPay-shaped flows. Each shares the same API surface, event stream and reporting model — the mix of markets and currencies differs.
-
Multi-country EU, UK and Commonwealth e-commerce
DTC brands selling across regional markets and receiving traffic from further afield. Local card acceptance for local shoppers, cross-border acceptance for the rest.
-
Subscription software
SaaS teams with paying customers on every continent. Network-tokenised renewals survive cross-border card reissue without silent churn.
-
Professional services
B2B service firms invoicing international clients on higher tickets, with named-payer trust lists and enforced 3-D Secure 2 over a threshold you set.
-
Digital publishers
Global membership and paywall sales reconciled per SKU on one MID. Metadata carries the buyer country through settlement.
Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM — regardless of the shopper's country. BazPay is not a merchant of record and not a marketplace of third-party PSPs.
Security and compliance across borders
Card handling runs inside a PCI DSS Level 1 environment assessed each year. Hosted fields and gateway-side vaulting keep merchant scope at SAQ A regardless of the shopper's country. Authentication runs on regional-issued cards with exemption logic; cross-border issuers follow their own equivalent step-up when they require it. In-region data residency is default under GDPR.
- PCI DSS Level 1
- Annual assessment on the acquiring and gateway environment
- Merchant SAQ A
- Hosted fields and gateway vault keep card data out of your stack
- Authentication
- 3-D Secure 2.2 with automatic exemption logic on regional-issued cards
- GDPR
- In-region data residency; DPA on request
- SEPA / SEPA Instant
- Direct participation for merchant payouts in supported corridors
Questions cross-border merchants ask first
What is a payment gateway for international payments, and where does BazPay sit?
A payment gateway for international payments is a platform that lets a merchant accept card payments from shoppers located anywhere in the world, present prices in multiple currencies and settle back into the merchant's own bank. BazPay is that gateway for regional-domiciled merchants: authorisation runs on our regional acquiring licence, but the card networks (Visa, Mastercard) are global — so international-issued cards clear on the same contract.
Is BazPay an Indian payment gateway for international transactions?
No. BazPay is a regional payment gateway operated by NEWERA PAYMENT TECHNOLOGIES LTD; it is not licensed as a payment aggregator by the Reserve Bank of India. Merchants domiciled in India that need to accept international transactions on an RBI-licensed gateway should look for a locally licensed provider. BazPay is a fit when the merchant's legal entity is in-region and the customer base is international.
Can BazPay board cross-border merchants as a payment gateway for international merchants?
BazPay boards merchants whose legal entity meets regional underwriting criteria. That typically means a locally registered company. A cross-border-domiciled merchant selling into the regional is generally not in scope; a genuine regional-established entity — even one owned by a cross-border parent — usually is. Fit is confirmed during KYC on a case-by-case basis.
Which currencies can we present to shoppers?
Card authorisation runs in EUR and more than twenty presentment currencies including EUR, EUR, AUD, CAD and GBP. The charge object records both the presentment currency and the settled amount, so your finance stack sees each side of the FX conversion as a distinct field.
How does settlement work for cross-border card payments?
Funds settle from our regional acquiring balance into your local settlement account in EUR by default, per scheme cycle. Named settlement currencies and instant payout routes are available on approved corridors — the specific list is confirmed during boarding and lives on the pricing page.
How is 3-D Secure handled for foreign-issued cards?
Authentication and the associated 3-D Secure 2.2 flow are mandatory for regional-issued cards where an exemption does not apply. Non-regional issuers step up to their own equivalent when their scheme rules require it, and remain frictionless when they do not. The exemption engine picks the correct path per BIN, so friction only lands where a network insists on it.
Is this suitable for restricted international verticals?
No. BazPay is scoped to merchants in the EU, UK, Australia, Canada and New Zealand — e-commerce sellers, subscription software firms, professional-services businesses and digital publishers. BazPay does not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants regardless of the shopper's country.
How does chargeback attribution work across borders?
Because you hold a named regional MID, cross-border chargebacks are attributed to your entity rather than diluted across a pool. The signed dispute event includes the 3-D Secure result, the BIN country and any metadata you sent at charge time, so the evidence packet is pre-assembled for the scheme's current template.
Accept international card payments on one regional contract
Share your markets, presentment currencies and monthly volumes. A named engineer will confirm boarding fit and map the FX and settlement configuration inside one working day. See also accept online payments, payment processors and payments solutions.