universal-money-address-primary-sources-2026-05-02

Universal Money Address (UMA) primary sources — 2026-05-02

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest current source of truth is the official UMA site, developer page, source-of-truth protocol repository, and the UMA Auth extension spec.
• The materials consistently frame UMA as an interoperability standard for money addressing, cross-currency payment negotiation, and compliance-aware messaging over Lightning rather than as a single company product.

Primary-source snapshots

1) Main UMA site

• URL: https://www.uma.me/
• Key excerpt:
  • The site says UMA is an open-source standard that uses the Bitcoin Lightning Network for fast, low-cost, real-time settlement.
  • It describes UMA addresses as human-readable identifiers for sending and receiving fiat or crypto, with users able to choose a preferred receiving currency.
  • It also says any wallet, exchange, or bank can integrate UMA and interoperate with other UMA-enabled providers.

2) Developer page

• URL: https://www.uma.me/developers
• Key excerpt:
  • The developer page says UMA was designed for scale and exposes currency FX, human-readable addresses, native onboarding, Travel Rule support, end-to-end encryption, and built-in compliance workflows.
  • It says institutions can use their existing compliance services for sanctions screening, transaction monitoring, and Travel Rule obligations rather than replacing those systems.
  • That framing makes UMA look more like inter-provider payments-and-compliance middleware than a simple alias standard.

3) Protocol repository README

• URL: https://raw.githubusercontent.com/uma-universal-money-address/protocol/master/README.md
• Key excerpt:
  • The README calls itself the source-of-truth UMA protocol definition.
  • It explicitly says UMA is an extension of LNURL and organizes the protocol as message-level docs for addresses, keys/authentication/encryption, LNURLP requests/responses, payreq flows, post-transaction hooks, versioning, invoices, and requests.
  • It also links language SDKs and example VASP implementations, which is a strong clue that UMA is meant as a practical interoperability standard rather than a marketing concept.

4) UMAD-05 payreq request

• URL: https://raw.githubusercontent.com/uma-universal-money-address/protocol/master/umad-05-payreq-request.md
• Key excerpt:
  • UMAD-05 says UMA’s payreq is a POST request rather than LNURL’s GET because payer data and Travel Rule information may be too large to fit in a URL.
  • It adds explicit fields for payer data, currency-denominated amounts, conversion into the receiver’s preferred currency, UMA versioning, payee-data negotiation, and settlement-layer selection.
  • The compliance section includes encrypted Travel Rule data, optional travel-rule format identifiers, KYC status, signatures, and a post-transaction callback URL.

5) UMAD-07 post-transaction hooks

• URL: https://raw.githubusercontent.com/uma-universal-money-address/protocol/master/umad-07-post-tx-hooks.md
• Key excerpt:
  • UMAD-07 defines a mechanism for counterparties to notify each other of the UTXOs used to complete a transaction.
  • It says this is useful so both sides can register those UTXOs with their compliance providers for transaction monitoring.
  • This is a strong clue that UMA is standardizing compliance operations around payments, not only address syntax.

6) UMA Auth extension

• URL: https://raw.githubusercontent.com/uma-universal-money-address/protocol/master/extensions/umade-01-auth.md
• Key excerpt:
  • The UMA Auth spec says it combines UMA, OAuth 2.0, and Nostr Wallet Connect so users can connect UMA-enabled wallets to third-party apps.
  • It describes OAuth authorization-code flows, Nostr-based decentralized client registration, granular command requests, budgets, expirations, and revocation.
  • This expands UMA from payment addressing into wallet-app connectivity and programmable payment permissions.

Working conclusion

UMA is best cataloged as Lightning-based payment-and-compliance interoperability infrastructure: a standard for human-readable money addresses, cross-currency negotiation, encrypted compliance payloads, post-transaction monitoring hooks, and wallet-to-app connectivity. The decisive evidence in this pass was the combination of LNURL extension mechanics with concrete compliance, settlement, and auth specifications.