# Overview

Instead of the traditional approach in blockchain where the sender initiates the transaction, with Pull Payments, the tables are turned. Imagine you've availed a service and instead of sending the money directly, the service provider sends you a detailed payment request. The receiver sets up this request, pre-filled with all transaction specifics, and dispatches it to the sender’s wallet, functioning much like a straightforward notification.

<figure><img src="/files/C66I7AYdXB9eGoFigBQW" alt=""><figcaption><p>Pull Payments</p></figcaption></figure>

When the sender spots this notification in their wallet, they can conveniently open it, review the outlined details, and with a quick confirmation, approve the payment. What’s fascinating is the way the payment is then processed. The system pulls the mentioned amount from the sender’s account, but it’s done with the the sender’s authority.

Moreover, the evolving landscape of digital wallets is making this process even slicker. The upcoming auto-approve feature in many wallets promises to streamline this further. Regular or trusted transactions can be set to get approved automatically, minimizing the need for manual checks each time. In simple terms, Pull Payments lets the receiver start the payment process while the sender still has the final approval. This creates a clear and easy way for both sides to handle transactions.

* Chains Fetcch's pull payments layer is catered to a wide range of blockchains including major EVM Chains, Solana, Aptos, SUI, Fuel, Near, and several others.


---

# 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://docs.fetcch.xyz/pull-payments-layer/overview.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.