> For the complete documentation index, see [llms.txt](https://blockwork.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blockwork.gitbook.io/docs/platform-guides/deposits/deposit-processing-time.md).

# Deposit Processing Time

Deposit processing time on the "Blockwork.app Web3 Freelancer Platform" refers to the duration it takes for the deposited funds or cryptocurrency to be successfully credited to the client's account on the platform. The processing time can vary depending on several factors, including the chosen deposit method and the underlying blockchain network's transaction processing speed.

1. **Cryptocurrency Wallets**: Deposits made from Web3-compatible cryptocurrency wallets typically have faster processing times since they involve direct transfers on the blockchain network. The processing time can range from a few seconds to a few minutes, depending on the network's congestion and the transaction fees paid by the client.
2. **Bank Transfers**: Bank transfers can take the longest processing time, typically ranging from a few hours to several business days, depending on the banking system and the specific transfer method.


---

# 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://blockwork.gitbook.io/docs/platform-guides/deposits/deposit-processing-time.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.