PayoutSchedule
- Status
- Implemented
- Family
- 3 of 13
- Registry
- @lopifi/payout-schedule
npx shadcn@latest add @lopifi/theme @lopifi/payout-scheduleThe component, rendering
Real data, the shipped component. Switch the theme to check the claims the spec makes below.
The four-layer spec
Upcoming payouts on a calendar or list, with cutoff times stated in the user's timezone. Business days respected, holidays flagged.
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/payout-schedule.tsx
- Lopifi dependencies · 8
- cnfiscal-periodformat-moneyiconsmoneymoney.typesstatus-pilltooltip
- npm packages
- @base-ui-components/reactclass-variance-authorityclsxtailwind-merge
- Registry entry
- /r/payout-schedule.json
The whole component
No compiled bundle, no black box. This is the file the registry copies, and the file you will edit.
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 { Money } from "@/components/ledger/money";
import { StatusPill } from "@/components/ledger/status-pill";
export type Payout = {
id: string;
date: Date;
amount: MoneyValue;
destination: string;
/** Stated in the user's timezone; a cutoff without a zone is a guess. */
cutoff: string;
holiday?: string;
};
export interface PayoutScheduleProps extends React.ComponentPropsWithoutRef<"div"> {
payouts: Payout[];
}
/** Business days respected, holidays flagged, cutoffs stated with the zone. */
export const PayoutSchedule = React.forwardRef<HTMLDivElement, PayoutScheduleProps>(
({ className, payouts, ...props }, ref) => (
<div className={cn("rounded-xl border border-border bg-surface", className)} ref={ref} {...props}>
<ul>
{payouts.map((p) => (
<li
className="flex items-center gap-4 border-b border-border-subtle px-4 py-3 last:border-b-0"
key={p.id}
>
<div className="w-24 shrink-0">
<p className="numeric text-label font-medium">{formatDate(p.date)}</p>
<p className="text-caption text-text-tertiary">Cutoff {p.cutoff}</p>
</div>
<div className="min-w-0 flex-1">
<p className="truncate text-body">{p.destination}</p>
{p.holiday ? (
<p className="text-caption text-warning">
Bank holiday: {p.holiday} — settles the next business day
</p>
) : null}
</div>
{p.holiday ? <StatusPill entity="Payout" status="scheduled" /> : null}
<Money accounting size="sm" value={p.amount} />
</li>
))}
</ul>
</div>
),
);
PayoutSchedule.displayName = "PayoutSchedule";
Also in Payments
- AmountInputThe hardest input in fintech.
- CurrencySelectSearchable, with recents.
- PayeeSelectRecipient picker with fuzzy search and last-paid.
- 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.
- 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.
Elsewhere in the system
Where PayoutSchedule 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.
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.