BankAccountInput
- Status
- Implemented
- Family
- 3 of 13
- Registry
- @lopifi/bank-account-input
npx shadcn@latest add @lopifi/theme @lopifi/bank-account-inputThe component, rendering
Real data, the shipped component. Switch the theme to check the claims the spec makes below.
The four-layer spec
Routing + account number. ABA checksum validation with the institution name resolved and displayed once valid — instant confirmation that they typed the right bank. IBAN mod-97 validation for international, with country-aware length and formatting.
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/bank-account-input.tsx
- Lopifi dependencies · 2
- cnicons
- npm packages
- clsxtailwind-merge
- Registry entry
- /r/bank-account-input.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 * as React from "react";
import { cn } from "@/lib/ledger/cn";
import { CheckIcon } from "@/components/ledger/icons";
/** ABA routing checksum: 3·(d1+d4+d7) + 7·(d2+d5+d8) + 1·(d3+d6+d9) ≡ 0 mod 10. */
export function validateAba(routing: string): boolean {
const d = routing.replace(/\D/g, "");
if (d.length !== 9) return false;
const w = [3, 7, 1, 3, 7, 1, 3, 7, 1];
const sum = d.split("").reduce((acc, ch, i) => acc + Number(ch) * w[i], 0);
return sum % 10 === 0;
}
/** IBAN mod-97: move the first four characters to the end, letters → numbers. */
export function validateIban(iban: string): boolean {
const s = iban.replace(/\s/g, "").toUpperCase();
if (!/^[A-Z]{2}\d{2}[A-Z0-9]{10,30}$/.test(s)) return false;
const rearranged = s.slice(4) + s.slice(0, 4);
const expanded = rearranged.replace(/[A-Z]/g, (c) => String(c.charCodeAt(0) - 55));
let remainder = 0;
for (const ch of expanded) remainder = (remainder * 10 + Number(ch)) % 97;
return remainder === 1;
}
const INSTITUTIONS: Record<string, string> = {
"021000021": "JPMorgan Chase Bank, N.A.",
"026009593": "Bank of America, N.A.",
"071000013": "JPMorgan Chase Bank, N.A. (Illinois)",
"121000248": "Wells Fargo Bank, N.A.",
};
export interface BankAccountInputProps {
className?: string;
mode?: "us" | "iban";
onChange?: (value: { routing: string; account: string; valid: boolean }) => void;
}
/**
* The resolved institution name is the point: instant confirmation that the
* user typed the right bank, before any money moves.
*/
export function BankAccountInput({ mode = "us", className, onChange }: BankAccountInputProps) {
const [routing, setRouting] = React.useState("");
const [account, setAccount] = React.useState("");
const [iban, setIban] = React.useState("");
const routingValid = validateAba(routing);
const ibanValid = validateIban(iban);
const institution = routingValid
? (INSTITUTIONS[routing.replace(/\D/g, "")] ?? "Verified routing number")
: null;
React.useEffect(() => {
onChange?.(
mode === "us"
? { account, routing, valid: routingValid && account.length >= 4 }
: { account: iban, routing: "", valid: ibanValid },
);
}, [mode, routing, account, iban, routingValid, ibanValid, onChange]);
if (mode === "iban") {
return (
<label className={cn("block", className)}>
<span className="mb-2 block text-label font-medium text-text-secondary">IBAN</span>
<input
aria-invalid={iban.length > 0 && !ibanValid}
aria-label="International bank account number"
className={cn(
"reference-numeric h-10 w-full rounded-sm border bg-surface px-3 text-body outline-none focus-visible:border-accent focus-visible:ring-2 focus-visible:ring-accent-subtle",
iban && !ibanValid ? "border-negative" : "border-border focus-visible:border-accent",
)}
onChange={(e) => setIban(e.target.value.toUpperCase())}
placeholder="DE89 3704 0044 0532 0130 00"
value={iban}
/>
{iban && !ibanValid ? (
<span className="mt-1 block text-caption text-negative" role="alert">
That IBAN fails its checksum — check the country code and digits.
</span>
) : ibanValid ? (
<span className="mt-1 flex items-center gap-1 text-caption text-positive">
<CheckIcon aria-hidden="true" className="size-3" /> Valid IBAN
</span>
) : null}
</label>
);
}
return (
<div className={cn("grid gap-3 sm:grid-cols-2", className)}>
<label className="block">
<span className="mb-2 block text-label font-medium text-text-secondary">Routing number</span>
<input
aria-invalid={routing.length === 9 && !routingValid}
aria-label="ABA routing number"
className={cn(
"reference-numeric h-10 w-full rounded-sm border bg-surface px-3 text-body outline-none focus-visible:border-accent focus-visible:ring-2 focus-visible:ring-accent-subtle",
routing.length === 9 && !routingValid
? "border-negative"
: "border-border focus-visible:border-accent",
)}
inputMode="numeric"
maxLength={9}
onChange={(e) => setRouting(e.target.value.replace(/\D/g, ""))}
placeholder="021000021"
value={routing}
/>
{institution ? (
<span className="ledger-crossfade mt-1 flex items-center gap-1 text-caption text-positive">
<CheckIcon aria-hidden="true" className="size-3" /> {institution}
</span>
) : routing.length === 9 ? (
<span className="mt-1 block text-caption text-negative" role="alert">
That routing number fails its checksum.
</span>
) : null}
</label>
<label className="block">
<span className="mb-2 block text-label font-medium text-text-secondary">Account number</span>
<input
aria-label="Bank account number"
className="reference-numeric h-10 w-full rounded-sm border border-border bg-surface px-3 text-body outline-none focus-visible:border-accent"
inputMode="numeric"
onChange={(e) => setAccount(e.target.value.replace(/\D/g, ""))}
value={account}
/>
</label>
</div>
);
}
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.
- 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.
- PayoutScheduleUpcoming payouts calendar.
- CardInputPAN / expiry / CVC with correct autocomplete.
- 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
- AccountA GL account in the chart of accounts. Always qualify when a bank account is meant.Term
Elsewhere in the system
Where BankAccountInput 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.
- BankAccountInput, runningThe payments showcase — live, with theme, density, greyscale and reduced-motion switches.Live
- IBAN, routing, VAT, EINChecksums, offline. A valid IBAN is not a real account, and this says so.Tool
- 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.