## Usage

```tsx React theme={null} import { WhopElements, Wallet, ActivityElement } from "@whop/elements-react"; import { loadWhop } from "@whop/elements"; function Example() { return ( console.log("activitySelected", payload)} onDateRangeChanged={(payload) => console.log("dateRangeChanged", payload)} /> ); } ``` ```html Vanilla theme={null} ```

## Props Only show activity for this currency. Without it, activity from every currency is shown. A scoped token for the read. An account needs `company:balance:read`, and a user needs `user:balance:read`. Mint it on your server with `POST /v1/access_tokens`. Without it the read uses the viewer's own session, which only works same-origin. When off, card transaction rows render inert (no click, no hover) instead of firing `activitySelected`. Use it when you know the viewer isn't allowed to see those details. Defaults to `true`. ## Events Pass a callback in the create options (or React prop) to receive these. ### `onActivitySelected` A row was clicked. Open your own detail view or route for it; the element never navigates. **Signature:** `((payload: { activity: LedgerActivity; }) => void)` ### `onDateRangeChanged` The viewer changed the date filter through the filter row rather than through `setDateRange`. Clear any range selection of your own, 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. This is 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, which is 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` ### `setDateRange` Set the date filter from outside the element, for example wiring a chart brush selection into the list. Pass `null` to clear it. **Signature:** `(input: ActivityDateRangeOverride | null) => Promise` ### `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, and it re-renders with the merged props. React consumers never call it; updating the JSX props does the same. **Signature:** `(options: Partial) => 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 ``; `appearance` also applies globally at `WhopElements({ appearance })`.

`ActivityElement` shows an account's ledger activity: payments, payouts, transfers, swaps and disputes, newest first. It loads its own data and pages as the viewer scrolls, so the only thing you have to pass in is the account id. Pass a closure as well and you get the row the viewer tapped. It never navigates, so routing stays yours. ### Usage ```swift theme={null} import SwiftUI import WhopElements // WhopSDK.configure(tokenProvider:) runs once at app launch. See Getting started. struct ActivityScreen: View { var body: some View { ScrollView { ActivityElement( accountId: "biz_xxxx" ) { activity in print(activity.title, activity.amount) } .padding() } } } ``` ### Parameters Whose ledger to list, given as a company's `biz_…` tag or a user's `user_…` tag. Both work directly; the feed reads the tag without resolving a ledger first. Shows the built-in "Activity" heading. Defaults to `true`. Turn it off when your screen already has one. Called with the row the viewer tapped. The view never navigates, so route to your own detail screen. ### `WalletActivity` What a selection hands back: * `id: String`: stable per row * `title: String` / `subtitle: String`: the row's two lines * `amount: Decimal`: signed, negative for money out * `currencyCode: String` * `postedAt: Date` * `isIncoming: Bool` ### States Shows a skeleton list while the first page loads, `No activity found` when the ledger has no movements, and the failure message with a `Try again` button when the read fails. If a later page fails, the rows already loaded stay on screen and a `Try again` appears at the bottom. ### Good to know * **Give it a scroll container.** The feed is a `LazyVStack` and pages as its last row appears, so outside a `ScrollView` it renders page one and never loads another. * Takes `biz_…` and `user_…` tags directly, so unlike the other wallet views it never has to resolve a ledger first. Authentication is set once for every element, not per element, so `WhopSDK.configure(tokenProvider:)` at app launch is enough. A view mounted before it lands renders a spinner and picks the token up when it arrives. See [Getting started](/elements/upcoming/getting-started) for the token provider. Theme with the `.whopTheme(_:)` modifier.