## How it works

Payment Performance helps compare transaction outcomes and processing behavior. A successful volume metric and a successful transaction count answer different questions.

## Implementation

Choose the scope and period, then inspect successful, failed, declined and pending outcomes. Compare processor and method breakdowns with the same filters. Investigate error reasons and individual attempts from transaction details. Refund volume should not be mistaken for a decline or lost checkout. Test payments and configured analytics exclusions affect the reported population.

## In this area

- Outcomes
- Cards that need explaining

## Controls and values

| Control | Values and related labels |
| --- | --- |
| **Successful** | `Succeeded`, `Partially captured` |
| **Open** | `Processing`, `Awaiting payment`, `Customer action`, `Merchant action`, `Awaiting confirmation`, `Awaiting capture` |
| **Failed** | `Failed` |
| **Void** | `Cancelled`, `Expired` |
| **Successful volume** | `Total` |
| **Payment trend** | `Bucket` |
| **Volume by processor** | `Direct` |
| **Volume by payment method** | `All processors` |

## Related guides

- [Analytics](/docs/dashboard/analytics/)
- [Analytics exclusions](/docs/dashboard/settings/analytics-exclusions/)