> For the complete documentation index, see [llms.txt](https://docs.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsvblockchain.org/paymail/overview.md).

# Overview

**paymail** is a collection of protocols for Bitcoin SV wallets that allow for a set of simplified user experiences to be delivered across all wallets in the ecosystem.

❌ No more complicated `17Dx2iAnGWPJCdqVvRFr45vL9YvT86TDsn` addresses

✅ Simple payment handles like `<alias>@<domain>.<tld>`

The goals of the paymail protocol are:

* User friendly payment destinations through memorable handles
* Permissionless implementation
* Self-hosted or delegated to a managed service
* Automatic service discovery/location
* PKI infrastructure
* Cross-wallet exchange of single-use transaction output scripts of any construction
* Request and response authentication
* Security and policy management
* Capability extensibility and discovery

## bsvalias

The family of related protocols are collectively referred to as the `bsvalias` protocols. At the time of writing, these include:

* [BRFC Specifications](/paymail/brfc-specifications.md)
* [Service Discovery](/paymail/service-discovery.md)
* [Public Key Infrastructure](/paymail/public-key-infrastructure.md)
* [Payment Addressing](/paymail/payment-addressing.md)

## paymail

**paymail** is the name for the implementation of the following protocols:

* [Service Discovery](/paymail/service-discovery.md)
* [Public Key Infrastructure](/paymail/public-key-infrastructure.md)
* [Basic Address Resolution](/paymail/payment-addressing/basic-address-resolution.md) from the [Payment Addressing](/paymail/payment-addressing.md) protocol group

The **paymail** brand is reserved for products and services that, at a minimum, implement each of the above.

## Extension Protocols

As defined in the [BRFC Specifications](/paymail/brfc-specifications.md), anybody can propose an extension to the `bsvalias` and paymail protocols, and as per the [Capability Discovery](/paymail/service-discovery/capability-discovery.md) section of the [Service Discovery](/paymail/service-discovery.md) protocol, implementations can declare support for extensions to allow for cross-wallet processes.

Extension protocols are the collection of protocols not contained within the core paymail set defined above, but that are fully compatible with `bsvalias` protocols and paymail implementations. Notable examples presently include:

* [Sender Validation](/paymail/payment-addressing/sender-validation.md)
* [Receiver Approvals](/paymail/payment-addressing/receiver-approvals.md)
* [PayTo Protocol Prefix](/paymail/payment-addressing/payto-protocol-prefix.md)
* MultiSig authorisations
* Threshold signature group secret setup and message signing
* Payment channels


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bsvblockchain.org/paymail/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.