> For the complete documentation index, see [llms.txt](https://defiolio.gitbook.io/defiolio_wallet/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://defiolio.gitbook.io/defiolio_wallet/wallet-features/payment-requesting-system.md).

# Payment Requesting System

Let's face it – the process of sending and receiving funds within the crypto space can be a real headache. The need to obtain and share lengthy wallet addresses often leaves both new and experienced users scratching their heads in confusion. 😖📥📤

It's time to simplify the way we interact with wallets, and that's exactly what DefiOlio aims to achieve. 🌟🔁

Say goodbye to the days of copy-pasting complex wallet addresses and the bewildered expressions that come with it. DefiOlio is here to streamline the entire fund transfer process through our innovative Payment Requesting System. With this game-changing feature, requesting funds becomes as easy as sharing a simple deep link. 📲🔗

Here's how it works: Instead of expecting users to memorize or meticulously copy wallet addresses, DefiOlio generates a unique deep link. This deep link serves as a recognized format by the wallet, eliminating the need for manual address input. Your security is our top priority, and rest assured, the generated link is not a functional URL (unless the user doesn't have the DefiOlio Wallet installed, in which case it will route to the proper app based on their platform). It is specifically designed to trigger the wallet and initiate the seamless payment request process. With DefiOlio, requesting funds becomes as easy as sharing a single link, revolutionizing the way you interact with wallets and ensuring a hassle-free experience for all users. 🚀💼💰

When you request funds through DefiOlio, you simply specify the desired token, the amount, and the corresponding chain (which may automatically populate based on the selected token). With just a few taps, your payment request is sent. Within seconds, the recipient receives a notification, providing them with the option to fulfill the payment or decline it. 💸💬📩

But we're not stopping there. In the future, we envision expanding the capabilities of our Payment Requesting System to include automated token swaps. This means that if the requested token is not currently held by the user, DefiOlio may facilitate an automatic swap from the user's existing tokens to the requested token. This seamless integration ensures that users can effortlessly fulfill payment requests, regardless of their token holdings. 🔄🌐

At DefiOlio, we value your privacy and the principles of decentralization. Rest assured, we do not store or distribute any of the sensitive payment request data. We believe in keeping your transactions secure, confidential, and entirely within your control. Our secret sauce lies in the intricate design of the Payment Requesting System – just like a magician never reveals their tricks. 🎩🔐

\
\
Note:  DON'T FORGET WE ARE STILL IN THE DEVELOPMENT STAGES!


---

# 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://defiolio.gitbook.io/defiolio_wallet/wallet-features/payment-requesting-system.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.