An electronic payment system built for EU, UK and Commonwealth merchants.
BazPay is a regional electronic payment system that combines acquiring, gateway, tokenisation, PSD2-compliant authentication, instant payouts and reporting behind one REST API. Cards, wallets, local payment methods and bank rails share the same charge object and the same signed webhook stream.
Built for e-commerce sellers, subscription software firms, professional-services businesses and digital publishers. Direct acquiring on our own licence, regional settlement into your named settlement account, no reseller layer between you and the schemes.
Components of an electronic payment system, on one platform
A working electronic payment gateway needs four cooperating parts: a checkout surface, the gateway itself, an acquirer with scheme membership, and clearing plus payout. BazPay ships all four inside a single contract and dashboard.
-
Front end
Checkout surface
Hosted fields, drop-in components or hosted pages render the payment form inside our PCI environment, so card data never touches the merchant server.
- Hosted fields
- Drop-in
- Hosted page
-
Gateway
Message routing
The gateway translates the checkout request into scheme, wallet or bank-rail messages, applies tokenisation and returns one canonical response.
- Tokenisation
- 3-D Secure engine
- Routing
-
Acquirer
Scheme membership
Direct card scheme membership on the regional licence. The acquirer sends the authorisation to the issuer and settles the merchant.
- Visa
- Mastercard
- CB
- eftpos
-
Clearing
Settlement and payouts
Funds reconcile per scheme cycle and pay out over SEPA or SEPA Instant into a named local settlement account. Refunds and chargebacks book against the same balance.
- SEPA Instant
- SEPA Instant
- settlement account payouts
Depth on each rail: card and APM processing, open banking and payouts. The direct scheme membership itself lives on merchant acquiring. See how this compares with online payment platform, payment processors and gateway services.
Benefits of an electronic payment system, delivered
The advantages of an electronic payment system are widely rehearsed. The four below are the ones merchants tell us matter after boarding — the reasons product, engineering and finance teams stay with one platform.
-
One integration, every rail
Cards, device wallets, local payment methods and account-to-account rails share one REST endpoint and one signed webhook stream. Engineering keeps one integration surface, not five.
-
Reduced PCI scope
Hosted fields and gateway-side vaulting keep raw PAN data out of your infrastructure. Most integrations qualify for merchant SAQ A instead of a full audit.
-
SCA exemptions applied automatically
Low-value, risk analysis, trusted-beneficiary and merchant-initiated exemptions are claimed where the rules allow. Fewer challenges, the same liability shift on the ones that do fire.
-
Line-level reporting
Interchange, scheme fees and gateway margin appear separately on every settled transaction so finance teams reconcile against the source, not a blended rate summary.
The life of one electronic payment
Six stages sit between a checkout button and a settled dollar on your bank account. Each stage is visible in the dashboard and each state change fires a signed webhook keyed to the same charge ID.
-
Collect
Hosted fields or the mobile SDK gathers card entry, wallet approval or bank-selection alongside device signals in one request.
-
Score
Inline fraud rules apply device, velocity and geography checks. Bad orders never reach the acquirer.
-
Authenticate
3-D Secure 2.2 runs when the risk earns it. Exemption logic resolves the majority of card charges frictionlessly.
-
Authorise
The tokenised charge posts to the chosen scheme, wallet network or bank rail through one canonical charge object.
-
Confirm
The response and a signed webhook confirm the authorisation, the 3-D Secure outcome and the exemption applied.
-
Settle
Funds reconcile per scheme cycle and pay out on SEPA Instant into your local settlement account. Every line ties back to its own transaction ID.
Advantages and disadvantages, plainly
No payment method is free. The comparison below sets the working properties of a modern electronic payment system next to the traditional alternatives, so decision-makers can weigh the trade-offs on evidence rather than marketing.
| Dimension | Electronic payment system (BazPay) | Traditional methods (cash, wire, cheque) |
|---|---|---|
| Cost | Interchange++ transparency, no blended surprise | Cash: no per-transaction fee, but reconciliation and float cost |
| Reach | Global card acceptance, local APMs, bank rails | Cash and local paper: geographically limited |
| Chargeback risk | Present, mitigated by 3-D Secure and dispute tooling | Bank transfers: irreversible; cash: no chargeback |
| Reconciliation | Automated per-transaction, machine-readable | Manual for cash; batch files for legacy bank rails |
| Compliance overhead | PCI, PSD2, GDPR — handled by the platform | None for cash; heavy custom work for bespoke integrations |
| Failure modes | Declines, network timeouts — retried automatically | Physical loss for cash; opaque bank returns for wires |
Rate cards on the pricing page. Dispute and chargeback controls on anti-fraud controls.
Features engineered into the electronic payment gateway
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.
-
REST API
One endpoint creates a charge across every connected rail. The response object shape does not change between payment methods.
-
Hosted fields
Card, expiry and CVC inputs served from our PCI environment inside your checkout — the merchant scope stays at SAQ A.
-
Gateway-side vault
Store credentials once and reuse across renewals, upgrades and one-clicks. Portable if you ever change stack.
-
Network tokens
Visa and Mastercard network tokens replace PAN at storage. Automatic refresh on card reissue keeps saved cards alive.
-
3-D Secure 2.2 engine
Frictionless first; challenge only when a rule or the issuer requires it. Liability shifts on successful authentication.
-
Idempotent requests
Retry-safe create requests keyed to your idempotency header. A network blip never becomes a double charge.
-
Signed webhooks
HMAC-signed, replay-protected events for every state change — approvals, declines, refunds, disputes, settlements.
-
Interchange++ reporting
Scheme fees, interchange and gateway margin split on every settled transaction for finance reconciliation.
One API for every electronic payment
The charge object is the unit of work. One endpoint authorises, captures and refunds across every connected rail. Idempotency keys make retries safe. 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",
"customer": "cus_5F9k",
"metadata": { "invoice_id": "INV-10842" }
}
Switch payment_method to ideal, apple_pay or
sepa_debit and the same call routes to the corresponding rail. Read the
full schema in the API reference.
Who runs on these electronic payment services
BazPay is a regional electronic payment services provider. Underwriting is scoped to four merchant profiles with predictable chargeback ratios and clean AML posture.
-
E-commerce sellers
DTC brands and multi-country storefronts running Shopware, Magento 2, WooCommerce or PrestaShop. Local cards and APMs on one integration.
-
Subscription software
SaaS teams 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 enforced 3-D Secure 2 over a ceiling you set.
-
Digital publishers
Media businesses selling memberships and single-issue purchases with clean per-SKU and per-region reporting.
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.
Security and compliance signals
The platform runs inside a PCI DSS Level 1 environment assessed each year. Hosted fields, network tokens 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
Questions merchants ask first
What is an electronic payment system?
An electronic payment system is the collection of software, hardware, contracts and clearing rules that lets a business accept money digitally and receive the funds in its bank account. It normally includes a checkout surface, a gateway that carries the message, a processor and acquirer that talk to the schemes, and clearing plus payout infrastructure. BazPay bundles these into one platform for merchants across the EU, UK, Australia, Canada and New Zealand.
What are the main components of an electronic payment system?
A shopper-facing checkout, a payment gateway, tokenisation and vault services, an acquirer with scheme membership, an authentication layer (usually 3-D Secure for cards), a fraud rule engine, a clearing and settlement pipeline, and reporting for finance. BazPay provides every component under one contract, so merchants do not need to stitch several electronic payments companies together.
What are the advantages of an electronic payment system?
Speed and consistency — a charge resolves in seconds, not days. Automated reconciliation — every transaction carries a machine-readable identifier and cycle. Reach — a single integration accepts a card issued anywhere the scheme runs. Auditability — the platform records every state change, signs it, and makes it queryable. Reduced cash-handling risk and the ability to bill recurring customers without manual re-entry.
What are the disadvantages of an electronic payment system, and how does BazPay mitigate them?
Per-transaction fees, chargeback exposure and integration effort are the usual trade-offs. BazPay counters with interchange++ transparency (no blended surprise), an PSD2-aware fraud engine and dispute tooling that reduce chargeback loss, and prebuilt plugins plus a single REST API that shrink integration effort to days rather than months.
How does BazPay differ from other electronic payments companies?
BazPay is a direct regional acquirer and gateway, not a reseller of a downstream PSP. That means one contract, a named merchant identifier at each scheme, interchange++ statements and settlement into your own local settlement account. Acceptance, billing, payouts, fraud and reporting run on the same platform, so the surface area you integrate against is one system rather than several.
Can BazPay be used as an electronic bill payment system for subscriptions and invoices?
Yes. Recurring billing with card-on-file, network-tokenised renewals, dunning-aware retries and merchant-initiated exemptions is native to the platform. One-off invoices go out as hosted payment page links. Both share the same charge object, the same signed webhook stream and the same reporting surface as one-off card charges.
Which merchant profiles fit these electronic payment processing solutions?
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 it is not a marketplace of third-party PSPs.
How secure are the platform's electronic payment services?
The acquiring and gateway environment is assessed to PCI DSS Level 1 each year. Hosted fields, network tokens and gateway-side vaulting mean PAN data does not enter your infrastructure, so most integrations stay at merchant SAQ A. Authentication runs with 3-D Secure 2.2, and signed HMAC webhooks make server-to-server events replay-safe.
Scope your electronic payment system today
Share your business model and volumes. A payments specialist will confirm boarding fit and map the components — acceptance, recurring billing, payouts, anti-fraud controls and real-time analytics — within one working day. See the wider payments solutions and network payment gateway pages for adjacent context.