The insights dashboard provides merchants with all the tools to deep dive into their payments data. With the use of cross-filters it’s possible to analyze volume, auth rate, and uncover both opportunities and issues.

​
Control

The top controller allows you to control the metric for which data is shown on the dashboard. All visible data will be filtered on the basis of this selection. Once selected, all date on the page will use this configured filter.

The insights controller

The metric selector lets you switch between volume, transactions, and auth rate.

  • Volume is calculated by accumulated transaction value for processed transactions.
  • Transactions are calculated as total count of processed transactions
  • Auth rate is calculated as the number of successfully authorized transactions, divided by the number of transactions sent to the PSP for processing that did not resulting in a failure.
    • auth_rate = num_authorized / num_processed
    • num_authorized = sum(status in ["authorization_succeeded", "capture_succeeded"])
    • num_processed = sum(status in ["authorization_succeeded", "capture_succeeded", "authorization_declined"]) - flow_decline
    • flow_declines = sum(error_code starts with flow_*)

The only transactions represented in this dashboard are those that were sent to a payment service and reached an authorization_succeeded, capture_succeeded or authorization_declined state. Transactions that were declined by Flow, resulted in a authorization_failed status, or are still in some pending status are not included as they either did not reach the service, or were rejected for technical reasons.

The currency selector is only available for the volume filter and switches between the currencies used in a time frame. Only currencies processed in the selected time range are shown.

The period selector allows you to change the period for which the data on the dashboard is shown. It’s currently only possible to show the data for today, the last 7 days, and the last 30 days. Once selected, the page will show data for the selected period as well as the previous period of the same length. For example, the last 7 days period will be compared against the previous 7 days before.

​
Rolling window

The period selector uses a rolling time window. For the daily and weekly window, the data is shown in hourly slots. For the 30 day period, the rolling window uses 24 hour slots. Slots are always shown up until the most recent hour. In other words, for a 30 day window, the most recent 24 hour slot ends at the most recent hour.

​
Line chart

The line chart provides an overview of the metrics over the given period, compared to the previous period.

Line chart

The data in the line chart is shown hourly for every completed hour and updated every hour. For the 24 hour and 7 day period each data point represents an hour. For the 30 days selection each period in the line chart represents a time range of 24 hours.

The chart displays the data with all the same filters applied from the controller. This means it will either show the volume, transaction count, or the auth rate. And it will only show transactions for the period and currency selected. The chart provides a delta with the previous period, comparing the current period with the previous fixed period, and providing a relative increase or decrease in the measured metric.

When filtering by the last 30 days, the data will be displayed in 24 hour slots while still using a rolling window. This means that the count for a day may change every hour as the 24 hour window changes over time.

​
Modules

The real power of our dashboard comes from the ability to cross-filter modules. Selecting one module will filter down the rest of the modules on the dashboard. This allows you to effectively drill down into your data and find opportunities, and potential issues.

For authorizations, we have divided the dashboard into three sections.

​
Requests

The request section gives insight into the request and response data.

  • Error codes: This module shows the Gr4vy standardized error_code values for decline payments. These error codes are mapped from your payment service’s response codes to a set of standardized Gr4vy error codes.
  • Methods: This module shows the method used for the transaction. To see the scheme used for card payments see the Schemes module in the Card details section..
  • Metadata: The key/value pair provided in the metadata field in the payment request. This module only shows the top 25 of metadata key:value pairs in descending order.
  • Country: The country code provided by the merchant in the payment request. If no country code is provided this will be counted towards the Unknown country code value.
  • Connector: The configured payment service that was used for routing the payment.
  • Flow rule applied: This module shows which flow rule was applied to route the transaction.
  • Currency: The currency the transaction was processed in.
  • Authorization: This module allows you to filter between successful and declined transactions.

​
Card Details

This section gives insight in the card details used in the authorizations. From BINs to issuers to card types.

  • Issuer name: The issuer of the card used in the transaction. This module only provides the top 25 issuers in descending order.
  • BIN: The BIN of the card that was used in the transaction. This module only provides the top 25 BINs in descending order.
  • Issuer country: The issuing country of the card used in the transaction.
  • Card type: The card type of the transaction, providing insight in credit, debit or prepaid.
  • Schemes: The card scheme that processed the transaction.

​
Recurring

This section gives insight in the data regarding recurring, card on-file, CIT and MIT transactions.

  • Transaction type: The transaction type refers to the payment_source of the transaction. Whether the transaction was e-commerce, card-on-file, moto, installment or recurring.
  • Initiator: This module provides insight in whether the transaction was a customer initiated transaction (CIT) or merchant initiated transaction (MIT).
  • Subsequent payment: This module shows whether a transaction was a subsequent payment.