View transaction history

Use this guide to review transaction activity in Reah from one unified ledger, so your team can trace movement across rails and support reporting, auditing, and accounting workflows from a single source of truth.

Last updated 1 day ago

Summary

Use this guide to review transaction activity in Reah from one unified ledger, so your team can trace movement across rails and support reporting, auditing, and accounting workflows from a single source of truth.

What transaction history is used for

Transaction history helps businesses:

  • review completed transaction activity
  • inspect individual payment or transfer details
  • investigate unexpected or unclear activity
  • support reporting, reconciliation, and audit preparation

Why this is useful in Reah

Reah brings on-chain and off-chain transaction activity into one unified ledger, so teams can review financial activity in one place instead of piecing records together across separate systems.

What appears in Transaction History

Transaction History includes all activities involving the movement of funds across Reah.

This includes:

  • Transfers — sending and receiving assets
  • Conversions — asset swaps & bridges, on-ramp and off-ramp (conversion between fiat and crypto)
  • Wallet & banking activity — all transactions across wallets and bank accounts
  • Card activity — card payments, as well as deposits and withdrawals from card accounts
  • Treasury activity — deposits into and withdrawals from Treasury strategies
  • Gas Station activity — transactions related to gas station deposits

How to view transaction history in Reah

  1. Open the Transactions tab in the left-hand menu.
  2. Review the transaction history list or activity feed.
  3. Filter by date range, status, asset, rail, account, or transaction type when available.
  4. Open an individual transaction to inspect more detail.
  5. Export records separately if your team needs an offline file for reporting or reconciliation.

What to check in transaction history

When reviewing transaction history, check:

  • transaction dates and times
  • sent or received amounts
  • asset or currency type
  • transaction status
  • source and destination details
  • network, rail, or payment method where applicable
  • any references, notes, or fees shown in the transaction detail

Best practices

  • Use filters before reviewing large transaction volumes
  • Check transaction status first when something looks off
  • Export records when your team needs formal reporting or reconciliation support

What to do next

  • Check transaction status
  • Understand pending transactions
  • Troubleshoot failed transactions
  • Export transaction records