Payment merchant accounts for EU, UK and Commonwealth businesses.
BazPay opens direct payment merchant accounts on its own regional acquiring licence. Every account carries a named MID for your legal entity, a regional settlement account for settlement, interchange++ reporting on every cycle and a dashboard your team runs itself.
Built for EU, UK and Commonwealth e-commerce sellers, subscription software firms, professional-services businesses and digital publishers. One contract, one acquirer, no reseller layer.
Why merchants pick a direct payment merchant account
Four properties separate a direct merchant account from an aggregated PSP arrangement. All four show up in the finance-team reconciliation once the volumes grow.
-
Your own named merchant identifier
Every account gets a named MID with the schemes for your legal entity. Chargeback ratios, decline data and settlement reporting are attributed to your business — never diluted across a shared pool.
-
One contract, direct with the acquirer
You contract with BazPay directly. No downstream reseller, no aggregated payment merchant account, no third party in the reporting chain. The credentials that authorise your traffic and the ones that settle your funds belong to the same platform.
-
Interchange++ statements every cycle
Scheme fees, interchange and gateway margin appear on every settled transaction. Your finance team reconciles against the source data, not against a blended rate on a monthly summary.
-
Dashboard your team runs itself
Add engineers, finance analysts and support agents with role-scoped access. Refunds, captures, rule thresholds and payout schedules stay self-service — no ticket for a routine account change.
What's included with a payment merchant account
Four families of capability ship with every account BazPay opens. Each has a stable interface into your team's tooling.
-
Identity
Named MID and legal-entity binding
The payment merchant account is opened for your named legal entity, with a MID at each supported scheme. Descriptor, MCC and region are configured against your business, not against a pool.
- Named MID
- Legal-entity binding
- Descriptor control
-
Settlement
Payouts and reconciliation
Settlements land in your local settlement account per scheme cycle. Signed webhooks fire on each payout with interchange++ line detail attached, so your ledger reconciles automatically.
- local settlement account
- SEPA Instant
- SEPA Instant
-
Access
Users, roles and audit
Invite engineers, finance analysts and support agents with role-scoped access. Every dashboard action is audit-logged and retrievable per-user for compliance reviews.
- Users
- Roles
- Audit log
-
Ops
Refunds, captures and disputes
Issue full or partial refunds, adjust captures and manage dispute evidence from the dashboard or the API. Every action fires a signed webhook keyed to the same charge ID.
- Refunds
- Captures
- Dispute evidence
The acquiring contract itself sits on merchant acquiring. The ongoing service envelope on gateway services.
What you need to open an online payment merchant account
Six document families cover standard regional boarding. Everything is discussed with a named integration manager, and the pack is short — nothing here is unusual for a business accepting cards in-region.
-
Legal entity documents
Certificate of incorporation, registered address, articles of association or equivalent for your jurisdiction.
-
Beneficial ownership
UBO evidence covering shareholders above the applicable threshold, plus ID for signatories on the account.
-
Business model description
Product or service description, target markets, expected monthly volume and average ticket, plus terms and refund policy.
-
Website and checkout preview
Live URL or a staged preview so underwriting can review the pages the shopper actually sees — pricing, T&Cs, contact and privacy notice included.
-
Bank details for settlement
The local settlement account that will receive payouts. Named-currency settlement in supported corridors is configured after boarding.
-
Compliance basics
AML posture proportional to your business model. Higher-ticket B2B accounts may need additional evidence for named payers on the trust list.
Direct merchant account vs aggregated PSP account
The shortest route to acceptance is often a reseller PSP with an aggregated MID — useful for the first month, less useful once volume matters. Where the trade-off shows up is below.
| Dimension | BazPay (direct account) | Aggregated PSP account |
|---|---|---|
| Contract holder | Direct with BazPay (regional acquirer) | Reseller PSP on aggregated MID |
| Merchant ID | Named MID per merchant account | Shared MID pool |
| Chargeback attribution | Attributed to your MID | Diluted across the pool |
| Settlement | Per-scheme cycle to your local settlement account | Aggregated payouts, common delay |
| Reporting | Interchange++ line detail per transaction | Blended-rate monthly summary |
| Dashboard changes | Self-service, effective on next order | Ticket to the reseller |
| Descriptor control | Your named descriptor | Reseller-owned or shared |
Rate structure on the pricing page. Buyer's-shortlist context on payment processors. Adjacent surface: merchant services.
Merchant-account features you use every week
Every capability below ships on every merchant account BazPay opens, regardless of monthly volume. No premium tier that unlocks the dashboard, the audit log or the signed-webhook scheme.
-
Named MID at each scheme
Visa, Mastercard, Cartes Bancaires and eftpos opened against your named legal entity. Chargeback attribution and reporting stay attached to your MID.
-
SEPA and SEPA Instant payouts
Direct participation for merchant payouts in supported corridors; SWIFT and push-to-card options on approved routes.
-
Interchange++ statements
Scheme fees, interchange and gateway margin broken out on every settled charge — no blended rate obscuring the underlying cost.
-
Signed webhooks
HMAC-signed, replay-protected events for approvals, refunds, disputes and payouts on the same envelope across every rail.
-
Role-scoped dashboard access
Engineers, finance, ops and support each get the smallest scope they need. Every action audit-logged for compliance.
-
Hosted fields + gateway vault
Card data stays inside our PCI DSS Level 1 scope, so your annual return stays at merchant SAQ A.
-
3-D Secure 2.2 + exemptions
Authentication with automatic exemption logic so most card checkouts stay frictionless while liability shifts on step-ups.
-
Real-time analytics
Approval, decline and payout data visible within seconds; export as CSV for your data warehouse.
Every merchant account exposes the same REST surface
One versioned endpoint creates a charge on your MID. The response returns the authorisation code, the MID it posted against and any exemption applied. Idempotency keys make retries safe end to end. Signed webhooks confirm state changes 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 is the canonical charge object described in the API reference. Handler samples in the developer docs.
Who BazPay opens payment merchant accounts for
BazPay is a regional acquirer. Merchant-account underwriting is scoped to four merchant profiles with predictable chargeback ratios and clean AML posture.
-
E-commerce sellers
DTC brands and multi-country storefronts on Shopware, Magento 2, WooCommerce or PrestaShop with one merchant account across every regional market.
-
Subscription software
SaaS businesses billing monthly and annual plans with card-on-file renewals, dunning-aware retries and MIT exemptions.
-
Professional services
Agencies, consultancies and B2B service firms invoicing recurring retainers with named-payer trust lists and enforced 3-D Secure 2.
-
Digital publishers
Membership renewals, single-issue purchases and paywall unlocks reconciled per SKU on one merchant account.
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.
Security and compliance on every merchant account
The environment behind every payment merchant account is assessed against PCI DSS Level 1 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.
- 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 payment merchant account, and what does BazPay provide?
A payment merchant account is the arrangement that lets a business accept card payments and receive settlement into its bank. It includes a named MID with the card schemes, a contract with an acquirer, and the technical rails that carry authorisations and settlements. BazPay provides a direct regional merchant account: one contract with the acquirer, one named MID per merchant, one dashboard and one API.
How is an online payment merchant account different from a reseller PSP arrangement?
A reseller PSP opens an aggregated MID under its own name and places your traffic on top. Boarding is fast but you get diluted chargeback attribution, blended reporting and delayed settlement. A direct merchant account with BazPay opens a named MID for your legal entity — chargebacks are attributed to you, reporting arrives at interchange++ line detail, and settlement lands per scheme cycle in your own local settlement account.
What is required to open a BazPay payment merchant account?
Legal entity documents, beneficial ownership evidence, a description of the business model, the live website or a staged preview, the local settlement account that will receive settlement and AML documentation proportional to your model. The full list is discussed with a named integration manager during boarding and is standard for regional underwriting.
How long does it take to open a merchant account?
Standard regional boarding typically completes in a few business days once the KYC pack, UBO evidence and business-model description have been received. Higher-ticket or multi-entity applications need longer for legal review. Sandbox credentials are available before boarding finishes, so integration work can start in parallel with underwriting.
Which businesses can open a payment merchant account with 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 merchant of record or a marketplace of third-party PSPs.
Do I control the descriptor that appears on my customers' statements?
Yes. The descriptor is configured against your named MID and reflects your legal entity name or a scheme-approved trade name. That is a direct benefit of a named merchant account: no reseller descriptor squatting on your brand.
What happens on chargebacks under a BazPay merchant account?
Because your MID is named, chargebacks are attributed to your business — 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 for one-click submission.
Can I migrate an existing merchant account from another acquirer?
Yes. Stored credentials, network tokens and debit-order mandates can be imported under a scheme-approved migration, subject to the receiving bank's consent letters. Old and new webhook streams typically run in parallel until traffic is proven on the new merchant account.
Open a payment merchant account
Share your business model, monthly volumes and existing processor. An integration manager will confirm boarding fit within one working day and share the KYC pack. See also merchant services, merchant acquiring, payments solutions and card and APM processing.