What Data RivetMonitor Collects
RivetMonitor programmatically imports transaction data from your payment gateway to identify downgrade patterns, qualification issues, authorization outcomes, and card-level trends across your payment activity.
Data from each processor is normalized into Rivet's Unified Transaction (RUT) format as it is loaded. This lets RivetMonitor compare records consistently even when different processors use different export formats, field names, or reporting conventions.
Data Categories
- Transaction details: identifiers, timestamps, amounts, currency, transaction type, entry method, and merchant name.
- Processor responses: status, response text, AVS response codes, and human-readable response descriptions.
- Interchange and downgrade data: interchange rates, descriptions, non-qualified reasons, downgrade flags, downgrade reasons, warning flags, and warning reasons.
- Card attributes: BIN, brand, issuer, issuing country, card class, and debit or credit indicator.
Normalized Transaction Fields
The fields below are the normalized RUT fields RivetMonitor can ingest from payment processors
| Field | Description | Example |
|---|---|---|
customer_transaction_id | Unique customer-provided transaction identifier used to prevent duplicate imports. | 198697882 |
transaction_date | Date and time the transaction occurred | 2025-09-30T23:17:22.000Z |
transaction_merchant_name | Merchant name on the transaction record. | COREY EMLIN TRISTRUX |
transaction_amount | Transaction amount as a decimal value. | 1510.5000 |
transaction_ic_rate | Interchange rate applied to the transaction. | 0.030000 |
transaction_status | Whether the transaction was successful or failed. | SUCCESSFUL |
transaction_response_text | Response text from the processor or gateway. | Approval |
transaction_avs_resp | AVS response code or enum. | NOT_PROVIDED |
transaction_currency | ISO 4217 currency code. | USD |
transaction_type | Transaction type, such as sale, refund, or void. RivetMonitor imports sale transactions for downgrade analysis. | SALE |
transaction_entry_method | How the card data entered the payment flow. | KEYED_SWIPE |
transaction_nonqual_reason | Non-qualified pricing reason, when the processor provides one. | TRANSACTION CLEARED AS CORP / BUSINESS CARD |
transaction_ic_desc | Interchange description text. | VH35 : VI-US BUS TR5 LVL2 |
transaction_avs_resp_desc | Human-readable AVS response description. | Not Provided |
card_brand | Card brand code or name as provided by the processor. | VISA |
card_country | Card issuing country. | United States of America |
card_bin | First 6 digits of the PAN, also known as BIN or IIN. | 414846 |
card_issuer | Issuing bank name. | CELTIC BANK |
card_bin_type | BIN product type or card product name. | Visa Business Tier 1 (US) / Visa Business (non-US) |
card_issuer_regulated | Issuer regulation flag. | Unregulated |
card_class | Card class or program. | Business |
card_debit_credit | Debit or credit indicator, when available. | CREDIT |
Date And Time Format
Date and time values should be ISO 8601 with a timezone, such as 2026-01-09T19:58:35.294Z or 2026-01-09T19:58:35.294-05:00.
Data Retention
By default RivetMonitor retains aggregated reporting data for 24 months and raw imported transaction data for 2 months.
This can be configured for your organization, contact your Rivet account manager for details.