Analytics & Reporting

Slicker Analytics gives you a payment and recovery workbench for understanding why revenue is lost, where retries are working, and which customer or issuer segments need attention. Start with Ask: it is the fastest way to turn a business question into an answer, a report, or a focused follow-up investigation. Open Analytics from app.slickerhq.com/analytics.

​

Start with Ask

Use the Ask tab to ask natural-language questions about your payment and recovery data. The analytics assistant can answer directly, generate a report, and help you decide which segments are worth investigating next. Good starting questions include:

​

Save and Schedule Reports

When Ask produces a report, you can keep it as a reusable artifact instead of rebuilding the same analysis each time. Reports can be:

• Saved for later review.
• Marked private or shared with your organization.
• Reopened from the Reports tab.
• Scheduled so recurring report runs email recipients when they finish.

Use reports for recurring reviews such as weekly recovery performance, issuer regressions, 3DS drop-off, or payment-method trends.

​

Use Dashboards for Follow-Up

The dashboard tabs are supporting lenses for deeper investigation. They are useful when you already know which part of the payment or recovery funnel you want to inspect, or when Ask points you toward a specific segment. These views will continue to evolve as Slicker adds new analytics surfaces, but the main investigation areas are:

​

Filters and Time Controls

Use the date range picker to set the reporting window. Trend charts can be grouped daily, weekly, or monthly. Use filters to narrow the analysis to a specific slice of your business, such as:

• Countries and currencies.
• Payment methods and card brands.
• Error codes and normalized Slicker error types.
• Gateway or payment processor.
• Business entities, plans, or billing cycles when available.

Filtered views are useful when a headline metric looks stable but one segment is degrading.

​

Invoices

Use Invoices for invoice-level collection and recovery performance. An invoice is counted once, even if it has multiple payment attempts. Common questions:

• What percentage of invoices are paid on the first attempt?
• How much collection improves after recovery activity?
• Which error codes, countries, card brands, payment methods, or billing cycles drive failed invoices?
• Which segments recover well, and which segments turn into invoice churn?

The overview compares first-attempt outcomes with final invoice outcomes, so you can see the recovery uplift between the initial payment attempt and the eventual result.

​

Transactions

Use Transactions for authorization-level analysis. A transaction is one authorization attempt, so retries on the same invoice appear as separate rows. Transactions helps you inspect:

• Authorization rate and succeeded or failed volume over time.
• Gateway performance across payment processors.
• Decline reasons by normalized Slicker error type, provider error code, and scheme error code.
• Issuer country, card brand, card product, and payment method behavior.
• Customer-initiated, merchant-initiated, and MOTO transaction performance.
• Issuer-level patterns that may indicate routing, 3DS, or processor issues.

This tab is best for diagnosing payment acceptance problems before they become invoice recovery problems.

​

Failure Analysis

Use Failure Analysis to study invoices that had at least one failed payment attempt and entered recovery. Recovery status means: Key views include:

• Outcomes: How the failed-invoice cohort split between recovered, in recovery, and failed recovery.
• First Failure: The first failed transaction that pushed each invoice into recovery.
• Subsequent Failures: Retry attempts that also failed after the initial failure.
• Error Code: Normalized error types, provider codes, and scheme codes within the failed cohort.
• Issuer: Bank-level, country-level, and card-brand patterns inside the failed cohort.

Use this tab when you need to understand why some failed invoices recover and others do not.

​

Recovery

Use Recovery to measure recovery effectiveness and efficiency. The recovery views show:

• Recovered invoices and recovered amount.
• Recovery method, such as Slicker retries, recovery emails, or other recovery paths.
• Average time from first failure to successful recovery.
• Number of retries needed before recovery.
• Retry success rate and retry cost ratio.
• Slicker’s share of recovery activity compared with other retry sources.

This tab is useful for monitoring whether recovery is improving, slowing down, or becoming more expensive in retry attempts.

​

3D Secure

Use 3DS to understand authentication performance for card payments that enter a 3D Secure flow. The 3DS views cover:

• Enrollment volume, challenge rate, authentication success, and liability shift.
• Funnel drop-off from enrollment to challenge completion.
• Abandonment versus issuer challenge failure.
• EMVCo cancel and reason-code breakdowns.
• Performance by card brand, currency, device type, gateway, issuer, issuer country, and customer.

Use this tab when authentication required, challenge abandonment, or issuer rejection is affecting payment success.

​

Dashboard and Recovery Pages

The main Dashboard is still the best place for a quick executive overview of subscription health, payment health, churn, and recovered revenue. The Revenue Recovery page provides operational visibility into past and scheduled recovery attempts. Use Analytics when you need deeper investigation, segment comparisons, or reusable reporting.

​

Recommended Workflows

​

Related Docs

• Recovery Strategies
• Emails
• Multi Gateway Routing
• 3D Secure Authentication