Filament Iban Laravel Package

Product Decisions This Supports

• Payment and payout readiness. Whether you are adding an IBAN field to vendor onboarding, supplier payout setup, invoicing, refunds, or subscription billing, this package provides a validated, Filament-native form component instead of a hand-rolled text field. The v1.0.2 label fixes mean the field reads as "IBAN" in the UI and the validation message reads "The IBAN must…" rather than the jarring "iBAN"/"Iban" inconsistencies — a real polish item for finance-adjacent flows where trust and clarity matter.
• Build vs. buy. IBAN collection looks trivial but involves country-specific length/format rules and MOD-97 checksum validation. Adopting a maintained Filament component pushes that maintenance burden off your team and standardizes behavior across forms.
• Roadmap enablement. The workbench demo and screenshots added in v1.0.2 lower the cost of evaluating the field in a realistic setup (the DemoSeeder Acme Supply data) — useful for a spike or design review without wiring it into your product first. This is a cheap way to de-risk a roadmap item such as international payouts or KYC.
• Use cases to scope: vendor/supplier payout details, customer bank accounts for direct debit/SEPA, refund destinations, donation/payment forms inside an admin panel, and any back-office tool where operations staff enter or correct IBANs.

When to Consider This Package

Adopt when:

• Your application uses Filament and you need an IBAN form field with validation, rather than a generic text input.
• You want consistent, localized-looking field labels and validation messages (the acronym-handling fix in v1.0.2 matters here; explicit ->validationAttribute() is still available if you need a custom message key).
• You value a demo/workbench and screenshots in the docs as part of the evaluation — the v1.0.2 additions make a trial quick.

Look elsewhere or reassess when:

• You are not on Filament (the component is Filament-specific; the underlying IBAN logic would need to be pulled in separately for plain Livewire/Blade).
• Your requirement extends beyond a single input: SEPA mandate handling, BIC/SWIFT alongside IBAN, multi-step bank-account verification, name-matching, or payment-provider tokenization are out of scope for this field.
• You need a formal support/SLA or a large maintainer team — this is a focused package; confirm maintenance cadence before depending on it for revenue-critical flows.
• Your compliance process requires a vendor security review of every dependency; size the package (single field) against the overhead.

How to Pitch It (Stakeholders)

For executives: This is a small, targeted Filament component for collecting bank account numbers (IBANs) with validation. The latest release is a maintenance and documentation update — better screenshots, a runnable demo, and corrected "IBAN" labeling in the UI and validation messages — no breaking changes. It lets us ship international payment/payout fields faster with less custom validation code to maintain, at low adoption cost.

For engineering: Filament-native IbanInput with validation and sensible defaults (a field named iban renders as "IBAN"). v1.0.2 preserves acronym casing in validation messages and adds a workbench demo and README screenshots. Easy to trial in a branch against the DemoSeeder; no migration or breaking API changes to plan for.