Menu
Talk with sales

Integration questions? [email protected]

Payment gateway for digital goods and downloadable products.

BazPay is a regional payment gateway for digital goods — software licences, SaaS plans, ebooks, courses, stock media and other intangible products. Instant fulfilment fires through a signed webhook, dispute evidence is pre-assembled for intangibles and every charge carries your SKU metadata end to end.

Built for merchants across the EU, UK, Australia, Canada and New Zealand: software vendors, SaaS platforms, digital publishers and digital-asset marketplaces. One direct regional acquirer, one REST API, one dashboard.

Talk with sales Read the API reference

Why digital-goods sellers pick a purpose-tuned gateway

Digital-goods flows have three concerns most e-commerce gateways treat as an afterthought: instant fulfilment, chargeback defence for intangibles and clean per-SKU reporting. Four benefits BazPay ships by default cover all three.

  • Instant fulfilment on a signed webhook

    As soon as a charge succeeds, a signed event fires to your fulfilment service. Your endpoint hands out the download key, activates the licence or unlocks the account — no polling, no batch job, no delay for the shopper.

  • Low PCI scope for a lean digital storefront

    Hosted fields and gateway-side vaulting keep card data out of your stack. Digital-goods sellers with tiny engineering teams get to stay at merchant SAQ A instead of running a full PCI environment.

  • Dispute defence built for intangible goods

    Chargebacks on digital products often lose on "delivery not provided". BazPay attaches the 3-D Secure result, the fulfilment webhook confirmation and any metadata you send at charge time to the case packet automatically.

  • Per-SKU reconciliation

    Metadata on the charge object propagates through to settlement, refund and dispute events. Your finance team reconciles revenue per licence tier or per content bundle, not against a blended lump sum.

The digital-goods catalogue BazPay covers

Four category families sit under the same merchant contract. Every one uses the same charge object, the same webhook envelope and the same interchange++ reporting.

  • Software

    Software licences and downloads

    Perpetual and term licences, one-off downloads, plugin marketplaces and desktop software. Licence keys are minted on your side; BazPay signals when the payment is safe to fulfil.

    • Perpetual
    • Term
    • Plugin marketplace

  • SaaS

    SaaS subscriptions

    Monthly and annual plans with card-on-file renewals, trial-to-paid conversions and MIT exemptions on rebills. Network-tokenised so a card reissue does not silently churn a customer.

    • Monthly
    • Annual
    • Trial-to-paid

  • Media

    Digital media and courses

    Ebooks, audiobooks, courses, streaming subscriptions, membership content and downloadable video. Metadata carries the SKU and licence type through settlement.

    • Ebooks
    • Courses
    • Streaming

  • Assets

    Digital assets and templates

    Stock photos, video and audio libraries, design templates, presets, 3-D models and code snippets. Per-asset pricing with instant delivery under one merchant contract.

    • Stock media
    • Templates
    • Presets

Recurring flow behind SaaS and membership models on recurring billing. Payment-method depth on card and APM processing. Foundational primitives on the payment infrastructure page.

The life of one digital-goods charge, end to end

Six stages sit between the shopper hitting pay and the licence key landing in their inbox. Each stage is visible in the dashboard and each stage change fires a signed webhook.

  1. Charge

    Shopper submits payment through hosted fields or a hosted checkout page. Card data stays inside our PCI scope.

  2. Authorise

    3-D Secure 2.2 runs only when the risk earns it. Fraud rules score the order against your merchant history.

  3. Confirm

    The response returns a canonical charge object with the payment_intent and any metadata you attached.

  4. Fulfil

    A signed charge.succeeded webhook fires to your fulfilment endpoint. Your service releases the download or licence.

  5. Deliver receipt

    Send the download link, licence key or account activation via your existing email or in-app channel — BazPay stays out of the delivery loop.

  6. Reconcile

    Settlement lands per scheme cycle. Refunds, chargebacks and disputes fire as signed events keyed to the same charge ID.

Purpose-tuned digital goods payment services vs generic gateway

The difference between a gateway that ships digital-goods primitives and one that does not shows up on six axes. Below is the shortlist a digital-goods merchant should apply during procurement.

BazPay digital-goods primitives compared with a generic payment gateway
Dimension BazPay (digital-goods tuned) Generic e-commerce gateway
Fulfilment signal Signed webhook on charge.succeeded Poll a status endpoint
PCI scope Merchant SAQ A via hosted fields Full PCI where PAN passes servers
Dispute evidence 3DS + fulfilment webhook auto-attached Manual evidence assembly
Metadata propagation SKU / licence tier through all events Metadata lost after auth
Renewals Network tokens + MIT exemptions Rebills fail after card reissue
Reporting granularity Interchange++ per SKU Blended monthly summary

Fees and settlement on the pricing page. See payment processors for the broader buyer's comparison, gateway services for the operational envelope, and fintech payment solutions for the SaaS-billing sibling of the same platform.

Features the digital goods payment processor 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 digital-goods sellers depend on.

  • charge.succeeded webhook

    Sub-second dispatch after authorisation and 3-D Secure resolve — the trigger every digital-goods fulfilment service actually needs.

  • Charge metadata

    Attach SKU, licence tier, tax code and shopper reference to any charge; the metadata rides through settlement, refund and dispute events.

  • Hosted fields

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

  • Gateway vault + network tokens

    Store credentials once for card-on-file. Network tokens refresh through Visa and Mastercard token services when a card is reissued.

  • 3-D Secure 2.2

    Authentication with automatic exemption logic — low-value, risk analysis and MIT — so most digital-goods checkouts stay frictionless.

  • Refund API

    Full and partial refunds by API or dashboard, per SKU. Refund events fire on the same signed-webhook stream as charges.

  • Dispute evidence

    3-D Secure result, fulfilment webhook confirmation and your charge metadata are pre-assembled into the case packet for one-click submission.

  • Interchange++ reporting

    Interchange, scheme fees and gateway margin split per settled charge; per-SKU revenue reconciles cleanly against your product ledger.

A charge object built to carry your fulfilment metadata

Attach the SKU, licence tier, buyer identifier and any tax code to the metadata field on the charge. Every downstream event — settlement, refund, dispute — carries that metadata forward, so fulfilment revocation and reconciliation stay one-step operations. 

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 LICENCE",
  "metadata": {
    "sku": "PRO-ANNUAL-01",
    "licence_tier": "pro",
    "buyer_ref": "usr_02H9K",
    "tax_code": "TBE"
  }
}

The response returns the canonical charge object with the payment_intent, the exemption applied and the full metadata blob. The complete schema lives in the API reference.

Digital goods payment processing solutions in the wild

The four merchant profiles below already run on BazPay-shaped digital-goods flows. Each gets the same API surface, the same fulfilment webhook and the same interchange++ reporting.

  • Software vendors

    Licence keys minted on your side, dispatched the moment the fulfilment webhook lands. Trial-to-paid upgrades happen on the same charge object with card-on-file.

  • SaaS platforms

    Monthly and annual subscriptions with dunning-aware retries, MIT exemptions on rebills and network-token refresh so reissues do not silently churn a paying account.

  • Digital content publishers

    Ebooks, courses, streaming and paywall unlocks reconciled per SKU. Metadata carries the licence terms through to dispute evidence.

  • Digital-asset marketplaces

    Stock media, templates and presets sold on a per-asset basis; refunds and disputes handled without unpicking a bundled monthly rate.

Out of scope for BazPay: adult content, gambling credits, cryptocurrency downloads or wallets, CBD, nutraceuticals, forex, CFD, debt-collection and MLM. BazPay is not a merchant of record and does not act as a marketplace of third-party PSPs. New to online payments? See accept online payments. German checkout method: iDEAL payments.

Security, compliance and dispute evidence for intangibles

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 automatic exemption logic so most digital-goods 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
Tax metadata
VAT code and buyer-location fields propagate through settlement

Questions digital-goods merchants ask first

What makes a digital goods payment gateway different from a generic one?

Digital goods rely on webhook-driven instant fulfilment, low chargeback tolerance for "item not received" claims, and per-SKU reconciliation across many small-ticket orders. A digital goods payment gateway ships sub-second signed webhooks, dispute evidence that includes the fulfilment confirmation, and metadata that carries a SKU or licence tier through every downstream event.

How does the payment gateway for digital products handle instant delivery?

The charge.succeeded webhook is signed with your endpoint secret using HMAC and fires as soon as authorisation and 3-D Secure resolve. Your fulfilment service verifies the signature and releases the download link, licence key or account entitlement. No polling, no batch job, no CS ticket.

How are chargebacks defended on intangible goods?

When a dispute opens, BazPay pre-assembles an evidence packet that includes the 3-D Secure 2 authentication result, the fulfilment webhook confirmation, the charge metadata you sent (SKU, licence tier, buyer identifier) and any delivery events you post through the fulfilment API. You review the packet, add anything specific and submit it in one click.

Does BazPay handle regional VAT / OSS for digital goods sales?

No. BazPay is a payment gateway, not a merchant of record. Tax calculation, invoicing and OSS filing remain with your legal entity. What BazPay does provide is buyer-location and VAT-code metadata support on the charge object, so your tax layer sees consistent data across cards, wallets and APMs.

Can the digital goods payment processor run subscription renewals?

Yes. Network-tokenised card-on-file, MIT exemptions on rebills and dunning-aware retry cadences are native to the platform. Recurring digital-goods models — SaaS plans, membership sites, streaming subscriptions — use the same charge object as one-off downloads with a subscription reference attached.

Which digital-goods categories are in scope, and which are not?

In scope: software licences, SaaS subscriptions, ebooks, audiobooks, courses, streaming subscriptions, membership content, stock media, design templates, code snippets and in-app purchases in compliant consumer or B2B apps. Not in scope: adult content, gambling credits, cryptocurrency downloads or wallets, CBD, nutraceuticals, forex, CFD, debt-collection tooling and MLM products — those verticals fall outside BazPay's regional underwriting.

How are refunds and partial refunds handled for digital orders?

Full and partial refunds are issued by API or from the dashboard, per SKU line. Every refund fires a signed webhook so your fulfilment stack can revoke the licence key or entitlement in the same flow. Refund events retain the charge metadata and settle in the next scheme cycle.

Does the digital goods payment gateway work for storefronts on WooCommerce or Shopware?

Yes. Maintained plugins for WooCommerce, Magento 2, PrestaShop and Shopware 6 cover checkout, refunds, capture, webhooks and recurring billing out of the box. Digital-goods storefronts running on custom stacks integrate against the REST API — the same endpoints the plugins use.

Ship your digital-goods checkout on a purpose-tuned gateway

Share your catalogue, monthly volume and existing fulfilment stack. An integration manager will confirm boarding fit and map the webhook wiring inside one working day. See also payment gateway services, payments solutions, merchant acquiring, open banking and payouts.

Talk with sales Read the developer docs