> For the complete documentation index, see [llms.txt](https://docs.digitalturbine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalturbine.com/dt-console/finance/managing-payouts-in-the-dt-console.md).

# Managing Payouts in the DT Console

The Finance section within the DT Console provides a centralized hub to configure your payment information and review payments history.

<div align="left"><figure><img src="https://2949766846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLbREhkP3WlLtP6TNVZ2Q%2Fuploads%2Fgit-blob-70295c4ed60d5f66b38b55946da7e7784c950e18%2FFinance-Module.png?alt=media" alt=""><figcaption></figcaption></figure></div>

You can navigate through the following areas to manage your earnings:

* **Payment Details.** A record of your personal and banking information used for receiving payouts from DT. You can use this section to securely set up or update your preferred payment methods.
* **Invoices.** A list of revenue sharing statements from DT. This area provides comprehensive, itemized breakdowns of your earnings for each billing cycle, giving you full visibility into your generated revenue and performance over time.
* **Payment History.** A list of completed payments from DT. You can view this tab to verify past transactions, confirm the exact dates of successful payouts, and reconcile the data with your own financial accounting.


---

# 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://docs.digitalturbine.com/dt-console/finance/managing-payouts-in-the-dt-console.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.
