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

# Payments

The **Payments** page in the clerk sidebar shows every card payment collected for your court, with receipts and a CSV export. It is available to **clerks, court admins, and platform admins** -- judges and judicial staff don't have it.

## Scope Toggle

Two views, switched at the top of the page:

* **Clerk fees only** -- court-bound money only, net of refunds; Cott's e-filing and convenience fees are excluded. The summary card reads "Collected for Clerk of Court."
* **All charges** -- everything the filer's card was charged, court costs plus platform fees, net of refunds.

## The Transactions Table

One row per charge, deposit top-up, or refund: **Date**, **Case #**, **Suit**, **Type**, **Filer**, **Clerk** (the clerk who accepted the filing), **Card**, **Status**, the fee breakdown columns (**To Clerk**, **E-Filing**, **Conv. 3.05%**, **Total**), and a receipt download icon.

* Sort by clicking a column header; filter with the funnel icon or the search box.
* Failed rows are struck through -- no funds moved; hover to see the decline reason.
* Refunds show as negative amounts, netted out of the footer totals.

## Export CSV

**Export CSV** downloads the table (respecting active filters) as `payments-{court}-{date}.csv`, including the accepting clerk per row -- useful for daily or monthly reconciliation against your deposit account.

{% hint style="info" %}
For the court's monthly settlement view (gross deposits, refunds, chargebacks, net), platform administrators use the parish [Payment Statements](/admin-guide/payment-statements.md) page.
{% 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 by asking a question.

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

```
GET https://docs.cottfile.com/clerk-guide/payments.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.