I need a validation step that confirms format correctness without implying the bank account actually exists.

This feature adds a validation step that checks whether a bank account identifier is syntactically well-formed. It helps users catch formatting errors early while making it clear that the check does not confirm the account exists or can receive funds.

This feature provides a dedicated validation step that verifies the format correctness of a bank account identifier (for example, length, allowed characters, and checksum rules where applicable). Its purpose is to prevent avoidable failures by catching typos and structural errors before submission or storage. The validation result is explicitly scoped to formatting only and does not indicate that the account is active, reachable, or owned by a specific party. This distinction helps avoid misleading “verified” messaging and reduces the risk of users assuming an account will accept transfers. The step can be used in data entry flows to give immediate feedback, or as part of backend processing to reject malformed inputs consistently. It is useful when collecting bank details during onboarding, invoicing, payroll setup, or beneficiary management. The feature improves data quality and reduces downstream support cases caused by simple input mistakes. It also supports clearer compliance and user communication by separating format validation from any existence or ownership checks. Teams can use the result to guide user prompts such as “Check the account number format” rather than “Account confirmed.”