Internet merchant accounts for EU, UK and Commonwealth businesses.
A merchant account is the account that receives funds from your card payments. BazPay opens direct regional merchant accounts for businesses — named MID at each scheme, settlement into your own local settlement account, and interchange++ statements you can reconcile line by line.
Built for EU, UK and Commonwealth e-commerce sellers, subscription software firms, professional-services businesses and digital publishers. No aggregated MID, no reseller layer, no third party standing on your shopper's statement.
Why choose a direct merchant account over an aggregated MID
Four properties stay true once your business needs finance-grade reporting and clean chargeback attribution. All four are default here.
-
A merchant account in your own name
Your legal entity holds the account, and the merchant identifier (MID) at each scheme is registered to that entity. No shared pool, no aggregator standing between you and the acquirer, no diluted chargeback attribution.
-
Local settlement, per scheme cycle
Funds settle from our own regional acquiring balance into the settlement account you nominate at boarding. Every settlement line ties back to a specific transaction ID for finance-team reconciliation.
-
Transparent processor economics
Interchange, scheme fees and BazPay margin appear on every settled transaction. Merchant accounts payment gateways that publish rates on interchange++ do not need to blend the numbers on your statement.
-
One dashboard for the account
Add users with role-scoped access. Rule changes, payout schedules, refunds and dispute submissions are all administered from the account dashboard — no ticket to change a threshold.
Account shapes for regional merchant profiles
Four account configurations share the same underlying merchant contract. Each one turns different features on by default and ships a policy set tuned to that merchant profile.
-
Standard
Standard internet merchant account
The default account for regional online sellers accepting Visa, Mastercard and local payment methods for one-off purchases. Named MID, local settlement account settlement, hosted fields and gateway vault included by default.
- One-off charges
- Named MID
- local settlement account
-
Recurring
Subscription-billing merchant account
Same account structure with card-on-file, dunning-aware retries and MIT exemptions on rebills. Suited to SaaS platforms and membership businesses where renewals are the revenue.
- Card-on-file
- MIT
- Dunning
-
Multi-store
Multi-outlet or multi-brand accounts
One merchant entity with per-store descriptors and per-outlet reporting. Ideal for retail chains and digital publishers running several storefronts under one legal entity.
- Per-store IDs
- SKU reporting
-
Professional
Professional-services accounts
Higher-ticket B2B invoicing with named-payer trust lists, enforced 3-D Secure 2 over a ceiling you set, and clean reconciliation lines that match your accounting system.
- Named payers
- Higher tickets
- 3DS2
The wider services envelope on merchant services. The acquiring contract that underpins the account on merchant acquiring. Payment-method depth on card and APM processing.
Opening a merchant account, from application to first settlement
Six stages sit between the boarding pack and your first settlement into a regional settlement account. Each stage is trackable in the dashboard and each stage change fires a signed webhook.
-
Application
Share your business model, legal entity documents, ownership evidence and expected volumes with the boarding team.
-
Underwriting
KYC and merchant review. Documents, ownership and revenue model are checked against underwriting policy for your vertical.
-
MID setup
A named merchant identifier is opened with the schemes for your legal entity. Sandbox and live API credentials issued to the dashboard.
-
Integration
One REST endpoint, one webhook signing secret and hosted fields for the checkout. Maintained plugins cover common regional commerce stacks.
-
Go live
Live keys enabled. Real-time analytics show approval quality from the first hour so any tuning happens against live traffic, not synthetic tests.
-
Steady state
Funds reconcile per scheme cycle and land in your local settlement account. Interchange++ statements and signed webhooks feed your finance stack.
Direct merchant account vs aggregated PSP account
The choice usually comes down to speed-to-live against everything else. Aggregators board fast but keep you on a shared MID; direct merchant accounts take longer to open and stay with you for the life of the business.
| Dimension | BazPay (direct merchant account) | Aggregated PSP account |
|---|---|---|
| MID structure | Named MID per merchant entity | Shared MID across the aggregator's book |
| Contract holder | Your legal entity, direct with BazPay | Aggregator as merchant of record |
| Settlement | Per-scheme cycle to your local settlement account | Aggregated payout, common delay |
| Chargeback attribution | Attributed to your account only | Diluted across the pool |
| Reporting | Interchange++ line detail | Blended-rate summary |
| Rule changes | Dashboard, effective on next order | Ticket to the aggregator |
| Underwriting | Direct with a named onboarding manager | Instant-approve, no relationship |
Statement structure and rate cards on the pricing page. Broader buyer's shortlist on payment processors. Ongoing service envelope on gateway services.
Features engineered into every merchant account
Every capability below ships on the standard account. Turn features on with a request flag or a dashboard toggle — no premium tier that unlocks the API vault or the settlement webhook.
-
Named MID
Your own merchant identifier at each scheme. Chargeback ratios, decline data and settlement reporting attributed to your entity alone.
-
Local settlement account
Funds settle in EUR into a regional settlement account by default; named settlement currencies available for approved corridors.
-
Hosted fields
Card, expiry and CVC inputs served from our PCI environment inside your checkout — merchant SAQ A instead of full PCI.
-
Gateway vault
Store credentials once and reuse them for renewals, upgrades and one-clicks; portable if you ever change stack.
-
3-D Secure 2.2 engine
Authentication with exemption logic — TRA, low-value, trusted-beneficiary, MIT — so most account traffic stays frictionless.
-
Dashboard admin
Users, roles, audit log, API keys, webhook secrets and rule builder for the merchant account — all administered by your team without a support ticket.
-
Signed webhooks
HMAC-signed, replay-protected events for every state change: charges, refunds, disputes and settlements — one signature scheme end to end.
-
Interchange++ statements
Every settled transaction breaks out interchange, scheme fees and acquirer margin for line-level finance reconciliation.
One API for every charge on the account
The charge object is the unit of work on the account. One endpoint authorises, captures and refunds against your named MID. Idempotency keys make retries safe. Signed webhooks confirm every state change asynchronously — even if your service was down when the event fired.
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" }
}The response returns a canonical charge object with the authorisation code, the MID the charge posted against, the interchange bucket and any exemption applied. Read the full schema in the API reference.
Who BazPay opens merchant accounts for
Merchant-account underwriting is scoped to the four regional profiles below. If your business fits, boarding typically clears in days.
-
E-commerce sellers
DTC brands and multi-country storefronts running Shopware, Magento 2, WooCommerce or PrestaShop under one merchant account with per-store descriptors.
-
Subscription software
SaaS teams billing monthly and annual plans with card-on-file renewals, dunning-aware retries and MIT exemptions on the same account.
-
Professional services
Agencies, consultancies and B2B service firms invoicing higher tickets with named-payer allow 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 merchant account.
Out of scope for BazPay merchant accounts: 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.
Security and compliance signals on the account
The merchant account 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. Authentication runs on every card charge with automatic exemption logic where the rules allow. Data stays inside the region and is handled under GDPR.
- 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 opening an account
What is a merchant account, and how is it different from a payment gateway?
A merchant account is the financial account that receives funds from card payments. A payment gateway is the software that carries authorisation messages between a merchant and the acquirer. You need both to accept card payments online. BazPay provides them as one — the merchant account holds the funds; the gateway runs the authorisation flow.
How do I open an internet merchant account with BazPay?
Share your business model, legal-entity documents, ownership evidence and expected volumes with the boarding team through the contact form. If the business fits regional underwriting — e-commerce, subscription software, professional services or digital publishers — an integration manager scopes the setup and issues sandbox credentials. Standard boarding typically completes in a few business days once the KYC pack is complete.
Which currencies and settlement corridors do web merchant accounts support?
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 on the pricing page and confirmed during boarding.
Is a BazPay merchant account a direct account or an aggregated one?
Direct. Your legal entity holds a named merchant identifier (MID) at each card scheme. There is no shared MID, no aggregator layered between you and the acquirer, and no third party appearing on the shopper's statement. BazPay is not a marketplace of third-party PSPs and does not act as a merchant of record.
How do chargebacks work on merchant accounts payment gateways structured this way?
Because your merchant account has a named MID, chargebacks are attributed to your entity — never diluted across a pool. Scheme dispute events fire as signed webhooks and land in the dashboard with the transaction, the 3-D Secure result, the signals that scored it and any early-warning alert. Evidence templates are pre-assembled to the scheme's current format.
Can I move an existing merchant account to BazPay?
Yes. Vault imports, network-token portability and debit-order mandate migration are supported under scheme-approved processes, subject to the receiving bank's consent letters. Old and new webhook streams typically run in parallel until traffic is proven on the new stack, so saved-card renewals never miss a cycle.
What business types can open a merchant account here?
Merchants across the EU, UK, Australia, Canada and New Zealand: e-commerce sellers, subscription software firms, professional-services businesses, digital publishers and multi-outlet retailers selling online. BazPay does not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants.
How is a merchant account closed if I need to leave?
You can close the account by written notice from a bound signatory of your legal entity. Outstanding settlement and any dispute reserve run through their normal cycle before final closure. Vault export and mandate handover are supported under scheme-approved processes, so you can migrate stored credentials rather than force shoppers to re-enter their cards.
Start the merchant account conversation
Share your business model, monthly volumes and existing stack. A boarding manager will confirm merchant-account fit, likely rate structure and settlement corridor within one working day. See also payments solutions, network payment gateway, payment infrastructure and about NEWERA PAYMENT TECHNOLOGIES LTD.