PayeeSelect
- Status
- Implemented
- Family
- 3 of 13
- Registry
- @lopifi/payee-select
npx shadcn@latest add @lopifi/theme @lopifi/payee-selectThe component, rendering
Real data, the shipped component. Switch the theme to check the claims the spec makes below.
The four-layer spec
Fuzzy search across name, account, and reference. Shows last-paid amount and date inline — the single most useful piece of context when choosing a recipient. New-payee flow inline, not a separate route.
Lifted verbatim from Payments. The doc and this page are the same paragraphs, so they cannot disagree.
What lands in your repository
One component is never one file. Everything below is copied into your project, where you own it.
- Files
components/ledger/payee-select.tsx
- Lopifi dependencies · 9
- cnentity-markfiscal-periodformat-moneyiconsmoneymoney.typesreferencetooltip
- npm packages
- @base-ui-components/reactclass-variance-authorityclsxtailwind-merge
- Registry entry
- /r/payee-select.json
The whole component
No compiled bundle, no black box. This is the file the registry copies, and the file you will edit.
"use client";
import { Popover } from "@base-ui-components/react/popover";
import * as React from "react";
import { cn } from "@/lib/ledger/cn";
import { formatDate } from "@/lib/ledger/fiscal-period";
import type { MoneyValue } from "@/lib/ledger/money.types";
import { EntityMark } from "@/components/ledger/entity-mark";
import { ChevronDownIcon, MagnifyingGlassIcon, PlusIcon } from "@/components/ledger/icons";
import { Money } from "@/components/ledger/money";
import { MaskedAccount } from "@/components/ledger/reference";
export type Payee = {
id: string;
name: string;
last4: string;
reference?: string;
lastPaid?: { amount: MoneyValue; date: Date };
};
export interface PayeeSelectProps {
className?: string;
onCreate?: (name: string) => void;
onValueChange: (id: string) => void;
payees: Payee[];
value: string | null;
}
/**
* Last-paid amount and date inline — the single most useful piece of context
* when choosing a recipient. The new-payee flow is inline, not a route.
*/
export function PayeeSelect({ payees, value, onValueChange, onCreate, className }: PayeeSelectProps) {
const [open, setOpen] = React.useState(false);
const [query, setQuery] = React.useState("");
const selected = payees.find((p) => p.id === value);
const filtered = React.useMemo(() => {
const q = query.trim().toLowerCase();
if (!q) return payees;
return payees.filter((p) =>
[p.name, p.last4, p.reference ?? ""].some((f) => f.toLowerCase().includes(q)),
);
}, [payees, query]);
return (
<Popover.Root onOpenChange={setOpen} open={open}>
<Popover.Trigger
aria-label={selected ? `Recipient: ${selected.name}` : "Choose a recipient"}
className={cn(
"flex h-12 w-full items-center gap-3 rounded-md border border-border bg-surface px-3",
"text-left transition-colors duration-1 ease-standard hover:border-border-strong",
className,
)}
>
{selected ? (
<>
<EntityMark category="company" name={selected.name} size={24} />
<span className="min-w-0 flex-1">
<span className="block truncate text-body">{selected.name}</span>
</span>
<MaskedAccount last4={selected.last4} />
</>
) : (
<span className="flex-1 text-body text-text-tertiary">Choose a recipient</span>
)}
<ChevronDownIcon aria-hidden="true" className="size-4 text-text-tertiary" />
</Popover.Trigger>
<Popover.Portal>
<Popover.Positioner align="start" className="z-dropdown" sideOffset={8}>
<Popover.Popup
className="w-[var(--anchor-width)] min-w-[320px] overflow-hidden rounded-md border border-border bg-surface-raised shadow-elevation-3"
style={{ transformOrigin: "var(--transform-origin)" }}
>
<div className="flex items-center gap-2 border-b border-border-subtle px-3">
<MagnifyingGlassIcon aria-hidden="true" className="size-4 text-text-tertiary" />
<input
aria-label="Search recipients"
autoFocus
className="h-10 flex-1 bg-transparent text-body outline-none placeholder:text-text-disabled"
onChange={(e) => setQuery(e.target.value)}
placeholder="Search name, account or reference"
value={query}
/>
</div>
<div className="max-h-[320px] overflow-y-auto py-1 scrollbar-thin">
{filtered.map((p) => (
<button
className={cn(
"flex w-full items-center gap-3 px-3 py-2 text-left",
"transition-colors duration-1 ease-standard hover:bg-surface-hover",
p.id === value && "bg-surface-selected",
)}
key={p.id}
onClick={() => {
onValueChange(p.id);
setOpen(false);
}}
type="button"
>
<EntityMark category="company" name={p.name} size={32} />
<span className="min-w-0 flex-1">
<span className="block truncate text-body">{p.name}</span>
<MaskedAccount last4={p.last4} />
</span>
{p.lastPaid ? (
<span className="text-right">
<Money size="xs" tone="secondary" value={p.lastPaid.amount} />
<span className="block text-caption text-text-tertiary">
{formatDate(p.lastPaid.date)}
</span>
</span>
) : null}
</button>
))}
{filtered.length === 0 && onCreate ? (
<button
className="flex w-full items-center gap-2 px-3 py-3 text-left text-body text-accent hover:bg-surface-hover"
onClick={() => {
onCreate(query);
setOpen(false);
}}
type="button"
>
<PlusIcon aria-hidden="true" className="size-4" />
Add “{query}” as a new recipient
</button>
) : null}
</div>
</Popover.Popup>
</Popover.Positioner>
</Popover.Portal>
</Popover.Root>
);
}
The accounting it encodes
Concepts this component renders. Each one is defined once, in the lexicon, and used identically in the code and the copy.
Also in Payments
- AmountInputThe hardest input in fintech.
- CurrencySelectSearchable, with recents.
- PaymentFormAmount → payee → method → date → memo.
- PaymentMethodListSelectable method cards.
- CheckoutSummaryItemized total with fees and tax.
- ConfirmPaymentDialogAmount, destination, timing. Hold-to-confirm.
- PaymentStatusTimelineSubmitted → sent → settled, with real timestamps.
- PaymentSuccessThe sanctioned delight moment.
- ReceiptSheetPrintable/shareable receipt.
- PayoutScheduleUpcoming payouts calendar.
- CardInputPAN / expiry / CVC with correct autocomplete.
- BankAccountInputRouting + account with checksum validation.
- RecurringScheduleFrequency, end condition, preview of next 3.
See also
A component is specified in one place, defined in another, and running in a third. All three, from here.
- Payments — the family specThe four-layer specification this component was built against, before it was written.Doc
- Payment forms, methods and receiptsThe family running, with real figures in it, in both themes and at every density.Live
- CatalogAll 179 components, specified before they are written.Doc
- PayeeThe party receiving a paymentTerm
Elsewhere in the system
Where PayeeSelect sits in the rest of the system — the live section it renders in, the calculators that compute what it displays, and the ledger payloads it is fed from.
- PayeeSelect, runningThe payments showcase — live, with theme, density, greyscale and reduced-motion switches.Live
- Contacts, customers and suppliersIs a customer who is also a supplier one record or two?API
- PaymentsPayments — specs for 14 React components: AmountInput, CurrencySelect, PayeeSelect, PaymentForm and 10 more.Doc
Components are copied into your repository and meant to be edited — rounding policy, fiscal calendar and compliance copy differ per company.
Told when Payments changes
Components are copied into your repo, so a fix here does not reach you on its own. One email when a component in this family changes in a way that needs a migration — and nothing when it does not.