Skip to main content
×

Payment Details Report

  • Updated

The Payment Details report provides a granular, row-level detail of an order processed through the platform. By aggregating order metadata, policy evaluations, shopping cart details, and custom fields into data tables, this report allows you to conduct deep-dive investigations into specific transactions, audit decisioning logic, and extract detailed row-level data for external analysis or compliance reporting.

Access and permissions

To access the report, sign in to Kount 360 and go to Analytics > Folders > Payments Fraud Reports > Payment Details. Users can view data corresponding to their assigned organizational hierarchy and role-based access permissions. Fraud analysts in child organizations are restricted to viewing data for their specific entity, while parent organization users can view aggregated portfolio metrics or select individual child organizations.

Use cases

Fraud analysts and payments teams can leverage this dashboard to monitor and respond to several scenarios:

  • Transaction auditing: Investigate individual orders to understand exactly why a specific decision was rendered by reviewing reason codes, Omniscores, and the assigned decisioning agent.

  • Customer dispute resolution: Access granular shopping cart items and custom fields associated with a specific transaction to quickly resolve customer escalations or chargeback inquiries.

  • Data extraction and reporting: Export raw, row-level payment details to integrate with internal business intelligence tools or for external compliance and reconciliation purposes.

  • Policy troubleshooting: Review the Payment Policy Details table to determine which specific policy sets triggered on a single order, aiding in the debugging of complex fraud strategies.

Access and permissions

To access the report, sign in to Kount 360 and go to Analytics > Folders > Payments Fraud Reports > Payment Details.

You can view data corresponding to their assigned organizational hierarchy and role-based access permissions. Fraud analysts in child organizations are restricted to viewing data for their specific entity, while parent organization users can view aggregated portfolio metrics or select individual child organizations.

Filters and parameters

You can refine the data using the following global filters:

  • Timezone: Adjusts the timezone of the report data (for example, UTC).

  • Event Timestamp: The default setting is two weeks including the current week.

Charts and descriptions

Refer to the following table for a list of charts and their descriptions:

Payment Details charts and descriptions table

Chart Name

Description

Payment Order Details

This table shows events by the Order ID. Fields with multiple values are in a JSON format (for example, Policies, Shopping Cart Items, and Custom Fields). Rows are not duplicated.

Payment Policy Details

This table extracts and flattens the Policy Name. Each Policy Name is in its own row, meaning if an Order has multiple Policies ran, the Order ID and other fields are duplicated per Policy.

Payment Shopping Cart Item Details

This table extracts and flattens the Shopping Cart Items. Each Shopping Cart Item is in its own row, meaning if an Order has multiple items in the Shopping Cart, the Order ID and other fields are duplicated per item.

Payment Custom Fields Details

This table extracts and flattens the Custom Fields. Each Custom Field for an Order is in its own row, meaning if an Order has multiple Custom Fields, the Order ID and other fields are duplicated per Custom Field.

Filters and parameters

You can refine the data using the following global filters:

  • Timezone: Adjusts the timezone of the report data (for example, UTC).

  • Event Timestamp: The default setting is two weeks including the current week.

Comments

0 comments

Article is closed for comments.

Can’t find what you’re looking for?
Submit a Ticket
Contact Us
+1.866.919.2167