> For the complete documentation index, see [llms.txt](https://docs.silopay.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silopay.io/how-silo-works/payment-requests.md).

# Payment Requests

Silo allows users to request payments using a QR code. The receiver enters the amount they want to receive, and Silo generates a QR code in one tap. The receiver shares that QR code with the sender, who scans it, confirms the payment, and sends.

The QR code contains the receiver's username and the requested amount. The sender does not need to manually type a username or figure out how much to send. They scan, confirm, and pay.

This flow follows the same routing logic as any other Silo payment. The sender chooses which asset and chain to pay from on their side. Silo reads the receiver's preferences and handles conversion, routing, and privacy automatically. The receiver gets paid according to their saved preferences, regardless of what the sender pays with.

Payment requests are useful for in-person transactions, invoicing, and any situation where the receiver wants to initiate the payment flow rather than waiting for the sender to look up their username and enter an amount manually.

<br>


---

# 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.silopay.io/how-silo-works/payment-requests.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.