Menu
Talk with sales

Integration questions? [email protected]

Credit card processing software — hosted, drop-in and REST.

BazPay ships credit card processing software as a set of interchangeable surfaces — hosted checkout, hosted fields, drop-in components, mobile SDKs and storefront plugins — all driven by one versioned REST API. The software and the regional acquirer are the same entity, so a card charge stays inside one platform from checkout to settled dollar.

Built for merchants across the EU, UK, Australia, Canada and New Zealand: e-commerce sellers, subscription software firms and professional-services businesses. No PAN on your servers, one signed webhook stream, interchange++ reporting on every charge.

Talk with sales Read the API reference

Why the software plus the acquirer beats software plus a separate bank

A gateway that forwards traffic to an external acquirer means two contracts, two portals and two webhook envelopes. Four properties collapse that surface when the software and the acquirer are the same entity.

  • Software and the acquirer under one contract

    Most credit card processing software is a gateway that forwards traffic to a separate acquiring bank. BazPay is both the software layer and the regional acquirer, so a card charge stays inside one platform from checkout to settled dollar.

  • Hosted fields keep raw PAN out of your stack

    The credit-card inputs render inside BazPay's PCI environment. Your servers never see the raw card number, and your annual PCI return stays at merchant SAQ A instead of the full merchant audit.

  • One integration surface across every checkout

    Hosted checkout page, drop-in components, hosted fields, mobile SDKs and storefront plugins share the same charge object. Pick the surface that suits your build without changing the acceptance code.

  • Interchange++ transparency on every settled charge

    The software reports interchange, scheme fees and BazPay's margin as separate lines on every credit card transaction. Finance teams reconcile against the source, not a blended rate.

The integration surfaces the software ships with

Four surfaces let you pick where BazPay meets your product. Every one uses the same underlying charge object; pick by build style, not by capability gap.

  • Hosted page

    Hosted credit-card checkout

    Redirect the shopper to a BazPay-hosted checkout page — the fastest way to run credit card processing without touching card data. The look and feel are themed to your brand and support cards, wallets and local APMs on the same page.

    • Zero PCI on your side
    • Themed
    • Refunds inline

  • Hosted fields

    Hosted fields inside your checkout

    Card, expiry and CVC inputs served from our PCI environment inside your existing checkout. Your shoppers stay on your site; your engineers never handle a live PAN.

    • SAQ A scope
    • In-page UX

  • Drop-in JS

    Drop-in components

    Prebuilt payment forms and checkout summaries drop into an admin or portal with a few lines of JavaScript, themed to match your product surface.

    • Admin-friendly
    • Themeable

  • API + plugins

    REST API and storefront plugins

    One versioned REST endpoint drives everything above; maintained plugins for the major regional commerce stacks configure the surface with a single screen.

    • Versioned REST
    • WooCommerce
    • Magento 2

Ready-made surfaces on hosted checkout products. Full plugin list on the integrations directory.

Credit card processing, how it works end to end

Six stages describe a single card charge from PAN entry to settled dollar. Each stage is visible in the dashboard and each stage change fires a signed webhook.

  1. Card entry

    The shopper types the card number into hosted fields — inside our PCI scope — or picks a saved card from your dashboard-driven vault.

  2. Tokenise

    The gateway vault issues a stable token. Network tokens replace the PAN at storage time for card-on-file renewals.

  3. Risk + 3-D Secure

    The inline fraud engine scores the order and requests 3-D Secure 2.2 only when the risk earns it — most credit card checkouts stay frictionless.

  4. Authorise

    The processor posts the request to the acquirer (also BazPay) on the regional acquiring licence, then to the card scheme, then to the issuer.

  5. Capture

    Capture immediately or later. Partial captures and partial refunds both post cleanly on the same charge object.

  6. Settle + report

    Funds reconcile per scheme cycle into your local settlement account. Every settled charge carries interchange++ line detail.

Software + acquirer on one platform vs stitched vendors

Buying the credit card processing software from one vendor and the acquiring from another is a valid pattern. The comparison below shows where a single-platform model saves engineering and reconciliation time.

BazPay software plus acquirer compared with stitched-vendor setup
Dimension BazPay (software + acquirer) Software + separate acquirer
Software + acquirer One contract, one entity Gateway software + separate acquirer
PCI scope on your side Merchant SAQ A via hosted fields Full PCI if PAN passes your servers
3-D Secure 2 engine Native, with exemption logic Bolt-on or off
Reporting Interchange++ per transaction Blended-rate summary
Webhook contract Signed HMAC, replay-protected, idempotent Unsigned or per-vendor formats
Settlement Per-scheme cycle to your local settlement account Aggregated payouts, common delay
Fraud engine Inline, dashboard-configurable Extra subscription per method

Buyer's shortlist on payment processors. Method depth on card and APM processing. Boarding path on merchant acquiring.

Features shipped in the standard software integration

Every capability below is available on the standard integration. No premium tier gates hosted fields, network tokens, dispute defence or the versioned webhook contract.

  • Hosted fields + drop-in JS

    Ready-made surfaces for credit card entry, saved cards and 3-D Secure 2 challenge rendering — themed to your product.

  • Gateway vault

    Store credentials once for card-on-file. Network tokens refresh automatically when a card is reissued so renewals keep working.

  • REST API + signed webhooks

    One versioned endpoint creates a card charge; every state change emits an HMAC-signed, replay-protected event.

  • 3-D Secure 2.2 engine

    Authentication with automatic exemption logic — TRA, low-value, trusted-beneficiary and MIT — kept off the frictionless path.

  • Idempotent requests

    Retry-safe writes across create, capture, refund and payout. A network blip never becomes a double credit card charge.

  • Dispute defence

    Chargebacks arrive from the issuer through the scheme; the software pre-assembles the evidence packet with the 3-D Secure result.

  • Interchange++ reporting

    Interchange (to the issuer), scheme fees and processor margin split per settled charge — every credit card line reconciles cleanly.

  • Storefront plugins

    Maintained plugins for WooCommerce, Magento 2, PrestaShop and Shopware — install once, configure keys, done.

One REST endpoint runs every credit card charge

The payment_method field selects card for a credit card charge; the response object shape is stable across cards, wallets, local APMs and SEPA Instant so your integration reads uniformly. Idempotency headers keep retries safe end to end. 

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 interchange bucket and any 3-D Secure result. Full schema in the API reference.

Where merchants run BazPay credit card processing software

Four merchant profiles fit BazPay's regional underwriting. Each uses the same software surfaces and the same signed-webhook stream.

  • E-commerce sellers

    DTC brands and multi-country storefronts using hosted fields or plugins to accept credit card payments inside their existing checkout.

  • Subscription software

    SaaS teams billing monthly and annually with card-on-file renewals, MIT exemptions and dunning-aware retries on the same software.

  • Professional services

    Agencies and B2B service firms sending hosted payment pages for higher-ticket invoices with card acceptance and named-payer trust lists.

  • Digital publishers

    Membership and paywall sites where a hosted checkout page or drop-in components accept credit cards without any custom code.

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 signals for credit card processing

Card handling 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 3-D Secure 2.2 and automatic exemption logic. Regional data residency and GDPR are default, not tier-gated.

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
Scheme registrations
Visa VIRP and Mastercard SPoC/PCI-CP where required

Questions merchants ask about credit card processing software

What is credit card processing software, and what does BazPay ship?

Credit card processing software is the technical layer between a merchant's checkout and the card networks. On BazPay that layer includes hosted checkout pages, hosted fields, drop-in JavaScript components, mobile SDKs, maintained storefront plugins and a versioned REST API — all backed by direct regional acquiring on the same platform.

How does credit card processing work when I integrate the BazPay software?

The shopper enters card details inside hosted fields (or a hosted page), the gateway tokenises the PAN, the risk engine scores the order and requests 3-D Secure 2.2 if needed, the acquirer posts the authorisation to the scheme, the issuer approves or declines, and the response returns as a canonical charge object. A signed webhook confirms the outcome. Settlement lands in your local settlement account per scheme cycle.

How do the credit card processing services and the acquirer fit together on BazPay?

They are one platform. BazPay operates both the gateway software and the acquiring role on its own regional licence, so a card charge does not cross an external boundary between the software and the acquirer. That collapses the reporting, the webhook contract and the reconciliation surface.

Does the software support ACH payment with credit card, or US bank rails?

No. ACH is a US bank rail; BazPay is a regional platform and does not connect to ACH. The bank-rail equivalent on BazPay is SEPA and SEPA Instant. If your business specifically needs US ACH processing, BazPay is not the right fit.

Which merchant services and credit card processing plans do merchants across the EU, UK, Australia, Canada and New Zealand pick?

The standard integration ships every capability listed on this page — hosted fields, drop-in JS, API, plugins, vault, 3-D Secure 2.2, dispute defence and interchange++ reporting. There is no premium tier that gates the sandbox or the webhook contract. Rate structure lives on the pricing page.

Can the credit card processing gateway also run subscriptions and refunds?

Yes. Recurring charges, saved-card renewals and partial refunds all use the same REST endpoint and the same signed-webhook envelope as one-off card payments. Recurring billing is native to the platform rather than a separate biller sitting on top of a card token.

How does compliance work for merchant credit card processing on BazPay?

Card handling runs inside a PCI DSS Level 1 environment assessed each year. Hosted fields and gateway vaulting keep your annual return at merchant SAQ A. Authentication runs on every card charge with 3-D Secure 2.2 and automatic exemption logic. GDPR runs on In-region data residency by default.

Which merchant profiles are eligible for online merchant services & credit card payment processing on 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.

Ship a credit-card checkout this sprint on one contract

Share your build style — hosted page, hosted fields, drop-in or custom API — and a named engineer will confirm boarding fit and map the integration inside one working day. See also merchant acquiring, payment processors and pricing.

Talk with sales Read the developer docs