> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/wiki/economics-and-payments/payments-in-bitcoin.md). # Payments in Bitcoin The term **payments** in a Bitcoin context generally refers the process of a purchaser paying for a good or service from a vendor. Payments are an important aspect of Bitcoin and it is crucial that comprehensive standards exist that enable parties and software systems to process payments in ways that cover a wide variety of use cases. There are several standards defined for Bitcoin SV that cover methods of requesting and performing payments. 1. BIP270 BIP270 (now specified as [BRC-27: Direct Payment Protocol](https://bsv.brc.dev/payments/0027)) is a streamlined version of the [BIP70 Payment Protocol](https://github.com/bitcoin/bips/blob/master/bip-0070.mediawiki) introduced in 2013. It is a protocol for communication between a \[(payment)] (usually either a merchant, a payment processor, or simply the recipient's wallet) and their customer (the sender of the funds). It enables: * Improved user experience * Simpler wallet infrastructure * Multiple outputs * Improved security against man-in-the-middle attacks BIP270 is designed for wallets that use Simplified Payment Verification to achieve huge improvements at scale. Transactions can be exchanged partially or in iterations. This is far faster when done peer to peer directly between the payer and the payee, writing to the ledger only at the end to settle the transaction(s). This BIP is an optimisation of BIP70. Changes include: * Moves all signature exchange and validation to the communication later (usually HTTPS) * Add multiple outputs * A library optimised for peer to peer transaction management 1. BSVAlias BSVAlias is a set of standards for using email type identities with Bitcoin SV, with making and receiving payments as one of its first use-cases. Paymail is the first practical implementation of BSVAlias. 2. Payment Channels Payment Channels are a mechanism where two or more parties can directly exchange and update a transaction. The mechanism includes: methods for establishing, or opening, updating, and finalising or closing the payment channel. The mechanism also covers the possibility of any of the parties becoming unresponsive, usually by enabling the recovery of funds after a fixed time. Payment channels support extremely rapid transaction updates with only the final closing transaction being confirmed in the blockchain. Payment channels can be useful for streaming data, operating a sequence of events, or operating with a live dataset in applications such as gaming and more. 3. Legacy Payment Protocols Many of the legacy payment protocols used a mechanism where the payer is asked to broadcast a transaction to the network, and the payee would scan the network for relevant transactions rather than handling the transaction directly peer-to-peer as with SPV. This mechanism does not scale when transaction volume increases and is inefficient. 4. IP to IP payments The original version of the Bitcoin node client had the facility to conduct IP to IP payments where a receiver could give a payer their IP address. The payer's client would reach out to the payee's client and request a public key for the payment to be addressed to. This payment method had valid security concerns, but rather than addressing these concerns, the mechanism was removed. Payment processes that draw from this original idea to allow network peers to interact securely using cryptographically verified IP addresses have since been proposed. 5. BIP21 [BIP21](https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki) has been one of the predominant means of making mobile payments in Bitcoin throughout its history. Almost all QR code based payment gateways used within Bitcoin are, or are an extension of, BIP21. BIP21 itself is an extension of [RFC-3986](https://tools.ietf.org/html/rfc3986), the RFC standard for URIs (Universal Resource Identifiers). 6. BIP70 [BIP70](https://github.com/bitcoin/bips/blob/master/bip-0070.mediawiki) was a payment protocol for reaching out to receivers using an extension of BIP21 that added a URL. The URL directed the device to reach out to a server which would provide it with a script, or an address linked to the QR code. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://hub.bsvblockchain.org/wiki/economics-and-payments/payments-in-bitcoin.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.