> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-us/payware-connect/settlements/corporate-portal-settlement-related-reports/settlement-summary-by-card.md).

# Settlement Summary by Card

This section includes steps on how to view the Settlement Summary by Card report in the PAYware Connect Corporate Portal for Resellers.

{% hint style="info" %}
**Use this when** you need to see a settlement summary broken out by card for a specific settlement date.
{% endhint %}

This report lists a settlement summary, by card, for a specified settlement date.

## View the report

{% stepper %}
{% step %}

### Find the report

Once signed in to the Corporate Portal, hover over **Reports**. A menu appears. Click **Settlement Summary by Card**.
{% endstep %}

{% step %}

### Select the settlement date

PAYware Connect displays the Settlement Summary By Card Report Parameter Selection window. Select the **Settlement Date** you want to view.
{% endstep %}

{% step %}

### View the report

Click **View** to display the report.
{% endstep %}
{% endstepper %}

<details>

<summary>Keywords</summary>

Also called: settlement summary by card report. Search terms: settlement summary, by card, corporate portal.

</details>


---

# 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.verifone.com/support-us/payware-connect/settlements/corporate-portal-settlement-related-reports/settlement-summary-by-card.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.