Payment gateway services for EU, UK and Commonwealth merchants.
An API is the interface; gateway services are what surround it. BazPay ships the operational envelope with the platform — integration engineering, migration support, a named onboarding manager, a public status page, versioned change management and dashboard admin that your team runs itself.
Built for EU, UK and Commonwealth e-commerce sellers, subscription software firms and professional-services companies. Direct regional acquiring, one dashboard, no ticket queue between you and the engineers who wrote the code.
Why gateway services matter as much as the API
An unsupported REST endpoint is a manual, and manuals do not survive contact with a live release. Four service commitments make the difference between an integration that goes live on time and one that ships six weeks late.
-
Named integration manager
Every merchant is paired with an integration engineer for boarding and go-live. Not a ticket queue — a person who has the boarding pack, your test data and the timing that matters to your release.
-
Migration services included
Moving from another gateway is scoped and executed as part of onboarding. Vault imports, mandate handovers and webhook cutover are planned before the go-live date, not after.
-
One dashboard, all merchants and users
Add engineers, finance analysts and support agents with role-scoped access. Every action is audit-logged. Rule changes and payout schedules are self-service — no ticket for a threshold move.
-
Status and incident transparency
A public status page shows rail health per network. Signed webhooks fire on scheduled maintenance and incidents so your on-call sees them where your alerts already live.
The service categories inside the platform
Four service families sit around the payment gateway API. Each one has a named owner on the BazPay side and a documented interface into your team.
-
Integration
Integration services
A named engineer scopes the integration against your stack, reviews the first pull request and validates the sandbox before you flip a key. Existing plugins cover common regional commerce stacks so the effort is calibrated to the delta, not the whole build.
- Scoping call
- PR review
- Sandbox sign-off
-
Migration
Migration services
Vault imports, network-token portability and debit-order mandate migration under scheme rules. Old and new webhook streams run in parallel until the cutover succeeds under load.
- Vault import
- Mandate handover
- Parallel webhooks
-
Support
Merchant support
Ongoing email and shared-channel support for engineering, finance and operations questions. Escalation paths named on day one, not discovered mid-incident.
- Shared channel
- Escalation matrix
-
Developer
Developer enablement
Sandbox that mirrors production traffic patterns, a versioned changelog and a documented deprecation policy. Client libraries and webhook verification helpers ship maintained.
- Sandbox
- Changelog
- SDK helpers
The wider platform lives on payment gateway. See payment processors for the buyer's shortlist and payments solutions for vertical-tuned bundles. Adjacent surface: payment services, online payment services and the electronic payment system primer.
Onboarding, migration and steady-state — the service lifecycle
Six stages describe how the service surface engages with a merchant, from first conversation to steady-state operations. Each stage has a named owner on both sides.
-
Discovery
Business model, volumes, markets and existing stack reviewed with a named integration manager before boarding kicks off.
-
Underwrite
KYC and merchant review. Documents, ownership and revenue model checked against underwriting policy for your vertical.
-
Sandbox
Sandbox keys, webhook signing secret and dashboard invites issued. Your engineers start integration work while boarding continues in parallel.
-
Migrate
If you are switching from another gateway, vault imports, mandate handovers and webhook cutover are planned and dress-rehearsed.
-
Go live
Live keys enabled. Real-time analytics show approval quality from the first hour and the shared channel is monitored during the cutover window.
-
Operate
Ongoing review of approvals, decline reasons, fraud verdicts and payout timing with your team. Rule changes stay self-service in the dashboard.
Managed gateway service vs raw API access
Two credible options exist when you buy a payment gateway. One ships a REST API and leaves you to run it. The other wraps that API in the services below. Both work — for different teams.
| Dimension | BazPay gateway services | Raw API access |
|---|---|---|
| Onboarding | Named integration engineer | Docs + self-serve keys |
| Migration | Vault import + mandate handover | Merchant plans and runs it |
| Support surface | Email, shared channel, named escalation | Ticketing queue |
| Status transparency | Public status page + signed webhooks | Twitter or nothing |
| Roadmap access | Quarterly review with product | Public marketing pages only |
| Change safety | Versioned API, documented deprecation | Silent breaking changes |
Rate structure on the pricing page. Plugin coverage on integrations. The engineering foundation the service envelope surrounds lives on payment infrastructure; vertical fits on fintech payment solutions and the payment gateway for digital goods. The build motion inside your own product is on integrated payment solutions; the getting-started guide is on accept online payments.
Operational features you use every week
Everything below ships to every merchant BazPay boards. There is no premium services tier that unlocks the status page or the changelog — they are part of the platform.
-
Dashboard admin
Users, roles, audit log, API keys, webhook secrets, rule builder — all administered by your team without a support ticket.
-
Real-time analytics
Approval, decline, fraud verdict and payout data visible within seconds — see what a rule change did before the next scheme cycle.
-
Public status page
Rail health, planned maintenance windows and incident timelines published in the open — the operational surface of the gateway service.
-
Signed webhooks
HMAC-signed, replay-protected events for every state change; delivery retries on an exponential schedule for up to 72 hours.
-
Sandbox parity
Sandbox replays production-shaped traffic, decline codes, 3-D Secure 2 flows and dispute events, so tests match the live surface.
-
Versioned API
Every breaking change ships behind a version header and follows a documented deprecation window; no silent surprises in your integration.
-
Changelog and roadmap
A public changelog and quarterly product review with named merchants means you see rate changes and features before they land in production.
-
Alerting and metrics
Push approval quality and settlement timing to your existing observability stack via webhooks and CSV export — the gateway service leaves your telemetry intact.
The service surface is part of the API
Status and maintenance are not out-of-band emails. They are first-class events on the same signed-webhook stream as approvals and settlements. Wire the same handler that processes payment events to also read the operational stream, and your on-call sees gateway health in the same channel as their existing alerts.
BazPay-Signature: t=1717257600,
v1=8b3f1c...9d2e
{
"id": "evt_02H9",
"type": "maintenance.scheduled",
"data": {
"object": {
"id": "mnt_5F9k",
"rail": "visa",
"window_start": 1717344000,
"window_end": 1717351200,
"impact": "reduced_throughput"
}
}
}Incident, degradation and recovery events use the same envelope. Read the full event catalogue in the API reference and handler samples in the developer docs.
Who uses BazPay's payment gateway services
The service model is scoped to the four merchant profiles BazPay boards. Underwriting policy is unchanged whether you contract for gateway services alone or the full platform.
-
E-commerce sellers
DTC brands and multi-country storefronts running Shopware, Magento 2, WooCommerce or PrestaShop. Named plugin support during peak season, not just at boarding.
-
Subscription software
SaaS teams with card-on-file books that cannot afford a silent renewal outage. Migration services move the vault safely between processors.
-
Professional services
Agencies and consultancies where the finance team is small and needs help wiring reconciliation once, not every quarter.
-
Digital publishers
Publishers running membership sites where paywall and renewal flows are audited alongside acceptance, not treated as a separate product.
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. Method and rail depth: iDEAL payments and Single Euro Payments Area processing.
Security, change management and audit
The gateway service runs inside a PCI DSS Level 1 environment assessed each year. Dashboard actions are audit-logged. API changes go through a versioned release with a documented deprecation window, so an integration you build against v1 keeps working when v2 lands.
- 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
- Change management
- Versioned API, published deprecation policy, audit-logged dashboard actions
Questions merchants ask about payment gateway services
What do BazPay's gateway services actually include beyond the API?
The service layer around the API — integration and migration engineering, ongoing merchant support, dashboard administration, public status/incident communication, sandbox parity, versioned changelog and quarterly roadmap access. In practice, that means a named integration manager during onboarding and a shared channel for engineering and finance questions once you are live.
How do online payment gateway services differ from just having a REST API?
An API is the interface. Payment gateway services are the operational envelope around it — the people who help you integrate, the process that keeps changes non-breaking, the status page that tells you when a rail is degraded, and the migration engineers who move your vault when you switch from another processor. The API without those services is a manual, and manuals do not go live under deadline.
Do I get a named point of contact, or a ticket queue?
A named integration manager during onboarding and go-live, plus a shared channel and email for the operational phase. Escalation paths are documented on day one. There is no long-tail chat widget between you and the engineers.
Which migration paths are supported?
The most common migration is moving from a reseller PSP or another regional acquirer. Card 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 run in parallel until traffic is proven on the new stack.
What runs on the dashboard, and what needs an engineer?
User and role management, API keys, webhook secrets, fraud rule thresholds, payout schedule, refunds and captures are all in the dashboard for authorised users. Anything that changes the shape of your integration — a new API version, a new payment method wired in — still needs an engineering release on your side, but the request itself is dashboard-driven.
How is uptime and incident status communicated?
A public status page publishes rail health per network and any active or planned maintenance. Signed webhooks fire on incidents and maintenance windows, so your on-call receives them where the rest of your alerts already live. Post-incident notes are published in the changelog.
Are these gateway services available to smaller merchants?
Yes. Onboarding, sandbox access, dashboard admin, the status page, the changelog and the shared channel are available to every merchant BazPay boards, regardless of monthly volume. Underwriting scope is unchanged — EU, UK and Commonwealth e-commerce, subscription software, professional services and digital publishers.
Is anything specific about the payment gateway services out of scope?
BazPay does not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants. BazPay is not a merchant of record, does not act as a marketplace of third-party PSPs and does not provide consumer wallet functionality.
Scope your integration with a named engineer
Share your business model, existing stack and timeline. An integration manager will confirm boarding fit and map the migration inside one working day. See also card and APM processing, merchant acquiring and the wider network payment gateway.