> 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/standards-protocols-and-tools/building-on-bitcoin/merchant-api.md).

# Merchant API

The mAPI (formally known as Merchant API) is a new development in Bitcoin, [released](https://bsvblockchain.org/bsv-releases/miner-id-and-merchant-api-beta-release/) in April 2020. The API enables merchants accepting Bitcoin transactions to get all of the assurance they need to be able to accept transactions on a 'zero confirmation' basis (see Confirmation). Merchants are able to find out in advance (even before broadcasting a transaction) what transaction fee is required by Miners to mine it.

1. Background As explained by Steve Shadders in [Steve Shadders Discusses the Bitcoin SV (BSV) Tech Pillars - Bitstocks Podcast Ep. 7](https://youtu.be/WDuvYp77tJU?t=2126) at 36m 12s: It also allows Miners to put user-based fee policies in place.
2. BRFC (Bitcoin Request for Comment) Specification The BRFC specification can be found (<https://github.com/bitcoin-sv-specs/brfc-merchantapi>).
3. Reference Implementation The reference implementation can be found (<https://github.com/bitcoin-sv/merchantapi-reference>).


---

# 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://hub.bsvblockchain.org/wiki/standards-protocols-and-tools/building-on-bitcoin/merchant-api.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.