> For the complete documentation index, see [llms.txt](https://upyy.gitbook.io/upyy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upyy.gitbook.io/upyy/main-functions/mobile-payments.md). # Mobile Payments UPYY mobile payment system accommodates both push and pull transactions, offering a versatile way to handle payments. This system allows users to make payments by scanning a payee's QR code with their smartphone camera, aligning with traditional mobile payment methods. Alternatively, UPYY enables users to make payments by presenting their own QR code to the payee. ### "Push" and "Pull" Transactions Overview There are two fundamental types of payment processes: push type and pull type. Push and pull transactions are key methods for transferring funds between parties in mobile payment systems. ### Push Transactions in UPYY In the UPYY push payment process, the payer initiates the transaction, taking an active role in sending funds to the payee. This gives payers full control over their payments, allowing them to decide the timing, amount, and recipient of the money. In UPYY, a push transaction refers to the action of sending or transferring assets from one party to another. The sender initiates the transfer, effectively "pushing" the asset to the recipient's UPYY address. ### Pull Transactions in UPYY Conversely, in the UPYY pull payment process, the payee (recipient) requests payment from the payer’s account. The payer then authorizes the payee to "pull" funds, thus starting the transaction process. In UPYY, a pull transaction is commenced by the payee, who issues a request to transfer an asset from the payer’s account or smart contract, thereby initiating the transaction. --- # 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://upyy.gitbook.io/upyy/main-functions/mobile-payments.md?ask=&goal= ``` `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.