✓ O.C.G.A. (archive.org 2024 item): print volumes of 2004-2024, per-volume vintage; older volumes partly replaced by 2019 Release 73 text; no 2025 or 2026 Acts
Code text and O.C.G.A. statutory annotations on this page reflect the 2019 Official Code of Georgia Annotated (Public.Resource.Org Release 73, 2019-08-21; public domain per Georgia v. Public.Resource.Org, 2020). The Syfert case-law annotations in Notes of Decisions, below, are current.
“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 canceling 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 require the use of algorithms or other codes, identifying words or numbers, 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 is not by itself a security procedure.
History
Code 1981, § 11-4A-201, enacted by Ga. L. 1992, p. 2685, § 4.
Annotations
RESEARCH REFERENCES U.L.A. Uniform Commercial Code (U.L.A.) § 4A-201.
Zeal Global Servs. Private Ltd. v. Suntrust Bank, 508 F. Supp. 3d 1303 (N.D. Ga. 2020). · cites it 2דO.C.G.A. § 11-4A-201, cmt. As a result, to “resort to principles of law or equity outside of Article 4A [would] not [be] appropriate to create rights, duties and liabilities inconsistent with those stated in this Article.”
Annotations are extracted automatically from the opinions in the
Syfert caselaw corpus and ranked by authority, recency, and
treatment. Dots show Syfertize treatment of the citing case itself.