> For the complete documentation index, see [llms.txt](https://help.activenow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.activenow.io/en/billing/withdrawing-funds-from-payu.md).

# Withdrawing Funds from PayU to Your Bank Account

Participants are paying through PayU, payments are showing in ActiveNow — but the money isn't reaching your bank account? Funds collected through PayU are held in your PayU account first, and you need to either withdraw them manually or set up automatic withdrawals. Here's how to do it.

{% hint style="info" %}
All withdrawals processed through PayU are free of charge.
{% endhint %}

## Withdrawing collected funds manually

Log in to your PayU account. Go to the ***Electronic payments*** tab and select the ***My shops*** section. Click the ***Withdraw funds*** button — PayU will transfer all funds collected so far to your bank account.

## Setting up automatic withdrawals

To avoid having to remember manual withdrawals, set up auto-withdrawals. In the ***Electronic payments*** tab, click ***Auto-withdrawals***, then select ***Edit auto-withdrawals*** in the top right corner. Set your preferred withdrawal frequency — funds will be automatically transferred to your bank account.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.activenow.io/en/billing/withdrawing-funds-from-payu.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.