> For the complete documentation index, see [llms.txt](https://docs.gobtcpay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gobtcpay.com/api-reference/wallet-api.md).

# Wallet API

This surface is for a non-custodial **web3 wallet** that lets its users accept and pay for Bitcoin purchases at a merchant's point of sale. The wallet holds the keys; GoBTC Pay builds the transactions that the wallet signs.

A typical integration is four steps: authenticate the user with their wallet key, register their multisig wallet, read balances, then pay at a POS by scanning a QR and signing the transaction.

* **Authentication:** sign a server-issued challenge with the wallet's private key, then exchange the signature for a Bearer JWT (`Authorization: Bearer <accessToken>`).
* **Operation groups:** Authentication, Wallet (register, address, balances), Payments (get, list, build, settle), and Multisig Withdrawal.


---

# 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://docs.gobtcpay.com/api-reference/wallet-api.md?ask=<question>&goal=<endgoal>
```

`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.