> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/components/component-library/self-service-components/component-payment-history-table.md).

# Component: Payment History Table

## Overview

The **Payment History** component allows customers to view their historical payments in a self-service Finance Portal. This improves transparency and reduces support requests by letting users check payment dates, statuses, amounts, and methods directly, without contacting sales or account managers.

This component is designed for B2B SaaS businesses and is part of the **Self-service / Manage My Account** section.

Please note, if a payment method used for a past payment has been deleted, the column will display as empty.

{% embed url="<https://69c2cf3a42a094f3cd354b8d-hbwumtssfk.chromatic.com/?path=/story/shop-components-self-service-payment-history--example&full=1&shortcuts=false&singleStory=true&embed=true>" %}

## Props

| Prop                                                                  | Type   | Default                                              | Purpose                    |
| --------------------------------------------------------------------- | ------ | ---------------------------------------------------- | -------------------------- |
| Label for the date header                                             | String | Date                                                 | Column label               |
| Label for the status column                                           | String | Status                                               | Column label               |
| Label for the amount column                                           | String | Amount                                               | Column label               |
| Label for the payment method column                                   | String | Payment Method                                       | Column label               |
| Label for the results per page                                        | String | Results per page                                     | Text label                 |
| Message displayed if no payments are found                            | String | There are no payments associated with your account.  | Text label for no payments |
| Message displayed if there is an error retrieving the payment history | String | There was a problem retrieving your payment history. | Text label for error       |


---

# 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.limio.com/components/component-library/self-service-components/component-payment-history-table.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.