Skip to main content
Beta Feature: Retry Performance is currently in a closed Beta. Reach out to your Pagos Account Manager to request access.
Retry Performance Page in Pagos Insights.
To access this page, click Retries in the main navigation of your Pagos Service Panel. Here, you can analyze how often you retry failed transactions and how successful your overall retry strategy is. Retry Performance is broken into three sections: Use the Date Range filter to select the time period for all sections of this page.
How the Date Range filter works:This page includes all unique transactions whose final attempt falls within the selected period, even if earlier attempts in that transaction’s retry sequence occurred before the chosen dates.If your selected date range includes today (e.g. Last 7 days), we treat the latest attempt on record as the final attempt, since future retries haven’t occurred yet. If you’re viewing a completed historical period (e.g. January 1-31, 2026), a transaction is only included if no further attempts were made after the period closes.

​
Retry Statistics

At the top of the page, you’ll find the following statistics around your retry strategy:
  • Unique Transactions - Your total transaction count, deduped to exclude identical transaction retries, for which the final attempt occurred in the selected time period
  • Transactions Retried - The total number of unique transactions you retried at least once after the initial failed transaction attempt
  • Recovered - The total number of unique transactions that eventually succeeded after at least one retry attempt
  • Retry Success Rate - The percentage of all retried transactions that eventually succeeded after at least one retry attempt
  • Avg Attempts per Success - The average number of retry attempts required before a failed transaction eventually succeeds

​
Retry Graph

Use the Include Initial Attempt toggle to determine what data appears in the main graph:
This graph demonstrates the percentage of retried transactions recovered with each retry attempt. Each bar uses the Transactions Retried value from the Retry Statistics section as the denominator, and the bars add up to equal your Retry Success Rate.
This graph demonstrates the percentage of total unique transactions approved with each attempt in the selected time period, starting with the initial transaction. Each bar uses the Unique Transactions value from the Retry Statistics section as the denominator, so the bars add up to equal your deduped approval rate.
By default, the graphs include bars for Retry 1, Retry 2, and Retry 3, and aggregate all further attempts into one bar (Retry 4+). Click the Expand All Attempts toggle to show data for every individual attempt beyond the fourth retry. In either graph, click a tab in the top-right corner to choose how each bar is broken down:
  • Processor
  • Card Brand
  • Card Type
To create these graphs, we look at the attributes associated with the final, successful transaction attempt. This helps you identify which transaction parameters are most likely to result in approval.

​
Retry Success Rate

This table breaks down your retry success rate by different attributes of your initial transaction attempts. Use this data to identify how likely certain transactions are to eventually succeed or which transactions are worth retrying.
This table doesn’t take into account changes made to your transaction routing or the customer’s payment method for subsequent transaction retry attempts.
Use the drop-down menu in the top-right corner of the table to determine which dimensions we group your data by. The options include:
  • Decline Code - The decline code your processor assigned to the initial transaction attempt
  • Card Type
  • Card Brand
  • Mastercard Network Advice
  • Issuing Country
  • Issuing Bank (Top 25)
  • BIN (Top 25)
  • Processor
Each row in the table includes the unique transaction count, recovered transaction count, average attempts per recovered transaction, and retry success rate for each transaction attribute. Click Export to download the displayed data as a CSV.