> For the complete documentation index, see [llms.txt](https://docs.fetcch.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fetcch.xyz/pull-payments-layer/security/storage.md). # Storage Pull payments are stored on Fetcch network and then to settled to respective blockchains ### Encryption All of the pull payments are only visible to the concerned parties (sender and receiver), wallets/applications can read the payment request only if they have the permission from the concerned user itself. We use HMAC based encryption algorithm for encrypting important data with a secret key. Private pull payments are going to be live on Fetcch network in coming months, this requests will be fulfilled through some kind of a stealth address. ### L1 Accepted There is a slot where data is accepted on L2 but is yet to be settled on an L1, data till then is considered as **L2 Accepted** and after it is settled on L1 then it is considered as **L1 Accepted** If a data is L2 Accepted then there are more chances of it being L1 Accepted than being dropped, it depends on the blockchain that we are settling on, some blockchains take more time than others. Also some blockchains are more costly than others, we have a lot of gas optimizations done for these blockchains to lower the costs --- # 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.fetcch.xyz/pull-payments-layer/security/storage.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.