Cross-border payments on one direct acquiring contract.
BazPay is a direct regional acquirer, and the card networks are global. Cards issued outside the regional authorise on the same contract as domestic ones, settle into the same EUR balance and pay out to the same local settlement account. Presentment across twenty-plus currencies keeps the shopper's checkout local.
Built for merchants across the EU, UK, Australia, Canada and New Zealand — e-commerce sellers, subscription software firms, professional services and digital publishers — that already serve international customers or plan to. No reseller PSP layer between you and the scheme.
Why direct regional acquiring works for cross-border card traffic
Four properties matter more on cross-border charges than on domestic ones — the interchange break-out, the 3-D Secure behaviour, the chargeback attribution and the settlement balance. All four are default on BazPay, not premium options.
-
Cross-border card reach on one contract
A card issued outside the region authorises on the same BazPay contract as a domestic one. The acquiring licence is local; the card networks are global. No secondary MID or reseller stack for international traffic.
-
Multi-currency presentment, single settlement balance
Charge in EUR or the shopper's local currency across more than twenty presentment currencies. Funds reconcile into an EUR settlement balance that pays out to your local settlement account per scheme cycle.
-
Cross-border interchange visible line by line
Cross-border and cross-region fees appear as their own lines on interchange++ statements — never blended into a headline rate. Finance teams see exactly what the cross-border share of a settlement cost.
-
Authentication and issuer scoring on international cards
3-D Secure 2.2 runs on every card charge with PSD2 exemption logic where the rules allow. Cross-border authentication carries the same authentication result to the acquirer and remains as dispute evidence.
The four dimensions of a cross-border card charge
Every cross-border transaction lives on the intersection of four dimensions. Below is how the BazPay platform resolves each one, so your integration does not have to.
-
Reach
Issuing country vs acquiring country
The acquiring bank is BazPay in-region. The issuing bank can be anywhere the schemes run. That combination decides the cross-border flag on the transaction, the interchange bucket and the exemption path — all resolved by the platform, not by your integration.
- Regional acquiring
- Global schemes
- Cross-border flag
-
Currency
Presentment vs settlement currency
Present the price in the shopper's currency at checkout; settle to your local settlement account in EUR. FX runs on scheme wholesale rates with the currency-conversion line broken out on the statement.
- Presentment 20+
- Settlement EUR
-
Rules
Cross-border scheme rules and 3-D Secure
Cross-region traffic follows scheme cross-border rules and authentication — 3-D Secure 2 with exemption logic. Rules-of-record are enforced by the platform, not left as a merchant checklist.
- Scheme rules
- Authentication
- MIT exemptions
-
Disputes
Chargeback attribution across borders
A named MID means cross-border chargebacks attribute to your entity, not to a shared pool. Evidence packets include the authentication result and any fulfilment metadata you sent on the charge.
- Named MID
- 3-D Secure evidence
- Metadata
Method depth on card and APM processing. The wider international framing on international payment and international payment gateway.
The life of one cross-border authorisation
Six stages sit between the shopper picking a currency and the settled dollar. Each stage change fires a signed webhook so your ledger stays in sync across borders.
-
Present
Checkout script shows the price in the shopper's currency using your configured presentment list — the same charge object regardless of the currency chosen.
-
Score
Fraud rules and PSD2 exemption logic decide the 3-D Secure path based on issuing country, BIN metadata and merchant history.
-
Authenticate
3-D Secure 2.2 runs when the risk earns it; frictionless when the exemption logic allows. Cross-border result binds to the authorisation.
-
Authorise
Card is posted to the scheme through BazPay's regional acquirer. The response returns the network code and cross-border flag on the same charge object.
-
Convert
Non-EUR presentment amounts convert at the scheme wholesale rate; the currency-conversion line is stamped on the settled transaction.
-
Settle
Funds land in your local settlement account in EUR per scheme cycle with interchange++ line detail — cross-border, cross-region and scheme fees all separate.
Direct regional acquirer vs stitched regional PSPs
The alternative to one direct acquirer is a stack of regional PSPs stitched together for cross-border reach. That stack can be fast to sign, and it multiplies the integration and reconciliation load once cross-border volume becomes material.
| Dimension | BazPay (direct regional acquirer) | Stitched regional PSPs |
|---|---|---|
| Contract | One direct regional acquirer for all card traffic | Regional PSPs stitched per country |
| Card reach | Cards issued globally on the same MID | Non-supported issuers routed away or declined |
| Presentment | EUR + 20 more, dashboard-configurable | One per PSP; add another to add a currency |
| Reporting | Interchange++ with cross-border split | Blended monthly summary |
| Chargeback attribution | Attributed to your named MID | Diluted across an aggregated pool |
| 3-D Secure | 3-D Secure 2.2 + PSD2 exemption logic | Blanket 3DS or none |
Rate structure on the pricing page. Buyer's shortlist on payment processors; the boarding side on merchant acquiring.
Features that matter on cross-border card traffic
Every capability below is on the standard integration. Turn features on with a request flag or a dashboard toggle — cross-border readiness is not gated behind an enterprise tier.
-
Multi-currency presentment
EUR plus more than twenty presentment currencies. Configure per market from the dashboard — one integration, no per-currency code change.
-
Regional acquiring on our licence
Cards issued globally authorise on BazPay's own regional acquiring licence. No reseller layer between the merchant and the scheme network.
-
Network tokens across borders
Visa and Mastercard network tokens refresh automatically after a card reissue, wherever the card was issued — cross-border card-on-file stays alive.
-
3-D Secure 2.2 with exemptions
Authentication runs with automatic exemption logic. Cross-border risk analysis and MIT exemptions applied where scheme rules permit.
-
Interchange++ per settlement
Every settled transaction breaks out interchange, scheme fees and processor margin — cross-border and cross-region components are separate lines.
-
Real-time decline data
Approval, decline and retry outcomes visible within seconds — cross-border BIN or issuer patterns show up before they become a monthly report.
-
Signed webhooks
HMAC-signed, replay-protected events for every state change. Cross-border and domestic events share the same envelope and signing scheme.
-
Dispute defence packet
authentication result, fulfilment webhook confirmation and charge metadata pre-assembled to the scheme's current template for cross-border chargeback cases.
A cross-border charge, expressed in the same API call
The API does not have a separate endpoint for cross-border payments. Attach the presentment currency and any market metadata to the charge; the platform resolves the cross-border flag, the exemption path and the interchange bucket. The response object keeps the same shape as a domestic charge.
POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
"amount": 4990,
"currency": "EUR",
"settlement_currency": "EUR",
"payment_method": "card",
"capture": "auto",
"three_d_secure": "required_if_needed",
"metadata": { "market": "US", "order_id": "ORD-10842" }
}The response returns the network authorisation code, a cross_border boolean, the 3-D Secure exemption applied and the currency-conversion line reference. Complete schema in the API reference.
Where cross-border payments earn their keep
The four merchant profiles below serve international customers today or plan to as they expand markets. All four use the same platform primitives — the reporting emphasis differs by business model.
-
Multi-country e-commerce
DTC brands and multi-country storefronts serving shoppers across our markets and beyond. One acquirer for domestic and cross-border card acceptance.
-
SaaS with global customers
Subscription software billing card-on-file customers in and out of the regional. Network tokens keep renewals alive after cross-border card reissues.
-
Digital publishers
Membership sites, ebooks, courses and streaming subscriptions sold to shoppers wherever the schemes run — one payout balance, one dashboard.
-
Professional services
B2B service firms invoicing higher-ticket cross-border charges with named-payer trust lists and enforced 3-D Secure 2 over a ceiling you set.
Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. BazPay is not a merchant of record and not a marketplace of third-party PSPs.
Compliance signals across borders
Card handling 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 scheme cross-border rules are enforced at the acquirer layer. 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
- Scheme rules
- Visa VIRP and Mastercard SPoC/PCI-CP registered where required
Questions merchants ask about cross-border payments
What counts as cross-border payments on BazPay?
A cross-border payment is any authorisation where the issuing country of the card differs from the acquiring country. BazPay is a regional acquirer, so any card issued outside the region that authorises on BazPay generates a cross-border transaction. The platform resolves the cross-border flag, the interchange bucket and the exemption path automatically — nothing to configure per corridor.
How does cross-border payment processing differ from domestic on BazPay?
Technically, the API call is identical. Commercially, cross-border charges carry a different interchange bucket and — for cross-region traffic — additional scheme fees. Those show up as their own lines on interchange++ reporting, so a finance team can see the cross-border cost of a settlement without doing arithmetic on a blended rate.
Does BazPay handle FX for cross-border payments?
BazPay supports multi-currency presentment (charge in the shopper's currency) with settlement to a regional settlement account in EUR. Currency conversion runs at the scheme wholesale rate and is stamped on the settled transaction. BazPay is a payment gateway and regional acquirer — not an FX broker, not a currency-hedging service and not a merchant of record for FX-facing verticals like forex trading or CFDs, which are out of scope for underwriting.
How does cross-border payments regulation apply through BazPay?
Card authorisation on the BazPay side runs under authentication with 3-D Secure 2.2 and exemption logic, and card handling sits inside PCI DSS Level 1. Scheme cross-border and cross-region rules are enforced at the acquirer layer. Non-payment regulatory obligations that apply to your business — sanctions screening on shoppers, VAT/OSS on digital-goods sales, consumer disclosures in your jurisdictions — remain with your legal entity.
Which countries and currencies are supported for presentment?
Authorisation runs in EUR plus more than twenty presentment currencies. Settlement defaults to EUR into a regional settlement account. Named settlement currencies and additional corridors are available on approved routes and confirmed during boarding — the current schedule is published on the pricing page.
Where do cross-border payments fintech and BazPay overlap?
Fintech SaaS businesses that bill international customers (accounting, expense, treasury, insurance and wealth software) use BazPay as the acceptance layer for their own subscription revenue. Cross-border card traffic on those subscriptions runs on the same BazPay MID as domestic. See the fintech payment solutions page for the SaaS-billing angle.
How are chargebacks handled on cross-border card charges?
Because you hold a named MID, cross-border chargebacks are attributed to your entity — not diluted across a pool. Scheme dispute events fire as signed webhooks with the transaction, the 3-D Secure 2 result and any fulfilment metadata you sent at charge time. Evidence packets are pre-assembled to the scheme's current template for one-click submission.
Which merchant types are eligible for cross-border acceptance on 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 does not act as a marketplace of third-party PSPs.
Scope your cross-border card acceptance today
Share your target markets, existing acquirer and monthly cross-border volume. An integration manager will confirm boarding fit and map presentment currencies and corridors inside one working day.