Card transaction parts
Cells shared by the card transaction screens: the merchant with its category and statement descriptor, and the amount with the billed figure of a foreign purchase. Status and receipt marks come from expenses-status.
Component: A piece you place inside your own screens: a table, a form, a card or a dialog. You decide the layout around it. Pages vs components
Works with Dolfin’s SDK context, with appearance and behaviour you can customise. Requires DolfinProvider.
Installation
Needs the Dolfin registry token. The CLI copies the source into your app.
bunx --bun shadcn@4.23.0 add @dolfin/expenses-card-transaction-partsAlso installs: base-entity-cell, base-money, base-theme, ui-expenses-card-transaction-parts.
Usage
import { CardTransactionMerchant } from "@/components/dolfin/expenses/card-transaction-parts";
// Place it anywhere inside your <DolfinProvider>.
<CardTransactionMerchant transaction={transaction} />Renders inside DolfinProvider (set it up once). It renders the data you pass as props.
API reference
| Prop | Type | Description |
|---|---|---|
transaction required | { id?: string; cardConnectionId?: string; expenseId?: null | string; status?: components["schemas"]["CardTransactionStatus"]; descriptor?: n… | |
className | string |
Customisation
Without editing the source, you can change:
- Class names
className- Messages
expenses.cardTransactions
Or edit the installed file directly: it is your code. See theming for colours and fonts.
Hooks
The SDK hooks this component uses. Use them directly from @dolfinai/react to build your own version.
useMessagesFiles
Written to your app by the install command:
components/dolfin/expenses/card-transaction-parts.tsx37 lines