An international payment gateway for merchants selling across borders.
BazPay is a direct regional acquirer that accepts card traffic from international shoppers on the same contract as your domestic volume. Multi-currency presentment, PSD2-compliant strong authentication and interchange++ reporting on every settled cross-border charge.
Built for EU, UK and Commonwealth e-commerce sellers, subscription software firms and professional-services businesses invoicing international clients. One contract, one API, one dashboard — settlement lands in your local settlement account regardless of where the shopper sits.
Why regional acquiring beats offshore aggregation for cross-border sellers
An offshore aggregator promises fast onboarding for international traffic. A direct regional acquirer trades that speed for named-MID reporting, cleaner chargeback attribution and settlement into your own local settlement account. Four properties make the trade-off worth it.
-
Regional acquiring, international card reach
The licences are local; the card networks are not. A card issued outside the region authorises on the same acquiring contract as a domestic one and settles into the same balance you pay out from — no offshore MID to explain.
-
Multi-currency presentment on one integration
Authorise in EUR and more than twenty other presentment currencies without wiring per-country gateways. The response object shape stays stable across currencies.
-
Authentication and international 3-D Secure 2
PSD2 exemption logic runs on every card charge. When an international issuer requires a challenge, 3-D Secure 2.2 handles the step-up and binds the result to the charge for liability shift.
-
One dashboard for cross-border reporting
Interchange++ line detail shows scheme fees per region, per BIN country and per currency. Finance teams reconcile international traffic against the source, not against a blended rate.
What the international payment gateway reaches
Four families cover the international traffic a regional merchant realistically sees: global cards, tokenised wallets, local payment methods for cross-border shoppers paying in a local channel, and multi-currency presentment.
-
Schemes
Global card scheme membership
Visa, Mastercard, Cartes Bancaires and eftpos acquire on our regional licence. Cards issued anywhere the schemes reach authorise on the same contract — the acquiring is local, the networks are global.
- Visa
- Mastercard
- Cartes Bancaires
- eftpos
-
Wallets
Tokenised international wallets
Apple Pay and Google Pay ride the same card rail worldwide, supplying a network token that keeps the PAN out of your servers regardless of where the shopper is.
- Apple Pay
- Google Pay
-
Local methods
Local alternative payment methods
Local methods sit alongside international card acceptance under one merchant contract, so a Dutch iDEAL shopper and a Polish card checkout resolve on the same charge object.
- iDEAL
- Bancontact
- BLIK
- Pay by bank
- PayTo
- Interac
-
Currencies
Multi-currency presentment
Authorise in the shopper's currency across EUR and more than twenty other presentment currencies. Settle in EUR to your nominated IBAN by default; named settlement currencies available on approved corridors.
- EUR
- GBP
- AUD
- CAD
- NZD
- 20+ more
Method depth on card and APM processing. The acquiring contract itself on merchant acquiring. Wider international payment topics on international payments.
The life of a cross-border card charge
Six stages sit between an international shopper's tap and a settled dollar in your regional settlement account. Each stage is visible in the dashboard and each stage change fires a signed webhook.
-
Collect
Hosted fields or a hosted checkout page capture the card inside our PCI environment, regardless of the shopper's country.
-
BIN check
BIN metadata identifies the issuing country and card programme so risk scoring and 3-D Secure logic can react to a cross-border profile.
-
Score
The fraud engine grades the order against your rules and your merchant history — cross-border signals are weighted per your policy.
-
Authenticate
3-D Secure 2.2 runs when the risk earns it. PSD2 exemption logic keeps most international checkouts frictionless.
-
Authorise
The charge posts to the acquirer on your named MID; the international issuer authorises across the scheme network.
-
Settle
Funds reconcile per scheme cycle and land in your local settlement account. Interchange++ line detail shows the international fee structure per transaction.
Direct regional acquirer vs offshore aggregator for international traffic
Two credible routes exist for accepting international card traffic as a regional merchant: a direct regional acquirer with global scheme reach, or an offshore aggregator on a shared MID. Where each route earns its keep is on the axes below.
| Dimension | BazPay (direct regional acquirer) | Offshore aggregator |
|---|---|---|
| Acquirer location | Direct regional acquirer | Offshore aggregator |
| Contract | One contract with BazPay | Chain of local sub-processors |
| MID structure | Named MID per merchant | Shared MID pool |
| Authentication | 3-D Secure 2.2 with exemption logic | Blanket 3DS or none |
| Settlement | Per-scheme cycle to your local settlement account | Delayed aggregated payouts |
| Reporting | Interchange++ per currency and BIN region | Blended cross-border rate |
| Underwriting scope | Merchants across the EU, UK, Australia, Canada and New Zealand (explicit list) | Broad, few exclusions |
Rate structure on the pricing page. Buyer's shortlist context on payment processors and boarding path on merchant acquiring.
Features engineered for cross-border acceptance
Every capability below ships on the standard integration. No premium tier gates international acceptance, PSD2 handling or the multi-currency response object.
-
Global card acceptance
Non-regional-issued cards clear on the same contract as domestic cards; no separate integration for cross-border traffic.
-
Multi-currency presentment
Authorise in EUR plus twenty-plus presentment currencies through the same API — the response shape stays stable.
-
Hosted fields
Card, expiry and CVC inputs served from our PCI environment, so cross-border checkouts keep merchant SAQ A scope.
-
3-D Secure 2.2 engine
Frictionless flow first; challenge only when the international issuer or your fraud rules require it.
-
SEPA / SEPA Instant payouts
Direct SEPA Instant participation for locally denominated payouts; SWIFT and push-to-card available on approved corridors.
-
Interchange++ reporting
Interchange, scheme fees and processor margin split per settled international charge — cross-border rates are transparent.
-
Signed webhooks
HMAC-signed, replay-protected events for approvals, declines, refunds, disputes and payouts across every currency.
-
Real-time decline data
Cross-border decline reason codes visible within seconds so your team can act inside the same hour.
One REST call for domestic and cross-border alike
The charge object does not care whether the shopper's card was issued in Dublin or Berlin. Attach amount, currency and payment method; the response returns a canonical charge object with the authorisation code, the network it landed on, and any exemption applied.
POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
"amount": 4990,
"currency": "EUR",
"payment_method": "card",
"capture": "auto",
"three_d_secure": "required_if_needed",
"descriptor": "ACME EU LTD",
"metadata": { "order_id": "ORD-10842", "region": "NA" }
}Full schema in the API reference. Approval and decline detail across every currency lives in real-time analytics.
Who sells cross-border on BazPay
Four merchant profiles already run international card acceptance on BazPay's regional acquiring rail. Each uses the same charge object, the same signed webhook stream and the same interchange++ reporting.
-
Multi-country e-commerce
Regional storefronts selling to international shoppers on cards, wallets and local payment methods — one contract, one dashboard, cross-border reporting per BIN region.
-
Subscription software
SaaS billing customers worldwide with card-on-file renewals, MIT exemptions on rebills and network-token refresh across international issuers.
-
Professional services
Regional consultancies, agencies and B2B service firms invoicing international clients in the shopper's currency, settling in EUR to your nominated IBAN.
-
Digital publishers
Membership sites, courses and streaming subscriptions billed to a global audience with signed webhooks for instant fulfilment and per-SKU reconciliation.
Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, cold-call or remote-fix tech-support, debt-collection and MLM. BazPay is not a consumer wallet, not a merchant of record and not a marketplace of third-party PSPs.
Security and compliance for cross-border acceptance
The acceptance layer runs inside a PCI DSS Level 1 environment assessed each year. Hosted fields and gateway vaulting keep your annual return at merchant SAQ A. Authentication runs on every card charge with 3-D Secure 2.2 and automatic exemption logic. Regional data residency is default; a DPA is available on request.
- 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 every card charge
- GDPR
- In-region data residency; DPA on request
- Scheme registrations
- Visa VIRP and Mastercard SPoC/PCI-CP where required
Questions merchants ask about international acceptance
How does an international payment gateway route foreign-issued cards?
A card issued outside the region authorises through the card scheme's international rails, but the acquiring contract that clears the transaction is local. BazPay's own regional acquiring licence covers Visa, Mastercard, Cartes Bancaires and eftpos globally, so cross-border authorisations settle into the same balance your domestic traffic does.
Is BazPay an international payment gateway for individuals?
No. BazPay boards registered legal entities under regional merchant underwriting — sole traders and self-employed professionals with a regional business registration can qualify, but personal accounts, consumer wallets and peer-to-peer transfers are not in scope. If you need a consumer-side wallet, BazPay is not the platform for that.
Are there free international payment gateway providers?
No credible international payment gateway is free. Cross-border card acceptance always carries interchange, scheme fees and a processor margin — a "free" claim usually shifts the cost to the shopper as a surcharge or blends it into a higher headline rate. BazPay uses interchange++ so every component is visible on every settled transaction; that is the transparent alternative to a headline "free" claim.
Do you support payment gateway for tech support business models?
Cold-call and remote-fix tech-support businesses are not in scope for BazPay. Inbound B2B IT services under a professional-services model — contracted support for named business clients, managed-service subscriptions, developer-tools subscriptions — can qualify when they meet BazPay's regional underwriting. Boarding is decided case by case on the business model rather than the label.
Which presentment currencies does the international payment gateway support?
Authorisation runs in EUR and more than twenty other presentment currencies. Settlement lands in EUR into your local settlement account by default; named settlement currencies and SWIFT or push-to-card payouts are available on approved corridors. The current schedule is confirmed during boarding and published on the pricing page.
How is authentication handled for international shoppers?
PSD2 exemption logic runs on every card charge — TRA, low-value, trusted-beneficiary and MIT are claimed where the rules allow. When an international issuer requires a challenge, 3-D Secure 2.2 handles the step-up and binds the CAVV to the charge, so liability shift applies to the international transaction the same way it does to a domestic one.
How are cross-border chargebacks handled?
Because you hold a named MID with the scheme, chargebacks are attributed to your entity even on international traffic. The 3-D Secure 2 result, the fraud signals that scored the order and any charge metadata are pre-assembled into the case packet. Dispute events fire as signed webhooks alongside domestic ones.
Can I migrate international card traffic from an existing gateway?
Yes. Vault imports and network-token portability are supported under scheme-approved migrations, subject to the receiving bank's consent letters. Old and new webhook streams typically run in parallel until international traffic is proven on the new stack, so subscription renewals and card-on-file charges continue without interruption.
Accept international card traffic on one regional contract
Share your target markets, monthly volume and existing processor. An integration manager will confirm boarding fit and map the cross-border wiring inside one working day. See also open banking for account-to-account alternatives on cross-border payouts.