Payment Analytics
How to understand where conversion “hurts” in 5 minutes
The
Payments report exists exactly for this moment — so you don’t guess, but quickly localise the issue down to a gateway/channel/integration and make a decision.1) Where to start: 3 switches that solve most cases
Period and aggregation
Date → select the range.Day / Week / Month → choose the “zoom”.Day is for operations, Week/Month is for trends.
By count vs By amount
By count — how many attempts.By amount — how much money (turnover).By amount mode everything is converted to the Base currency. This makes comparisons consistent.Direction
All / Deposits / PayoutsSometimes “everything looks fine” until you switch to payouts — and that’s where the surprise is.
2) How to read any “Distribution …” widget in 10 seconds
3) The main screen: what to check first
3.1 Status distribution — “is the patient alive?”
Success — blueFailed — redProcessing/Created — yellow (if it gets stuck — bad)Processing/Created usually trends to ~0 by end of day (unless you have long async flows)Success drops by ~3–5 pp+ vs your usual levelProcessing/Created “tail” persists for several daysGateway → Integration → Channel.3.2 Gateway distribution — “who is most likely responsible”
GW Failed spikes on one gatewayChannel and Integration.3.3 Channel distribution — “where exactly it leaks”
Integration and Gateway.3.4 Integrations — “did a specific key/endpoint die?”
Failed or stops receiving trafficGW Failed3.5 Pipelines — “is routing doing what you expect?”
3.6 Merchants and currency — “local or systemic issue?”
4) Funnels: where conversion is lost by stage
Negative payment funnel — “where we fail”
GW Failed grows, it’s almost always “gateway/method/limits/anti-fraud”.Gateway → Integration → Channel, watch the trend and correlate it with traffic shifts.Positive payment funnel — “where we don’t reach success”
PS Created → GW Created → GW SuccessPS Created → GW Created is typically ~98–100% (if there’s no reason to not send to the gateway)GW Created → GW SuccessGW Created — usually pre-gateway issues (routing/validation/infrastructure)GW Success — usually gateway/method/channel issues5) The 5-minute “combat” algorithm
1.
Status distribution → confirm the drop is real.2.
By count ↔ By amount → what matters more: “units” or “money”?3.
Gateway → Integration → Channel → Pipeline.4.
5.
6) Mini checklist for messaging gateway/PSP/bank support
Terms (short)
Payment — an attempt to execute a deposit/payout through a route and a gateway.Pipeline — routing/processing scenario logic.Channel — a specific route/segment inside a pipeline.Integration — a specific gateway connection configuration.Gateway — a bank or PSP.Typical cases: what to do when “payments don’t go through”
Case 1. GW Failed suddenly spiked (gateway-side failures)
GW Failed grows in the Negative funnel.Gateway distribution one gateway turns “red” or sharply increases its error share.1.
Gateway = problematic.2.
Integration distribution → see if one integration is dragging everything down.3.
Channel distribution → identify whether one channel/method is broken.4.
By count ↔ By amount (sometimes only high-value traffic fails).5.
GW Failed share, top channels/integrations.Issue localised to
Gateway + (Integration/Channel).Case 2. Conversion dropped but GW Failed barely changed
Success rate drops, but GW Failed in the Negative funnel doesn’t explain it.Positive funnel, the drop is often before GW Created.1.
Positive funnel: do we drop on PS Created → GW Created?2.
Pipeline, then Channel (often a specific routing condition).3.
4.
Processing/Created increased (stuck states).A pre-gateway problem: routing/validation/infrastructure.
Case 3. Processing/Created tail doesn’t close
Processing (or Created) grows in Status distribution and stays as a “tail”.1.
Gateway → is it all gateways or one?2.
Integration → sometimes one endpoint doesn’t receive callbacks.3.
Day vs Week — systemic tail or one-off.4.
Either the gateway delays finalisation, or there’s an issue receiving/processing statuses.
Case 4. Drop only in one currency
Currency distribution (or with a currency filter) Success is noticeably lower.By amount mode)1.
Currency = problematic.2.
Gateway → Channel → Integration (the “culprit” is usually there).3.
Deposits/Payouts (sometimes only payouts are affected).Problem in a specific currency routing bundle.
Case 5. Drop only for one merchant
Merchant distribution one merchant degrades.1.
Merchant = X.2.
Gateway → Integration → Channel → Pipeline.3.
By amount vs By count — sometimes only “expensive” payments fail.Merchant-local issue or its routing.
Case 6. Traffic shift: shares changed sharply and quality dropped
Success drops and Failed grows.1.
2.
3.
Not “everything got worse”, but “traffic moved to a weaker route”.
Case 7. By count is fine, but By amount drops (or the opposite)
By count is stable, but By amount turnover drops (or vice versa).1.
By count vs By amount for the same segment.2.
Channel (high-value traffic often uses a dedicated route).3.
Issue is in the “amount segment”, not overall volumes.
Case 8. Numbers “don’t match” between widgets
1.
2.
3.
Success) — differences often disappear.A data/stage nuance, not a report “bug”.