The Authorization Research & Downloads tool is your deep-dive interface for transaction-level analysis. It's designed to provide full transparency into individual authorization records, enabling detailed case research, ad hoc reporting, and audit validation.
Whether you're investigating a specific transaction, validating processor charges, or building a custom report, this tool gives you the controls and visibility needed.
On-Screen Notice
The dashboard displays the following banner at the top of the page:
Default view shows Authorizations. Use filters or saved views to access Verifications and Rejects.
Check your date range first. The Authorization Date filter defaults to the last 3 days. Widen it before drawing any conclusion about volume or before exporting.
What It Does
-
Displays raw, row-level authorization data
-
Includes comprehensive filters for narrowing to specific transactions
-
Offers 110+ fields across client, processor, MID, card data, and metadata
-
Allows for on-screen review or CSV download
-
Supports multi-transaction analysis for operational follow-up, dispute validation, or performance modeling
Filtering Capabilities
At the top of the tool, a full panel of filters allows you to precisely target the transactions you need:
|
Filter Name |
Function |
|---|---|
|
Acquirer (PSP) |
Filter to a specific payment service provider or processor |
|
Auth Response Category |
Select by response grouping (e.g., Approved, Declined, Rejected) |
|
Auth Type |
Narrow to a specific authorization type |
|
Authorization Amount |
Filter by a minimum and maximum authorization value |
|
Authorization Code |
Search by specific authorization code (exact match) |
|
Authorization Date |
Defaults to the last 3 days. Widen it before any volume analysis or export |
|
BIN (First 6) |
Enter first six digits of card number (BIN) to analyze issuer trends |
|
Card Funding Source |
Split by debit, credit, prepaid, and similar funding types |
|
Card Issuer Group |
Search transactions by card issuers |
|
Card Number |
Filter by card number pattern (masked, ends with) |
|
Issuer Region |
Narrow to issuers in a particular region, useful for separating domestic from cross-border approval behaviour |
|
Merchant Account |
Look up transactions by merchant account |
|
Merchant Order Number |
Search using exact or partial merchant order reference |
|
MID |
Filter by specific Merchant ID |
|
MID Name (Division) |
Select by merchant division name |
|
MID Rollup 2 (Harmonize Group) |
View grouped MIDs under a harmonized rollup |
|
MOP Name |
Refine by method of payment |
|
MOTO Indicator |
Isolate mail order and telephone order transactions, which is also how card-not-present volume is identified for several acquirers |
|
Network Response Code |
Search or group by network-specific response codes |
|
Presenter |
Filter by the presenting entity on the authorization |
|
Txn Category |
The default view shows Authorizations. Use this filter to reach Verifications and Rejects, which are otherwise not in your results |
|
Wallet Type |
Separate wallet-originated transactions such as Apple Pay or Google Pay from direct card entry |
Multiple filter combinations can be applied simultaneously to zero in on specific use cases.
Example Use Cases
|
Use Case |
How to Do It |
|---|---|
|
Find all declined Visa auths for a specific MID |
Set |
|
Audit all transactions above $1,000 from a certain card BIN |
Set |
|
Download all approvals from a specific PSP in February |
Set |
|
Review verification or reject traffic |
Set |
Downloading the Data
Once you've applied your filters:
-
Confirm your Authorization Date range, since three days is rarely what you want in an export
-
Click Download CSV at the top right of the filter panel
Downloads are limited to 1 million records. If you are near that ceiling, narrow by date range or MID and export in batches rather than assuming you received everything. Clear Filters, next to the download button, resets the panel.
CSV is the only export format offered here.
Best Practices
-
Use Authorization Code or Merchant Order Number to pin down a single transaction, and MID plus Authorization Date to scope a batch
-
Use BIN (First 6) and Card Issuer Group to isolate patterns from specific banks
-
Use Auth Response Category with Network Response Code together when investigating declines, since the category tells you what happened and the response code tells you why
-
Pair this with the Declines Dashboard to validate reject behavior in context