International payment processing for EU merchants.
BazPay handles the international payment flow end to end. Accept cards, wallets and local methods from shoppers outside your home market, then send payouts to beneficiaries in supported corridors — through one EU payment gateway, one REST API and one dashboard.
Built for EU e-commerce sellers, subscription software firms and professional-services businesses that trade across borders. Multi-currency acceptance, SEPA and SWIFT payouts, and FX quoted with the reference rate and the applied margin printed on every line.
Why merchants run cross-border volume on BazPay
The same platform authorises the inbound charge, executes the FX conversion and pushes the outbound payout. That removes the treasury handoff between the PSP and the bank — the place where most business international payment work loses time and money.
-
One gateway for cross-border acceptance
Charge non-EU-issued cards on the same acquiring contract that clears your domestic card volume. Wallets and EU local methods share the same charge object and the same signed webhook.
-
Two-way FX transparency
Every international payment order shows the reference rate, the applied margin and the executed rate on the same line. Finance teams reconcile against a single source, not a blended statement.
-
Rails matched to the corridor
SEPA and SEPA Instant for euro area, SWIFT for reach, push-to-card for named corridors. The payout picks the fastest supported rail for the beneficiary you enter, not a lowest-common denominator.
-
One tracker for every leg
The API returns a stable identifier for each cross-border leg, plus the SWIFT UETR when applicable. Wire it into your dashboard, your CRM or your customer's account and every transfer is traceable end to end.
Accept, convert, send, track
Four flows share the same platform. Turn any of them on from the dashboard — no new contract, no additional integration, no separate ledger to reconcile.
-
Accept
Receive international payment
Non-EU shoppers pay by international payment card, device wallet or a local method. Authorisation runs against your MID and clears into the same settlement balance as EU volume.
- Cards
- Wallets
- EU APMs
-
Convert
Multi-currency conversion
Present prices in the shopper's currency and settle in EUR, or hold selected named currencies for approved corridors. The applied margin is published, not opaque.
- EUR
- GBP
- USD
- SEK
- PLN
-
Send
Send international payment
Trigger a payout from the API or the dashboard. The platform picks the fastest supported rail for the beneficiary. Signed webhooks confirm each stage of the transfer.
- SEPA Instant
- SWIFT
- Push-to-card
-
Track
International payment tracker
Every leg has a status, an end-to-end identifier and an itemised fee breakdown. Export the register as CSV or subscribe to state-change webhooks in real time.
- Status
- UETR
- Fees
Deeper on the acceptance side: card and APM processing and merchant acquiring. Deeper on the send side: payouts and open banking.
The international payment transfer, step by step
Six stages between the quote request and the reconciled statement. Each stage emits a signed webhook, so your systems stay in sync without polling.
-
Quote
Fetch a quote on the target currency. The response includes the reference rate, applied margin and expiry timestamp.
-
Authorise
For inbound, the charge is authorised on the acquiring rail. For outbound, funds are earmarked against the source balance.
-
Convert
The FX conversion executes at the quoted rate if the quote is still valid, otherwise at the fresh reference plus published margin.
-
Route
Payouts pick the fastest supported rail for the beneficiary — SEPA Instant, SEPA, SWIFT or push-to-card where enabled.
-
Track
Each leg emits a status webhook and updates the international payment tracker with the corridor's own reference where available.
-
Reconcile
Statements break out fees, FX margin and the executed rate per transaction so treasury and accounting close cleanly.
Features that make cross-border cheaper to run
Every capability below ships on the standard integration. Turn features on with a request flag or a dashboard toggle. No enterprise-tier gate on the primitives.
-
Multi-currency acceptance
Present prices in more than twenty currencies. Authorisation, capture and refund all round-trip on the same charge object.
-
FX quote API
Lock a rate for a short window before authorisation or payout. Every quote returns the reference rate and the published margin.
-
SEPA and SEPA Instant
Direct participation for euro-area payouts in supported corridors. SEPA Instant clears in seconds, SEPA in a working day.
-
SWIFT payouts
Correspondent-bank reach for non-euro corridors on approved routes. Every payout carries a UETR for end-to-end tracing.
-
Push-to-card
Send funds directly to eligible Visa or Mastercard debit cards where the corridor permits — often within minutes.
-
Cross-border refunds
Refunds route back to the original method in the original currency. FX exposure is disclosed on the refund object.
-
Signed webhooks
HMAC-signed, replay-protected events for every quote, payout, arrival and failure. Wire them into your ledger and your CRM.
-
Interchange++ reporting
Scheme fees, interchange, gateway margin and executed FX rate broken out on every settled inbound transaction.
One API for quotes, charges and payouts
The API exposes an FX quote endpoint, the shared charge object and a payout object. Lock a quote, apply it to an authorisation or a payout, and read the executed rate back on the same record. Idempotency keys keep retries safe on any leg.
POST /v1/payouts
Idempotency-Key: 3e9c-1a2b-7f4d
{
"amount": 250000,
"currency": "USD",
"beneficiary": "bnf_02H9F...",
"rail": "auto",
"quote": "qte_5F9k_...",
"reference": "INV-2026-08-1108"
}The response includes the selected rail, the corridor identifier, the fee breakdown and — where applicable — the SWIFT UETR that surfaces on your international payment tracker. Read the complete schema in the API reference.
Cross-border use cases we tune for
The default configuration reflects the four merchant profiles below. Adjust the currency list, corridor list and payout rail defaults from the dashboard against your own volume distribution.
-
Multi-country e-commerce
Sell in the shopper's currency, settle in EUR, refund on the original method — even when the payer's card is issued outside the EU.
-
Subscription software
Renew international customers in their preferred currency and settle centrally. Failed renewals dunn through the same rules as domestic orders.
-
Professional services
Invoice cross-border B2B clients, receive payment through cards, SEPA or bank transfer, and pay international suppliers on the same platform.
-
Digital publishers
Charge global memberships in local currencies and pay contributors internationally through SEPA Instant, SWIFT or push-to-card.
Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM.
Unified international flow vs stitched PSP + bank
Many teams pay for two systems — a PSP for cross-border acceptance and a bank for outbound transfers — and stitch reporting together after the fact. The comparison below explains where the unified model earns its keep.
| Dimension | BazPay (unified) | PSP + separate bank |
|---|---|---|
| Corridor selection | Automatic per beneficiary | Single rail, wrong tool for many corridors |
| FX display | Reference + margin + executed rate | Blended quote only |
| Payout tracking | UETR + signed webhooks per leg | Batch export, day-late |
| Inbound + outbound | Same platform, one dashboard | Separate PSP and treasury tools |
| Reconciliation | Interchange++, per-transaction fees | Aggregate statement |
| Refund behaviour | Original method, original currency | Manual FX unwind |
Fees, corridor coverage and FX margin are published on the pricing page. Storefront plugins are on integrations.
Plain-English glossary for international payment terms
The words below sit on every FX line and every payout object. Reading them the same way we do makes reconciliation and treasury conversations faster.
- Presentment currency
- The currency the shopper sees at checkout. Not always the settlement currency.
- Settlement currency
- The currency in which BazPay pays out to your IBAN. Default is EUR.
- Reference rate
- The interbank market rate used as the FX baseline for a quote.
- Applied margin
- The published percentage BazPay adds to the reference rate for the executed conversion.
- UETR
- Unique End-to-end Transaction Reference — the identifier SWIFT uses to track a cross-border payment.
- Corridor
- A named country-plus-currency route the payout engine supports on a specific rail.
Security and compliance signals
The international payment bank rails and card acquiring run inside a PCI DSS Level 1 environment audited each year. Hosted fields and gateway-side vaulting keep your annual return at merchant SAQ A. AML and KYC obligations are applied to boarding and to beneficiary payouts.
- 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
- PSD2 SCA
- 3-D Secure 2.2 with exemption engine on international card charges
- GDPR
- EU data residency; DPA available on request
- AML / KYC
- EU obligations applied to beneficiary payouts and merchant boarding
- SEPA / SEPA Instant
- Direct participation in supported euro-area corridors
Questions merchants ask about international payment processing
Which cards does BazPay accept for international payment processing?
Visa and Mastercard credit and debit cards, plus Maestro and Cartes Bancaires. Cards issued outside the European Union authorise on the same EU acquiring contract as domestic cards. Apple Pay and Google Pay ride the same rail through their network tokens. The gateway does not act as a marketplace of third-party PSPs — every authorisation posts against BazPay's own MID.
Which payout rails are used for send international payment flows?
SEPA and SEPA Instant for euro-area beneficiaries where BazPay participates directly, SWIFT for correspondent-bank reach on approved corridors, and push-to-card for eligible Visa or Mastercard debit cards in supported countries. The API picks the fastest supported rail for the beneficiary you enter — you do not have to route manually.
How does FX pricing work on an international payment order?
Each quote returns the reference rate at the moment of the quote, the published margin BazPay applies, and the resulting executed rate the payout or capture will use. That trio prints on the transaction record and on the interchange++ statement. There is no hidden spread and no blended rate.
How do I receive international payment from a non-EU shopper?
Nothing changes in your integration. The same charge request handles a non-EU-issued card, wallet or supported local method. 3-D Secure 2.2 runs where the issuer or your risk rules require it, funds settle into the same EU IBAN, and the interchange breakdown identifies the region so finance can attribute revenue correctly.
Can BazPay be used as a business international payment tracker?
Yes. Every inbound charge carries the acquiring reference; every outbound payout carries the internal identifier and, on SWIFT rails, the UETR. State changes fire signed webhooks — arrived, returned, failed — so you can drive a real-time dashboard, a customer-facing tracker, or a treasury reconciliation feed from the same source of truth.
How are cross-border refunds and chargebacks handled?
Refunds route back to the original method in the original presentment currency. Any FX difference between the capture and the refund date is disclosed on the refund object. Chargebacks on international card volume attribute to your named MID, and evidence packets include the 3-D Secure result, the enriched signals and the FX detail scheme rules require.
What are the standard international payment terms with BazPay?
Payment terms are agreed during boarding and confirmed in your commercial contract. Standard terms cover the settlement currency, per-scheme cycle timing, the SEPA and SWIFT fee schedule, the published FX margin, and rolling reserve arrangements where applicable. The pricing page holds the current headline schedule.
Which merchant types are eligible for international acceptance and payouts?
BazPay boards EU low-risk merchants: e-commerce sellers, subscription software firms, professional-services businesses and digital publishers. It does not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants, and it does not resell the acquiring of third-party PSPs.
Map your corridors with a payments specialist
Share the countries and currencies you already sell into — plus the ones where you pay suppliers or contributors — and we will confirm supported rails, FX margin and boarding fit within one working day. Sandbox keys are self-service so integration work can start in parallel. See also merchant acquiring, the network payment gateway and payment orchestration for the wider platform view.