Skip to main content

Payment Summary Report

The Payment Summary Report aggregates transaction outcomes across your business and splits them into two payment buckets — first-charge (FC) and recurring — alongside refund, chargeback, gross and net revenue metrics.

Use it to monitor approval rates, track refunds and chargebacks, and compare gateway, product, or campaign performance.

Open the report

In the Odus Dashboard, navigate to Insights → Payments. The page shows a summary chart of revenue, refunds, and chargebacks, with a detailed breakdown table below.

Date range and timezone

The date range selector filters payments by their createdAt timestamp. Switch between UTC and your merchant timezone to align daily boundaries with your business hours. The merchant timezone is configured in Settings → Merchant Configuration; if unset, the report falls back to UTC.

Unlike the Customer Value Report, every payment is evaluated independently — there is no cohort anchoring. A payment is included whenever its creation time falls inside the window.

Grouping

Use the Group by tabs to organize rows by product, currency, calendar day, gateway profile, UTM source, or UTM campaign. Switching grouping updates the chart and table immediately.

What counts as a payment

The report excludes payments with display status unattempted or cancelled. Every other status — succeeded, reversed, partially_reversed, uncaptured, chargeback, failed, and incomplete — is eligible to appear in at least one metric below.

Each payment is classified as either first-charge (FC) or recurring based on its offSessionType:

  • Recurring — payments generated by the subscription billing engine to renew an active subscription (offSessionType = recurring).
  • First-charge (FC) — every other payment. This includes on-session checkout payments and unscheduled merchant-initiated charges. The "FC" label is a bucket name for "non-recurring" — it does not mean the customer's first-ever payment.
note

"FC" in this report has a different meaning than in the Customer Value Report. There, FC strictly means a customer's lifetime first charge. Here, it is shorthand for any non-subscription-renewal payment, regardless of whether the customer has paid before.

Both buckets are reported side-by-side so you can compare new payment activity against subscription renewal performance.

Metrics

First-charge metrics

MetricDefinition
FC Payments CountAll non-recurring payment attempts.
FC Successful CountFC payments with status succeeded, reversed, partially_reversed, uncaptured, or chargeback.
FC Successful ItemsTotal line items across all successful FC payments (a multi-item cart contributes one row per line item).
FC Incomplete CountFC payments that started but never completed (status incomplete).
FC Failed CountFC payments that were declined (status failed).
FC RevenueGross revenue from successful FC payments.
FC Approval RateFC Approved / (FC Approved + FC Failed) × 100, where approved excludes chargebacks.

Recurring metrics

MetricDefinition
Recurring Payments CountAll recurring (subscription) payment attempts.
Recurring Successful CountRecurring payments with status succeeded, reversed, partially_reversed, uncaptured, or chargeback.
Recurring Successful ItemsTotal line items across all successful recurring payments.
Recurring Declined CountRecurring payments declined by the gateway (status failed).
Recurring RevenueGross revenue from successful recurring payments.
Recurring Approval RateRecurring Successful / (All Recurring with a terminal outcome) × 100; chargebacks are included in both values.

Refunds, chargebacks, and totals

MetricDefinition
Refunded Payments CountPayments with status reversed or partially_reversed.
Refund AmountTotal refunded amount (full and partial).
Refund PercentageRefund Amount / Gross Successful Revenue × 100.
Chargebacks CountPayments with status chargeback.
Chargeback AmountTotal amount of chargebacked payments.
Chargeback PercentageChargeback Amount / Gross Successful Revenue × 100.
Total Gross RevenueAll successful revenue across FC and recurring, before deductions.
Total Net RevenueTotal Gross Revenue − Refund Amount − Chargeback Amount.

The Total row aggregates each metric across all groups.

All monetary metrics are converted to your display currency (set in Settings → Merchant Configuration) using the exchange rate effective at the time of each payment, so historical totals remain stable.

Multi-item carts

When grouped by Product, a payment whose cart contains multiple line items is split across rows proportionally to each line item's share of the payment amount. Counts use a distinct-payment formula so a multi-item cart still counts as one payment. Other groupings assign each payment to exactly one row.

Example

Say your store processed the following six payments on 2026-06-01, all in your display currency:

PaymentTypeAmountOutcome
#1Checkout$50Succeeded
#2Checkout$50Failed (declined)
#3Checkout$80Succeeded
#4Checkout$80Refunded ($80)
#5Rebill$30Succeeded
#6Rebill$30Failed (declined)

Grouped by Day, the report row for 2026-06-01 looks like this:

FC CountFC SuccessfulFC FailedFC RevenueFC ApprovalRecurring CountRecurring SuccessfulRecurring RevenueRecurring ApprovalRefund AmountTotal GrossTotal Net
431$21075%21$3050%$80$240$160

How each number is derived:

  • FC Count = 4 — payments #1–#4 are all non-recurring (checkout).
  • FC Successful = 3 — #1, #3, #4 (a refunded payment was originally successful).
  • FC Revenue = $210 — gross of the three successful FC payments ($50 + $80 + $80), before subtracting refunds.
  • FC Approval = 75%3 approved / (3 approved + 1 failed) × 100.
  • Recurring Successful = 1 and Approval = 50% — one of the two rebills (#5, #6) succeeded.
  • Refund Amount = $80 — payment #4 was fully refunded.
  • Total Gross = $240$210 FC + $30 recurring.
  • Total Net = $160$240 − $80 refund − $0 chargebacks.

Export to CSV

Click Export CSV in the top-right of the table to download the current view. The file contains one row per group plus a Total row, with monetary values in your display currency. The selected date range is included in the filename.

API access

The same data is available via GET /reports/payment-summary. The endpoint supports all grouping options, metric selection via measures, date filters, and status exclusions documented in the API reference.

Example

GET /reports/payment-summary?groupBy=product.name&createdAt[gte]=2026-01-01T00:00:00Z&createdAt[lte]=2026-01-31T23:59:59Z&displayStatus[nin]=unattempted,cancelled

The response contains a data array (one entry per group) and a total object with the aggregate across all groups.