Skip to main content
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. The transactions included 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.

​
Control

The controller for the Authorizations tab has an extra option and allows you to filter all the data on auth rate.
  • 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_*)

​
Modules

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 our standardized error_code values for decline payments. These error codes are mapped from your payment service’s response codes to a set of standardized 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.
  • Payment service response codes: This module shows the response codes received from the payment services, corresponding to the raw_response_code transaction field.

​
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.
⌘I