Menu
Talk with sales

Integration questions? [email protected]

Merchant payment processing for EU, UK and Commonwealth businesses.

BazPay handles merchant payment processing end to end — application, boarding, live acceptance, dispute defence, SEPA Instant settlement and interchange++ statements — under one direct regional acquiring contract. No aggregated MID, no reseller in the reporting chain, no blended monthly summary to reverse-engineer.

Built for EU, UK and Commonwealth e-commerce sellers, subscription software firms and professional-services businesses. One named merchant identifier, one dashboard, one signed webhook stream — and one person you talk to when you need something changed.

Talk with sales See pricing

Why merchants choose BazPay for the processing relationship

Four things stay true whether you take a hundred euros a day or a million. They are the reasons product, engineering and finance teams stay after the switching cost is paid.

  • Predictable settlement, not aggregated payouts

    Funds settle per scheme cycle into your named local settlement account. Chargebacks and refunds attribute to your MID, not a shared pool. Finance teams can forecast cash without waiting on a reseller's reconciliation queue.

  • Statements that reconcile line by line

    Every settled transaction shows interchange, scheme fees and processor margin as separate lines. No blended rate on a monthly summary, no reverse-engineering fees against your ledger.

  • One contract for the full processing surface

    Acceptance, subscription billing, dispute defence, payouts and reporting sit under the same merchant agreement. One boarding pass, one signing secret, one dashboard.

  • Regional underwriting on purpose

    Direct regional acquiring on our own licence, scoped to a defined set of merchant profiles. That focus is why approval rates and scheme-ratio compliance hold steady across the book.

The merchant onboarding journey

Four blocks describe how a merchant moves from first conversation to live processing. Each one has a named owner on the BazPay side and a defined interface into your team.

  • Apply

    Application and business review

    Share your business model, ownership structure, monthly volume and target markets. A named onboarding manager checks fit against regional underwriting policy before any documents change hands.

    • Model review
    • Volume estimate
    • Market coverage

  • Board

    KYC and merchant boarding

    KYC and beneficial-ownership documents, financials where applicable and website/product review. Standard regional applications typically clear in a few business days.

    • KYC
    • Ownership
    • Product review

  • Provision

    MID and API provisioning

    A named merchant identifier is opened with the schemes for your legal entity. Sandbox and live credentials plus dashboard invites are issued to the team you nominate.

    • Named MID
    • Sandbox
    • Live keys

  • Migrate

    Migration from another processor

    Optional. Vault imports, network-token portability and debit-order mandate handovers are planned as part of onboarding, so subscription renewals do not miss a cycle during cutover.

    • Vault import
    • Mandate handover
    • Parallel cutover

The acquiring contract itself lives on merchant acquiring. The broader merchant surface on merchant services.

How a merchant charge moves through processing

Six stages sit between the shopper hitting pay and the dollar settling into your account. Every stage is visible in the dashboard and every stage change fires a signed webhook.

  1. Charge

    Authorisation request created via REST API, hosted fields or a hosted checkout page. Card data stays in our PCI scope.

  2. Authenticate

    3-D Secure 2.2 runs only when the risk earns it. PSD2 exemption logic keeps most orders frictionless.

  3. Authorise

    The processor posts against your MID with the authentication result bound to the transaction for issuer scoring.

  4. Capture

    Capture immediately or later. Partial captures and partial refunds both post cleanly on the same charge.

  5. Settle

    Funds reconcile per scheme cycle. Each line on the statement carries interchange, scheme fees and margin separately.

  6. Reconcile

    Signed webhooks and CSV export feed your finance stack. Chargeback and refund events are first-class.

Direct merchant processing vs aggregated PSP

The choice usually comes down to how much transparency and attribution you want on the processing relationship. The comparison below explains where each model earns its keep.

BazPay direct merchant processing compared with an aggregated PSP
Dimension BazPay (direct) Aggregated PSP (reseller)
Contract holder Direct with BazPay as regional acquirer Reseller PSP on aggregated MID
MID structure Named MID per merchant Shared MID pool
Statement Interchange++ line detail Blended-rate monthly summary
Settlement timing Per scheme cycle to your local settlement account Aggregated payout, common delay
Chargeback attribution Your MID, your case queue Diluted across the pool
Onboarding contact Named onboarding manager Ticket queue
Underwriting scope Merchants across the EU, UK, Australia, Canada and New Zealand (defined list) Broad, few exclusions

Buyer's-shortlist context on payment processors. Statement structure and rates on the pricing page. Plugin coverage on integrations.

Features that make merchant payment processing operational

Everything below is on the standard integration. Turn features on with a request flag or a dashboard toggle — no enterprise-tier gate on the primitives merchants actually depend on.

  • Named MID per merchant

    Your own merchant identifier at each scheme. Chargeback ratios, decline data and settlement reporting attributed to your entity.

  • Interchange++ statements

    Every settled transaction breaks out interchange, scheme fees and processor margin as separate lines on the statement.

  • Hosted fields

    Card, expiry and CVC inputs served from our PCI environment inside your checkout, keeping your annual return at SAQ A.

  • Gateway-side vault

    Store credentials once, charge them repeatedly across renewals, upgrades and one-clicks. Portable if you ever change stack.

  • 3-D Secure 2.2 engine

    Authentication with automatic exemption logic. Liability shift where the scheme permits it, less friction where it does not.

  • Dispute tooling

    Early scheme alerts, pre-assembled evidence packets with authentication result and delivery events attached, one-click submission.

  • SEPA + SEPA Instant

    Direct participation for merchant payouts in supported corridors. SWIFT and push-to-card options for approved routes.

  • Signed webhooks

    HMAC-signed, replay-protected events for every state change — authorisations, captures, refunds, disputes and payouts.

The statement, the way finance teams want to read it

Every settled transaction is a line on the statement, with interchange, scheme fees and processor margin split out. The same detail is available via signed webhook for your reconciliation service and as CSV export for spreadsheet users. 

charge_id       : ch_02H9F...
authorized_at   : 2026-04-08T12:44:03Z
settled_at      : 2026-04-10
amount          : 49.90 EUR
scheme          : visa
mcc             : 5734
interchange     : 0.32 EUR
scheme_fees     : 0.04 EUR
processor_fee   : 0.45 EUR
merchant_net    : 49.09 EUR
sca             : 3ds2 (frictionless)

Every line ties back to the original charge. Refunds, chargebacks and reversals sit on the same statement keyed to that same charge_id. See real-time analytics for the live view and the API reference for the field schema.

Merchants BazPay processes for

BazPay boards four regional merchant profiles. Underwriting is scoped so scheme ratios and approval quality hold steady across the book — that focus is deliberate.

  • E-commerce sellers

    DTC brands and multi-country storefronts on Shopware, Magento 2, WooCommerce or PrestaShop. One processing contract across every regional storefront.

  • Subscription software

    SaaS teams billing monthly and annual plans with card-on-file renewals, MIT exemptions and dunning-aware retries.

  • Professional services

    Agencies, consultancies and B2B firms invoicing higher tickets with named-payer trust lists and enforced 3-D Secure 2 over a ceiling you set.

  • Digital publishers

    Membership renewals, single-issue purchases and paywall unlocks reconciled per SKU on one MID.

Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. BazPay is not a marketplace of third-party PSPs and does not act as a merchant of record. Vertical bundles for supported profiles live on payments solutions.

Security and compliance signals across the processing surface

The processing environment runs inside a PCI DSS Level 1 assessment renewed each year. Hosted fields, gateway vaulting and network tokens keep your annual return at merchant SAQ A. Authentication runs on every card charge with automatic exemption logic where the rules allow.

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 / SEPA Instant
Direct participation for merchant payouts in supported corridors
Scheme registrations
Visa VIRP and Mastercard SPoC/PCI-CP where required

Questions merchants ask before signing a processing contract

What does merchant payment processing include on BazPay?

The processing surface covers authorisation across cards, wallets and local payment methods, capture and refunds, 3-D Secure 2.2 authentication, dispute defence, SEPA and SEPA Instant payouts, interchange++ statements and signed-webhook events for every state change. All under one merchant contract, one API and one dashboard.

How long does merchant payment processing setup take?

Standard regional boarding typically clears in a few business days once KYC documents, beneficial-ownership evidence and a business-model description have been received. Sandbox credentials are issued before boarding finishes, so integration work runs in parallel with the underwriting review.

What does the processing statement actually look like?

Every settled transaction is a line on the statement with interchange, scheme fees and the BazPay margin as separate columns. Refunds, chargebacks and reversals sit on the same statement, keyed to the original charge. Finance teams reconcile against the source line — there is no blended rate to reverse-engineer.

How are chargebacks handled?

Because you hold a named MID, every chargeback attributes to your entity. Scheme dispute events fire as signed webhooks and land in the dashboard alongside the transaction, the 3-D Secure result, the fraud signals that scored it and any early-warning alert. Evidence templates are pre-assembled to the scheme's current format for one-click submission.

Which merchant types can BazPay process for?

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 process for adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants, and does not act as a marketplace of third-party PSPs or as a merchant of record.

Can I keep saved cards when moving merchant processing to BazPay?

Yes. Stored credentials, network tokens and debit-order mandates can be imported from an incumbent processor under a scheme-approved migration, subject to the receiving bank's consent letters. Renewals continue on the new processor without asking shoppers to re-enter their card.

Which currencies and settlement corridors are supported?

Authorisation runs in EUR and more than twenty presentment currencies. Settlement defaults to EUR into a regional settlement account. Named settlement currencies and SEPA Instant, SWIFT or push-to-card payouts are available on approved corridors; the current schedule is confirmed during boarding.

Does BazPay integrate with the storefront I already run?

Maintained plugins ship for WooCommerce (WordPress), Magento 2 / Adobe Commerce, PrestaShop and Shopware 6 — each covering checkout, refunds, capture, webhooks and recurring billing out of the box. Custom stacks integrate directly against the REST API.

Start the processing conversation

Share your business model, volumes and existing processor. A named onboarding manager will confirm boarding fit, likely rate structure and settlement corridor within one working day. See also card and APM processing, merchant acquiring, open banking and NEWERA PAYMENT TECHNOLOGIES LTD.

Talk with sales Read the API reference