> For the complete documentation index, see [llms.txt](https://docs.exads.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exads.com/ad-server/payments.md).

# Payments

Use **Payments** to configure payment methods and manage payment records across your Ad Server.

Set up the required company and payment-provider details first. Then use the advertiser workflow to manage funding records. Use the publisher workflow to create invoices and process eligible payouts.

## Payment Guides

* [Setting Up Payments](/ad-server/payments/saas-payments-setup.md) - provide company details and configure supported payment methods.
* [Managing Advertiser Payments](/ad-server/payments/saas-adv-payments-tab.md) - record invoices, balance adjustments, refunds, and other advertiser transactions.
* [Managing Publisher Payments](/ad-server/payments/saas-pub-payments-tab.md) - manage publisher invoices and process individual or mass payouts.

{% hint style="info" %}
Confirm payment-provider configuration before enabling a payment method for client accounts.
{% endhint %}


---

# 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.exads.com/ad-server/payments.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.