Menu
Talk with sales

Integration questions? [email protected]

Shopping cart payment gateway for online storefronts.

BazPay handles shopping cart payment processing behind the four commerce stacks that most merchants in the EU, UK, Australia, Canada and New Zealand already run — WooCommerce, Magento 2, PrestaShop and Shopware. Hosted fields render inside the cart checkout, line items ride with the charge, and returning shoppers pay in one tap with a network-tokenised saved card.

Built for merchants in the EU, UK, Australia, Canada and New Zealand: DTC brands, multi-country e-commerce, membership shops and subscription-plus-add-on storefronts. Direct regional acquiring, no cart handoff to a foreign domain.

Talk with sales Explore integrations

Why storefronts pick a purpose-tuned shopping cart gateway

The gap between a generic payment API and a shopping cart integration is the amount of e-commerce plumbing you do not have to write. Four commitments below make that gap visible.

  • Drop-in plugins for the regional commerce stack

    Maintained plugins for WooCommerce, Magento 2, PrestaShop and Shopware ship with checkout, refunds, capture, webhooks and recurring billing wired up. A storefront takes test traffic in an afternoon.

  • Cart line items travel with the charge

    SKU, quantity, unit price, tax bucket and shipping line are attached to the charge object as metadata and propagate through settlement, refund and dispute events. Reconciliation stays line by line, not lump-sum.

  • Guest checkout without a vault handoff

    First-time shoppers pay through hosted fields without an account. Returning shoppers see a saved card via network tokens — no third-party wallet redirect, no cart handoff to a foreign domain.

  • Abandonment tools that fit an existing CRM

    Every stalled cart fires a signed webhook with the payment_intent and the line items. Wire it to your existing email or CRM automation — no closed abandonment loop that only speaks to the gateway.

Plugins for the four common regional shopping-cart platforms

Each plugin is signed, maintained and installable through the platform's normal channel. Configuration is a public API key, a webhook secret and the merchant account identifier — no bespoke connector work.

  • WordPress

    WooCommerce plugin

    Full block-based checkout support, hosted fields, saved cards for logged-in shoppers, refunds and captures from the WordPress admin. Compatible with the WooCommerce Subscriptions add-on for recurring billing.

    • Block checkout
    • Saved cards
    • Subscriptions

  • Adobe Commerce

    Magento 2 module

    Composer-installable module for Magento 2 Open Source and Adobe Commerce. Multi-store IDs are preserved, so each storefront reports and reconciles under its own scope.

    • Multi-store
    • Composer
    • Order sync

  • PrestaShop

    PrestaShop module

    Module for PrestaShop 1.7 and 8.x. Configures hosted fields in the cart checkout, wires refund and capture flows, and posts order events to the shop's back office.

    • 1.7 / 8.x
    • Back-office sync

  • Shopware

    Shopware 6 plugin

    Signed Shopware 6 plugin that plugs into the storefront's shopping cart and admin flows for capture, refund and recurring billing. Compatible with headless Shopware storefronts via the Store API.

    • Shopware 6
    • Headless-ready

Full listing on the integrations page. Prebuilt checkout surfaces available in hosted checkout products.

From add-to-cart to settled order

Six stages sit between the shopper adding an item and the funds landing in your regional settlement account. Each stage is visible in the dashboard and each stage change fires a signed webhook.

  1. Add to cart

    Shopper adds items. The storefront updates the cart total and applies your tax and shipping rules — BazPay is not yet in the flow.

  2. Checkout

    On checkout, the plugin creates a payment intent for the cart total and renders hosted fields inside the storefront's own template.

  3. Authenticate

    3-D Secure 2.2 runs only when the risk earns it. Frictionless flow first; PSD2 exemption logic covers most low-value shopping-cart baskets.

  4. Authorise

    The charge posts to our acquirer with the line items and the authentication result attached. The storefront receives the response and marks the order.

  5. Confirm order

    The plugin marks the order as paid and triggers your fulfilment queue (stock reservation, warehouse pick, download key).

  6. Settle & report

    Funds settle per scheme cycle to your local settlement account. Line items reconcile per SKU in interchange++ reports and back in your commerce admin.

Cart-aware gateway vs a generic checkout redirect

Two credible integration paths exist for a shopping cart. One keeps the shopper inside your storefront's template and preserves the line items end to end. The other bounces the cart off your domain and returns a lump-sum charge. The comparison below explains why the first path holds up on reconciliation and returning-shopper conversion.

BazPay cart-aware gateway compared with a generic checkout redirect
Dimension BazPay (cart-aware) Generic checkout redirect
Cart integration path Signed plugin per commerce stack Manual API build per storefront
Checkout render Hosted fields inside cart template Full-page redirect off-store
Saved cards Network-tokenised, one-tap returning Reprompt for PAN every session
Abandonment signal Signed cart_intent.expired webhook None or vendor-locked email tool
Line-item reconciliation SKU / tax / shipping through settlement Lump-sum charge total only
Recurring on the same cart Native subscription reference on charge Separate biller with a card token

Fees and settlement structure on the pricing page. Compare the wider platform on payment processors and payments solutions.

Features the shopping cart integration ships by default

Every capability below is on the standard integration. Turn features on with a request flag or a dashboard toggle — no enterprise-tier gate on the primitives storefronts depend on.

  • Hosted fields in the cart

    Card, expiry and CVC inputs served from our PCI environment inside the storefront checkout, keeping your annual return at SAQ A.

  • Saved-card returning flow

    Returning shoppers see a one-tap saved card via network tokens — no third-party redirect, no cart handoff, no lost session cookies.

  • Apple Pay / Google Pay

    Express-checkout buttons render in the cart summary as well as at checkout. Wallet-supplied network tokens keep PAN out of the flow.

  • Guest checkout

    First-time shoppers pay without an account. Their card can be vaulted at the end of the flow if they choose to create one.

  • Multi-currency totals

    Cart totals authorise in the shopper's currency and settle in EUR to your nominated IBAN. Named settlement currencies available on approved corridors.

  • Cart abandonment webhook

    A signed cart_intent.expired event fires when a shopper leaves before authorising. Wire it into your existing recovery email or CRM.

  • Line-item metadata

    SKU, quantity, unit price, tax bucket and shipping line ride with the charge — refunds, disputes and settlement all reference the same lines.

  • Refund at line level

    Full and partial refunds by line item from the plugin admin or the API. Refund events fire on the same signed-webhook stream as charges.

A payment intent that carries your cart lines

The cart total is one number; the story behind it is the line items. BazPay accepts both on the same payment-intent create call. Every line item survives through settlement and shows up in refunds and dispute evidence, so your commerce admin and your finance ledger stay in agreement. 

POST /v1/payment_intents
Idempotency-Key: 8f1c-2b3a-9e4d
{
  "amount": 12450,
  "currency": "EUR",
  "payment_method_types": ["card", "ideal", "apple_pay"],
  "capture_method": "automatic",
  "line_items": [
    { "sku": "SHIRT-M-BLK", "qty": 2, "unit_price": 4500, "tax_code": "STD" },
    { "sku": "STICKER-01", "qty": 1, "unit_price": 200, "tax_code": "STD" },
    { "type": "shipping",  "unit_price": 750,           "tax_code": "STD" }
  ],
  "shopper_ref": "cust_9C21"
}

The response returns a canonical payment intent with client secret, next actions and any 3-D Secure step-up requirement. The complete schema lives in the API reference.

Storefronts already running on BazPay carts

The four storefront profiles below share the same shopping cart integration. Each gets the same plugins, the same API surface, the same webhook envelope and the same interchange++ reporting.

  • DTC brands

    Single-currency storefronts on WooCommerce or Shopware where checkout speed and saved-card returning flow drive repeat conversion.

  • Multi-country e-commerce

    Cross-border stores on Magento 2 or PrestaShop with per-country tax, shipping and payment-method preferences reconciled under one merchant contract.

  • Membership and subscription shops

    Storefronts selling recurring memberships and one-off add-ons in the same cart. Card-on-file renewals plus fresh add-to-cart flow on the same charge object.

  • Digital-good storefronts

    Cart-driven purchase of downloadable products with instant fulfilment webhook after authorisation. See also the digital goods gateway page for the fulfilment specifics.

Vertical detail on payment gateway for digital goods and recurring billing. Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM.

Security and compliance for cart checkout

Hosted fields render inside your cart template but from our PCI DSS Level 1 environment, so card numbers never touch the storefront database. That keeps your merchant scope at SAQ A even on custom themes. Authentication runs on every cart checkout 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 in the cart keep card data out of your storefront database
Authentication
3-D Secure 2.2 with automatic exemption logic on every cart checkout
GDPR
In-region data residency; DPA on request
Plugin signing
Signed distribution for WooCommerce, Magento 2, PrestaShop and Shopware 6

Questions storefronts ask first

How does BazPay handle shopping cart payment processing?

The BazPay plugin renders hosted fields inside your storefront's cart checkout, creates a payment intent for the cart total on the server side, then authorises against our regional acquirer. Line items — SKU, quantity, unit price, tax and shipping — are attached to the charge as metadata and stay with the transaction through settlement, refunds and disputes.

Which shopping cart platforms are supported with maintained plugins?

Maintained plugins ship for WooCommerce (WordPress block and legacy checkout), Magento 2 (Open Source and Adobe Commerce), PrestaShop 1.7 and 8.x, and Shopware 6 (including headless via Store API). Each plugin covers checkout, refunds, capture, webhooks and recurring billing out of the box. Custom shopping carts integrate against the REST API — the same endpoints the plugins use.

Can shoppers check out as guests, or do they need an account?

Guest checkout is supported natively. First-time shoppers pay through hosted fields without creating an account. If they do register during the flow, the plugin vaults the card gateway-side so their next visit is a one-tap saved-card checkout with a network token — no third-party wallet handoff.

Does the shopping cart payment gateway support cart abandonment recovery?

Yes. Every stalled payment intent fires a signed cart_intent.expired webhook containing the line items, the shopper reference and the last-seen state. Wire it into your existing email service or CRM to trigger the recovery flow that already lives in your marketing stack — no proprietary abandonment loop.

How are refunds handled from the shopping cart admin?

Refunds are issued from the plugin admin in your commerce stack (WordPress, Magento, PrestaShop, Shopware) or directly via the API. Full and partial refunds work at line-item granularity so a single returned SKU refunds cleanly without unpicking the rest of the cart. Every refund fires a signed webhook so downstream systems stay in sync.

Can the shopping cart authorise in the shopper's currency?

Yes. Cart totals authorise in the shopper's currency across EUR and more than twenty presentment currencies. Settlement defaults to EUR into a regional settlement account, with named settlement currencies available on approved corridors. Currency conversion applies where the merchant contract and the presentment currency differ; specifics live on the pricing page.

Which shopping-cart merchant types does BazPay board?

Merchants across the EU, UK, Australia, Canada and New Zealand: DTC brands, multi-country e-commerce, membership shops, subscription software with add-on carts, professional-services shops and digital-goods storefronts. BazPay does not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants, regardless of the shopping cart platform they run.

Do saved cards survive a shopping-cart migration or theme change?

Yes. Card credentials live in the gateway vault — not in the storefront database — and are keyed to your BazPay merchant. Theme changes, plugin upgrades and cart-platform migrations do not invalidate the vault, and network tokens keep working through card reissues.

Plug the payment gateway into your shopping cart today

Share your storefront platform, monthly volume and any incumbent gateway. An integration manager will confirm boarding fit and map the plugin install inside one working day. See also card and APM processing, network payment gateway and payment processors.

Talk with sales Read the developer docs