#iso20022

Live, measured metrics for the hashtag #iso20022 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #iso20022

This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.

$110.68/ year · 8-character #name
Claim #iso20022$110.68/yrBuy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
13
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 13
0
Avg reactions / post
Mastodon · last 13

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 17:52 UTC
0
07-22
0
07-23
0
07-24
0
07-25
0
07-26
0
07-27
0
07-28

0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.

Related hashtags

measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-28 17:52 UTC

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 17:52 UTC

Everything below is measured over the latest 13 public posts (spanning ~27811 hours).

Posting hours (UTC) — busiest: 15:00

00:0012:0023:00

Languages: English (10) · Dutch (2) · Portuguese (1)

Avg boosts / post: 0

Top of the latest posts

  • Global instant payments are scaling, but fragmented infra and legacy tech debt keep the real value out of reach. 🐧 To achieve true cross-border efficiency, we must solve the interoperability puzzle. Standards like #ISO20022 are "well-lit p

    Chuck Mattern@[email protected]002026-04-02 15:34 UTCView post →
  • Standardized payment data formats are enabling interoperability across global fintech systems, reducing cross-border friction. #ISO20022 #GlobalPayments

    Kanishka Naik@[email protected]002026-02-25 18:09 UTCView post →
  • Omg, I'm looking at the #ISO20022 specs at the moment. The #XML schema files they provide have no xsd:documentation elements, it's instead provided in a separate word document. Why do it like that? It's so weird.

    xmlns="Dan"@[email protected]002025-11-20 15:53 UTCView post →

Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/iso20022