Documentation

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.

Normalized SALE Transaction Fields

The fields below are the normalized sale transaction fields RivetMonitor ingests from payment processors

Field Description Example
processor_transaction_id Transaction identifier assigned by the payment processor. ch_example123
transaction_type Normalized transaction type. RivetMonitor currently imports sales for transaction analysis. SALE
transaction_status Normalized transaction outcome, such as successful, pending, declined, or failed. SUCCESSFUL
transaction_created_at Date and time the payment attempt was created at the processor. 2026-07-16T07:09:22Z
amount Nonnegative transaction amount in the currency's major unit. 125.000000
currency ISO 4217 currency code. USD
failure_code Processor failure or decline code, when provided for an unsuccessful transaction. card_declined
failure_message Processor failure or decline message, when provided. Card declined
description Processor-provided transaction description, when available. Order 10482
processor_company_account Top-level processor company account associated with the transaction, when available. ExampleCompany
processor_merchant_account Processor merchant account that handled the transaction, when available. ExampleMerchant_US
mcc Four-digit merchant category code applied to the transaction, when available. 5734
payment_method_type Normalized payment method used for the transaction. CARD
card_brand Normalized global card brand. VISA
card_network Card network that processed the transaction, which can differ from the global brand. VISA
card_funding Funding category reported for the card. CREDIT
card_issuer_country Two-character country code for the card issuer. US
card_bin First eight digits of the PAN, also known as the BIN or IIN, when available. 41484646
card_issuer Name of the card-issuing bank, when provided by the processor. Example Bank
card_present Whether the card was physically present for the transaction. false
card_entry_method Method used to read or enter the card, when reported by the processor. contactless_emv
network_token_used Whether a network token was used for the transaction, when known. true
acquirer Acquirer that processed the transaction. stripe

Normalized FEE Transaction Fields

The fields below are the normalized feefields RivetMonitor ingests from payment processors

Field Description Example
processor_fee_id Fee identifier assigned by the payment processor. fa_example123
fee_type Fee classification. INTERCHANGE
fee_plan_name Processor fee or interchange plan name, when available. CPS Retail 2
interchange_program_code Processor-provided interchange program code, when available. CPS_RETAIL_2
processor_fee_category Processor's source category for the fee. network_cost
fee_currency ISO 4217 currency code for the fee. USD
fee_amount Signed amount of the individual fee component. 4.875905
fee_variable_rate Variable fee rate expressed as a decimal fraction; for example, 0.0235 represents 2.35%. 0.0235000000
fee_fixed_rate Fixed per-item portion of the fee in the fee currency, when provided. 0.100000

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.

Top