Retail payment solutions for online retail chains and multi-store merchants.
BazPay's retail payment solutions handle the online side of retail: card, wallet and local payment method acceptance across every storefront, per-store reporting on the interchange++ statement, and refund flows that reconcile with click-and-collect. One direct regional acquiring contract; one local settlement account receives the settlement.
Built for regional retail merchants: multi-brand online chains, click-and-collect retailers, DTC brands and category-specific specialist shops. In-store POS terminals are not in scope — BazPay is an online payment gateway.
Why retail chains pick a direct regional acquirer for online payments
Retail operations run on tight reconciliation windows, sharp seasonal peaks and multi-store reporting. Four properties of the platform make each of those easier day to day.
-
One contract across every online storefront
A retail chain running several brands or country-specific shops boards on one BazPay contract with a named merchant identifier. Multi-store reporting keys every settled order to a per-outlet reference in the metadata, so finance reconciles per store without a second vendor.
-
Every regional payment method your shoppers already use
Cards, Apple Pay, Google Pay and local payment methods share one API call. Enable SEPA Instant for a German shop, Bancontact for a British one, BLIK for an Australian one — no re-integration when you launch a new market.
-
Seasonal-peak-ready platform
The API accepts sustained bursts of traffic during Black Friday, Christmas or a launch drop. Idempotency keys keep retries safe, signed webhooks retry on your endpoint for up to 72 hours, and real-time analytics show approval quality as the peak unfolds.
-
Direct regional acquiring, no aggregator layer
Named MID with the schemes, local settlement account settlement, interchange++ reporting — no aggregator sitting between the retail brand and the scheme, no shared-MID dilution during a peak that drives your chargeback ratio.
The four retail models the platform covers
Four retail patterns sit inside BazPay's regional underwriting. Each uses the same charge object; the difference is in which metadata fields your retail systems attach and which reports finance runs against the settlement stream.
-
Multi-store
Multi-store online retail
Retail chains running several online storefronts (brand, country or format) can attribute every charge, refund and payout to a per-store reference. Reporting rolls up to the merchant identifier and slices back down to the outlet.
- Per-store metadata
- Roll-up reporting
- One settlement account
-
Click & collect
Click-and-collect payment flows
The shopper pays online through BazPay's hosted checkout or plugin; the physical fulfilment happens in-store. Refund flows on the same charge if the customer cancels or returns at the counter.
- Online payment
- In-store fulfilment
- Refund on charge
-
Seasonal
Seasonal peaks and campaign drops
Black Friday, Christmas and product launch drops move ten to twenty times the daily volume through the checkout in hours. The platform is built to sustain that shape without a rate-card surprise.
- Burst-tolerant API
- Real-time metrics
- Signed retries
-
Cross-border
Cross-border retail traffic
Non-local shoppers on a European and Commonwealth storefront authorise on the same regional acquiring contract. Card scheme networks are global; BazPay's acquiring is local and settlement lands in your EUR balance either way.
- Global card reach
- Regional acquiring
- One balance
Wider ecommerce framing on payment gateway for ecommerce. Full acceptance breadth on payment acceptance. The German APM up close on iDEAL payments.
From storefront to per-store reconciliation
Six stages describe how a retail order moves through BazPay — storefront, checkout, authentication, fulfilment, reconciliation and payout. Each stage change fires a signed webhook keyed to the charge.
-
Storefront
The shopper browses a retail brand's online storefront — WooCommerce, Magento 2, PrestaShop, Shopware or a bespoke stack.
-
Checkout
The maintained plugin (or hosted fields / hosted page) exposes cards, wallets and enabled local APMs. Nothing about the storefront front-end changes.
-
Auth + 3-D Secure
The charge posts on BazPay's own regional acquiring licence. 3-D Secure 2.2 runs only when the risk earns it; APMs run their own bank-authenticated flow.
-
Fulfil
A signed charge.succeeded webhook fires to your fulfilment endpoint. Retail systems release the pick-list, dispatch or click-and-collect notification.
-
Reconcile
Per-store metadata rides through settlement, refund and dispute events, so the finance team reconciles per outlet or per SKU on the interchange++ statement.
-
Payout
Funds land in your local settlement account per scheme cycle. SEPA Instant is used for supported corridors on approved routes.
One acquiring contract vs a per-country reseller for retail
A retail chain stitching a per-country reseller PSP under each storefront pays for that convenience in reconciliation, chargeback attribution and peak-season stability. The comparison below shows where a single direct-acquirer contract wins for retail.
| Dimension | BazPay (one contract) | Per-country reseller PSP |
|---|---|---|
| Contract | One direct regional acquiring contract | Per-country reseller PSP |
| MID | Named MID + per-store metadata | Shared across pool |
| Store attribution | Metadata rides through every event | Reporting requires vendor-side mapping |
| Local APMs | iDEAL, Bancontact, BLIK, pay by bank, PayTo on toggle | Per-country vendor per method |
| Peak handling | Idempotency + retryable signed webhooks | Fragile under sustained peak load |
| Reporting | Interchange++ per line | Blended monthly summary |
| Underwriting scope | Regional retail merchants | Broad, few exclusions |
Rate structure on the pricing page. Acquiring contract detail on merchant acquiring. Packaged vertical bundles on payments solutions.
Features that matter to a retail operations team
Every capability below ships on the standard integration and inside the storefront plugins. No premium tier gates per-store metadata, local APMs or the webhook signing scheme.
-
Per-store metadata
Attach store ID, region or brand to the charge metadata; the fields propagate through settlement, refund and dispute events for per-outlet reconciliation.
-
Storefront plugin admin
Retail-facing plugins for WooCommerce, Magento 2, PrestaShop and Shopware — refunds, captures and payout schedules from the storefront's own admin.
-
Regional APM breadth
iDEAL, Bancontact, BLIK, pay by bank, PayTo and Interac alongside cards. Dashboard toggle per market when a retail brand enters a new country.
-
Apple Pay + Google Pay
Wallet buttons render inside the retail storefront's checkout; the wallet-supplied network token replaces PAN in the charge request.
-
3-D Secure 2.2 exemptions
Authentication with automatic exemption logic — most retail checkouts stay frictionless, risky orders step up to the issuer challenge.
-
Signed webhooks
HMAC-signed, replay-protected events across acceptance, refunds and disputes. Delivery retries on an exponential schedule for up to 72 hours.
-
Real-time analytics
Approval, decline, cancel and fraud verdicts per method and per store visible within seconds — see peak-hour performance without waiting for the daily batch.
-
Interchange++ reporting
Interchange, scheme fees and gateway margin split per settled order, keyed by store and SKU on the metadata.
Per-store metadata rides on the standard charge object
Attach a store or brand reference to the charge and it appears verbatim on every downstream event — settlement, refund, dispute. The finance team reconciles the same payload the plugin sent at checkout time, keyed to the outlet you operate.
POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
"amount": 4990,
"currency": "EUR",
"payment_method": "card",
"capture": "auto",
"three_d_secure": "required_if_needed",
"metadata": {
"order_id": "ORD-10842",
"store_id": "NL-AMS-01",
"brand": "example-outdoors",
"sku": "TENT-2P-04"
}
}The response returns a canonical charge object with your metadata bound to it. Read the full schema in the API reference.
Where retail merchants run BazPay
Four retail patterns already rely on BazPay for their online payment layer. Each uses the same charge object and signed webhook; the reporting emphasis differs by business model.
-
Multi-brand online retail chains
One merchant contract across several online brands or country-specific shops, with per-store metadata reconciling revenue per outlet.
-
Click-and-collect retailers
Online payment via BazPay, physical collection in-store, refund back on the same charge if the customer cancels at the counter.
-
DTC brands with seasonal peaks
EU, UK and Commonwealth DTC brands running Black Friday, Christmas and launch-drop volumes without a rate-card change or vendor renegotiation.
-
Fashion, home and specialist retail
Category-specific regional retail shops on Shopware, Magento or WooCommerce with plugin support during peak season, not only at boarding.
Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. BazPay is an online payment gateway and does not ship in-store POS terminals.
Security and compliance across every retail store
Card handling runs inside a PCI DSS Level 1 environment assessed each year. Hosted fields keep every retail storefront at merchant SAQ A on the annual return. Authentication runs on every card charge with 3-D Secure 2.2 and automatic exemption logic — most retail checkouts stay frictionless.
- 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
- SEPA / SEPA Instant
- Direct participation for merchant payouts in supported corridors
Questions retail merchants ask before switching
What are retail payment solutions, and what does BazPay cover?
Retail payment solutions are the set of acceptance, reporting, refund and settlement capabilities a retail merchant needs to run its checkout. BazPay covers the online side of that stack: card, wallet and local payment method acceptance across one or many storefronts, multi-store reporting, refunds inside the storefront's admin and SEPA Instant settlement to your local settlement account. In-store card-present terminals are not in scope.
Does BazPay cover in-store POS terminals for physical retail?
No. BazPay is an online payment gateway; the platform does not ship card-present POS terminals, chip-and-PIN devices or unattended kiosks. Retail merchants that need both online and in-store card acceptance pair BazPay's online payment platform with a dedicated in-store POS partner and reconcile the two streams in their own retail systems.
How do retail payment systems handle multi-store or multi-brand retailers?
Attach a store, brand or region reference to the charge metadata; the field rides through settlement, refund and dispute events. Reporting rolls up to your merchant identifier and slices back down per outlet or per brand. One settlement account receives the settlement across every store, so treasury does not have to reconcile multiple bank accounts.
Which storefront platforms does the retail payment platform integrate with?
Maintained plugins for WooCommerce (WordPress), Magento 2 / Adobe Commerce, PrestaShop and Shopware 6. Each plugin covers checkout, refunds, capture, webhooks and recurring billing out of the box. Retail chains on custom or headless stacks integrate directly against the REST API.
How does the platform handle click-and-collect and buy-online-return-in-store flows?
The payment side is online: the shopper pays through your checkout, and the charge sits on your BazPay account. When the customer collects (or returns) in store, your retail staff issue a full or partial refund from the storefront's order screen or your retail back-office; the refund event fires a signed webhook back into your systems and the funds return to the original card or settlement account.
Are online retail payment solutions built to survive Black Friday and Christmas peaks?
Yes. The API handles sustained bursts, idempotency keys keep retries safe under network turbulence, and signed webhooks retry on your endpoint for up to 72 hours if your storefront is briefly saturated. Real-time analytics show approval quality per store and per method as the peak unfolds, so operations can respond within the same hour.
Which retail merchant types can board with BazPay?
Regional retail merchants: multi-brand online retail chains, click-and-collect retailers, DTC brands and category-specific specialist retail shops. 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.
How is compliance handled across multi-store retail operations?
PCI DSS Level 1 covers the acquiring and gateway environment; hosted fields and gateway vaulting keep every store at merchant SAQ A on the annual return. Authentication runs on every card charge with automatic exemption logic. GDPR under In-region data residency is default across every store on the same contract.
Consolidate online retail payments on one direct regional acquirer
Share your storefront platforms, target markets and store count. A named engineer will confirm boarding fit and map the metadata rollout inside one working day. See also pricing, payment gateway for ecommerce and payment acceptance.