Payment processing software for online business.
BazPay is payment processing software built for merchants across the EU, UK, Australia, Canada and New Zealand. A REST API, a typed SDK client, hosted fields, mobile SDKs and a web dashboard share one signing secret and one charge object across cards, wallets, local payment methods and SEPA Instant.
Built for e-commerce sellers, subscription software firms, professional-services businesses and community organisations. The software product ships on the same platform that clears the transaction, so there is no separate gateway hop.
Why teams choose BazPay as their payment processing software
Four things stay true whether you integrate on a Friday afternoon or run a six-month enterprise procurement. They are the reasons product and engineering teams stay on the platform after the first go-live.
-
One software product, every rail
The same charge object covers cards, wallets, local methods and SEPA Instant. Adding a new rail is a request-flag change — no separate SDK, no separate dashboard, no separate webhook contract.
-
Deployment fits the stack you already run
Hosted checkout, drop-in components or server-to-server — the payment processing software adapts to the front end you have. Migrating between models later is a configuration change, not a rewrite.
-
Signals travel with every event
Every state change ships with the 3-D Secure outcome, the rule verdict and the interchange bucket. Your systems get the context they need without a second API call.
-
Developer surface designed for a review
Idempotency keys, HMAC-signed webhooks, versioned endpoints and typed error codes. Nothing surprising to explain in the code-review session before go-live.
Deployment models the software supports
Four surfaces, one payment engine. Pick the one that matches your product today — switching to a different model later is a configuration change, not a rewrite.
-
Hosted
Hosted checkout page
Fastest path to compliant acceptance. Shoppers land on a BazPay-hosted page, complete payment inside our PCI scope and return to your app on success or cancel. Zero card data ever touches your servers.
- Zero PCI code
- Brand-styled
- Auto 3-D Secure
-
Drop-in
Hosted fields / drop-in
Card, expiry and CVC inputs served from our PCI environment inside your own checkout page. Full control over layout and CSS, no PAN in your DOM. The right default for most e-commerce integrations.
- Custom layout
- Merchant SAQ A
-
S2S
Server-to-server
Full API access for products that need to render the entire checkout in their own UI — native mobile, PoS software or embedded flows. Requires a wider PCI scope; hosted alternatives above avoid it.
- Full control
- Mobile SDK friendly
-
Mobile
iOS and Android SDKs
Native SDKs plug Apple Pay, Google Pay and card entry into your app with the same charge object, the same idempotency contract and the same signed webhook stream as the web integration.
- Apple Pay
- Google Pay
- Card entry
Ready-made checkout implementations live on hosted checkout products. Plugin coverage on the integrations page. Related cluster: payment processing platforms, transaction processing and the online payment platform.
What the software includes
Eight modules ship on the standard integration. Turn each one on from the dashboard. The API surface, the signing secret and the event catalogue stay the same across all of them.
-
Acceptance API
One REST endpoint authorises, captures and refunds across cards, wallets, local APMs and SEPA Instant.
-
Dashboard
Web UI for approvals, disputes, refunds, rule editing and payout reconciliation. Role-based access with per-team scopes.
-
Recurring billing
Card-on-file, dunning-aware retries and MIT exemptions on renewals — recurring billing native to the software.
-
Fraud rule engine
Device, velocity and geography signals scored inline with allow / step-up / review / block verdicts you tune yourself.
-
3-D Secure 2.2 engine
Frictionless flow first; PSD2 exemption logic claims TRA, low-value, trusted-beneficiary and MIT where the rules allow.
-
Payouts
SEPA and SEPA Instant to your named settlement account. SWIFT and push-to-card available on approved corridors.
-
Real-time analytics
Approvals, declines, fraud verdicts and disputes visible within seconds. Filter by BIN, country or rail; export any view.
-
Developer tooling
Sandbox with replay data, typed SDK client, versioned changelog and signed-webhook test dispatcher.
How the software handles one payment
Six stages sit between the checkout button and the settled dollar on your account. Each stage is visible in the dashboard and fires a signed webhook.
-
Create a payment
POST a charge with amount, currency and payment_method. Idempotency-Key headers make the request retry-safe.
-
Render the surface
Hosted redirect, drop-in fields or your own UI — the response tells the front end which surface to open next.
-
Authenticate
3-D Secure 2.2 fires only when the risk earns it; PSD2 exemption logic claims the rest transparently.
-
Authorise
The software posts to the network with the authentication result and CAVV bound to the transaction for issuer scoring.
-
Confirm
The response returns the authorisation code, the interchange bucket and any exemption applied.
-
Reconcile
Settlement events, refunds and disputes fire as signed webhooks keyed to the same charge ID.
The API surface engineers see on day one
The charge object is the unit of work. One endpoint authorises, captures and refunds. The typed SDK client wraps the REST calls with retries, idempotency and pagination baked in — a Node example is below; the developer docs cover every supported language.
import BazPay from "@bazpay/node";
const client = new BazPay(process.env.BAZPAY_SECRET_KEY);
const charge = await client.charges.create({
amount: 4990,
currency: "EUR",
payment_method: "card",
capture: "auto",
three_d_secure: "required_if_needed",
metadata: { order_id: "ORD-10842" },
}, {
idempotencyKey: "8f1c-2b3a-9e4d",
});Every request is idempotent under the header shown; a network retry never posts twice. The response returns a canonical charge object identical in shape across every payment method. Read the full schema in the API reference.
What separates the software from generic gateway software
Payment processing software solutions are not interchangeable. Below is the checklist BazPay's own procurement customers apply during evaluation, with our answer on each row.
| Dimension | BazPay software | Typical gateway-only vendor |
|---|---|---|
| Deployment options | Hosted / drop-in / S2S / mobile SDK | Hosted only or S2S only |
| Event contract | HMAC-signed, replay-safe, idempotent | Unsigned or per-vendor formats |
| PCI shape | Merchant SAQ A default, S2S optional | Full merchant PCI when PAN reaches server |
| Sandbox | Self-service, replay data, no demo call | Sales-gated sandbox |
| Rule editing | Dashboard, effective on next order | Ticket, deploy cycle |
| Language coverage | Typed SDK client + REST | REST only, no typed client |
| Data residency | In-region data residency, GDPR-native | Offshore fallback common |
For a direct-vs-reseller processor comparison, see payment processors. For the network-connectivity layer, the network payment gateway page.
Who runs on the software
BazPay is regional payment processing software. Underwriting is scoped to merchant profiles with predictable chargeback ratios and clean AML posture. Four common ones are below.
-
E-commerce software
DTC and multi-country storefronts embed hosted fields or drop-in components; refunds, capture and webhooks work out of the box.
-
SaaS billing software
Subscription products call the same API from their billing loop — MIT exemptions, dunning-aware retries and network-token refresh keep renewals alive.
-
Sports clubs and memberships
Payment processing software for sports clubs covers dues, event tickets, merchandise and membership renewals under one merchant contract.
-
Professional-services apps
Invoice-payment portals for agencies, consultancies and B2B firms with higher tickets and named-payer trust lists.
Out of scope for BazPay: adult, gambling, cannabis, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. BazPay is not white-label software for banks and is not a merchant of record.
Security and compliance signals
The software 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.
- PCI DSS Level 1
- Annual assessment on the acquiring and gateway environment
- Merchant SAQ A
- Hosted fields and 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
- Signed webhooks
- HMAC-SHA256 signature with timestamp header on every event
Questions engineers and product leads ask first
What does BazPay's payment processing software actually include?
A REST API for acceptance, refunds, captures and payouts; hosted-field and drop-in JavaScript components; iOS and Android SDKs; a web dashboard for approvals, disputes and reporting; a fraud rule engine; signed webhooks; and a sandbox with replay data. Every module talks to the same charge object and shares one signing secret.
How does online payment processing software differ from a bare gateway?
A bare gateway forwards authorisation messages to an acquirer you contract separately. Online payment processing software is the full stack — acceptance, billing, fraud, payouts, reporting and the dashboard — behind one API. BazPay is the second kind: the software and the acquiring live under one platform.
How do I evaluate payment processing software companies?
Look for: signed HMAC webhooks with replay protection, idempotency-key semantics on every write, versioned endpoints, a self-service sandbox with production-shaped data, and a rule engine editable from the dashboard rather than a code deploy. If any of those are absent, integration work stretches from weeks to quarters.
Do you offer payment processing software for banks?
No. BazPay is a licensed regional acquirer and gateway, not white-label software licensed to a bank. If your business processes payments on behalf of end-customer merchants under a bank licence, BazPay is not the right fit — this is direct-to-merchant software for the merchant themselves.
Is there payment processing software for sports clubs and community organisations?
Yes, where the model fits regional underwriting: membership dues, event-ticket sales, merchandise, sponsorship invoices and recurring subscriptions. Card-on-file with dunning-aware retries keeps renewals live, and hosted checkout keeps PCI scope at merchant SAQ A. Marketplace-style flows where the club redistributes funds to third parties are outside scope.
Which languages does the SDK client cover?
The typed SDK client covers the languages most common in regional commerce stacks — the current list is on the developer docs. Anything without a native client uses the REST API directly; the request and response shapes stay stable across versions, and the changelog notes every breaking change ahead of time.
How is electronic payment processing software priced?
Card acceptance runs on interchange++, so interchange, scheme fees and the BazPay margin appear on every settled transaction. Local payment methods and payouts carry their own per-transaction rates. Current schedules are on the pricing page — no seat licences, no per-endpoint charges, no hidden dashboard fees.
Can I migrate from another payment processing software solution?
Yes. Stored credentials and network tokens can be imported from an incumbent processor under a scheme-approved migration, subject to the receiving bank's consent letters. Renewals and card-on-file charges continue on the new platform without asking shoppers to re-enter their card.
Try the software on sandbox data
Open a sandbox account and post your first charge through the API in the same hour. Prefer a walkthrough? A payments specialist can map your integration alongside card and APM processing, recurring billing, anti-fraud controls and payouts.