Menu
Talk with sales

Integration questions? [email protected]

Payment analytics and reporting, live from the gateway.

Approval rates, decline reasons and settlement timing update the second they happen. No nightly export. No stale report. One payment analytics dashboard covers cards, open banking, payouts, subscriptions and fraud.

Built for merchants across the EU, UK, Australia, Canada and New Zealand — e-commerce, subscription software, professional services. The numbers finance ties out at month-end are the same numbers product watched at 10 a.m.

Talk with sales Read the API reference
  • SecondsEvent to dashboard
  • One viewEvery product line
  • regional dataStored in the region
  • CSV + APITake it anywhere
Authorisation rate · last 7 days Live
  • SEPA Instant settled Bank confirmed
  • Card · 3DS2 authorised Frictionless
  • Bancontact pending Awaiting code
  • Card · 3DS2 declined Insufficient funds
  • BLIK settled Bank confirmed

Sample dashboard view. Your figures come from your own traffic.

Why business payment analytics belongs inside the gateway.

When the analytics layer is bolted on afterwards, it always trails the truth. Ours reads from the same event log the acquirer writes to.

  • One dashboard, every product

    Card, wallet, APM, open banking, payout, subscription and fraud events land on the same timeline. No stitching between five vendor consoles to answer one revenue question.

  • Live, not nightly

    Payment data analytics update within seconds of the event. The number you see at 10:07 is the number the acquirer saw at 10:07 — no batch, no derived view.

  • Interchange++ line detail

    Every settled charge breaks out scheme fees, interchange and gateway margin on its own line. Finance can tie a bank statement row to an order without a spreadsheet dance.

  • Take the numbers with you

    The same figures are readable over the REST API, pushed through signed webhooks and exportable as CSV. Column names are stable, so a finance sheet built once keeps working.

Six numbers that move revenue.

Each metric states its unit and its window, so two people never read the same tile two ways. Definitions are fixed and documented.

  • percent · Rolling 60 min

    Authorisation rate

    Approved payments divided by attempts. Split it by issuer country, card scheme, plugin or checkout URL. It is the fastest read on revenue health and the first tile finance loads in the morning.

  • grouped codes · Live

    Decline reasons

    Raw issuer codes are mapped to plain labels. Soft declines are marked as retryable. Hard declines are flagged so you stop retrying them. Every code links to the underlying transaction.

  • hours · Per payout batch

    Settlement timing

    Track the gap between capture and money landing. SEPA Instant and standard credit transfer are shown as separate lines, and each payout links to the individual payments it contains.

  • score bands · Rolling 24 h

    Fraud score mix

    See how many orders your rules pass, step up, review or block. Tune a rule and the next hour shows the effect. The tile shares its data with the fraud engine — same numbers, one source.

  • cases · State counts

    Dispute pipeline

    Pre-dispute alerts, opened chargebacks, evidence-required cases and outcomes broken out. Each entry carries its 3-D Secure result and its reason code for finance-team review.

  • percent · Rolling 7 days

    Recurring recovery

    How many failed subscription renewals came back on the next dunning cycle. Split by dunning strategy, so you can see which retry cadence is actually recovering revenue.

How data analytics payment processing runs end-to-end.

Six stages sit between the event fired by a product and the number visible in your dashboard. Each stage is deterministic and each stage is visible in the API.

  1. Event fires

    Each product writes to the same event log as it runs — charge.created, charge.settled, dispute.opened.

  2. Enrichment attaches

    BIN metadata, issuer country, exemption used and rule IDs are joined onto the event as it is written.

  3. Rollups update

    Rolling counters (60-minute auth rate, 24-hour score mix) recompute inline. No batch job holds them back.

  4. Dashboard reflects

    Tiles, tables and charts read from the same records. What analysts see and what the API returns match to the second.

  5. Alerts and webhooks

    Thresholds you set fire an email or a signed webhook the moment the metric crosses the line.

  6. Export or query

    Every view exports to CSV. The same figures are queryable over the REST API for your own warehouse pipeline.

One timeline, every product.

Nothing is bolted on afterwards. Each product writes to the same event log as it runs. That is why the payment analytics and reporting layer has no lag and no gaps.

Browse all products
Event sources feeding the live view
SourceWhat it recordsProduct
Card and APM traffic Scheme, issuer, wallet, exemption applied and 3-D Secure 2 outcome Card and APM processing
Open banking debits Bank selection, approval step and confirmation timing Open banking
Payout batches Instruction, rail used (SEPA / SEPA Instant / SWIFT), settlement stamp Payouts
Subscription cycles Renewals, dunning attempts, recovered revenue and mandate status Recurring billing
Fraud decisions Rule hits, score band, verdict and manual review outcome Payment fraud prevention
Checkout sessions Session start, method chosen, drop-off step and completion Hosted checkout products

Features shipped with the analytics workspace.

Every feature below is on the standard plan. Turn them on from the dashboard or through the API — no enterprise-tier gate on the primitives.

  • Metric tiles

    Auth rate, decline mix, settlement gap, fraud bands, recovery rate — each with a fixed unit and a documented window.

  • Live event ticker

    Rolling feed of payments and payouts as they happen, filterable by method, status and merchant ID.

  • Slice-by filters

    Break any tile by issuer country, card scheme, plugin, checkout URL, currency or merchant ID with one click.

  • Cohort and time compare

    Compare this week against last week or against a 4-week rolling baseline, overlaid on the same chart.

  • Threshold alerts

    Email or signed webhook when a metric crosses a floor or ceiling. Alerts are logged and acknowledgeable.

  • Payout reconciliation

    Each payout links to the payments it contains and to your bank statement line. One-click drill from settlement account to order.

  • CSV export

    Every view exports with stable column names. Schema is versioned, so a finance sheet built once keeps working.

  • REST + webhooks

    Same numbers over API. Signed webhooks push state changes with HMAC-SHA256 and replay-safe idempotency keys.

Read every metric from the REST API.

The dashboard is a client of the same API you can call. Pull an authorisation-rate slice, page through settled charges, or subscribe to a signed webhook for events — payment data analytics is a first-class interface, not a screen-scrape.

Read the developer docs

GET /v1/analytics/auth_rate

{
  "window": "60m",
  "as_of": "2026-08-03T09:07:00Z",
  "slice": { "issuer_country": "NL", "scheme": "visa" },
  "attempts": 1284,
  "approved": 1163,
  "rate": 0.9058,
  "delta_vs_prior_hour": -0.012
}

POST /v1/webhooks/subscriptions

{
  "event_types": [
    "charge.succeeded",
    "charge.declined",
    "payout.settled",
    "dispute.opened"
  ],
  "url": "https://ops.example.com/hooks/bazpay",
  "signing_secret": "whsec_..."
}

Analytics in payment industry, tuned by merchant profile.

The default views reflect these four profiles. Turn on the ones you need and adjust slices against your own traffic history.

  • E-commerce sellers

    Approval rate by BIN country and plugin, cart-level decline funnels, chargeback rate against Visa scheme thresholds.

  • Subscription software

    Involuntary churn tracked as a metric. Dunning recovery split by retry strategy, MRR movement against gateway data.

  • Professional services

    Invoice-level tracing from issued charge to settled payout. Aged receivables reconciled against SEPA Instant rail settlement.

  • Digital publishers

    Subscription lifecycle from paywall unlock to renewal recovery, with method-mix breakdown by geographic segment.

Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM.

Live gateway analytics vs bolted-on reporting.

When reporting is added on top of the payment stack instead of built into it, latency and coverage suffer. The comparison shows what changes.

See pricing detail
BazPay live analytics compared with bolted-on reporting
Dimension BazPay live analytics Bolted-on reporting layer
Data freshness Seconds — event to tile Overnight batch, T+1 minimum
Scope Cards, APM, open banking, payouts, subs One product line at a time
Fee visibility Interchange++ per line Blended-rate summary
Programmatic access REST + signed webhooks + CSV CSV or PDF only
Payout reconciliation Batch links to individual payments Manual match against bank statement
Custom alerts Threshold rules per metric None or fixed alerts only

Get told before you get asked.

A dashboard you must remember to open is a dashboard you will miss. Set the rule once — the alert will find you.

  1. Set a threshold

    Pick a metric and a floor. Example: alert if the card approval rate drops five points inside a rolling hour.

  2. Choose a channel

    Alerts arrive by email or by signed webhook. The webhook body follows the event contract your code already handles.

  3. Export the detail

    Every view exports to CSV. Column names are versioned, so a finance sheet built once keeps working through releases.

  4. Reconcile the payout

    Each payout batch links to the payments inside it. Bank statement line to individual order takes one click.

Security and access controls.

Analytics reads the same event store the acquirer writes to, inside a PCI DSS Level 1 environment. Access is scoped by role and every export is written to an audit trail.

Card data never leaves gateway scope. The dashboard reads on tokens and enriched events — no PAN, no CVC — so your annual return stays at merchant SAQ A when the hosted checkout products are in place.

Gateway certification
PCI DSS Level 1
Your annual return
SAQ A (with hosted fields)
Data handling
GDPR-compliant, In-region data residency
Access control
Role-based; audit log on every export
Encryption
TLS 1.2+ in transit; AES-256 at rest

What merchants ask about the data.

How fresh is the payment analytics data?
Payment events reach the dashboard within seconds of the gateway processing them. There is no nightly batch and no derived view. The tiles, the tables, the API and the webhooks all read from the same event log written as each product runs.
Can I query the data from my own code?
Yes. Every figure visible in the dashboard is readable over the REST API, and signed webhooks push state changes to your service the moment they happen. The event contract is documented in the API reference and stays stable across releases.
Does it cover every product on one timeline?
Cards, wallets, APMs, open banking, payouts, recurring billing, fraud and checkout events sit on a single timeline — not five separate dashboards. Filters slice the view by method, issuer country, plugin, currency or merchant ID.
Who can see the numbers?
Access is role-based. Finance can have read-only reporting; engineering keeps key management; sandbox and live data are separated. Every export is written to an audit log. Data is stored inside the region.
How does the payment analytics dashboard handle interchange and scheme fees?
Every settled charge splits scheme fees, interchange and gateway margin on its own line. The interchange++ breakdown is available inside the dashboard, over the REST API and in the CSV export, so finance can reconcile without derived spreadsheets.
Can I push data into my warehouse or BI tool?
Yes. Scheduled CSV exports drop into an SFTP endpoint you nominate. Signed webhooks stream events into your own ETL pipeline. The REST API supports paginated reads with cursor tokens for backfill.
How does business payment analytics link to payout reconciliation?
Each payout batch page lists every individual payment it settled, alongside the SEPA Instant or transfer reference your bank shows on the statement. That means one click drills from your settlement account activity to the underlying order, with no manual matching.
Which merchant profiles is this reporting suitable for?
BazPay is a regional acquirer. The analytics in payment industry terms covered here are tuned for e-commerce sellers, subscription software firms, professional services and digital publishers. BazPay does not board adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection or MLM merchants.

Watch your own traffic first.

The sandbox ships with the same dashboard. Push test payments through it and the tiles fill straight away. Write to [email protected] with a reporting question.

Talk with sales See integrations