§ 8.4A-201 Security procedure
“Security procedure” means a procedure established by agreement of a customer and a receiving bank for the purpose of (i) verifying that a payment order or communication amending or cancelling a payment order is that of the customer, or (ii) detecting error in the transmission or the content of the payment order or communication. A security procedure may impose an obligation on the receiving bank or the customer and may require the use of algorithms or other codes, identifying words, numbers, symbols, sounds, biometrics, encryption, callback procedures, or similar security devices. Comparison of a signature on a payment order or communication with an authorized specimen signature of the customer or requiring a payment order to be sent from a known email address, IP address, or telephone number is not by itself a security procedure.
History
This law was first created in 1990. The record of its establishment is cataloged in chapter 9 of that year’s edition of “Acts of Assembly,” the annual state publication listing all changes made to the Code of Virginia in that year. Unfortunately, the 1990 “Acts” aren’t available online. It has been modified 1 time. Those modifications are cataloged by “The Acts of Assembly,” a state publication, by year and chapter. Those modifications that can be read on the General Assembly’s website will be linked accordingly. That modification is as follows: in 2024, chapter 652.
1990, c. 9; 2024, c. 652.