> ## Documentation Index
> Fetch the complete documentation index at: https://docs.whop.com/llms.txt
> Use this file to discover all available pages before exploring further.

# ActivityElement

> Lists an account's ledger activity — every movement of money in or out — with a type and date-range filter the viewer can work with directly. Needs an `accessToken`. Rows are click targets that emit `activitySelected` instead of navigating — a host wires up its own routing and detail views. A host driving its own date-range picker (a chart brush selection, say) can call `setDateRange` to set the filter, and should listen for `dateRangeChanged` to know when the viewer overrides it directly.

<Info>**Upcoming** — generated from the latest merged element source; documents unreleased development. Use the channel picker at the top of the sidebar for the docs of a published release.</Info>

*In development — not yet part of a stable release.*

Belongs to the [`Wallet`](/elements/upcoming/wallet/overview) group. Render `<ActivityElement />` inside it (React), or call `wallet.create('activity', { … })` on the handle (vanilla) — consumer props and `on<Event>` callbacks both go in the create options / JSX props.

## Preview

A live, interactive demo of this element with sample data:

<div data-whop-demo-shell style={{ position: "relative", minHeight: "320px", transition: "min-height 200ms ease" }}>
  <div data-whop-demo-skeleton style={{ position: "absolute", inset: "0", borderRadius: "12px", background: "rgba(140, 140, 140, 0.12)", pointerEvents: "none", transition: "opacity 200ms ease" }} />

  <div data-whop-demo-native="element:wallet/activity" data-whop-elements-version="" style={{ position: "relative" }} />
</div>

## Usage

<div data-whop-usage="wallet/activity">
  <CodeGroup>
    ```tsx React theme={null}
    import { WhopElements, Wallet, ActivityElement } from "@whop/elements-react";
    import { loadWhop } from "@whop/elements";

    function Example() {
      return (
        <WhopElements elements={loadWhop()}>
          <Wallet /* options */>
            <ActivityElement onActivitySelected={(payload) => console.log("activitySelected", payload)} onDateRangeChanged={(payload) => console.log("dateRangeChanged", payload)} />
          </Wallet>
        </WhopElements>
      );
    }
    ```

    ```html Vanilla theme={null}
    <script src="https://js.whop.cloud/elements/amber/elements.js" data-whop-elements></script>
    <script type="module">
      const wallet = window.WhopElements().wallet.create({ /* options */ });
      wallet.create('activity', {
        onActivitySelected: (payload) => console.log("activitySelected", payload),
        onDateRangeChanged: (payload) => console.log("dateRangeChanged", payload)
      }).mount('#wallet-activity');
    </script>
    ```
  </CodeGroup>
</div>

## Props

<ResponseField name="accessToken" type="string">
  A scoped token for the privileged read — needs `company:balance:read`. Mint it on your server with `POST /v1/access_tokens`. Omitted, the read carries the viewer's own session, which only answers same-origin.
</ResponseField>

<ResponseField name="canOpenCardTransactionDetails" type="boolean">
  Off, card-transaction rows render as inert (no click, no hover) instead of firing `activitySelected` — for a host that knows the viewer lacks permission to see those details. Defaults to `true`.
</ResponseField>

## Events

Pass a callback in the create options (or React prop) to receive these.

### `onActivitySelected`

A row was clicked. Open your own details view or route for it — the element never navigates.

**Signature:** `((payload: { activity: LedgerActivity; }) => void)`

### `onDateRangeChanged`

The viewer changed the date filter directly through the filter row — not via `setDateRange`. Clear any host-side range selection (like a chart brush) that no longer matches.

**Signature:** `((payload: { dateRange: { start: string; end: string; } | null; }) => void)`

### `onLoaderStart`

Fired the moment the element's own loading skeleton has painted inside its frame — the earliest point a consumer-managed loading state can hand off without ever exposing a blank. Always precedes `onReady`; most consumers only need `onReady`.

**Signature:** `(() => void)`

### `onReady`

Fired once the element has booted and painted its first complete frame.

**Signature:** `(() => void)`

### `onError`

Fired when the element fails to load or crashes; the element shows its own error fallback. `message` is human-readable; framework refusals also carry `code` (e.g. `HOST_SOURCE_FAILED`, with `sourceKey` naming the failed hostState key) so hosts can switch on codes, never message text.

**Signature:** `((e: { message: string; code?: string | undefined; sourceKey?: string | undefined; }) => void)`

## Methods

Call these on the element handle — the return of `create` (vanilla) or the component `ref` (React).

### `refresh`

Re-fetch the account's activity from the first page. Call it after a mutation made elsewhere (a deposit, a send) so the list reflects it without waiting for the cache to expire.

**Signature:** `() => Promise<void>`

### `setDateRange`

Set the date-range filter from outside the element — e.g. wire a chart brush selection into the list. Pass `null` to clear it back to no date filter.

**Signature:** `(input: ActivityDateRangeOverride | null) => Promise<void>`

### `mount`

Place the element on the page: appends its container to `target` (a CSS selector or an element) and starts loading. Nothing renders until this is called. React consumers never call it — the component mounts itself.

**Signature:** `(target: string | HTMLElement) => void`

### `destroy`

Remove the element from the page and release its frame and subscriptions. Safe to call more than once. React consumers never call it — unmounting the component does it.

**Signature:** `() => void`

### `update`

Change this element's consumer props after mount — it re-renders with the merged props. React consumers never call it — updating the JSX props does the same.

**Signature:** `(options: Partial<ActivityElementProps>) => void`

## Styling

Each part below is a stable class name — safe to depend on. Restyle a part by mapping its class to a **style declaration object** under `appearance.classes` (properties camelCase or kebab-case, values as strings with units — the same shape as React's `style` prop). The element renders in its own frame, so page stylesheets can't reach it: these declarations are sanitized against a safe-property allowlist and injected inside the frame for you.

| Class                   | Targets                                                          |
| ----------------------- | ---------------------------------------------------------------- |
| `.whop-ActivityRow`     | One ledger activity row — its icon, title, timestamp, and amount |
| `.whop-ActivitySurface` | The activity feed — title, filters, and up to every fetched row  |

```ts theme={null}
const wallet = whop.wallet.create({
  appearance: {
    classes: {
      'whop-ActivityRow': { borderRadius: '8px', fontWeight: '600' },
      'whop-ActivitySurface': { borderRadius: '8px', fontWeight: '600' }
    }
  }
});

// restyle live at any point — the same shape through update()
wallet.update({
  appearance: { classes: { 'whop-ActivityRow': { fontWeight: '700' } } }
});
```

In React, pass the same object as the `appearance` prop on `<Wallet>`; `appearance` also applies globally at `WhopElements({ appearance })`.
