php-iban is a library for parsing and validating IBAN (and IIBAN) bank account information in PHP.

All parts of an IBAN can be retrieved, including country code, checksum, BBAN, financial institution or bank code, national checksum and where a fixed-length national system is in use, also branch/sort code and account number. Legacy national checksums may also be retrieved, where available. IBAN country codes can be coverted in to ISO3166-1 alpha-2 and IANA formats, to ease integration. IBANs can also be converted between human and machine representation. Finally, intelligent suggestions for originally intended input can be made when an incorrect IBAN is detected and is due to mistranscription error.

Tested on PHP versions as well as HHVM and nightly.

The parser was built using regular expressions to adapt the contents of the official IBAN registry available from SWIFT at https://www.swift.com/node/11971 then only manually modified for special cases such as errors and omissions in SWIFT's official specifications: https://php-php-iban.googlecode.com/git/docs/COMEDY-OF-ERRORS

Various deficiencies in the initial adaptation have since been rectified, and the current version should be a fairly correct and reliable implementation.

Where appropriate, European Committee for Banking Standards (ECBS) recommendations have also been incorporated.

Please bear in mind that because the specification changes frequently, it may not be 100% up to date if a new version has been recently released - I do my best though. We are currently thought to be up to date with the February 2016 release, ie. PDF release #63.

Licensed under LGPL, it is free to use in commercial settings.

The following 98 official and unofficial IBAN countries are supported.

• Åland Islands (AX)
• Albania (AL)
• Algeria (DZ)
• Andorra (AD)
• Angola (AO)
• Austria (AT)
• Azerbaijan (AZ)
• Bahrain (BH)
• Belgium (BE)
• Benin (BJ)
• Bosnia and Herzegovina (BA)
• Brazil (BR)
• British Virgin Islands (VG)
• Bulgaria (BG)
• Burkina Faso (BF)
• Burundi (BI)
• Cameroon (CM)
• Cape Verde (CV)
• Costa Rica (CR)
• Côte d'Ivoire (CI)
• Croatia (HR)
• Cyprus (CY)
• Czech Republic (CZ)
• Denmark (DK)
• Faroe Islands (FO)
• Greenland (GL)
• Dominican Republic (DO)
• Estonia (EE)
• Finland (FI)
• France (FR)
• French Guiana (GF)
• French Polynesia (PF)
• French Southern Territories (TF)
• Guadelope (GP)
• Martinique (MQ)
• Mayotte (YT)
• New Caledonia (NC)
• Réunion (RE)
• Saint Barhélemy (BL)
• Saint Martin (French Part) (MF)
• Saint-Pierre and Miquelon (PM)
• Wallis and Futuna (WF)
• Georgia (GE)
• Germany (DE)
• Gibraltar (GI)
• Greece (GR)
• Guatemala (GT)
• Hungary (HU)
• Iceland (IS)
• IIBAN (Internet) (AA)
• Iran (IR)
• Ireland (IE)
• Israel (IL)
• Italy (IT)
• Jordan (JO)
• Kazakhstan (KZ)
• Kosovo (XK)
• Kuwait (KW)
• Latvia (LV)
• Lebanon (LB)
• Liechtenstein (LI)
• Lithuania (LT)
• Luxembourg (LU)
• Macedonia (MK)
• Madagascar (MG)
• Mali (ML)
• Malta (MT)
• Mauritania (MR)
• Mauritius (MU)
• Moldova (MD)
• Monaco (MC)
• Montenegro (ME)
• Mozambique (MZ)
• Netherlands (NL)
• Norway (NO)
• Pakistan (PK)
• Palestine (PS)
• Poland (PL)
• Portugal (PT)
• Qatar (QA)
• Romania (RO)
• Saint Lucia (LC)
• San Marino (SM)
• São Tomé and Príncipe (ST)
• Saudi Arabia (SA)
• Senegal (SN)
• Serbia (RS)
• Slovakia (SK)
• Slovenia (SI)
• Spain (ES)
• Sweden (SE)
• Switzerland (CH)
• Timor-Leste (TL)
• Tunisia (TN)
• Turkey (TR)
• Ukraine (UA)
• United Arab Emirates (AE)
• United Kingdom (GB)

If you use composer you can simply run composer require globalcitizen/php-iban to get going. Reportedly (and ) were done via composer.

(If you don't yet have composer and wish to install it in an insecure fashion (not recommended, but convenient) you can run curl -sS https://getcomposer.org/installer | php or wget -O- https://getcomposer.org/installer | php)

Then just add the following to your composer.json file:

// composer.json
{
    "require": {
        "globalcitizen/php-iban": "2.3.1"
    }
}

Then, you can install the new dependencies by running composer's update command from the directory where your composer.json file is located:

# install
$ php composer.phar install
# update
$ php composer.phar update globalcitizen/php-iban

# or you can simply execute composer command if you set it to
# your PATH environment variable
$ composer install
$ composer update globalcitizen/php-iban

You can see this library on Packagist.

Use the git clone command:

# HTTP
$ git clone https://github.com/globalcitizen/php-iban.git
# SSH
$ git clone git@github.com:globalcitizen/php-iban.git

The following table compares php-iban to other PHP projects offering IBAN-related functionality, on the basis of general project information and the programming paradigms supported.

Notes:

• Original download records for php-iban releases were hosted on Google Code and are now lost. Prior to establishing a release process on Github, we just expected that people would download the code... so we're really not sure how many installs exist, but this is a fair guess. This library also powers adm-gravity-iban and the PHP SEPA XML class.
• php-iban's author is an Australian born, Australia/New Zealand/German citizen based in mainland China, who has formerly also worked and banked in the US, UK, and many Asian countries.
• The IsoCodes and SepaUtil's projects cover standards other than IBAN so their popularity should be considered in this light. (In essence, there is really only one directly competing library, Iban)

Now let's take a look at features.

Note:

• Gen. refers to the capacity to create checksum-accurate potential IBANs programatically. It is the author's opinion that generation features without IIBAN support (ie. authority) are of dubious use, except in one-off migrations.
• ISO refers to the capacity to convert between IBAN country codes and ISO3166-1 alpha-2 country codes
• IANA refers to the capacity to convert between IBAN country codes and IANA country codes (eg. 'GB' to '.uk' and vice versa)
• SEPA refers to the ability to check whether a particular IBAN country is a member of the Single Euro Payments Area (SEPA)
• IIBAN describes support for the open proposal for decentralized financial endpoint generation by private parties, such as crypto-currency exchanges, whilst maintaining compatibility with the emerging IBAN system. This system has been adopted by major cryptocurrency exchanges such as Kraken.
• Unofficial refers to support for countries whose IBAN formats have been published as in informal use by major financial institutions, but are not official SWIFT-published registry entries.
• MT refers to mistranscription support: the capacity to automatically detect what the user probably meant when they make a transcription error on IBANs, such as those manually written or printed in confusing fonts, for instance writing 'L' instead of 'I' or '1', or vice versa.
• Human? means support for input and output for the human, space-laden or presentation variant of an IBAN, ie. IBAN XXXX XXXX XXXX XXXX instead of XXXXXXXXXXXXXXXX - a lot more reasonable.

In short, while composer users have apparently lept on rival libraries (particularly Iban), probably due to the time it took us to integrate a composer file, those libraries are often either full-fledged web frameworks or burdensome in dependencies, less mature, fail to hat-tip to the free software foundation, do not support the procedural programming paradigm (for when AbstractProductClassMakerFactories just won't cut it), use data from dubious sources, tend to use licenses that are incompatible with certain commercial uses, and are frankly short on features.

So, fearless user ... choose php-iban: the ethical, functional, forward-looking, low-hassle library of choice for IBAN and IIBAN processing. Choose to win! ;)

Work continues on providing a major update to include string internationalization. We are also seeking help from you, the user community, to uncover national BBAN format and checksum documentation from official sources, or failing that simply a large enough list of known valid BBANs from a given country that we can determine the checksum algorithms by deduction. The goal is to support querying (done!), checking, setting (fixing) national BBAN checksums in those countries who support them. We may later attempt something similar at the bank level, if appropriate. To help with the detective work, see issue #39 and issue #41.

Version 2.3.1 has been released.

• Fix paste error in Bosnia IANA code
• Additional tests for new country functions

Version 2.3.0 has been released.

• All IBAN country records can now be cross-referenced with their corresponding IANA and ISO3166-1 alpha-2 codes, if available

Version 2.2.0 has been released.

• Fully up to date with SEPA membership list. (Added new member for 2016, Andorra)
• Fully up to date with latest SWIFT IBAN registry PDF.
• Many fixes and new features since 2.1.0
• All users are encouraged to ugprade.

Version 2.1.9 has been released.

• Example field updates attempting to include what is possible from SWIFT IBAN registry PDF version #63. There persist significant issues with this release process.

Version 2.1.8 has been released.

• National BBAN checksum offset data for Belgium added.

Version 2.1.7 has been released.

• National BBAN checksum offset data added to registry. This can be queried via the new functions iban_get_nationalchecksum_part(), iban_country_get_nationalchecksum_start_offset() and iban_country_get_nationalchecksum_stop_offset() and their OO-wrapper equivalents $myIban->NationalChecksum(), $myCountry->NationalChecksumStartOffset() and $mycountry->NationalChecksumStopOffset(). Test and documentation updated. If you know anything about national checksum algorithms, please lend a hand at issue #39.

Version 2.1.6 has been released.

• OO wrapper and documentation updated for new strict machine_format_only validation.

Version 2.1.5 has been released.

• Additional strict machine_format_only mode for verify_iban() to close issue #22.

Version 2.1.4 has been released.

• Simplified a function using a php4+ builtin.

Version 2.1.3 has been released.

• Behavior of iban_to_human_format() has been fixed when passed input already containing spaces.
• OO-based tests are now executed following successful procedural tests.
• An additional test library for testing edge-case behavior in general functions is now executed following the main tests.

Version 2.1.2 has been released. All known unofficial IBAN country codes are now integrated. As well as minor documentation updates and a shortening of the reported name of Kosovo, this version adds:

• Ivory Coast (CI)
• Madagascar (MG)
• Mali (ML)
• Mozambique (MZ)
• Senegal (SN)
• Ukraine (UA)

Version 2.1.1 has been released. Currently unofficial IBAN country codes are being integrated, and the process remains ongoing. This version adds:

• Burkina Faso (BF)
• Burundi (BI)
• Cameroon (CM)
• Cape Verde (CV)
• Iran (IR)

Version 2.1.0 has been released.
Currently unofficial IBAN country codes are being integrated, and the process remains ongoing. A new flag has been created to check whether a country is an official, SWIFT-issued record or not. The following new countries have therefore been added.

• Algeria (DZ)
• Angola (AO)
• Benin (BJ)

Note also that the IIBAN (AA) record has been marked unofficial, and features listed in docs/TODO have been migrated to Github issues and that file deleted.

Version 2.0.1 has been released. This is to celebrate real testing, composer support, as well as finally catching up with changes. This version should be up to date with all registry changes to the present, including changes or additions to the countries:

• IIBAN (AA)
• Brazil (BR)
• Costa Rica (CR)
• Kazakhstan (KZ)
• Kosovo (XK)
• Kuwait (KW)
• Saint Barthelemy (BL)
• Saint Lucia (LC)
• Saint Martin (French Part) (MF)
• Sao Tome and Principe (ST)
• Timor Leste (TL)
• Turkey (TR)

Version 1.6.0 has been released. This version features more registry corrections (newly added territories with faulty data, bad checksums in sample IBANs, etc.) as well as enhanced testing routines, extended documentation, and corrected documentation. All users are advised to upgrade. We now have automated test script execution with Travis CI, to provide additional robustness for all committed code. This took longer than expected as unfortunately I picked the exact time Travis broke their build logs - https://www.traviscistatus.com/incidents/fcllblkclgmb - to see what all the fuss was about... proving again that cloud computing is just great for breaking things unexpectedly. Because they want to hide things, there was literally no debug output whatsoever, and I was led to believe this was my fault. Fellow programmers, behold: it is the dawning of the age of the mystical fail.

Version 1.5.0 has been released. There are no code changes, but we now have http://packagist.org/ integration, hopefully this triggers it to start working. If you use packagist, you can now add the library to your project by just running composer require globalcitizen/php-iban (thanks to @acoulton for pointing the way)

Version 1.4.9 has been released using the new Github-based release process. Hopefully this provides a solid anchor point for those bundling the library with other software. We also have a contributed composer metadata file to ease integration. New IBAN registry URLs integrated. Removed old SVN tag/trunk structure.

Corrected SWIFT URL to IBAN page. Emphasized mistranscription error support.

Finally, google has killed code.google.com and we have migrated to Github! Once the old trunk/tag structure (lingering from svn) is cleaned up and this document translated from the old wiki format to markdown, a new version will be issued.

Version 1.4.6 has been released:

• Fixes for Jordan and Qatar. Turns out both of them have broken TXT registry entries, PDF entries differ and the PDF is the one to go for (familiar story).
• Some further improvements.

Unfortunately, Google now requires code.google.com projects to use Google Drive. I tried to use Google Drive (sign up for a new account, jump through email hoops, get treated as a robot, learn stupid new touchy-feely-friendly interface, get meaningless error messages like 'Your sharing limit has been exceeded' (with 2x290KB files on a new account I was told to create) and lost patience entirely.

So for the moment, you'll just have to download using git, instead. I will migrate php-iban to Github shortly. Google really is a pain in the ass recently, what with all of this Google+ and Google Drive junk, ruining Picasa, ruining Sketchup by lack of attention, etc. What are they thinking?

Version 1.4.5 has been released:

• Addition of Jordan and Qatar
• Minor changes to documentation and support scripts.

Version 1.4.4 has been released:

• Fix SEPA status of Croatia (HR)
• Subsqeuent SEPA status audit based upon https://en.wikipedia.org/wiki/Single_Euro_Payments_Area turned up some other status issues (this information is not contained within the official IBAN registry)
  • Faroe Islands, Greenland, San Marino status fixed. Everything else apparently hunky dory.

The project source code repository has switched from svn (ugh) to git (yay!).

• This should make future changes less painful.

Version 1.4.3 has been released:

• Add Aland Islands (AX), part of Finland (FI) that is only documented in the SEPA status field of Finland and does not have its own entry or mention elsewhere in the IBAN registry document.
  • Consider but do not add either of the somewhat similar Canary Islands (CI) or Ceuta/Melilla (EA) - both minor territories of Spain (ES) - due to lack of any evidence of usage.
• Fix SEPA status for Spain (ES), Finland (FI), Porgual (PT) due to registry values being mixed with free text.
  • Document this and further issues with the official IBAN registry document, both as documentation in docs/COMEDY-OF-ERRORS and inline within the registry converter.
• Update human country name of Palestine to better mirror current registry document ("State of" is dropped as is the reigning style, so simply "Palestine" is presented)
• Updating an outstanding last modified date within the registry from the previous release

Version 1.4.2 has been released:

• Resolve issue #19: incorrect SEPA status of France/French territories due to a parser bug. (Thanks to the reporter)

Version 1.4.1 has been released:

• Requests
  • Attempts to intelligently calculate the 'account' portion of a BBAN based upon the (non-)presence of a branch ID and bank ID portion, by request (for Germany/Austria. Previously this was requested for the Netherlands, however this solution should fix results for everyone!)
  • Add 'IIBAN' prefix removal support to machine format conversion function
  • Add gmp disable flag ($__disable_iiban_gmp_extension=true;)
• Silence warnings on some PHP engine configurations
• Update Brazil record (minor)
• No longer redistribute IBAN registry in .txt format
• Improve inline documentation

Version 1.4.1 is still being prepared, squashing some bugs and updating the registry ... meanwhile, it has come to my attention that we have been featured in the Code Candy blog! http://www.codecandies.com/2012/05/30/no-exceptions/ Hooray for the German sense of humour! Hahah.

Version 1.4.0 has been released:

• Resolves an issue reported affecting the last few versions when attempting to generate a correct checksum for a checksum-invalid IBAN.
• Adds VERSION file, to include hard version information in source tree, by request.

Version 1.3.9 has been released:

• Resolves issue reported in 1.3.7 re-enables the more efficient PHP gmp library based checksum code (thanks to rpkamp)

Version 1.3.8 has been released:

• An error in checksum processing for some IBANs using the new gmp library based MOD97 routine (only affects users with php-iban 1.3.7 and the PHP gmp library enabled) has been reported. As an immediate workaround 1.3.8 is being released with the following changes: ** Code from 1.3.6 ** Registry from 1.3.7

Version 1.3.7 has been released:

• Added Brazil
• Added two new French overseas territories
• Reduced 'Moldova' to normalized short-form name
• Large CPU efficiency improvement in IBAN validation routine (16x if PHP gmp extension is installed, 5x otherwise. Special thanks to algorithmic contributor Chris and to engineers everywhere upholding the Germanic tradition of precision and efficiency! Alas, I am but part-German, for shame...)
• Minor internal/tool updates
• Some comedy of errors additions

Version 1.3.6 has been released:

• Update IIBAN format for latest IETF draft.

Version 1.3.5 has been released:

• Correct lack of support for lower case alphabetic characters (ie. non ECBS-compliant) in human to machine format conversion function.

Version 1.3.4 has been released:

• Add reference to the latest ECBS recommendations and include them in documentation.

Version 1.3.3 has been released:

• Very minor efficiency improvement.

Version 1.3.2 has been released:

• Registry updates
  • Added Palestinian Territories
  • Moldova fixed its format
  • Finland fixed its bank identifier location
  • Saudi Arabia - remove spurious trailing space in example

Version 1.3.1 has been released:

• New countries added
  • Azerbaijan (AZ)
  • Costa Rica (CR)
  • Guatemala (GT)
  • Moldova (MD)
  • Pakistan (PK)
  • British Virgin Islands (VG)
• Miscellaneous updates
  • Normalize/simplify examples (FI,PT,SA)
  • Normalize/simplify human country name (BH,LI,MK)
  • Documentation updates

Version 1.3.0 has been released. This release adds mistranscription error suggestion support.

Version 1.2.0 has been released. This release adds Internet International Bank Account Number (IIBAN) support, as per the current IIBAN Internet Draft at http://tools.ietf.org/html/draft-iiban-01

Version 1.1.2 has been released. This adds long open tags to the main library file in order to simplify deployment on many default PHP installations.

Version 1.1.1 has been released. This fixes a typo in a function call in the new OO wrapper. Non OO users do not need to upgrade.

Version 1.1.0 has been released. This version adds an object oriented wrapper library and related updates to documentation and test scripts. It is not critical for existing users to upgrade.

Version 1.0.0 has been released. This version includes the following changes:

• Support for the SEPA flag ("Is this country a member of the Single Euro Payments Area?"), both in the registry and with a new function iban_country_is_sepa($iban_country)
• Placeholder support for converting machine format IBAN to human format (simply adds a space every four characters) with the function iban_to_human_format($iban)
• Fixed a series of domestic example issues in the registry file that had been imported from SWIFT's own broken IBAN registry
• Normalised example fields in the registry to better facilitate use in automated contexts (Austria, Germany, etc.)
• Updated test code
• Added a significant amount of new documentation
• *Reorganised file layout•
• Moved to x.y.z format versioning and use of subversion 'tags' in conjunction with the 1.0.0 release.

Earlier in the month... Small maintenance release, not critical.

• The split() function has been replaced with explode() to prevent warnings (or error on very new PHP engines)
• Resolved an issue on PHP environments configured to display warnings would display a warning when an IBAN input to be validated did not include a prefix that was a valid IBAN country code. (Nobody should be running production PHP environments with such warnings enabled, anyway!)

• We are now well over 1000 downloads: not bad considering how specific this project is!
• If you are using php-iban, you are encouraged to join the [http://groups.google.com/group/php-iban-users mailing list]. This way you can get news of updates and announcements (very infrequent, but better than not knowing!)
• A new version has been released that fixes many important changes to the official registry, plus adds some new features.
  • Add New French Territories (GF,GP,MQ,RE) Older versions of the specification did not include the GF,GP,MQ,RE French territories, only the PF,TF,YT,NC,PM,WF French territories. The new territories have now been added to the database.
  • Add New Countries We welcome Bahrain (BH), Dominican Republic (DO), Khazakstan (KZ), United Arab Emirates (AE) to the database.
  • Format/example updates There have apparently been some minor format/example changes, these have been rolled in to existing countries.
  • Inclusion of altered IBAN_Registry.txt Errors and omissions have been found within the official IBAN_Registry.txt file, namely the exclusion of Khazakstan (KZ) and only partial information on Kuwait (KW), and errors in both of these countries' PDF specifications. This is SWIFT's fault: shame on them! I suspect they have changed staff recently. Anyway, a version of IBAN_Registry.txt with these problems solved is now distributed along with php-iban.
  • Fix for Tunisia Strangely I visited Tunisia during the revolution in January this year. Sorry to the Tunisian people for getting their IBAN format wrong! TN59 + 20 digits is the correct format. This is now included in the new registry file.
  • Fix for Albania The SWIFT format information was updated for Albania. (Did not affect validation, since this uses regular expressions which were already correct)
  • Additional and revised documentation Further documentation has been added to the project.
  • Automated IBAN_Registry.txt fix/conversion tool A new convert-registry tool has been added to the project that attempts to automatically normalise/fix problems with the official SWIFT .txt specification as much as possible. Note that this is not enough to get a good registry.txt file (the internal format used by php-iban) as SWIFT's .txt release excludes entire countries in the PDF specification. In addition, there are some errors in the PDF specification that need to be manually resolved at present. These can be seen resolved in the IBAN_Registry.txt file.

*We now have a http://groups.google.com/group/php-iban-users mailing list. Feel free to post your feedback, queries or suggestions - we'd love to know how you are using the library. To date, the project has reached over 400 downloads and still going strong, with more than one new user per day - a pretty good showing for a specialised library!

*version 12 has been released. The registry file has been improved, partly as a result of user reports and partly as a result of issues uncovered while performing automated tests against version 11.

• Corrected header row Two columns were not represented in the title (bban_length and iban_length). They have now been added.

• Fixes to registry entries for French Territories (PF,TF,YT,NC,PM,WF) French territories are not explicitly included in the SWIFT specification textfile. They were duplicated from France according to an unstructured comments against that entry. Example IBANs were then made for illustrative purposes by simply modifying the country prefix without regenerating the checksums. The IBAN examples included for these territories should now be correct.

• Gibraltar and Hungary (GI,HU) Fixed a bug where both territories had a superfluous colon appended to their regular expressions after initial document conversion, which was causing validation failures for all IBANs in those countries.

• Mauritius (MU) Corrected IBAN length expectation from 31 to 30.

• Sweden (SE) Example IBAN had been manually modified from IBAN specification example early in development and did not pass checksum. The IBAN official example has been restored.

• Tunisia (TN) Corrected improper validation strings caused by a bug in initial document conversion (IBAN format-specifier to regular-expression conversion function).

require_once('php-iban.php');
# ... your code utilising IBAN functions...

# Verify an IBAN number.
#  An optional second argument specifies $machine_format_only (default is false)
#  If true, the function will not tolerate unclean inputs
#   (eg. spaces, dashes, leading 'IBAN ' or 'IIBAN ', lower case)
#  If false (default), input can be in either:
#   - printed ('IIBAN xx xx xx...' or 'IBAN xx xx xx...'); or 
#   - machine ('xxxxx')
#  ... string formats.
#  Returns true or false.
if(!verify_iban($iban,$machine_format_only=false)) {
 # ...
}

# Check the checksum of an IBAN - code modified from Validate_Finance PEAR class
if(!iban_verify_checksum($iban)) {
 # ...
}

# Suggest what the user really meant in the case of transcription errors
$suggestions = iban_mistranscription_suggestions($bad_iban);
if(count($suggestions) == 1) {
 print "You really meant " . $suggestions[0] . ", right?\n";
}

# Find the correct checksum for an IBAN
$correct_checksum = iban_find_checksum($iban);

# Set the correct checksum for an IBAN
$fixed_iban = iban_set_checksum($iban);

# Convert an IBAN to machine format.  To do this, we
# remove IBAN from the start, if present, and remove
# non basic roman letter / digit characters
$machine_iban = iban_to_machine_format($iban);

# Convert an IBAN to human format.  To do this, we
# add a space every four characters.
$human_iban = iban_to_human_format($iban);

# Get the name of an IBAN country
$country_name = iban_country_get_country_name($iban_country);

# Get the domestic example for an IBAN country
$country_domestic_example = iban_country_get_domestic_example($iban_country);

# Get the BBAN example for an IBAN country
$country_bban_example = iban_country_get_bban_example($iban_country);

# Get the BBAN format (in SWIFT format) for an IBAN country
$country_bban_format_as_swift = iban_country_get_bban_format_swift($iban_country);

# Get the BBAN format (as a regular expression) for an IBAN country
$country_bban_format_as_regex = iban_country_get_bban_format_regex($iban_country);

# Get the BBAN length for an IBAN country
$country_bban_length = iban_country_get_bban_length($iban_country);

# Get the IBAN example for an IBAN country
$country_iban_example = iban_country_get_iban_example($iban_country);

# Get the IBAN length for an IBAN country
$country_iban_length = iban_country_get_iban_length($iban_country);

# Get the IBAN format (in SWIFT format) for an IBAN country
$country_iban_format_as_swift = iban_country_get_iban_format_swift ($iban_country);

# Get the IBAN format (as a regular expression) for an IBAN country
$country_iban_format_as_regex = iban_country_get_iban_format_regex($iban_country);

# Determine whether an IBAN country is a member of SEPA (Single Euro Payments Area)
if(!iban_country_is_sepa($iban_country)) {
 # ... do something xenophobic ...
}

# Get the bank ID start offset for an IBAN country
$country_bankid_start_offset = iban_country_get_bankid_start_offset($iban_country);

# Get the bank ID stop offset for an IBAN country
$country_bankid_stop_offset = iban_country_get_bankid_stop_offset($iban_country);

# Get the branch ID start offset for an IBAN country
$country_branchid_start_offset = iban_country_get_branchid_start_offset($iban_country);

# Get the branch ID stop offset for an IBAN country
$country_branchid_stop_offset = iban_country_get_branchid_stop_offset($iban_country);

# Get the registry edition for an IBAN country (note: IIBAN country 'AA' returns 'N/A')
$country_registry_edition = iban_country_get_registry_edition($iban_country);

# Determine whether an IBAN country is an official, SWIFT issued country record
if(!iban_country_get_country_swift_official($iban_country)) {
 # ... do something against decentralization ...
}

# Get the IANA code for an IBAN country
$country_iana = iban_country_get_iana($iban_country);

# Get the ISO3166-1 alpha-2 code for an IBAN country
$country_iso3166 = iban_country_get_iso3166($iban_country);

# Get an array of all the parts from an IBAN
$iban_parts = iban_get_parts($iban);

# Get the country part from an IBAN
$iban_country = iban_get_country_part($iban);

# Get the BBAN part from an IBAN
$bban = iban_get_bban_part($iban);

# Get the Bank ID (institution code) from an IBAN
$bank = iban_get_bank_part($iban);

# Get the Branch ID (sort code) from an IBAN
#  (NOTE: only available for some countries)
$sortcode = iban_get_branch_part($iban);

# Get the (branch-local) account ID from an IBAN
#  (NOTE: only available for some countries)
$account = iban_get_account_part($iban);

# Get the checksum part from an IBAN
$checksum = iban_get_checksum_part($iban);

# Get the national checksum part from an IBAN (if it exists)
$checksum = iban_get_nationalchecksum_part($iban);

# Perform MOD97-10 checksum calculation
$mod97_10 = iban_mod97_10($string);

# Character substitution required for IBAN MOD97-10 checksum validation/generation
$mod97_internal_stuff = iban_checksum_string_replace($s);

OO use is discouraged as there is a present-day trend to overuse the model. However, if you prefer OO PHP then by all means use the object oriented wrapper, described below.

require_once('oophp-iban.php');
# ... your code utilising object oriented PHP IBAN functions...

# Example instantiation
$iban = 'AZ12345678901234'
$myIban = new IBAN($iban);

# Verify an IBAN number.
#  Tolerates spaces, prefixes "IBAN ...", dashes, lowercase input, etc.
#  Returns true or false.
if(!$myIban->Verify()) {
 # ...
}
# Verify an IBAN number in machine format only.
#  Does not tolerate lowercase input, separators, whitespace or prefixes.
#  Returns true or false.
if(!$myIban->VerifyMachineFormatOnly()) {
 # ...
}

# Check the checksum of an IBAN - code modified from Validate_Finance PEAR class
if(!$myIban->VerifyChecksum()) {
 # ...
}

# Suggest what the user really meant in the case of mistranscription errors
$suggestions = $badIban->MistranscriptionSuggestions();
if(count($suggestions)==1) {
 print "You really meant " . $suggestions[0] . ", right?\n";
}

# Find the correct checksum for an IBAN
$correct_checksum = $myIban->FindChecksum();

# Set the correct checksum for an IBAN
$fixed_iban = $myIban->SetChecksum()

# Convert an IBAN to machine format.  To do this, we
# remove IBAN from the start, if present, and remove
# non basic roman letter / digit characters
$machine_iban = $myIban->MachineFormat();

# Convert an IBAN to human format.  To do this, we
# add a space every four characters.
$human_iban = $myIban->HumanFormat();

# To list countries, use the IBAN Class...
$myIban->Countries();

# ... everything else is in the IBANCountry class.

# Example instantiation
$countrycode = 'DE';
$myCountry = new IBANCountry($countrycode);

# Get the country code of an IBAN country
$country_code = $myCountry->Code();

# Get the name of an IBAN country
$country_name = $myCountry->Name();

# Get the domestic example for an IBAN country
$country_domestic_example = $myCountry->DomesticExample();

# Get the BBAN example for an IBAN country
$country_bban_example = $myCountry->BBANExample();

# Get the BBAN format (in SWIFT format) for an IBAN country
$country_bban_format_as_swift = $myCountry->BBANFormatSWIFT();

# Get the BBAN format (as a regular expression) for an IBAN country
$country_bban_format_as_regex = $myCountry->BBANFormatRegex();

# Get the BBAN length for an IBAN country
$country_bban_length = $myCountry->BBANLength();

# Get the IBAN example for an IBAN country
$country_iban_example = $myCountry->IBANExample();

# Get the IBAN length for an IBAN country
$country_iban_length = $myCountry->IBANLength();

# Get the IBAN format (in SWIFT format) for an IBAN country
$country_iban_format_as_swift = $myCountry->IBANFormatSWIFT();

# Get the IBAN format (as a regular expression) for an IBAN country
$country_iban_format_as_regex = $myCountry->IBANFormatRegex();

# Determine whether an IBAN country is a member of SEPA (Single Euro Payments Area)
if(!$myCountry->IsSEPA()) {
 # ... do something xenophobic ...
}

# Get the bank ID start offset for an IBAN country
$country_bankid_start_offset = $myCountry->BankIDStartOffset();

# Get the bank ID stop offset for an IBAN country
$country_bankid_stop_offset = $myCountry->BankIDStopOffset();

# Get the branch ID start offset for an IBAN country
$country_branchid_start_offset = $myCountry->BranchIDStartOffset();

# Get the branch ID stop offset for an IBAN country
$country_branchid_stop_offset = $myCountry->BranchIDStopOffset();

# Get the national checksum start offset for an IBAN country
$country_nationalchecksum_start_offset = $myCountry->NationalChecksumStartOffset();

# Get the national checksum stop offset for an IBAN country
$country_nationalchecksum_stop_offset = $myCountry->NationalChecksumStopOffset();

# Get the registry edition for an IBAN country (note: IIBAN country 'AA' returns 'N/A')
$country_registry_edition = $myCountry->RegistryEdition();

# Determine whether an IBAN country is an official, SWIFT issued country record
if(!$myCountry->SWIFTOfficial()) {
 # ... do something against decentralization ...
}

# Get the IANA code for an IBAN country
$country_iana = $myCountry->IANA();

# Get the ISO3166-1 alpha-2 code for an IBAN country
$country_iso3166 = $myCountry->ISO3166();

# Get an array of all the parts from an IBAN
$iban_parts = $myIban->Parts();

# Get the country part from an IBAN
$iban_country = $myIban->Country();

# Get the checksum part from an IBAN
$checksum = $myIban->Checksum();

# Get the BBAN part from an IBAN
$bban = $myIban->BBAN();

# Get the Bank ID (institution code) from an IBAN
$bank = $myIban->Bank();

# Get the Branch ID (sort code) from an IBAN
#  (NOTE: only available for some countries)
$sortcode = $myIban->Branch();

# Get the (branch-local) account ID from an IBAN
#  (NOTE: only available for some countries)
$account = $myIban->Account();

# Get the national checksum part from an IBAN
#  (NOTE: only available for some countries)
$checksum = $myIban->NationalChecksum();

See for yourself how our approach and features compare favourably with all of these libraries...