← All NIPs

NIP-A3

payto: Payment Targets

DraftEvents

A kind 10133 list of the ways people can pay you, such as Bitcoin, Lightning or PayPal, each written as a payto tag with a type and an address.

Status
In use and still allowed to change.
Kinds
Tags
  • payto
Last changed
Sep 9, 2026

Try it

Edit the form or the JSON: both stay in sync, the badge says whether the result is valid, and tapping any field explains it.

Examples
Valid 1 note

Not signed yet · Demo keys only. These personas' secret keys are public on purpose.

Form
Jan 1, 2025, 12:00 AM UTC

Content

Empty: the addresses are in the tags.

This kind has no content: leave it as an empty string.

Tags

  1. payto Required

    One way to pay you.

  2. payto Required

    One way to pay you.

  3. payto Required

    One way to pay you.

Add tag

How this NIP works

Step 1 of 4

One list per person

Kind 10133 is replaceable: you publish one list with every way to pay you, and a new version replaces the old one.

In the course

No course chapter covers this NIP yet. The editor above is the quickest way in.

Builds on

See also

Specification

Specification text is quoted in English from the nostr-protocol/nips repository. Our explanations and the interface are translated. Source on GitHub at commit 0046368

Read the spec249 words, quoted from the repository at commit 0046368.

NIP-A3

payto: Payment Targets

draft optional

This NIP standardizes how payment addresses are declared across any network or platform.

Tag Format

Payment targets are specified using payto tags with the following structure:

["payto", "<type>", "<address>"]

Where:

  • The first element is always the literal string "payto"
  • The second element is the payment type (e.g., "bitcoin", "lightning"), always lowercase.
  • The third element is the address (e.g., address, username)

Clients may perform additional network- or platform-specific validation for recognized types.

Example

{
  "pubkey": "afc93622eb4d79c0fb75e56e0c14553f7214b0a466abeba14cb38968c6755e6a",
  "kind": 10133,
  "content": "",
  "tags": [
    ["payto", "bitcoin", "bc1qxq66e0t8d7ugdecwnmv58e90tpry23nc84pg9k"],
    ["payto", "nano", "nano_1dctqbmqxfppo9pswbm6kg9d4s4mbraqn8i4m7ob9gnzz91aurmuho48jx3c"],
    ["payto", "unknowntype", "l7tbta5b9xze6ckkfc99uohzxd009b0r"]
  ],
  ...
}

For each payto tag in kind 10133 events, clients can render the payment address as a button or link. Clients may use a specific URI scheme when one is available, such as bitcoin:<address> or ethereum:<address>. Otherwise fall back to the payto URI scheme defined by RFC-8905: payto://<type>/<address>.

Possible rendered URIs:

  • bitcoin:bc1qxq66e0t8d7ugdecwnmv58e90tpry23nc84pg9k
  • payto://nano/nano_1dctqbmqxfppo9pswbm6kg9d4s4mbraqn8i4m7ob9gnzz91aurmuho48jx3c
  • payto://unknowntype/l7tbta5b9xze6ckkfc99uohzxd009b0r

Commonly Used Tags

  • bip352 (silent payments)
  • bip353 (DNS addresses)
  • bitcoin
  • bitcoincash
  • cashme (Cash App $-prefixed cashtag)
  • ethereum
  • lightning (lightning address)
  • litecoin
  • monero
  • nano
  • paypal
  • revolut
  • solana
  • tron
  • venmo
  • zcash

New widely deployed formats can be added to this list later.

For an unknown payment type, in case of ambiguities, a specific address URI scheme may be used when one is available (such as bitcoincash from bitcoincash:<address>).