Payment landscape
Registered systems, the capability groups they cover, and how far each is observed.
Snapshot
Observed coverage, not market total — each card names its own source
Payment stack map
The six capability groups around the payment economy. Position is catalog order clockwise from the top; no edge here is a flow of value, and no flow is published on this site.
How to read: clockwise from the top is frozen-catalog order. A capability group with no catalog function is shown in its slot and says so.
The content mapping also uses "layer" for six regions of the payment economy. That is a different model, and it is not this map.iThe Landscape mapping §三 names six ecosystem layers — Stablecoin Rails, Payment Accounts, Payment Instruments, Merchant & Payments, Settlement & Infrastructure, Credit & Lending. This map renders the six capability groups instead, because that is what the frozen seventeen-function catalog can be assessed against. No registration pack declares a category, so the layer model has no per-protocol data to render; drawing it today would be six empty states in place of real assessments.
Protocol explorer
Sorted by identifier — not a ranking
| System | Registration | Networks | Chains | Functions | Active addresses | Coverage |
|---|---|---|---|---|---|---|
| Ether.fi Cash (cash-v3) etherfi-cash | DRAFT | 14 | 0 | 17/17 | — | Active nothing published Dormant nothing published |
| Gnosis Pay Safe Card Protocol gnosis-pay | DRAFT | 1 | 1 | 17/17 | — | Active 7085 batches · 47,817,934 – 48,021,665 · contiguous 48,021,665 |
| RedotPay redotpay | DRAFT | 3 | 0 | 17/17 | — | No deployment |
| UR Account / Card Protocol ur | DRAFT | 1 | 1 | 17/17 | n/aiC01 registers this system's account model as `ERC721_TOKEN_ID`, so its account identity is not an on-chain address and a count of addresses has no value to report for it — not a value of zero. Its activity is counted under `Active accounts`, the measure that spans every account model. | Active 2015 batches · 31,420,289 – 100,056,858 · contiguous 47,816,147 |
Capability groups
Identity
Not in catalogAccount
4 of 4 systems assessedFunding
4 of 4 systems assessedAuthorization
4 of 4 systems assessedSettlement
4 of 4 systems assessedCredit
Not in catalogChains
Chains with a published fact — not every registered network
Publication state
What the registry declares, against what has been published
Landscape insights
Each carries its figure, its window and its source
539 Payment events
2026-08-21 → 2026-08-31 · 11 windowspost_auth_funds_action_count · metric-v43 Active accounts
2026-08-21 → 2026-08-31 · 11 windowsactive_account_count · metric-v40 Active payment addresses
2026-08-28 → 2026-08-31 · 4 windowsactive_payment_address_count · metric-v4§六 also draws on a rule engine and research analysis for the reading behind each observation. Neither exists in this system, so these are published measurements with their windows attached and not an interpretation of them. §六 bans a prediction without evidence; nothing here extrapolates past its last window.
Recently added systems
Methodology
- Every count here is SpendGraph's observed coverage. It is not a total for the on-chain payment market, and no denominator for that market is published anywhere on this site.
- Counts are read from C09's published series at a pinned catalog revision. This page performs no count of its own — a second implementation of a published metric is a second thing that can be wrong.
- Publication batches answer how far coverage reaches, never how many facts exist. A repair republishes a range, so summing batch fact counts double-counts the repaired part: on 2026-08-21 that sum was 85,021 against 81,034 actual facts, with zero retractions.
- A registration status describes how far SpendGraph's own review of a pack has got. It is not an assessment of the protocol, and every review state is compatible with a deployment that stopped carrying payments months ago — which is why activity is a separate column.
- The payment function catalog is frozen at seventeen entries. A new protocol term is mapped onto an existing function rather than growing the catalog, so a function absent from a protocol's assessment means nobody has assessed it — not that it does not exist.
- The six capability groups are defined by this site alone, as a presentation over the seventeen. Two of them — Identity and Credit — have no catalog function, so no protocol can be assessed against them and they are shown as such.