Payment functions
The capability layer: six groups over a frozen catalog of seventeen.
Payment functions
Six capability groups over the frozen catalog
Function coverage
Assessed is not evidenced — the catalog is fully reviewed and partly proven
Function catalog — all 17 entries
| Code | Function | Assessed by | Evidence |
|---|---|---|---|
| F01 | Payment account | 4/4 | 3 fact 1 private only |
| F02 | User funds | 4/4 | 3 fact 1 private only |
| F03 | Account funding | 4/4 | 4 inference |
| F04 | Authorization request | 4/4 | 3 disproven 1 inference |
| F05 | Authorization decision | 4/4 | 2 disproven 1 fact 1 private only |
| F06 | On-chain payment control | 4/4 | 2 fact 2 inference |
| F07 | Post-authorization funds action | 4/4 | 4 fact 1 private only |
| F08 | Funds hold | 4/4 | 2 fact 1 private only 1 disproven |
| F09 | Authorization adjustment | 4/4 | 2 disproven 1 inference 1 unknown |
| F10 | Clearing instruction | 4/4 | 3 disproven 1 inference |
| F11 | Pre-settlement funds movement | 4/4 | 3 fact 1 unknown 1 disproven |
| F12 | Final network settlement | 4/4 | 3 disproven 1 inference |
| F13 | Reversal | 4/4 | 2 disproven 1 fact 1 private only |
| F14 | Authorization expiry | 4/4 | 2 disproven 1 private only 1 unknown |
| F15 | Refund | 4/4 | 2 disproven 1 private only 1 unknown |
| F16 | Dispute / chargeback | 4/4 | 1 inference 1 private only 1 unknown 1 disproven |
| F17 | Fees | 4/4 | 1 inference 1 private only 1 unknown 1 disproven |
Two models
Representative implementations
Which registered systems have assessed each capability — catalog order, not a ranking
The catalog defines no function for this capability, so there is nothing for a system to have assessed.
The catalog defines no function for this capability, so there is nothing for a system to have assessed.
§八 asks which systems implement each capability, and says it is neither a recommendation nor a ranking. Every system that assessed the capability is here, in the registry's catalog order, with no figure beside a name.
Function evolution timeline
Which capabilities matured when — not yet published
The capability matrix above is today's assessment. It is a snapshot, not the first point of a series.
Function deep dive
What each capability is made of — not yet published
Catalog revisions
assessments are not all against the same revision
Function insights
Each one names its fact, its scope, and what it was read from
Account is observed across 4 of 4 registered systems
Read from the capability matrix on this page — the group's 1 catalog functions, assessed per registration pack.Settlement is observed across 4 of 4
Same matrix, same denominator. A lower count is a statement about published evidence, not about the capability being absent from the system.Identity · Credit carry no catalog function
The frozen seventeen-function catalog defines nothing for them, so no system can be assessed against them at any coverage. The gap is the catalog's.§十 also draws on research analysis for why a function is implemented where it is. No component here produces that, so these are counts over the matrix and not an explanation of it.
Recent function updates
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.
Capability matrix
Assessed functions per group, with the evidence distribution
| System | Identity | Account | Funding | Authorization | Settlement | Credit |
|---|---|---|---|---|---|---|
| Ether.fi Cash (cash-v3) | —not in catalog | 1/1 1 fact | 2/2 1 fact 1 inference | 6/6 5 disproven 1 fact | 6/6 4 fact 4 disproven | —not in catalog |
| Gnosis Pay Safe Card Protocol | —not in catalog | 1/1 1 fact | 2/2 1 fact 1 inference | 6/6 3 fact 3 disproven | 6/6 4 disproven 2 fact | —not in catalog |
| RedotPay | —not in catalog | 1/1 1 private only | 2/2 1 inference 1 private only | 6/6 3 private only 2 inference 1 unknown | 6/6 3 private only 2 inference 1 unknown | —not in catalog |
| UR Account / Card Protocol | —not in catalog | 1/1 1 fact | 2/2 1 fact 1 inference | 6/6 2 inference 2 disproven 1 fact 1 unknown | 6/6 3 disproven 2 fact 1 unknown | —not in catalog |
Identity and Credit have no function in the frozen catalog, so no assessment can exist for them — a dash there is not a gap in any protocol's registration.