1# NIP-A323## payto: Payment Targets45`draft` `optional`67This NIP standardizes how payment addresses are declared across any network or platform.89#### Tag Format1011Payment targets are specified using `payto` tags with the following structure:1213```text14["payto", "<type>", "<address>"]15```1617Where:18- The first element is always the literal string `"payto"`19- The second element is the payment `type` (e.g., `"bitcoin"`, `"lightning"`), always lowercase.20- The third element is the `address` (e.g., address, username)2122Clients may perform additional network- or platform-specific validation for recognized types.2324### Example2526```json27{28 "pubkey": "afc93622eb4d79c0fb75e56e0c14553f7214b0a466abeba14cb38968c6755e6a",29 "kind": 10133,30 "content": "",31 "tags": [32 ["payto", "bitcoin", "bc1qxq66e0t8d7ugdecwnmv58e90tpry23nc84pg9k"],33 ["payto", "nano", "nano_1dctqbmqxfppo9pswbm6kg9d4s4mbraqn8i4m7ob9gnzz91aurmuho48jx3c"],34 ["payto", "unknowntype", "l7tbta5b9xze6ckkfc99uohzxd009b0r"]35 ],36 ...37}38```3940For 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](https://www.rfc-editor.org/rfc/rfc8905.html): `payto://<type>/<address>`.4142Possible rendered URIs:43- `bitcoin:bc1qxq66e0t8d7ugdecwnmv58e90tpry23nc84pg9k`44- `payto://nano/nano_1dctqbmqxfppo9pswbm6kg9d4s4mbraqn8i4m7ob9gnzz91aurmuho48jx3c`45- `payto://unknowntype/l7tbta5b9xze6ckkfc99uohzxd009b0r`4647### Commonly Used Tags4849- `bip352` (silent payments)50- `bip353` (DNS addresses)51- `bitcoin`52- `cashme` (Cash App `$`-prefixed cashtag)53- `ethereum`54- `lightning` (lightning address)55- `litecoin`56- `monero`57- `nano`58- `paypal`59- `revolut`60- `solana`61- `venmo`62- `zcash`6364New widely deployed formats can be added to this list later.