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

# Payments

## Listing purchase

* **From:** buyer wallet
* **To:** seller’s NQ address on the listing
* **Amount:** listing `price_luna`
* **Memo:** `dplace:content:{listing-id}`

The stall verifies the transaction on the configured RPC. Pending hashes are stored. A later confirm of the same hash grants the entitlement once.

## Bounty fund

* **To:** `ESCROW_ADDRESS`
* **Memo:** `dplace:bounty:{id}`

## Bounty payout

* **From:** escrow
* **To:** winner
* **Memo:** `dplace:payout:{id}`

## Bounty refund

* **From:** escrow
* **To:** bounty owner
* **Memo:** `dplace:refund:{id}`

## Explorer

Confirmed hashes link to `https://nimiq.watch/#{hash}`.

## Closing Hub

If you close Hub without finishing checkout, D place reports that no NIM left the wallet. That is not a failed chain payment. It is a cancelled Hub session.

## What this escrow is not

Nimiq Pay Mini App has no native HTLC or listing-level multisig in the SDK used here. Escrow is an address the operator controls, plus the stall’s records. Treat `ESCROW_ADDRESS` as a hot wallet you actually operate.


---

# 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.deplace.space/payments.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.