Menu
Talk with sales

Integration questions? [email protected]

Credit card payment processor — one API for online, mobile and recurring charges.

BazPay processes credit card payments end to end on a direct regional acquiring licence. Internet, mobile and recurring credit-card charges share the same REST API, the same signed webhook stream and the same canonical charge object. Interchange++ reporting lands on every settled line.

Built for merchants across the EU, UK, Australia, Canada and New Zealand: e-commerce sellers, subscription software firms and professional-services businesses. No aggregated MID, no reseller middle layer, no silent renewal churn.

Talk with sales Read the API reference

Why merchants pick a direct credit card payment processor

Direct acquiring beats reseller-on-shared-MID for merchants whose monthly credit-card volume is worth reconciling line by line. Four properties keep the acceptance layer transparent and predictable.

  • Direct acquirer, not a reseller

    BazPay is the credit card payment processor and the acquirer for its regional book. There is no aggregator sitting between you and Visa or Mastercard; your merchant identifier is named to your legal entity and settlement lands in your own local settlement account.

  • One API for internet, mobile and recurring

    The same charge object handles internet credit card payment processing on the web, mobile card entry in an app SDK, and merchant-initiated recurring credit card payment charges from a stored credential. No separate SDK per surface.

  • Low PCI scope by construction

    Hosted fields serve card, expiry and CVC inputs from our PCI DSS Level 1 environment, so raw PAN never touches your stack. Your merchant PCI scope stays at SAQ A whether you charge one card or millions.

  • Interchange++ transparency on every settled charge

    Interchange, scheme fees and the processor margin split per settled credit card charge. Finance teams reconcile against the source, not against a blended rate on a monthly summary.

Every credit-card surface, one credit card payment gateway

Four surfaces cover where credit-card charges actually happen. Every surface uses the same charge object and the same signed webhook — the difference is where the shopper or merchant initiates the charge.

  • Web

    Online credit card payment processing

    Hosted checkout page or hosted fields render inside your web checkout. 3-D Secure 2.2 runs only when the risk earns it, so most e-commerce credit-card charges stay frictionless.

    • Hosted page
    • Hosted fields
    • Drop-in JS

  • Mobile

    Mobile credit card payment processing

    iOS and Android SDKs render card entry, Apple Pay and Google Pay natively inside your app and produce the same charge object as the web integration.

    • iOS SDK
    • Android SDK
    • Apple Pay
    • Google Pay

  • Recurring

    Recurring credit card payment

    Card-on-file with network tokens, MIT exemptions and dunning-aware retries. Card reissue is handled by automatic network-token refresh, so subscription renewals stay warm.

    • Card-on-file
    • MIT exemptions
    • Dunning

  • Virtual

    Virtual credit card acceptance

    Virtual credit cards issued by corporate expense and B2B payment tools authorise on the same rails as physical cards. BazPay does not issue virtual cards — it accepts them.

    • Corporate cards
    • Expense platforms

Underlying method depth on card and APM processing. The recurring flow up close on recurring billing.

How a credit-card charge processes end to end

Six stages describe processing a credit card payment from checkout to settled dollar. Each stage is visible in the dashboard and each stage change fires a signed webhook.

  1. Collect

    Shopper enters card details on hosted fields or a hosted checkout page. Card data stays inside our PCI environment.

  2. Score

    Device, velocity and geography signals grade the order. Fraud rules read the reason code and set the 3-D Secure path.

  3. Authenticate

    3-D Secure 2.2 runs when the risk earns it. Exemption logic (TRA, low-value, trusted-beneficiary, MIT) claims the rest.

  4. Authorise

    The credit card charge posts to the acquirer with the authentication result bound to the transaction for issuer scoring.

  5. Capture

    Capture at once or later. Partial captures and partial refunds both post cleanly on the same charge ID.

  6. Settle

    Funds reconcile per scheme cycle and land in your local settlement account with interchange++ line detail on every row.

Direct acquirer vs aggregator on credit card processing

The choice usually comes down to time-to-live versus reporting quality and MID structure. The comparison below shows where each model earns its keep for credit-card processing specifically.

BazPay direct acquirer compared with an aggregator for credit card processing
Dimension BazPay (direct) Aggregator
Contract Direct with BazPay as acquirer Reseller on aggregated MID
MID Named to your legal entity Shared across the aggregator's pool
PCI scope Merchant SAQ A via hosted fields Full PCI where PAN passes servers
Recurring Network tokens + MIT exemptions default Silent renewal churn on card reissue
Reporting Interchange++ per transaction Blended-rate summary
Settlement Per-scheme cycle to your local settlement account Aggregated payout, common delay

Fees and settlement on the pricing page. The two sides of a card payment on issuing and acquiring. Buyer's shortlist on payment processors.

Features engineered into the credit card payment processing system

Every capability below is on the standard integration. Turn features on with a request flag or a dashboard toggle — no premium tier gates hosted fields, network tokens or the webhook contract.

  • Hosted fields

    Card, expiry and CVC inputs served from our PCI environment inside your checkout — no raw PAN on your servers.

  • Gateway-side vault

    Store credentials once and re-use them across renewals, upgrades and one-clicks; portable if you ever migrate processor.

  • Network tokens

    Visa and Mastercard network tokens refresh automatically after card reissue, so a saved card keeps working across renewals.

  • 3-D Secure 2.2 + exemptions

    Authentication on every card charge with automatic exemption logic; liability shifts on qualifying authentications.

  • Signed webhooks

    HMAC-signed, replay-protected events for every state change — one signature scheme handles authorisation, capture, refund, dispute and settlement.

  • Idempotent API

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

  • Refunds and disputes

    Full and partial refunds return to the original PAN through the scheme. Dispute evidence is pre-assembled with the authentication result and metadata.

  • Interchange++ reporting

    Interchange, scheme fees and processor margin split per settled charge — the credit card economics fully visible.

One REST call processes a credit-card charge

The payment_method is card. Attach amount and currency; capture immediately or later. Idempotency headers keep retries safe. The response returns a canonical charge object with the authorisation code and any exemption applied. 

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" }
}

Read the full schema in the API reference. Handler samples in the developer docs.

Who runs credit-card processing on BazPay

Four merchant profiles below already run credit-card processing on BazPay across web and mobile surfaces, with recurring charges where the business model calls for it.

  • E-commerce sellers

    DTC brands running regional storefronts on WooCommerce, Magento 2, PrestaShop or Shopware. One credit card payment processor across every market with local acceptance turned on per country.

  • Subscription software

    SaaS teams billing monthly and annual plans with recurring credit card payment on card-on-file, dunning-aware retries and network-token refresh.

  • Professional services

    Agencies and B2B service firms invoicing higher-ticket amounts with enforced 3-D Secure 2 over a ceiling and named-payer trust lists.

  • Digital publishers

    Membership and paywall businesses reconciling small-ticket, high-volume credit-card charges per SKU alongside SEPA Instant-backed corporate subscriptions.

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 does not act as a card issuer.

Security and compliance 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. GDPR applies under In-region data residency; a DPA is available on request.

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 registered where required

Questions merchants ask about credit card payment processing

What does processing a credit card payment actually involve?

The gateway captures card details, tokenises them and forwards an authorisation request to the acquirer. The acquirer presents the request to the card scheme, which routes it to the issuing bank. The issuer authorises or declines, the response returns, and — if approved — funds settle to the acquirer on the scheme cycle and are paid out to the merchant. On BazPay the gateway and the acquirer are the same entity, so there is no external hop.

Are there free credit card payment processing options?

No. Card acceptance always carries interchange, scheme fees and a processor margin. Services that market themselves as "free credit card payment processing" either pass the cost to the shopper as a surcharge or blend it into a higher rate elsewhere. BazPay publishes an interchange++ rate card so every component is visible.

How does virtual credit card payment processing work?

Virtual credit cards issued by corporate expense-management tools or B2B payment platforms authorise on the same card scheme rails as physical cards. BazPay accepts them like any other Visa or Mastercard number. BazPay does not issue virtual cards — that is the issuing side of the payment.

Can BazPay run internet and mobile credit card payment processing under one integration?

Yes. Hosted fields and drop-in JS handle internet credit card payment processing on the web. iOS and Android SDKs handle mobile credit card payment processing inside your native app. Both produce the same canonical charge object and share the same signed webhook stream — one fulfilment handler covers both surfaces.

How is recurring credit card payment handled?

Card-on-file with network tokens is native to the platform. Renewals fire on the schedule you set with MIT exemptions where PSD2 permits. Dunning-aware retries handle soft declines automatically. When a card is reissued, the network token refreshes on the issuer side without asking the shopper to re-enter their card.

What happens on credit card payment settlement?

After authorisation and capture, the transaction moves through the scheme cycle to the acquirer and settles into your EUR balance. Payouts land in your named local settlement account per scheme cycle. Every settlement line carries interchange++ detail, keyed to the charge that produced it.

Which credit card payment platforms and gateways does BazPay compete with?

BazPay is a direct regional acquirer + gateway with a defined acceptance list. It competes most closely with other direct regional acquirers that publish interchange++ rates and name the MID per merchant. It is not comparable to aggregator platforms that pool merchants on a shared MID for faster onboarding — that model trades reporting quality for time-to-live.

Does BazPay process ACH or handle a returned ACH card payment reversal?

No. ACH is a US bank rail; BazPay is regional-focused and does not process ACH. For local bank-rail equivalents, BazPay covers instant credit transfer, BACS Direct Debit and SEPA Instant on the same platform as credit card payment processing.

Which merchant types can board on BazPay's credit card payment processing system?

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.

Process credit-card charges on a direct regional acquirer

Share your business model, monthly volumes and existing processor. A named engineer will confirm boarding fit and map the integration inside one working day. See also payment processors, issuing and acquiring and pricing.

Talk with sales Read the developer docs