Volume Distribution — Report documentation

Purpose

The Volume Distribution report helps finance and operations teams see where successful deposit volume goes: which payment providers (PSPs) and routes (PSP accounts) drive the business, how volume splits between alternative payment methods and cards, how operator fees trend over time, and how volume spreads across markets. Use it for daily or period checks, provider mix, and fee behaviour after you set the date range and other filters you care about.

What data this report uses

The report is built on General all tx: one row per payment transaction for your organisation, with amounts in client base currency, provider routing, customer and channel context, and outcome flags. For full field meanings, grain, and how amounts are converted, see the General all tx user guide.

Report-level filters

The report is usually read with yesterday’s date range, Successful transactions only, and Deposit only—adjust these when you need a different day or window or other flows.

Filter (as in Looker)	What it does	How to use it	When it’s useful
Date range	Keeps transactions whose created date falls in the range you pick.	Choose Yesterday for a single day, or a custom range.	Daily monitoring or any period comparison.
State	Keeps rows with the transaction state you select (for example Successful).	Pick one or more states.	Focus on completed, failed, or other lifecycle states.
Method	Narrows by transaction method (for example Deposit vs Withdrawal).	Pick the methods you need.	Deposit-only volume vs withdrawals or other methods.
Orchestrator	Narrows by orchestrator context from the data.	Pick from the dropdown.	When you segment by orchestration setup.
Legacy Entity	Narrows by a legacy entity label derived from routing (for example SandTech, Igloo).	Pick one or more.	Reporting aligned to legacy entity groupings.
Brand	Keeps the brand (or mapped brand context) you select.	Pick one or more.	One brand or a brand family.
Status Code	Filters by status code on the transaction.	Pick codes you care about.	Drill into specific decline or outcome codes.
Country	Filters using the country field wired to this control (typically customer-facing country).	Pick one or more.	Market or geography slices.
Channel	Narrows by channel (and related channel fields in the source).	Pick from the list.	How the transaction was taken (e.g. web vs app style splits when present).
Deposit Type	Narrows by deposit type when populated.	Pick values that appear in your data.	Finer deposit segmentation.
Payment Type	Narrows by payment type when present.	Pick from the list.	Further method or product splits.
TX Type	Narrows by transaction type in the source.	Pick from the list.	When you need a specific TX type bucket.
Affiliate ID	Keeps transactions for the affiliate ids you select.	Pick one or more.	Partner or affiliate reporting.
User Categories	Narrows by user category fields from the source.	Pick categories.	Segmenting by customer or user class.
User ID	Narrows to selected user identifiers.	Pick users.	Individual or small-group analysis.
User Email	Narrows to selected email values when available.	Pick emails.	Support or case-level lookups.
First Time / Returning User	Splits or filters first-time vs returning style buckets when exposed.	Pick the segment you need.	New vs repeat behaviour.
FTD / Trusted	Uses the report’s FTD vs Trusted classification (first-time deposit style vs trusted).	Pick one or both.	Risk or onboarding style cuts.
Initial PSP / Initial PSP MID	Narrows by first provider or first merchant account on the route.	Pick PSP or MID.	Where the journey started.
Final PSP / Final PSP MID	Narrows by final provider or final merchant account that processed the payment.	Pick PSP or MID.	Where volume landed.
Final PSP Service	Narrows by final PSP service when present.	Pick from the list.	Service-level splits under a PSP.
Final PSP Mapped	Narrows by the mapped final PSP label (grouped / cleaned names for reporting).	Pick one or more labels.	Consistent PSP names when raw codes differ.
Include Multiple Failed Attempts?	Uses the fail-flag logic: whether to include rows flagged as multiple failed attempts.	Set as your team standard.	Cleaner success-focused views vs full attempt history.
Card Scheme	Narrows by card scheme (Visa, Mastercard, etc.) when the transaction is card-based.	Pick schemes.	Card-brand mix.
Card Issuer Country	Narrows by issuer country on the card.	Pick countries.	Cross-border issuing patterns.
Issuer	Narrows by card issuer name when present.	Pick issuers.	Issuer-level analysis.
BIN	Narrows by bank identification number when present.	Pick BINs.	BIN-level concentration.
Transaction ID	Keeps a specific transaction when you enter an id.	Type or paste an id.	Lookup one payment.
Search for a Rule ID	Narrows using rule identifiers when your data fills this field.	Enter a rule id.	Rule or compliance drill-downs.
PD True Data	Narrows using the PD True Data flag as wired on the report.	Choose the option your team uses.	Data-quality or source splits.
Include Test Users?	Controls whether test users appear.	Toggle or pick as designed.	Live vs test views.
Include Flagged Spam Users?	Controls whether spam-flagged users appear.	Toggle or pick as designed.	Excluding noisy or spam-flagged traffic.
Custom Sub Master	Narrows by custom sub-master grouping (merchant / brand buckets defined in Looker).	Pick a group.	Executive or internal groupings.

Use Export when you need a file of the current view.

Resource-level filters

Some charts or tables add their own limits so the numbers stay meaningful. They only affect the named visual, not necessarily every other tile.

Filter (as in Looker)	Which part of the report it affects	What it does	How to use it
Excl. null volume	PSP Volume Over Countries	Hides rows where there is no client base amount (usually no usable currency conversion for that transaction).	Leave on for a fair share-of-bar view; talk to the report owner if you need to include NULL-amount rows for investigation.

If a chart’s default date is set to a long or “all time” window while the rest of the page follows Yesterday, that tile can look out of step—adjust the page date range first, then ask the report owner to align any tile that still looks wrong.

PSP Volume

The PSP Volume view shows how much volume (in euros, using client base total amount) sits with each Final PSP Mapped label. Larger slices are the providers that took the most successful deposit volume for your current filters. Use it to see mix by provider name at a glance.

This block uses one breakdown (the mapped final PSP) and one amount (total client base total amount in scope), so a short prose description is enough: each slice is a provider’s share of the filtered volume.

APM vs Card Volume

The APM vs Card Volume view splits the same filtered volume into alternative payment methods (APM) versus card. Each segment is the sum of client base total amount for that payment category. Use it to see whether deposits are card-heavy or APM-heavy for the selected day or period.

Operator Fee

The Operator Fee chart shows monthly trends (by year–month of created date) for:

Series	What it shows
Gross Volume	Total transaction amount in the period (bars).
Operator Fee	Fees booked alongside that volume (bars).
Net Volume	Volume after fees (line)—money left after operator fees in the same basis as the chart.
Operator Fee%	Average fee percentage for the period (line on the right-hand scale)—fee as a share of amount, so you can see if the fee rate is drifting even when gross volume moves.

Use it to connect volume size, fee amount, and fee rate over recent months. If the page date filter is one day, this chart may still show many months if the tile uses its own date window—compare the axis labels to your date picker when numbers look unexpected.

PSP Volume Over Countries

The PSP Volume Over Countries chart shows each Final PSP Mapped row as a full-width bar, with segments by market (country-style codes in the legend). The length is built from client base amount so you see which countries contribute to each provider’s bar. Sorting is by amount so the strongest providers appear first.

Together with the pie, this answers “where is this PSP’s volume coming from by market?” rather than only “how big is the PSP?”.

PSP MID Overview

The PSP MID Overview table lists aggregator-style group, final PSP merchant account (MID), and user country (short country code), with activity and fee columns for the current selection.

Column / label	What it shows
Aggregator	High-level provider or platform group (for example the family name shown next to several MIDs).
Final PSP MID	The specific merchant account or route string used when the payment completed.
User Country	The customer or user country for the row, as a short code.
TX Count	How many transactions are in that slice.
Volume	Total volume in client base currency (euros in the export) for the slice.
Successful Volume	Volume where the transaction is successful.
Successful Count	Count of successful transactions.
Failed Count	Count of failed transactions.
Cancelled Count	Count of cancelled transactions.
Successful Player Fee	Sum of fees on successful rows (player-side fee in client base currency).

Use the table to move from “which PSP” (pie) to which account and country drive the numbers. Pagination shows how many MID × country rows exist for your filters.

Successful Net Volume (Final PSP and Final PSP MID)

The Successful Net Volume pivot-style block groups rows by Final PSP, then Final PSP MID, and shows Successful Net Volume: the successful slice of volume where deposits add and withdrawals would subtract (with Deposit at the top of the report, you normally see deposit-style totals). The grand total is the rolled-up successful net volume for the expanded slice.

Use this when you need exact MID-level successful net under each final PSP, for example to reconcile to account-level targets or to compare MIDs within one PSP.

---