The starting point for validating bank account details depends upon the format that they are supplied in:
In a number of countries, such as Luxembourg and Latvia, the IBAN is used as the domestic account number format. For these countries, to perform full validation, you must pass the IBAN as the BBAN. This is because Bank Wizard does not validate the bank and branch details against the IBAN, only the BBAN.
Where the user enters an IBAN into your business application, use Bank Wizard to validate the IBAN.
You must now check for any conditions that have been returned.
If there are any error conditions, the IBAN has failed validation and you should reject the entered details.
If no conditions are returned, Bank Wizard converts the IBAN to the BBAN.
Conditions that can be returned:
Make sure the country specified in the IBAN is a country supported by your application. If not, stop all processing and reject the details.
Where the user enters the BBAN or Bank Wizard has retrieved the BBAN after validating the IBAN, use Bank Wizard to validate the BBAN.
You must now check for any conditions that have been returned when validating the BBAN.
If there are any Error conditions, the validation has failed and you should reject the entered details.
Conditions that can be returned:
Depending on the type of transaction you are validating the account details for, some warning or information conditions may need to be treated as errors. For example, if you are setting up a Direct Debit, you must reject the details if "Sort code does not support Direct Debit transactions" is returned. However you can ignore this condition if this is a Direct Credit transaction.
Check for the specific warning and information conditions determined by your business process. If any of these conditions exist, the validation has failed and you should reject the entered details.
Conditions that can be returned:
If Bank Wizard cannot confirm that the account details are correct, for instance if there are no modulus check rules for this bank or branch code, to validate the details ask the user to enter the details again.
|
You do not need a manual reconfirmation if the BBAN was decomposed from the IBAN because the account details have been generated by Bank Wizard. |
If you ask the user to re-enter the account details there is no need to re-validate them using Bank Wizard. You should compare them against the original account details.
If the details are different, warn the user and reject the details. You can then re-prompt for the entry of the BBAN (and BIC), or the IBAN and start the process again as described in Validate the BBAN (and BIC) and Validate the IBAN.
You can determine if the account details have been transposed by checking for the condition "Account details were not in standard form and have been transposed". Where this condition has been set, retrieve the transposed values from Bank Wizard.
Condition to check for: Warning 1 (BWG_W_TRANSPOSED)
Store the transposed values within your business application for use when making payments. Ideally, you should also retain the original values for confirmation purposes or of you need to discuss the payment with the customer.
Does the business application require an IBAN for making a payment?
|
If you started with the IBAN, ignore steps 12 and 13. |
If the business application needs an IBAN, then use Bank Wizard to form and retrieve the IBAN.
|
If you will also be verifying the details using Bank Wizard Absolute, omit steps 14 and 15. |
Check the number of bank records that have been returned. If multiple branches have been returned, display a list of the branches so that the user can select the correct one.
When the correct branch has been identified (or only one match is found) display the branch details to the user.
The user should then confirm that the branch details are correct.
If you are licensed for Bank Wizard Absolute, you should now follow the Bank Wizard Absolute flowchart to verify the account and personal details.