SpendGraphTERMINAL INTELLIGENCE no index 2/4 publishing 2 chains 2026-09-07 08:14 UTC 27% fact 17% inference 14% private 中文

Onchain Card Intelligence

What changed in onchain card payments?

See what is actually happening across tracked stablecoin cards — and what changed.

Explore the landscape →How this is evidenced
optimismscrollethereumbasearbitrumbschyperevmpolygonsonicmantleavalanchelineachain-9745chain-4217gnosis-mainnettron-mainnetethereum-mainnetbsc-mainnetmantle-mainnet
2 / 19

networks with facts

Ether.fi Cash (cash-v3)0/14
Gnosis Pay Safe Card Protocol1/1
RedotPay0/3
UR Account / Card Protocol1/1

One node per declared network, grouped by the system that declares it. A spoke is membership, not a flow of value — no flow is published here.

Tracked scope

what this terminal observes
Cards tracked4
Deployments4
Chains with facts2

Latest complete data through 2026-09-07 08:14 UTC

Data note

Every figure here is SpendGraph's observed coverage within its own scope. It is not a total for the on-chain payment market, and no denominator for that market is published anywhere on this site.

Methodology →

Latest signals

Deterministic changes across onchain card payments — no cause is inferred

Top signal
Not applicableThe product design has a signal feed. No component produces one, so there is no panel here rather than an empty panel.
industry_signals
Also not published
observed_amount_totals
Not observed
WhyAmounts are reported per denomination with no total. A cross-currency figure would need an exchange rate, and SpendGraph does not observe one on-chain.
Also not published
market_share
Not observed
WhyThe observed population is SpendGraph's coverage, not the market. A share would need a denominator nobody here has measured.
Everything this terminal will not publish →

Card usage snapshot

Each tracked card, and what this terminal can publish about it

Ether.fi Cash (cash-v3)etherfi-cash
The most recent fully elapsed UTC day. Not the current day, and not real time.
Payment countT1 · C06
Not yet published
WhyNo figure is published for this system yet.
Active payment accountsT1 · C08
Not yet published
WhyNo figure is published for this system yet.
GrowthT1
Not yet published
WhyNo figure is published for this system yet.
Observed payment amountC09 · D020
Not observed
WhyAmounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.
Rolling 7 days, compared against the previous equal 7 days.
Payment countT1 · C06
Not yet published
WhyNo figure is published for this system yet.
Active payment accountsT1 · C08
Not yet published
WhyNo figure is published for this system yet.
GrowthT1
Not yet published
WhyNo figure is published for this system yet.
Observed payment amountC09 · D020
Not observed
WhyAmounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.
Rolling 30 days, compared against the previous equal 30 days.
Payment countT1 · C06
Not yet published
WhyNo figure is published for this system yet.
Active payment accountsT1 · C08
Not yet published
WhyNo figure is published for this system yet.
GrowthT1
Not yet published
WhyNo figure is published for this system yet.
Observed payment amountC09 · D020
Not observed
WhyAmounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.
Rolling 90 days, used as context. No method publishes this window yet.
Payment countT1 · C06
Not yet published
WhyThis window is not in the rolling-window catalog, so no method produces a figure for it. Waiting does not change that — the capability has to be built.
Active payment accountsT1 · C08
Not yet published
WhyThis window is not in the rolling-window catalog, so no method produces a figure for it. Waiting does not change that — the capability has to be built.
GrowthT1
Not yet published
WhyThis window is not in the rolling-window catalog, so no method produces a figure for it. Waiting does not change that — the capability has to be built.
Observed payment amountC09 · D020
Not observed
WhyAmounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.
Gnosis Pay Safe Card Protocolgnosis-pay
The most recent fully elapsed UTC day. Not the current day, and not real time. Through 2026-09-06 UTC, the last complete window
Payment countT1 · C06
4,788
2 published windows on this system
Active payment accountsT1 · C08
2,009
GrowthT1
-21.4%
Observed payment amountC09 · D020
Not observed
WhyAmounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.
Rolling 7 days, compared against the previous equal 7 days. Through 2026-09-06 UTC, the last complete window
Payment countT1 · C06
38,681
2 published windows on this system
Active payment accountsT1 · C08
4,637
GrowthT1
-3.3%
Observed payment amountC09 · D020
Not observed
WhyAmounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.
Rolling 30 days, compared against the previous equal 30 days. Through 2026-09-06 UTC, the last complete window
Payment countT1 · C06
101,378
2 published windows on this system
Active payment accountsT1 · C08
6,125
GrowthT1
Not yet published
WhyThe previous equal window has a zero baseline, so a ratio would be undefined rather than large.
Observed payment amountC09 · D020
Not observed
WhyAmounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.
Rolling 90 days, used as context. No method publishes this window yet.
Payment countT1 · C06
Not yet published
WhyThis window is not in the rolling-window catalog, so no method produces a figure for it. Waiting does not change that — the capability has to be built.
Active payment accountsT1 · C08
Not yet published
WhyThis window is not in the rolling-window catalog, so no method produces a figure for it. Waiting does not change that — the capability has to be built.
GrowthT1
Not yet published
WhyThis window is not in the rolling-window catalog, so no method produces a figure for it. Waiting does not change that — the capability has to be built.
Observed payment amountC09 · D020
Not observed
WhyAmounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.
RedotPayredotpay
The most recent fully elapsed UTC day. Not the current day, and not real time.
Payment countT1 · C06
Not yet published
WhyNo figure is published for this system yet.
Active payment accountsT1 · C08
Not yet published
WhyNo figure is published for this system yet.
GrowthT1
Not yet published
WhyNo figure is published for this system yet.
Observed payment amountC09 · D020
Not observed
WhyAmounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.
Rolling 7 days, compared against the previous equal 7 days.
Payment countT1 · C06
Not yet published
WhyNo figure is published for this system yet.
Active payment accountsT1 · C08
Not yet published
WhyNo figure is published for this system yet.
GrowthT1
Not yet published
WhyNo figure is published for this system yet.
Observed payment amountC09 · D020
Not observed
WhyAmounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.
Rolling 30 days, compared against the previous equal 30 days.
Payment countT1 · C06
Not yet published
WhyNo figure is published for this system yet.
Active payment accountsT1 · C08
Not yet published
WhyNo figure is published for this system yet.
GrowthT1
Not yet published
WhyNo figure is published for this system yet.
Observed payment amountC09 · D020
Not observed
WhyAmounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.
Rolling 90 days, used as context. No method publishes this window yet.
Payment countT1 · C06
Not yet published
WhyThis window is not in the rolling-window catalog, so no method produces a figure for it. Waiting does not change that — the capability has to be built.
Active payment accountsT1 · C08
Not yet published
WhyThis window is not in the rolling-window catalog, so no method produces a figure for it. Waiting does not change that — the capability has to be built.
GrowthT1
Not yet published
WhyThis window is not in the rolling-window catalog, so no method produces a figure for it. Waiting does not change that — the capability has to be built.
Observed payment amountC09 · D020
Not observed
WhyAmounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.
UR Account / Card Protocolur
The most recent fully elapsed UTC day. Not the current day, and not real time. Through 2026-09-06 UTC, the last complete window
Payment countT1 · C06
72
2 published windows on this system
Active payment accountsT1 · C08
38
GrowthT1
-17.2%
Observed payment amountC09 · D020
Not observed
WhyAmounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.
Rolling 7 days, compared against the previous equal 7 days. Through 2026-09-06 UTC, the last complete window
Payment countT1 · C06
516
2 published windows on this system
Active payment accountsT1 · C08
167
GrowthT1
21.1%
Observed payment amountC09 · D020
Not observed
WhyAmounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.
Rolling 30 days, compared against the previous equal 30 days. Through 2026-09-06 UTC, the last complete window
Payment countT1 · C06
2,088
2 published windows on this system
Active payment accountsT1 · C08
404
GrowthT1
-52.3%
Observed payment amountC09 · D020
Not observed
WhyAmounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.
Rolling 90 days, used as context. No method publishes this window yet.
Payment countT1 · C06
Not yet published
WhyThis window is not in the rolling-window catalog, so no method produces a figure for it. Waiting does not change that — the capability has to be built.
Active payment accountsT1 · C08
Not yet published
WhyThis window is not in the rolling-window catalog, so no method produces a figure for it. Waiting does not change that — the capability has to be built.
GrowthT1
Not yet published
WhyThis window is not in the rolling-window catalog, so no method produces a figure for it. Waiting does not change that — the capability has to be built.
Observed payment amountC09 · D020
Not observed
WhyAmounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.

Among SpendGraph-tracked cards

A comparison across the tracked set — not a market ranking

Ether.fi Cash (cash-v3)UnavailableNot published
Gnosis Pay Safe Card Protocol38,681
RedotPayUnavailableNot published
UR Account / Card Protocol516

No figure is published for this system yet.

Ether.fi Cash (cash-v3)UnavailableNot published
Gnosis Pay Safe Card Protocol4,637
RedotPayUnavailableNot published
UR Account / Card Protocol167

No figure is published for this system yet.

Ether.fi Cash (cash-v3)UnavailableNot observed
Gnosis Pay Safe Card ProtocolUnavailableNot observed
RedotPayUnavailableNot observed
UR Account / Card ProtocolUnavailableNot observed

Amounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.

Bars compare magnitude against the largest value shown. They are not a share of any market and no total for one is published anywhere on this site.

Data trust

Coverage iDeployments with a committed publication batch. A batch answers how far coverage reaches, never how many facts exist.
2/4
2 with a contiguous watermark
Function assessment iRegistration packs that carry payment-function assessments against the frozen catalog of seventeen.
4/4
packs carrying assessments
Architecture profile iA draft profile counts as none: a claim under review presented as established is what review status exists to prevent.
3/4
published profiles

Data trust and quality

Every figure is a count over a stated denominator — nothing is weighted into a score

Publishing
2/4
deployments with a committed batch
Contiguous
2/4
with an unbroken watermark
Republished
19
overlapping committed batches
Fact evidence
19/70
assessment rows proven on chain
Catalog proven
8/17
functions with any fact row
Metric series
5/5
core metrics with a published series

Explore deeper

From high-level usage to verifiable evidence

Payment architectureHow these systems work Functions & featuresWhat each one can do Onchain evidenceSee the data behind a figure Compare systemsDifferences described, never scored

Capability coverage

Systems per group

Identity0/4Account4/4Funding4/4Authorization4/4Settlement4/4Credit0/4

Payment economy at a glance

systems reaching each capability
Identity0/4
Account4/4
Funding4/4
Authorization4/4
Settlement4/4
Credit0/4

Market snapshot

Observed coverage, not market total — each card names its own source

Payment events observedC06 · C09
177,104
400 published points
Payment systemsC01
4
4 registration packs
Active payment addressesC06 · C09
6,150
1 of 4 systemsiCounted over gnosis-pay. An on-chain address is the account identity on those systems and not on the others: UR's account is a Fiat24Account ERC-721 token id, which the registry states is not the holding address, and RedotPay registers no on-chain account. The boundary is in the metric definition, not in this rendering. This is not a share of `Active accounts` and must not be added to it — every address counted here is also one of those accounts. C01 registers an account-identity break for gnosis-pay: a holder who migrated holds an address on each side of it, and this count — which is over the whole observed window — counts both. That is two addresses, which is what this measures. It is not two holders, and the registry forbids reading it as one series of holders across the break.
Tracked payment activityC06
Not observed
needs an amount model iAmounts are reported per denomination with no total. A cross-currency figure would need an exchange rate, and SpendGraph does not observe one on-chain.
Connected chainsC01
2
chain id 100 · 5000

Payment economy flow

How a payment system is structured — a semantic model, not a flow of funds

Source of funds
4/4
  • F02 User funds
  • F03 Account funding
Stablecoin rails
Research required
Carried as an infrastructure rail — chains, roles, custody — none of which is a payment function.
Payment accounts
4/4
  • F01 Payment account
Payment instruments
4/4
  • F04 Authorization request
  • F05 Authorization decision
  • F06 On-chain payment control
  • F08 Funds hold
  • F09 Authorization adjustment
  • F14 Authorization expiry
Merchant & payments
Research required
The frozen catalog defines no acceptance function. F16 is a dispute, which is not the same thing.
Settlement layer
4/4
  • F07 Post-authorization funds action
  • F10 Clearing instruction
  • F11 Pre-settlement funds movement
  • F12 Final network settlement
  • F13 Reversal
  • F15 Refund
Financial services
Research required
Yield, lending and insurance are not in the frozen catalog; F17 is a charge on a payment, not a service sold beside one.

Payment ecosystem map

Registered systems, grouped by the capability ground they cover — nothing sized by data, no share, no order of magnitude

Account Funding Authorization Settlement
Ether.fi Cash (cash-v3)4/4 Gnosis Pay Safe Card Protocol4/4 RedotPay4/4 UR Account / Card Protocol4/4

No node is weighted, scaled or ranked by any figure — a node is as wide as its own text and nothing else. The count is assessed groups out of 4. The mapping forbids an unfounded market share, so the only relation this map draws is that two systems in one cluster cover the same capability ground.

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.