> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/get-started/getting-started/finance-and-accounting/quick-payment-reports.md).

# Quick payment reports

## Overview

Quick payments allow you to provide extra money to your top affiliates either though a one-time payment or via recurrent payments.

## Availability

All 2Checkout accounts.

## Generate quick payments reports

You can find the **Quick payments** tab in the **Accounting -> Direct payments** menu.

1. Use the **Quick payments search** section to configure the filters used in generating the report. You can filter the results by target affiliate, website or the payment date.
2. Once you have finished configuring your filters, click **Search**. The report is displayed below and it contains 10 results/page. You can extend the displayed results number to 20 results/page
3. To export the entire report as a CSV file you can use the **Export as CSV** button.

The report shows you the payment date, the target affiliate, the amount you paid to your affiliate, 2Checkout's commission and the payment status (**Succeeded** or **Failed**).

Related resources:

* <https://verifone.cloud/docs/2checkout/Documentation/myAccount/Products-and-subscriptions-listing-query-parameters>
* <https://verifone.cloud/docs/2checkout/Documentation/Subscription-Billing/03Subscriber-management-and-self-service>
* <https://verifone.cloud/docs/2checkout/Documentation/Subscription-Billing/01Subscription-Billing-Set-up/03Contracts>


---

# 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.2checkout.com/get-started/getting-started/finance-and-accounting/quick-payment-reports.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.