Onchain payments analytics is dominated by dashboard aggregates and opaque classifiers. When the underlying rows aren't accessible, or the labeling logic can't be reproduced, teams can't trust the numbers, reconcile them, or explain why a specific transaction was included.
Card payments, agentic settlements, and commerce flows in a single schema for end-to-end payments analysis.
Card payment growth across issuers, programs, and networks with standardized, deduplicated transfer-level records.
The agentic payments landscape across protocols and chains, identifying who is actually settling real value onchain today.
Commerce and payroll stablecoin settlement without overcounting treasury rebalancing or operational movements, monitoring how the mix shifts.
Most “payments” views stop at dashboards or labels you can't verify. Dune gives you transfer-level rows that join back to the underlying token transfers, so you can drill into any metric, check what's counted, and reconcile edge cases.
Card payments, agentic payments, and stablecoin commerce flows in one collection. Benchmark rails and providers, and understand transaction purpose and counterparties.
Transparent, deterministic rule-based labeling that removes non-payment stablecoin activity like ops, DeFi, routing, or issuer mechanics.
| Key features | Dune | Competitor avg. |
|---|---|---|
| Data granularity | Transfer-level | Aggregate filters |
| Labeling methodology | Transparent rules + confidence | Black-box logic |
| One schema across cards, agentic payments, and commerce | Siloed dashboards | |
| Deep-dive with SQL | – | |
| Ongoing maintenance | Daily refresh | Partial |
| Geo corridors | On roadmap | ~0.2% of payment volume labeled |
Most “card payments” views stop at dashboards or program-level aggregates, with limited coverage and no way to audit what's included. Dune provides curated, transfer-level card payment records across issuers, providers, networks, and chains — so you can benchmark adoption and drill into any transaction, all linked back to the underlying transfer.
How card payments are exposed onchain depends on the card's settlement model. Non-custodial programs (e.g. Gnosis Pay) record each Card spend as an onchain event; custodial top-up programs (e.g. Holyheld) record Top-up deposits into a pooled wallet; custodial batch-settlement programs (e.g. Immersve) record periodic Batch settlement transactions rather than individual spends. Volume figures reflect whichever signal is observable per program.
| No rows returned. | ||||||
See how volume distributes across Visa and Mastercard, which issuers and programs run on each rail, and how the two networks compare in settled volume.
| No rows returned. | |||||
Agentic payments are an emerging category, and many onchain events are intermediate steps — not the final settlement. Dune captures the transfers where value actually settles, so you can measure adoption by protocol and chain and drill into any settlement.
Coverage map for the dataset. Each row confirms an actively tracked blockchain and protocol pair, with full history, transaction counts, and volume showing the depth behind each.
| No rows returned. | ||||||||
Every facilitator wallet is labeled. The dataset exposes every transaction routed through each facilitator, so you can drill into volume, transaction size, payer reach, and chain activity at the facilitator level.
| No rows returned. | |||||||
Not all stablecoin volume is real-world spending — much of it is ops, routing, or DeFi activity. Dune applies transparent rules to filter out non-payment activity, then classifies what remains into commerce and payroll using explicit protocol signals plus behavior-based patterns, with purpose and counterparties for benchmarking and drilldowns.
Each dataset is transfer-level, built from explicit onchain signals, and designed for benchmarking and drilldowns.
Crypto card spend, top-ups, and batch settlements, deduplicated across every rail and program. Onchain card payments data capturing purchases, top-ups, and settlement transfers across issuers and providers. Programs are counted exactly once, and detection logic is public per provider.
Machine-to-machine onchain payments via open HTTP 402 (x402) standards, every settlement, with facilitator and pattern. Agentic payments data capturing value at settlement across x402 and MPP. Each row is one onchain payment settlement. Order creation, authorization, and intermediate protocol events are excluded.
Classified stablecoin transfers for commerce and payroll, B2B, C2B, and B2C with protocol matches and behavioral heuristics. Stablecoin commerce and payroll flows data that filters non-payment activity and labels rows by purpose and counterparties. Conservative by design: transfers that do not match any rule are excluded.
| Capability | Card transactions | Agentic payments | Commerce flows |
|---|---|---|---|
| Card transactions | Stablecoin-only | ||
| Agentic payments | Stablecoin-only | ||
| Counterparties (B2B / C2B / B2C) | |||
| Payroll flows | |||
| Commerce flows | |||
| Card network | |||
| Card issuer | |||
| Card program | |||
| Labeling rule + confidence score |
Real rows from payments.card_transactions. See who spent what, with which card, on which chain. Trace each payment back to its onchain transfer.
| No rows returned. | |||||||||||||||||
Real rows from payments.agentic_payments. One row per agentic payment, with the payer, recipient, facilitator, blockchain, and token all exposed.
| No rows returned. | ||||||||||||||||||||||||
Real rows from payments.commerce_flows. See the buyer / merchant pair, the heuristic that classified the row, the protocol it routed through, and the source transfer.
| No rows returned. | ||||||||||||||||
Flexible pricing based on your actual usage. Start with a preview dataset today.
Missing a chain or contract?
Sync the full payments schema to Snowflake, BigQuery, or Databricks. No API limits.
Query the payments schema directly in Dune's SQL editor. Start from a template or write your own.
Programmatic access to the payments schema. Same shape, REST-ready for pipelines, integrations, and product features.
Plug payments data into Claude, Cursor, Codex, and other MCP-compatible agents.