See every payment the second it happens.
Approval rates, decline reasons and settlement timing update live. No nightly export. No stale report. One view covers cards, open banking, payouts and fraud.
- SecondsEvent to dashboard
- 13 pillarsOne shared timeline
- EU dataStored in the region
- CSV + APITake it anywhere
- iDEAL settled Bank confirmed
- Card · 3DS2 Frictionless
- BLIK pending Awaiting code
- Card · 3DS2 declined Insufficient funds
- Bancontact settled Bank confirmed
Sample dashboard view. Your figures come from your own traffic.
Four 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 or plugin. It is the fastest read on revenue health.
-
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.
-
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.
-
score bands · Rolling 24 h
Fraud score mix
See how many orders your rules pass, review or block. Tune a rule and the next hour shows the effect.
One timeline, every product.
Nothing is bolted on later. Each product writes to the same event log as it runs. That is why the dashboard has no lag and no gaps.
Browse all products| Source | What it records | Product |
|---|---|---|
| Card and APM traffic | Scheme, issuer, wallet and 3-D Secure 2 outcome | Card & APM processing |
| Open banking debits | Bank selection, approval step and confirmation | Open banking |
| Payout batches | Instruction, rail used and settlement stamp | Payouts |
| Subscription cycles | Renewals, dunning attempts and recovered revenue | Recurring billing |
| Fraud decisions | Rule hits, score band and manual review outcome | Anti-fraud |
Get told before you get asked.
A dashboard you must remember to open is a dashboard you will miss. Set the rule once.
-
Set a threshold
Pick a metric and a floor. An example: alert me if the card approval rate drops five points in an hour.
-
Choose a channel
Alerts arrive by email or by webhook. The webhook body matches the event contract your code already handles.
-
Export the detail
Every view exports to CSV. Column names stay stable, so a finance sheet built once keeps working.
-
Reconcile the payout
Each payout links to the payments inside it. Bank statement to order line takes one click.
What merchants ask about the data.
- How fresh is the data?
- Payment events reach the dashboard within seconds of the gateway processing them. There is no nightly batch. Reports and the live view read the same records.
- Can I query it from code?
- Yes. The same figures are readable over the REST API, and webhooks push state changes to you. See the API reference for the exact fields.
- Does it cover every product?
- It covers all thirteen pillars on one timeline. Cards, open banking, payouts, subscriptions and fraud sit in a single view, not five dashboards.
- Who can see the numbers?
- Access is role based. Give finance read-only reporting and keep key management with your engineers. Data stays inside the EU.
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.
- DevelopersOne REST API behind every metric
- Checkout productsWhere the first event is written
- IntegrationsPlugins for the major EU carts
- CompanyWho runs the platform, and how