Weave Code
Filament Iban Laravel Package
asignua/filament-iban
A Filament package for adding IBAN input handling to Laravel admin forms, with validation to help collect and verify international bank account numbers cleanly in your Filament panels.
IBAN input, validation rule, infolist entry and table column for Filament 5: grouped display, compact storage, SWIFT registry checks for every IBAN country and bank names for Ukraine and Poland. 10 languages.
Frequently asked questions about Filament Iban
- How do I install and use asignua/filament-iban in a Laravel Filament form?
- Install it with Composer using composer require asignua/filament-iban, then add the IbanInput component to your Filament form schema in place of a plain TextInput. The package is distributed as a standard Composer package and requires no database migrations; check the composer.json constraints against your app before merging and pin the version during evaluation. After swapping the field, keep any existing server-side IBAN validation rule until you have confirmed equivalent behaviour.
- Which Laravel, PHP and Filament versions does asignua/filament-iban support?
- The package targets Filament 5 and is installed into a Laravel application that already uses Filament for admin or operations panels. Exact PHP and Laravel constraints are declared in the package composer.json, so verify them against your application before requiring it. Pin the release version while you evaluate and re-check constraints on each Filament major upgrade.
- How does the package validate IBANs, and which checksum implementation does it use?
- The package ships a Filament validation rule for IBAN input, but the underlying checksum library is not named in the release notes, so review the source or run your own test cases before relying on it in production. Test with known valid and invalid IBANs across the countries you actually support, including edge cases like spaces and lowercase input. Keeping a server-side validation rule in parallel is a sensible safety net.
- How is the IBAN stored in the database, compact or full format?
- The package uses compact storage, meaning the IBAN is normalised before persistence, while the form input and table display can show it in grouped, human-readable blocks. Make sure your column is wide enough for the full IBAN, which can be up to 34 characters. Confirm the exact stored format in your own environment before writing queries or exports against the column.
- Does the package show bank names or SWIFT/BIC details, and for which countries?
- It performs SWIFT registry checks for every IBAN country, and it resolves bank names for Ukraine and Poland specifically. Other countries get validation and formatting but not localised bank name lookup. If bank name display is a hard requirement outside UA and PL, plan a supplementary data source.
- How do I fix the iban versus IBAN label casing in validation messages?
- Version 1.0.2 changed the default label from iban to IBAN and fixed label handling that depended on Filament's lcfirst behaviour. Where an acronym must be preserved in validation messages, use the documented validationAttribute() method to set it explicitly, for example IBAN or BIC. If you have snapshot or visual regression tests, re-baseline them because this is a cosmetic output change.
- Which languages are included, and can I publish or override the translations?
- The package ships with 10 languages of translations for labels and validation messages. Laravel packages typically expose translations via the publish command, so check the README for the exact tag and whether overrides are supported in your setup. If your locale is not covered, publish and add the missing keys rather than editing vendor files.
- Can I display an IBAN in a Filament table column or infolist entry, not just as a form field?
- Yes. The package provides not only the IbanInput form component but also an infolist entry and a table column, so grouped IBAN display works consistently in resource tables and view pages. That makes it suitable for payout, vendor and KYC detail screens where the IBAN is shown read-only. Reuse the same column across resources to keep formatting consistent.
- How can I try asignua/filament-iban locally before adding it to my application?
- The repository ships a workbench demo with a DemoSeeder, so you can run a local proof of concept without touching your main application. Use it to reproduce the screenshots, check grouped display and verify label casing in your target locales. Once satisfied, integrate the field into one non-critical dev form before rolling out further.
- Is asignua/filament-iban production-ready, and what are the maintenance risks?
- The technical assessment rates risk as low: there are no migrations, no new configuration surface and no announced API breaks, so rollout can be staged behind a feature flag for one release cycle. The main residual risk is tight coupling to Filament's label pipeline, particularly the lcfirst behaviour, so re-verify label and validation-message output on every Filament upgrade. Compared with a hand-rolled TextInput plus custom IBAN rule, this package saves work on formatting, translations and column display, but you still own end-to-end validation testing. Review the license and CI posture in the repository before adopting.
Weaver
How can I help you explore Laravel packages today?