Payment Analytics

The Payment Analytics page gives you a comprehensive view of your payment performance from checkout to final outcome. Use it to understand your payment funnel, identify where transactions fail, and find opportunities to improve your authorization rate.

Payment Funnel

The Payment Funnel visualizes the complete transaction flow from checkout through risk screening, 3D Secure authentication, and final outcome. Each stage shows both the count and the dollar volume, so you can see both the frequency and financial impact at every step.

The funnel has four stages:

• Checkout: Total checkout sessions initiated by customers, and how many lead to attempted payments.

• Risk Model: Transactions evaluated by fraud prevention services, typically offered by your payment provider or a 3rd party, including by Corgi Labs. Shows how many transactions were approved vs. blocked.

• 3DS: Transactions routed through 3D Secure authentication, performed by the card issuer. Shows three outcomes: No 3DS (not required), 3DS Passed, and 3DS Failed.

• Outcome: Final result of the payment: succeeded or declined by the issuer.

Core Payment Metrics

Two metrics show top-line payment performance:

• Payment Success Rate: The overall percentage of payment attempts that resulted in a successful charge. This metric accounts for all failure points, including fraud blocks, 3DS failures, and issuer declines. A trend comparison against the previous period is shown.

• Authorization Rate: The percentage of payment attempts that were authorized (approved) by the issuing bank, after passing through risk screening and 3DS. This isolates network-level acceptance from fraud blocks performed by your payment and fraud prevention providers.

The distinction matters for diagnosis. Payment Success Rate tells you whether customers are completing payment. Authorization Rate tells you specifically how the issuing bank is responding, independent of what your fraud tools did upstream.

Block, Decline & Abandonment Rates

Three rates show why payments do not succeed:

• Block Rate: Percentage of transactions blocked by your fraud rules or risk model before reaching the payment network.

• Decline Rate: Percentage of transactions declined by the card network or issuing bank.

• Abandonment Rate: Percentage of checkout sessions abandoned by the customer.

Each represents a different failure mode with a different corrective action. Blocks happen before the network (a merchant or fraud provider decision), declines happen at the issuer level, and abandonment is customer-initiated.

Block Reasons

This section breaks down why transactions were blocked during risk screening. A stacked bar chart shows monthly volumes by block source, so you can see which rules or signals are driving the most blocks over time.

3D Secure Authentication

This section examines 3DS challenge rates and authentication performance across four metrics:

• 3DS Rate: Percentage of transactions routed through 3D Secure.

• 3DS Success Rate: Percentage of 3DS authentications that were successful.

• Challenge Rate: Percentage of 3DS transactions that triggered an active challenge, as opposed to frictionless authentication.

• Challenge Success Rate: Percentage of 3DS challenges that were successful.

A monthly breakdown chart shows Successful Challenges, Successful Frictionless, and Failed Challenges over time. A summary table shows the count, share, and request volume for each outcome.

Decline Reasons Distribution

A stacked bar chart shows decline counts by reason category over time.

Use this to identify whether declines are driven by preventable issues (like expired cards) or systemic problems (like issuer-side fraud flags). The distinction shapes what action to take. Preventable issues can often be addressed through payment operations changes, while systemic issuer-side declines may require a different approach to authorization optimization.

Geographic Payment Distribution

A world map visualization shows payment volume by card-issuing country. Use it to understand the geographic distribution of your customers and identify regions with unusually high decline or fraud rates.

Deduplication Setting

Payment metrics can be viewed as deduplicated or raw:

• Deduplicated: Counts only the final outcome per payment, removing duplicate retries. Multiple attempts are treated as the same payment when they share:

  • The same invoice_id for subscription payments, or
  • The same Customer + close-in-time + same amount, or
  • The same card number + close-in-time + same amount

• Raw: Counts all payment attempts.

Tracking the same metrics across the same setting allows a fair evaluation of performance over time. Depending on your business model, a significant difference between deduplicated and raw metrics may indicate increased customer checkout friction.