Transactions
Decode transaction lifecycle language privately; Community clarifies glossary only.
Individual (mock)
Individual · activity stream (mock)
Sample activity label 1
Status: illustrative • Settlement mock
Sample activity label 2
Status: illustrative • Settlement mock
Sample activity label 3
Status: illustrative • Settlement mock
Sample activity label 4
Status: illustrative • Settlement mock
Illustrative mock • not signed-in data • not a real screenshot
- List rows imitate transaction density without merchant fingerprints or amounts.
- Drill-down details remain inside authenticated histories.
Overview
Transaction feeds translate settlement, risk queues, merchant descriptors, and card activity into chronological stories. Understand the glossary here; authoritative ordering and reversal reasons remain visible only inside authenticated history exports.
Lifecycle vocabulary
Authorized
A merchant or ACH originator secured permission to debit/credit—you may still see pending overlays.
Pending / processing
Funds or messages are riding batch windows or risk checks—not every pending row fails.
Posted
The leg booked to your ledger for that statement period; downstream adjustments may still happen privately.
Reversed / returned
Partners recalled value—timing depends on ACH return windows or card schemes; Support cites account-specific codes.
Statuses you can ask peers about safely
| Status | What it usually means |
|---|---|
| Pending hold | Common for rentals, hospitality, or large first-time recipients—mention category, never auth codes. |
| Review | Human or AML queues; cannot be debated in public forums—describe wait buckets only. |
| Duplicate sensation | Split merchant descriptors mimic doubles; Statements + Support validate definitively. |
Constructive Community questions
- Quote the generic label (“Card auth hold”) instead of pasting alphanumeric trace IDs.
- Reference duration as “hours vs days” buckets rather than timestamps that fingerprint you.
- If POS chatter matters, skim Cards concurrently—interaction effects are common.
Analogies peers use
Authorization vs capture
Hotels and gas pumps often authorize more than they capture—helps explain disappearing pending rows.
"Double charge" feelings
Single merchants may ledger an auth plus final capture; diagnosing specifics requires authenticated views.