Transaction Filters

Transaction Filters allow you to save frequently used filter combinations so you can quickly reapply them when analysing transaction data. Filters are always organised into folders and are shared with your team or Organisation - they are never private to a single user.

Types of Filters

There are three types of filters available:

  • Predefined filters – Provided by Apata. Ready-to-use filters that everyone can apply but no one can edit or delete.
  • Organisation filters – Saved at the Organisation level. Visible to users across all Financial Institutions in your organisation.
  • FI filters – Saved at your specific Financial Institution level. Only visible to users with access to that FI.
Filter TypeVisible To
PredefinedAll users
OrganisationUsers in any Financial Institution within the Organisation
FIOnly users with access to that specific Financial Institution

Saving a New Filter

  1. Apply the filters you want on the transactions page.
  2. Click Save Filter.
  1. Give your filter a clear name (e.g. low-risk-browser).
  2. Choose an existing folder or create a new one.
  1. Confirm to save.
📘

If you are working at the Organisation level, your filter will be saved as an Organisation filter. If you are working at the FI level, it will be saved as an FI filter. All users with access to that level will immediately see your new filter.


Applying a Saved Filter

  1. Click on Saved Filters in the transactions page.
  1. Browse or use the search box to find the filter you want.
  2. Click the filter name to apply it - the transaction list updates immediately.

You can also apply a filter directly via URL:

https://portal.apata.io/app/transactions-anatomy?filterId=FILTER_ID

Editing and Deleting Filters

Editing: You can update the name or criteria of filters that belong to your current level. The Update Filter button is disabled for Predefined Filters or filters from a different level.

Deleting: Select a filter in the side panel and choose delete. You can only delete filters at your current level.

Managing Folders:

  • Rename folders that belong to your current level
  • Delete a folder only if it is empty

Predefined Filters

Apata provides a collection of Predefined Filters that let you instantly view important transaction categories. All predefined filters apply to transactions from the last 24 hours.

Challenged
FilterDescription
Challenged TransactionsAll transactions where the cardholder was sent for a Challenge.
Exemptions

Transactions processed under specific SCA exemptions:

FilterDescription
Frictionless TransactionsCompleted without any challenge.
Acquirer ExemptionsGranted an Acquirer Exemption.
Data Share ExemptionsUsing the Data Share exemption.
Low Value Payment ExemptionsLow Value Payments that qualified.
Low Risk ExemptionsClassified as low risk via TRA.
Merchant Initiated ExemptionsMerchant-Initiated Transactions.
Non Payment ExemptionsNPA transactions exempted.
One Leg ExemptionsOne-Leg Transactions exempted.
Recurring ExemptionsSubsequent Recurring Payments.
Secure Corporate Payment ExemptionsSecure Corporate Payments.
Merchant Whitelisted ExemptionsMerchants on the cardholder's Whitelist.
Cancelled Transactions
FilterDescription
Cancelled Via Challenge PageCardholder cancelled from the challenge page.
Cancelled OOBCancelled via OOB authentication.
Timeout Transactions
FilterDescription
Timed outReached TIMEOUT waiting for authentication.
No Challenge Page SubmitCardholder did not return to proceed.
No OOB ConfirmationOOB callback was not received.
Merchant Aborted Transactions
FilterDescription
Merchant AbortedMerchant chose to abort the challenge.
Rejected Transactions
FilterDescription
Rejected Because of Risk RulesREJECTED due to low confidence in risk assessment.
Rejected Card DisabledREJECTED because card was disabled.
Failed Transactions
FilterDescription
Failed Attempts ExceededMaximum challenge attempts reached.
Rejected Retries ExceededToo many retry attempts.
Unsupported ChannelDevice Channel not supported.
Missing Required DetailsRequired info missing (phone, email).
Fallback ExceededAuthentication fallbacks exceeded.
BIN Attack
FilterDescription
Suspected BIN AttackREJECTED due to suspected BIN Attack.
Issuer Errored Transactions
FilterDescription
Decoupled Authentication Not SupportedIssuer doesn't support Decoupled Authentication.
SMS Couldn't be sentUnable to send SMS OTP.
Email Couldn't be sentUnable to send Email OTP.
Card Not EnrolledCard not enrolled for 3DS.
Issuer Connectivity ErrorFailed to connect to issuer.
Issuer Card Link ErrorError calling Card Link API.
Misconfigured ErrorInvalid or missing configuration.
Card Doesn't Exist ErrorPAN does not exist.
Scheme Errored Transactions
FilterDescription
Directory Server ErrorError from the card scheme's DS.
Merchant Errored Transactions
FilterDescription
Validation ErrorMerchant data failed validation.
Merchant App ErrorError from merchant's application.

Tips

  • Use clear, descriptive names for filters and folders so your team can easily find them.
  • Group related filters in the same folder for better organisation.
  • Start with Predefined Filters – they cover most common use cases.