This is a small crate that is able to validate an IBAN account number. It has many tests and uses proptest for fuzzing.
The crate can be found on crates.io. To use this crate, just add it as an dependency:
[dependencies]
iban_validate = "3"
This crate provides an easy way to validate an IBAN (International Bank Account Number). To do
so, you can use the function parse()
. This will check the IBAN rules
as well as the BBAN structure. The provided Iban
structure provides many methods
to easy the handling of an IBAN. Many of these methods are provided via the IbanLike
trait.
When BBAN parsing fails, the error type ParseIbanError
provides useful
information about what went wrong. Additionally, the error contains BaseIban
,
which can still be used to access useful information.
The following example does a full validation of the IBAN and BBAN format. ```rust use iban::*;
let account = "DE44500105175407324931".parse::
asserteq!(account.countrycode(), "DE"); asserteq!(account.checkdigits(), 44); asserteq!(account.bban(), "500105175407324931"); asserteq!(account.electronicstr(), "DE44500105175407324931"); asserteq!(account.tostring(), "DE44 5001 0517 5407 3249 31"); asserteq!(account.bankidentifier(), Some("50010517")); asserteq!(account.branch_identifier(), None); ```
serde
support for [Iban
] and [BaseIban
].The full documentation is available at docs.rs.
If you experience issues with this crate or want to help, please look here.
This crate has the goal of being usable on the latest stable version of Rust. Its minimum version is documented and tested against, although no extra effort is taken to support earlier versions. The minimum version of Rust can be increased, although this corresponds to a new major release. The crate does not use unsafe itself, although dependencies might. Breaking changes are not avoided in new major versions, although these will always be well-documented and the process of upgrading made clear.
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.