On this page
No Headings
Last updated: May 21, 2026
Provides an overarching snapshot of mobile app activity and overall mobile wallet usage.
Update frequency: Daily
Time Zone filter.
Provides a nuanced breakdown of transaction behavior, with a main focus on Transaction Amount.
Update Frequency: Hourly
Wallet Issuer, Date Range, Location, Tender Type, Store Code, Timezone, and Transaction Result.Purchase, Fuel, Void, Cash Access, or Refund).Success, Failure, Partial Success, Reversal Success, Reversal Failure, and Void).Wallet Issuer, Acceptance Partner, Location, or Tender Type.success and failure.Wallet Issuer, Acceptance Partner, Location, Tender Type, or Transaction Result.Time Zone filter (not shown in this sample).
Provides a nuanced breakdown of transaction behavior with a focus on Transaction Count.
Update Frequency: Hourly
Wallet Issuer, Date Range, Location, Tender Type, Store Code, Timezone, and Transaction Result.Success, Failure, Partial Success, Reversal Success, Reversal Failure, and Void).Wallet Issuer, Acceptance Partner, Location, or Tender Type.Success and Failure.Wallet Issuer, Acceptance Partner, Location, Tender Type, Transaction Result, or Failure Reason.Time Zone filter (not shown in figure).
Provides an analysis of the number of enrolled users in a mobile wallet.
Update frequency: Daily
Enrolled Only - the user has created an account on the customer portal, but does not have an associated device or a verified payment account in the wallet.Enrolled Partially - the user has a registered active device or a verified payment account in the wallet.Enrolled Fully - the user has a registered active device and a verified payment account in the wallet.Enrolled and Paid Ever - the user is fully enrolled (device + payment account) and has had a successful transaction since enrolling.Enrolled and Paid Recently - the user is fully enrolled (device + payment account) and has had a successful transaction in the last 30 daysWallet Issuer, Device Type, or Payment Account.Wallet Issuer, Date Range, Device Type, and whether or not the user has a payment account.Wallet Issuer, Device Type, and whether or not the user has a payment account.Time Zone filter.
Provides an analysis of the individual users who have made transactions.
Update Frequency: Hourly
Wallet Issuer, Date Range, Location, Store Code, Timezone, and Transaction Type.Wallet Issuer, Acceptance Partner, Acceptance Location, Device Type, Tender Type, Payment Status, Transaction Result, and Failure Reason.Wallet Issuer, Acceptance Partner, Payment Status, Transaction Result, or Failure Reason.Average Spend per Visit and Average Visitors per Week, which can be further filtered by Location, User Name, Wallet Issuer, Acceptance Partner, or Acceptance Location.Time Zone filter (not shown in this sample).
Provides merchants who implement the WLW Offers functionality with an analysis of the performance of their offer programs.
Update Frequency: Daily
Active, Redeemed, Expired, Cancelled, Redeem Pending, and Reversal Failed.Wallet Issuer, Network Name, Date Range, Offer Status, Store Code, and Offer Campaign.Mobile or External.Offer Status, Offer Campaign, Wallet Issuer, Advertising Network, Acceptance Partner, and Acceptance Location.Time Zone filter.
Provides fuel partners with a complete end-to-end picture of every fuel transaction, from preauthorization to payment capture.
Update Frequency: Daily
Wallet Issuer, Acceptance Partner, Location, Capture Status, Store Code, Timezone, or Tender Type.Wallet Issuer, Date Range, Location, Preauth Status, Tender Type, and Capture Result.Preauth Success – the preauth was successful.Preauth Reversal Success – the preauth was successfully reversed because the processor could not be reached.Preauth Failed – the processor declined the preauth.Preauth Reversal Failed – there was an attempt to reverse the preauth, but the processor could not be reached.Success – the preauth was successfully captured and payment was collected.Decline – the preauth resulted in a decline from the processor and payment was not collected.System Canceled – the preauth was unsuccessful due to a processor failure and the capture attempt was canceled by our platform.Full Reversal Failed – there was an attempt to reverse the capture event, but the processor could not be reached.Scan No Pay – the preauth was successful but tender information could not be collected and the payment was not processed.No Capture – the preauth was successful but there is no record of a capture attempt and payment was not collected.Time Zone filter (not shown in this sample).