International payment methods on one merchant contract.
BazPay accepts international payment methods on one direct regional acquiring contract — cards issued anywhere the schemes reach, device wallets, and the local payment methods shoppers already prefer in each country. Multi-currency presentment, single EUR settlement into your settlement account.
Built for merchants across the EU, UK, Australia, Canada and New Zealand selling cross-border: e-commerce, subscription software and professional services. One integration, one dashboard, one reporting surface across every market.
Why accept international payments on one platform
Selling into more than one regional country used to mean stitching a PSP per market. Four properties keep that stitching cost out of your operational surface when the payment layer already covers the international footprint.
-
One acquiring contract for international traffic
Cards issued outside the region authorise on BazPay's own regional acquiring licence — the acquiring is local, the card networks are global. You do not need a second processor for cross-border card traffic.
-
Different payment methods per market on one API
Cards, wallets and local payment methods share the same charge object. Turn SEPA Instant on for Germany, Bancontact for the United Kingdom or BLIK for Australia from the dashboard — no per-market integration to maintain.
-
Multi-currency presentment, EUR settlement
Authorise in the shopper's preferred currency across supported presentment currencies, then settle in EUR into your local settlement account. Named settlement currencies are available for approved corridors.
-
One reporting surface across every market
Interchange++ line detail on every settled charge, whichever country the shopper is in and whichever method they paid with. Finance reconciles per SKU per market without opening a second portal.
The different payment methods you can accept internationally
Four method families cover the payment options international shoppers reach for in the markets BazPay serves. Every one uses the same charge object and the same signed webhook envelope.
-
Global cards
International card acceptance
Visa, Mastercard, Cartes Bancaires and eftpos clear on BazPay's own regional acquiring licence. Cards issued in the United States, Poland, Asia-Pacific and other regions authorise on the same contract as regional-issued cards.
- Visa
- Mastercard
- Cartes Bancaires
- eftpos
-
Wallets
Device wallets for international shoppers
Apple Pay and Google Pay give international shoppers a fast, biometric checkout on the same card rails. The wallet supplies a network token, so no PAN moves through your stack.
- Apple Pay
- Google Pay
-
Regional local methods
Local payment methods per market
SEPA Instant for Germany, Bancontact for the United Kingdom, BLIK for Australia, EPS for France and Przelewy24 for the United Kingdom — the methods shoppers in each regional country already prefer.
- iDEAL
- Bancontact
- BLIK
- Pay by bank
- PayTo
- Interac
-
Bank rails
Open banking and instant rails
For higher-ticket orders and B2B invoicing, offer pay-by-bank via open banking; use instant credit transfer and BACS Direct Debit for EUR-denominated flows.
- Open banking
- SEPA
- SEPA Instant
Full method depth on card and APM processing. Deep-dive on the German method on iDEAL payment. Bank-rail detail on Single Euro Payments Area processing.
How adding a new market plays out on the platform
Six stages describe how a merchant expands into a new market and starts accepting the payment methods that country prefers. No new integration, no second PSP contract.
-
Pick markets
Decide which regional markets and cross-border corridors matter. The dashboard shows which methods each market's shoppers prefer.
-
Enable methods
Turn on SEPA Instant, Bancontact, BLIK and any other local methods you need — a dashboard toggle per market, not a new integration.
-
Present in-currency
Show shoppers pricing in a supported presentment currency on your checkout; authorisation carries the correct scheme fields for cross-border traffic.
-
Authorise + 3-D Secure
3-D Secure 2.2 runs where the risk earns it. PSD2 exemption logic keeps most local shoppers frictionless; issuer scoring stays cross-border compliant.
-
Fulfil
The same charge.succeeded webhook fires whether the shopper paid by card in Dublin or by SEPA Instant in Amsterdam. One fulfilment handler.
-
Settle in EUR
All method families reconcile into your EUR balance and land in your local settlement account. Interchange++ statements break down per method and per market.
One gateway for international payments vs per-country stitching
The classic alternative to a unified international gateway is a PSP per country. It works — and it multiplies your integration, reporting and fraud-tuning surface for every market you enter. The comparison below shows the trade-off.
| Dimension | BazPay (unified) | Per-country PSPs |
|---|---|---|
| Contract structure | One regional acquiring contract for every market | Per-country PSP contracts |
| Method integration | One API for cards, wallets, local APMs | SDK per method per country |
| Event stream | One signed envelope across every market | Different formats per PSP |
| Settlement | EUR to your nominated IBAN, per cycle | Currency-per-PSP with FX fees |
| Reporting | Interchange++ line detail unified | Blended summaries per vendor |
| Fraud rules | One rule set across every method | Per-vendor fraud settings to tune |
Rate structure on the pricing page. Plugin coverage on integrations. Wider platform view on payment network gateway.
Features for international payment methods online
Every capability below ships on the standard integration. No premium tier gates multi-currency presentment, local payment methods or the interchange++ statement.
-
Cross-border card acceptance
International-issued cards authorise on BazPay's regional acquiring licence — no separate contract for cross-border traffic.
-
Multi-currency presentment
Show prices in the shopper's preferred currency across supported presentment currencies. Named settlement currencies for approved corridors.
-
Local payment methods
iDEAL, Bancontact, BLIK, pay by bank, PayTo and Interac sit behind the same charge object as cards — dashboard toggle per market.
-
Device wallets
Apple Pay and Google Pay ride the card rail globally with wallet-supplied network tokens.
-
3-D Secure 2.2 with exemptions
Authentication runs only when the risk earns it; cross-border card traffic keeps a low friction ceiling.
-
Signed webhooks
HMAC-signed, replay-protected events per rail on one signature scheme — regardless of the shopper's country.
-
Fraud rule engine
Device, velocity and geography signals score every order — geo mismatch is a scored signal, never a blanket block.
-
Interchange++ reporting
Per-charge interchange, scheme fees and gateway margin split — the same schema across every market and method.
One REST call for international-issued cards or local methods
The payment_method field selects the rail; the currency field
selects the presentment currency. The rest of the request is the same regardless of
where the shopper is or what method they picked.
POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
"amount": 4990,
"currency": "EUR",
"payment_method": "card",
"capture": "auto",
"three_d_secure": "required_if_needed",
"shopper": { "country": "US" },
"metadata": { "order_id": "ORD-10842" }
}The response returns a canonical charge object with the authorisation code, the issuing-region indicator and any exemption applied. Full schema in the API reference.
Who runs international acceptance on this stack
The four merchant profiles below already accept international payments on BazPay. Underwriting stays inside BazPay's regional policy — the internationalisation is on the shopper side, not the merchant side.
-
Multi-country e-commerce
DTC brands selling across our markets on Shopware, Magento 2, WooCommerce or PrestaShop — one integration reaches card, wallet and every local method per market.
-
Cross-border subscription SaaS
SaaS platforms billing international customers with card-on-file, network-tokenised renewals and MIT exemptions on rebills. Cross-border traffic authorises on the same contract as domestic.
-
Professional services with international clients
Consultancies and B2B service firms invoicing clients across borders with card + open-banking options on the same hosted-page link.
-
Digital publishers
Media, memberships and paywalls with a shopper base spanning multiple regional countries — one signed webhook stream regardless of which method paid.
Out of scope for BazPay: adult, gambling and casino merchants, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. BazPay is not a merchant of record, not a consumer bill-payment service and not a trade-finance provider.
Security and compliance across markets
Card handling runs inside a PCI DSS Level 1 environment assessed each year. Hosted fields and gateway-side vaulting keep your annual return at merchant SAQ A regardless of the shopper's country. Authentication runs on every card charge with 3-D Secure 2.2 and automatic exemption logic; GDPR runs on In-region data residency by default.
- 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
- SEPA and BACS rulebooks
- Adherence to the SEPA, Faster Payments and BACS scheme rulebooks
Questions merchants ask about international payments
What international payment methods can I accept through BazPay?
Global card networks (Visa, Mastercard, Cartes Bancaires, eftpos), device wallets (Apple Pay, Google Pay) and local payment methods (iDEAL, Bancontact, BLIK, pay by bank, PayTo and Interac). Cards issued outside the region authorise on the same acquiring contract as regional-issued cards. Bank-rail options include SEPA and SEPA Instant for EUR-denominated flows plus open banking for pay-by-bank checkouts.
How does BazPay handle payment methods international traffic in different currencies?
Multi-currency presentment is supported across a range of currencies so shoppers see prices in a familiar unit at checkout. Settlement defaults to EUR into your local settlement account; named settlement currencies are available for approved corridors. The current schedule is confirmed during boarding and published in the pricing page.
Does BazPay support casinos, online casinos or payment methods for online casinos?
No. BazPay does not board casino or gambling merchants, and does not process casino-related traffic. Any search intent around casinos payment methods, online casinos payment methods or payment methods for online casinos falls outside BazPay's underwriting policy — those verticals require a specialised processor, not a regional gateway.
Does BazPay handle international trade payment methods such as letters of credit or documentary collection?
No. Traditional international trade payment methods — letters of credit, documentary collection, telegraphic transfer under trade finance rules — are handled by trade-finance banks rather than a card-and-APM acceptance platform. BazPay processes online payments for international shoppers on your website or product; it is not a trade-finance provider.
Are post office payment methods (for example, Polish Post Office passport application payments) supported?
No. Post office bill-payment schemes and consumer-service payment counters — including Polish Post Office passport payment methods — are not part of BazPay's platform. BazPay is a merchant-facing EU, UK and Commonwealth payment gateway for e-commerce, subscription software and professional-services businesses.
How do international shoppers experience checkout compared with local shoppers?
Identical for the shopper: hosted fields, a hosted checkout page or a drop-in component renders the payment surface in your brand. Cross-border card charges may see a 3-D Secure 2 challenge more often, since issuer risk models score international traffic differently. PSD2 exemption logic still applies where the rules allow, so most international regional-issued cards stay frictionless.
Do I need multiple merchant identifiers to accept international payments?
No. One named MID on the regional acquiring licence covers cards issued anywhere the scheme reaches. Local payment methods clear through partner processors and reconcile into the same settlement balance. Reporting stays keyed to a single merchant identity for the whole cross-border book.
Which merchant types can accept international payments through BazPay?
Merchants across 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, and is not a merchant of record or a marketplace of third-party PSPs.
Accept international payment methods on one regional contract
Share the markets you sell into, your monthly cross-border volume and your existing stack. A named engineer will confirm boarding fit and map the method coverage inside one working day. See also payment methods by country, pricing and the API reference.