Gnosis Pay Analytics

On-chain card payment analytics from the Gnosis Pay Spender Module.

Funding sources over time

Where Gnosis Pay users' spending balances came from. Stablecoin inflows to known GP Safes, classified by the on-chain source contract. Monthly, EUR-equivalent (1:1 across stables). "Other" combines inflows from unclassified addresses (personal wallets and unlabelled protocols, ~39% of volume) with Treasury refunds from reversed card transactions (~3% of volume).

On-chain funding diversity

How many distinct labelled funding sources each GP user has touched. Counts six source categories: CoW, Monerium IBAN, bridges, wallet apps, DEX swaps, yield protocols. Users in the zero row have been funded only by unclassified addresses (personal wallets or unlabelled protocols) or merchant refunds.

Cross-product user overlap

How many distinct Gnosis Pay Safes funded via each on-chain source at least once. A user who funded via both CoW and Monerium counts in both rows — this shows the breadth of ecosystem touchpoints, not partition. Unknown / personal-wallet sources and merchant refunds are excluded (they're not cross-product signals).

Spend Volume by Currency

User Activity

Transaction Size Distribution

Monthly User Retention

Currency Breakdown

Top Spenders

Top unclassified senders

Operator diagnostic. Addresses with many distinct recipient Safes are platform contracts worth labelling — identify them via gnosisscan, add to gnosis_address_registry, then call ?action=reclassify. Addresses with ≤ 5 distinct Safes are personal wallets — leave as P2P.