{"formats":[{"name":"JSON","format":"json","url":"\/downloads\/2025\/code-json\/8.4A-201.json"},{"name":"Plain Text","format":"text","url":"\/downloads\/2025\/code-text\/8.4A-201.txt"},{"name":"XML","format":"xml","url":"\/downloads\/2025\/code-xml\/8.4A-201.xml"},{"name":"HTML","format":"html","url":"\/downloads\/2025\/code-html\/8.4A-201.html"}],"law_id":72906,"edition_id":1,"section_id":72906,"structure_id":14106,"section_number":"8.4A-201","catch_line":"Security procedure","history":"1990, c. 9; 2024, c. 652.","full_text":"&#8220;Security procedure&#8221; 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.","order_by":null,"text":{"0":{"id":262649,"text":"&#8220;Security procedure&#8221; 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.","type":"section","prefixes":[""],"prefix":"","entire_prefix":"","prefix_anchor":"","level":1}},"ancestry":[{"id":14106,"edition_id":1,"name":"Issue and Acceptance of Payment Order","identifier":"2","label":"part","depth":2,"order_by":1,"parent_id":13362,"metadata":{},"date_created":"2026-06-26 03:46:53","date_modified":"2026-06-26 03:46:53","permalink":{"id":283223,"object_type":"structure","relational_id":14106,"identifier":"2","token":"8.4A\/2","url":"\/8.4A\/2\/","edition_id":1,"permalink":0,"preferred":1}},{"id":13362,"edition_id":1,"name":"Commercial Code \u2014 Funds Transfers","identifier":"8.4A","label":"title","depth":1,"order_by":1,"parent_id":null,"metadata":{},"date_created":"2026-06-26 03:44:42","date_modified":"2026-06-26 03:44:42","permalink":{"id":283187,"object_type":"structure","relational_id":13362,"identifier":"8.4A","token":"8.4A","url":"\/8.4A\/","edition_id":1,"permalink":0,"preferred":1}}],"structure_contents":[{"id":72906,"structure_id":14106,"section_number":"8.4A-201","catch_line":"Security procedure","url":"\/8.4A-201\/","token":"8.4A\/2\/8.4A-201","metadata":false},{"id":81942,"structure_id":14106,"section_number":"8.4A-202","catch_line":"Authorized and verified payment orders","url":"\/8.4A-202\/","token":"8.4A\/2\/8.4A-202","metadata":false},{"id":68248,"structure_id":14106,"section_number":"8.4A-203","catch_line":"Unenforceability of certain verified payment orders","url":"\/8.4A-203\/","token":"8.4A\/2\/8.4A-203","metadata":false},{"id":78010,"structure_id":14106,"section_number":"8.4A-204","catch_line":"Refund of payment and duty of customer to report with respect to unauthorized payment order","url":"\/8.4A-204\/","token":"8.4A\/2\/8.4A-204","metadata":false},{"id":77755,"structure_id":14106,"section_number":"8.4A-205","catch_line":"Erroneous payment orders","url":"\/8.4A-205\/","token":"8.4A\/2\/8.4A-205","metadata":false},{"id":64984,"structure_id":14106,"section_number":"8.4A-206","catch_line":"Transmission of payment order through funds-transfer or other communication system","url":"\/8.4A-206\/","token":"8.4A\/2\/8.4A-206","metadata":false},{"id":59923,"structure_id":14106,"section_number":"8.4A-207","catch_line":"Misdescription of beneficiary","url":"\/8.4A-207\/","token":"8.4A\/2\/8.4A-207","metadata":false},{"id":65335,"structure_id":14106,"section_number":"8.4A-208","catch_line":"Misdescription of intermediary bank or beneficiary's bank","url":"\/8.4A-208\/","token":"8.4A\/2\/8.4A-208","metadata":false},{"id":78930,"structure_id":14106,"section_number":"8.4A-209","catch_line":"Acceptance of payment order","url":"\/8.4A-209\/","token":"8.4A\/2\/8.4A-209","metadata":false},{"id":55237,"structure_id":14106,"section_number":"8.4A-210","catch_line":"Rejection of payment order","url":"\/8.4A-210\/","token":"8.4A\/2\/8.4A-210","metadata":false},{"id":85898,"structure_id":14106,"section_number":"8.4A-211","catch_line":"Cancellation and amendment of payment order","url":"\/8.4A-211\/","token":"8.4A\/2\/8.4A-211","metadata":false},{"id":69041,"structure_id":14106,"section_number":"8.4A-212","catch_line":"Liability and duty of receiving bank regarding unaccepted payment order","url":"\/8.4A-212\/","token":"8.4A\/2\/8.4A-212","metadata":false}],"next_section":{"id":81942,"structure_id":14106,"section_number":"8.4A-202","catch_line":"Authorized and verified payment orders","url":"\/8.4A-202\/","token":"8.4A\/2\/8.4A-202","metadata":false},"metadata":false,"official_url":"https:\/\/law.lis.virginia.gov\/vacode\/8.4A-201\/","history_text":"<p>This law was first created in 1990. The record of its establishment is cataloged in chapter 9 of that year\u2019s edition of \u201cActs of Assembly,\u201d the annual state publication listing all changes made to the Code of Virginia in that year. Unfortunately, the 1990 \u201cActs\u201d aren\u2019t available online. It has been modified 1 time. Those modifications are cataloged by \u201cThe Acts of Assembly,\u201d a state publication, by year and chapter. Those modifications that can be read on the General Assembly\u2019s website will be linked accordingly. That modification is as follows: in 2024, chapter <a href=\"https:\/\/legacylis.virginia.gov\/cgi-bin\/legp604.exe?241+ful+CHAP0652\">652<\/a>.<\/p>","references":[{"id":76749,"section_number":"8.4A-105","catch_line":"Other definitions","order_by":null,"url":"\/8.4A-105\/"}],"refers_to":false,"permalink":{"id":283225,"object_type":"law","relational_id":72906,"identifier":"8.4A-201","token":"8.4A\/2\/8.4A-201","url":"\/8.4A-201\/","edition_id":1,"permalink":0,"preferred":1},"url":"\/8.4A-201\/","token":"8.4A\/2\/8.4A-201","dublin_core":{"Title":"Security procedure","Type":"Text","Format":"text\/html","Identifier":"\u00a7 8.4A-201","Relation":"Code of Virginia"},"html":"\n\t\t\t\t\t\t<section><p>&#8220;Security procedure&#8221; means a procedure established by agreement of a customer and a receiving bank for the purpose of (i) verifying that a payment <span class=\"dictionary\">order<\/span> or communication amending or cancelling a payment <span class=\"dictionary\">order<\/span> is that of the customer, or (ii) detecting error in the transmission or the content of the payment <span class=\"dictionary\">order<\/span> 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 <span class=\"dictionary\">order<\/span> or communication with an authorized specimen signature of the customer or requiring a payment <span class=\"dictionary\">order<\/span> to be sent from a known email address, IP address, or telephone number is not by itself a security procedure.<\/p><\/section>","plain_text":"                                 CODE OF VIRGINIA\n\nSECURITY PROCEDURE (\u00a7 8.4A-201)\n\n&#8220;Security procedure&#8221; means a procedure established by agreement of a\ncustomer and a receiving bank for the purpose of (i) verifying that a payment\norder or communication amending or cancelling a payment order is that of the\ncustomer, or (ii) detecting error in the transmission or the content of the\npayment order or communication. A security procedure may impose an obligation on\nthe receiving bank or the customer and may require the use of algorithms or\nother codes, identifying words, numbers, symbols, sounds, biometrics,\nencryption, callback procedures, or similar security devices. Comparison of a\nsignature on a payment order or communication with an authorized specimen\nsignature of the customer or requiring a payment order to be sent from a known\nemail address, IP address, or telephone number is not by itself a security\nprocedure.\n\nHISTORY: 1990, c. 9; 2024, c. 652.","edition":{"id":1,"name":"2025","slug":"2025","date_created":"2026-06-21 22:39:22","date_modified":"2026-06-21 22:39:22","current":1,"order_by":1,"last_import":null}}