The digitalization of contractual relationships in Brazil has accelerated rapidly over the past decade. Along with this shift, debates have grown around the legal validity of electronic contracts, especially those executed outside the formal standards of ICP-Brasil, which stands for Brazilian Public Key Infrastructure \u2014 the country\u2019s official digital certification framework.<\/p>\n
ICP-Brasil, maintained by the National Institute of Information Technology (ITI), is Brazil\u2019s governmental system that issues qualified digital certificates with a legal presumption of authenticity. When it was created through Provisional Measure 2.200-2\/2001, it included a frequently overlooked provision: Article 10, Paragraph 2, which expressly allows other methods of proving the authorship and integrity of electronic documents, so long as both parties agree to them. This rule has served as the foundation for a growing body of case law from the Superior Court of Justice (STJ), which has become increasingly open to recognizing different forms of digital authentication.<\/p>\n
The recent ruling in Special Appeal (REsp) 2,197,156 by the STJ\u2019s Third Panel, concluded in March 2026, represents the most precise and up\u2011to\u2011date development in this area.<\/p>\n
<\/p>\n
In a unanimous decision, the Third Panel confirmed the validity of a loan agreement executed through a private electronic-signature platform not accredited by ICP-Brasil. Minister Nancy Andrighi, the reporting justice, rejected the notion of automatic invalidity and established two central criteria for analyzing these types of contracts.<\/p>\n
The first criterion concerns the authentication method used. Certification through ICP-Brasil is not<\/strong> a mandatory requirement for validity. Law 14.063\/2020, which regulates the use of electronic signatures in interactions with public entities and private transactions, recognizes multiple levels of evidentiary strength. Advanced electronic signatures \u2014 such as those based on tokens, facial biometrics, geolocation and IP address records \u2014 fall within this regulatory framework and carry legal validity when used properly.<\/p>\n The second criterion addresses challenges to the signature after the contract has been executed. The court held that a generic objection raised later by one of the parties, without concrete evidence suggesting fraud, is insufficient to invalidate the agreement. The decision aligns with STJ\u2019s Binding Theme 1,061, reaffirming that when a consumer contests the authenticity of a signature in a banking contract, the financial institution must prove that the contract was executed properly. The burden of proof remains with the creditor. What the court rejected was the idea that any signature not certified by ICP-Brasil should automatically be viewed with suspicion, regardless of the evidence presented.<\/p>\n <\/p>\n Among the most relevant aspects of the precedent are:<\/p>\n <\/p>\n For fintechs, financial institutions and companies whose operations rely on digital contracts, this precedent creates tangible effects on contractual governance. The legal discussion shifts away from whether a formal certificate exists and toward the quality of the authentication process: its ability to record consent, ensure the document\u2019s integrity and reliably attribute authorship.<\/p>\n Companies already using advanced electronic-signature platforms gain reinforced legal certainty. Those that have not yet structured their digital authentication procedures properly should view this ruling as a warning: certain minimum conditions must be met to sustain contract validity in possible disputes.<\/p>\n The regulatory and judicial landscape is moving consistently in one direction: Brazil\u2019s legal system is embracing widespread recognition of digital contracting, while still requiring robust evidence of the parties\u2019 intent.<\/p>\n <\/p>\n Companies that work with electronic contracts should consider:<\/p>\nPoints of Attention<\/strong><\/h3>\n
\n
Impacts for Companies and Fintechs<\/strong><\/h3>\n
Next Steps<\/strong><\/h3>\n