Reports In-depth

The following table shows the start and expected completion times for Coordinated Universal Time (UTC).

The 3:45 PM sync time reconciles the previous day’s activities, and is useful for comparing the prior day’s activity with today’s.

The following time windows are applicable for US clients using the default network timing options.

The Network Detail/Day report provides information similar to the Balance — Overview/Day report. The Balance — Overview/Day report is at the day and program level; however; the Balance - Overview/Day report provides expanded columns to include network details. For example, instead of providing only the sig_purchases_net column, the Balance - Overview/Day report includes a column for every network and subnetwork of sig_purchases_net.

The Balance - Program Funding Balances/Prefunded — Day/Month report provides a daily or monthly aggregated view of a program’s funding account balance based on a prefunding (on authorization) model. Each day is encompassed by a starting balance, which matches the prior day’s ending balance, and daily activity for funds in and funds out.

For detailed information, see JIT Funding Reports.

This report does not represent a program’s entire account balance, but only the program’s funding account balance. For example, a non-JIT program could have a majority of funds in the cardholder account with minimal amount in the program’s funding account.

The Card Transactions - Authorizations (Detail/Day/Week/Month) report provides transaction-level and aggregated views of authorizations activity. These records are added as they occur and are updated when the Transaction Status shifts based on the lifespan of a transaction. For example, an initial transaction is listed with a Transaction Status of Pending Settlement. After a day or more it may be cleared and switch to a status of Successfully Completed. With that event, additional fields such as completion_token are populated.

Not all authorization activity is signature purchase attempts. Activities such as token activation requests are also included.

This report is linked to both the Loads reports and the Clearing report by a token. The transaction_token field in the authorizations report appears as the initiating_transaction_token field in each of those reports.

This report can be joined to the Core API Transaction Token report using the transaction_token field to get the transaction token, listed in webhooks as integer value such as alphanumeric hash. The transaction_token value is the unique value per row, with one row per transaction_token per program. When a transaction changes state, the same row is updated.

Settlements reports includes the following types:

The Card Transactions - Declines/Detail/Day/Week/Month) report has some overlap with Authorizations in that they both show declined activity (declines detail shows pin also and authorizations doesn’t). However, this one is more expansive for a decline analysis as it will show the reasoning behind why a transaction gets declined and the primary entity as to why it was declined.

The Card Transactions - Loads/Detail/Day/Week/Month) report shows cardholder loads, which are funds moved into a cardholder’s account.

The primary source of this activity are funds going from the program funding account into the user’s general purpose account. For most programs this is where JIT Loads, JIT Unloads, Partner Funds Loads, and Partner Funds Unloads are contained. These values all refer back to the balance reports. Some other loads that may show up in this report are ACH Loads and Direct Deposit activity.

To see program transfers, filter for transaction_type = transfer.program in Loads/Detail.

Amount to Send can be calculated from this report by summing the transaction_amount values for records with a transaction_element value in:

Direct Deposits typically have three records in the report:

These three records can be tied together by a shared initiating_transaction_token. Loads detail only reports balancesheet amount though so all Pending Direct Deposits show $0 instead of the pending amount.

The following activity leads to a cardholder load:

ACH reports include:

The Other Transactions - Bill Payments/Detail report provides transaction-level detail for bill payments.

The Other Transactions - Direct Deposit/Detail report shows transaction-level detail for direct deposits.

The Other Transactions - ATM/Detail/Day/Week/Month report includes four types of transactions relative to ATM transactions: ATM Withdrawal, Quasi Cash, Manual Cash, and Balance Inquiry. The atm_sub_network field supports billing ATM transactions that come through ATM sub networks.

This report includes both cleared and declined transactions. Cleared transactions use the same logic as amounts_day for cleared ATM withdrawal, quasi cash, manual cash, and balance inquiries. Declined ATM withdrawal, quasi cash, and manual cash follow the logic of a monthly atm_non_atm report that is heavily used by accounting.

The Credit - Account Adjustments report provides details on adjustments made to the credit accounts in a program, including the adjusted amount, reason, and date the adjustment was made. Key fields include original_ledger_entry_token, external_adjustment_id, and adjustment_detail_token.

The Credit - Account Adjustments Monthly report provides adjustments data for all the credit accounts for a month in a program. Key fields are account_token, total_amount, and month_key.

The Credit - Account Details report provides details on all of the credit accounts in a program. This report includes intra-monthly balance calculations attached to each account, including purchases, interest, fees, credits, and payments, which are updated whenever an activity occurs that might affect the ledger. Key fields are current_balance, available_credit, and credit_limit.

The Credit - Account Daily Balances report provides details on daily balances, including principal, interest, fees, and payment allocations.

The Credit - Account Cards report provides detailed information for the cards in a program, such as the current card state, product, and creation and end dates.

The Credit - Disputes report provides dispute details of all dispute activity for the credit accounts in a program.

The Credit - Disputes Monthly report provides dispute data by month for all credit accounts in a program. This report provides an aggregated sum of all disputes grouped by account and status (WON, LOST, or REVERSED). Active disputes are skipped. For example, if an account has three disputes, with two won and one lost, two records are returned—one record with the sum of all disputes won, and the other with the sum of all disputes lost.

The Credit - Journal Entries report provides details of all ledger entries for all credit accounts in a program, such as the status and amount.

The Credit - Payments report provides payment details for all the credit accounts in a program, such as payment method, interest, and fees.

The Credit - Rewards report provides a rewards detail for all the credit accounts in a program.

The Credit - Rewards Monthly report provides a sum of all credit account rewards for a given month grouped by account token.

The Credit - Statements report provides a statements summary for credit accounts. This report is an amalgamation of Credit’s Statement Summary, Statement Payment Info, and Statement Year-to-date. Each entry in this report encapsulates the data that is associated with an account for these three statements. Key fields include opening_balance, closing_balance, available_credit, and past_due_amount.

The Program Stats - Cards reports provides a Detail view and Card Counts — Day/Week/Month views.

The Program Stats - Users report provides a Detail view and User Counts — Day/Week/Month views.

Refresh rate: Incremental refresh (3x a day)
Endpoint: /v2/views/chargebacks/status & /detail+ Reporting location: Risk Monitoring - Chargebacks/Status/Detail

Refresh rate: Once a month refresh
Endpoint: /v2/views/platformresponse/month
Reporting location: System - Platform Response/Month

The Utilities - Core API Transaction Token/Lookup report is a pure lookup between the Core API transaction token and the transaction token as listed in many reports. Because the transaction token set in the Core API often is not the same transaction token as in the report, you can join this table as a lookup to match to your internal data logs.

The core_api_tranaction_token and core_api_initiating_transaction_token fields are available in several endpoints. For these reports, a lookup to this report is not required.

The Data Dictionary provides information on the data dictionary, which describes the data for each of the columns in reports.

The RiskControl Real-Time Decisioning - Authorizations report provides information on all the transaction authorizations processed by Real-Time Decisioning, including Transaction Token, Acting User Token, User Token, Card Token, Amount, Risk Score, Risk Level, Recommended Action, Rule Violation, and Tags.

The RiskControl Real-Time Decisioning - Transaction Count by Rules report provides information on the count of transactions per triggered rule for a program.