# Example QR codes

Reference QR codes for [wallet developers](/wallets.md) (and the [Branta scanner](https://scan.branta.pro/scan)) to confirm a Branta integration handles each destination type correctly — on-chain, Lightning, ZK variants, and not-found. Scan them with your wallet to verify counterparty info renders before broadcast.

Pages are split by [environment](/tech-and-setup/environments.md):

* [**Production**](/wallets/example-qr-codes/production.md) — points at `guardrail.branta.pro`.
* [**Staging**](/wallets/example-qr-codes/staging.md) — points at `staging.branta.pro`.

Each page exposes the QR variants as tabs:

* **On-chain** vs **Lightning** — the destination network.
* **ZK** vs non-ZK — [Zero-Knowledge](/tech-and-setup/api/v2/adding-payments.md#zero-knowledge) destinations encrypt the payment destination so it never reaches Branta in plain text. On-chain ZK QRs carry `branta_id` + `branta_secret` query params alongside the address; Lightning ZK relies on the SDK encrypting the invoice itself before lookup. Non-ZK destinations are plain addresses or invoices.
* **Not found** — an unregistered destination. Per the [wallet integration pattern](/wallets.md), wallets should render nothing on a miss.


---

# Agent Instructions: 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:

```
GET https://developer.branta.pro/wallets/example-qr-codes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.