Skip to main content
Filters in Insights

​
Applying Filters

1

Apply Date Range filter

Click the drop-down menu in the top-right corner of the dashboard.
2

Apply other filters

Click Add Filter.
3

Select filter parameters

Click a filter in the drop-down menu, select your preferred filter parameters, then click Apply Filters.
4

Add additional filters

Click More Filters, then repeat the previous steps to select a filter and the desired filter parameters.
If you’ve created custom MID hierarchies within your Pagos Organization, click the dropdown beneath your company name in the top-left corner of the Pagos Service panel to access a list of your hierarchy categories and subcategories. Click an option to filter the entire service panel to only show data for that business segment.

​
Filter Options

Depending on the page or section of Insights you’re in, you may see any of the following filter options:
Set a date range, along with a time interval to group the data by (hour, day, week, month, quarter, or year). Click Custom date until now, then select a start date to view data between that date and today; click Custom dates to choose a start and end date for your data.
  • Hourly data is only available for date ranges of up to seven days. Larger date ranges default to a daily grouping.
  • Daily data is only available for date ranges of up to 365 days. Larger date ranges default to a weekly grouping.
View data for transactions processed through the selected processor.
View data for transactions processed through the selected data connection.
View data for transactions processed through the selected merchant account ID. If you’ve assigned aliases to your Merchant Account IDs, those alias names will appear in the filter menu.
View data for transactions associated with the selected Merchant Category Code (Chase only).
View data for transactions made using payment cards from the selected card brands.
View data for transactions made with the selected payment card types (e.g. credit, debit, prepaid).
View data for transactions made with the selected prepaid card type (Reloadable, Non Reloadable, Not Applicable, or No Value Provided).
View data for transactions made with the selected card product.
View data for transactions made with the selected card product category (e.g. Business, Consumer, Healthcare, etc.).
View data for transactions made with the selected payment methods (e.g. amazon_pay, android_pay, apple_pay, card, google_pay, PayPal wallet, sepa, klarna, and ideal).
View data for the selected transaction types, identified by their use of stored payment credentials (e.g. one-time, recurring, installment).
View data for transactions made with customer primary account numbers (PANs) or network tokens.
View data for transactions with the selected status at the time indicated in the Date Range filter.
View data for transactions with the selected issuer response codes (e.g. do_not_honor, expired_card, decline_gateway, etc.).
View data for transactions whose total value was greater than, less than, or between the indicated amount(s) in USD; for transactions processed in other currencies, view data for transactions whose total value converts to the filtered USD amount.If applied to a chart demonstrating chargeback data, this filter applies to the size of the original transaction. Use the Chargeback Size filter to filter for specific chargeback values.
Remove duplicate transaction data (e.g. retries) from your visualizations. At this time, the retry deduplication filter doesn’t apply to duplicate retries processed through PayPal, dLocal, or Klarna.If you imported historical payments data into your Pagos account at signup, the retry deduplication filter may not apply to your historical data. Some processors don’t provide all the necessary details (e.g. BIN, last four digits, or expiration date) with historical data imports to meet the retry filter’s logic.
View data for transactions made using payment cards issued by the selected issuing banks.
View data for transactions made with cards issued in the selected regions.
View data for transactions made with cards issued in the selected countries.
View data for transactions made with Durbin-regulated cards or those that are exempt from Durbin. Learn more about the Durbin Amendment.
The fintech, neobank, BNPL, or wallet card program a card’s BIN belongs to (e.g. Chime, Cash App, Nubank), matched on the most specific known BIN prefix (8 digits where available, else 6). Available only in Charts.
The kind of fintech card program a card’s BIN belongs to (e.g. neobank, BNPL, prepaid, earned-wage access, crypto). Available only in Charts.
View data for transactions made by customers located in the selected regions.
View data for transactions made by customers located in the selected countries.
View data for transactions processed in the selected presentment currencies.
View data for transaction events of the selected settlement type.
View data for transaction events settled in the selected currency.
View data for transactions made with payment cards with the selected bank identifier numbers (BINs).
View data for transactions with the selected CVV response codes.
View data for transactions with the selected AVS line codes.
View data for transactions with the selected AVS post codes.
View data for disputed transactions resolved by Visa as Rapid Dispute Resolution. Transactions from any other card brand will be categorized as No Value Provided.
View data only for disputed transactions with the selected chargeback status code.
View data only for disputed transactions with the selected chargeback reason code.
View data for chargebacks whose total value was greater than, less than, or between the indicated amount(s) in USD; for chargebacks made in other currencies, view data for chargebacks whose total value converts to the filtered USD amount.
View data only for transactions where the customer’s payment card information was captured in the selected manner. See POS Entry Mode Codes for all possible values.
View data for Adyen transactions tagged with specific retry flags (Adyen retries some failed transaction attempts multiple times based on their own internal logic; when we pull your transaction data from Adyen, we only ingest the final attempt of a retried Adyen transaction, tagging it with a custom retry flag indicating the total number of times Adyen attempted the transaction).
View data for transactions the processor collected device data for or did not. At this time, this filter only applies to transactions processed through Braintree; transactions processed through other processors will be categorized under No Value Provided.
View data for transactions tagged with specific soft descriptors; if you’re unsure what soft descriptors you currently use, check out the Soft Descriptors tab in the Custom Data section of your Pagos account.
View data for transactions tagged with specific metadata. Click Metadata Name to select the metadata field, enter the metadata value, then click Add; if you’re unsure what metadata values you currently use, check out the Metadata tab in the Custom Data section of your Pagos account.
View cost data associated with specific fee types.
View cost data associated with specific fee categories.
View cost data associated with specific fee subcategories.
Use the text field to enter a specific raw fee name as it appears in your processor data. The field uses contains logic, meaning we’ll filter for all raw fee names containing the text you enter. Apply the filter, then export your Aggregated Data; the Fee Descriptions column identifies the exact raw fee names you filtered for.
If you’ve worked with your Pagos Account Manager to build out custom dimensions, you’ll see the names of your custom dimension(s) in the drop-down menu. Click the filter option, then type the exact parameter value you want to view data for, then hit Enter.
Keep in mind:
  • You can only select one parameter from the custom dimension to filter your data by
  • For a full list of the parameter options available for your custom dimension(s), navigate to Charts, create a chart using the custom dimension, and copy the parameter from the chart’s legend.