Cristina Junqueira explained the origin of the incorrect message, acknowledged the disruption caused, and stated that the issue has already been corrected.
The co-founder of Nubank, Cristina Junqueira, publicly admitted the error that led to the sending of an incorrect notification about a supposed extrajudicial liquidation of the bank. The message was sent on Friday, June 12, 2026, mentioned procedures linked to the Credit Guarantee Fund (FGC), and caused concern among the institution’s clients.
The central point of the episode was the executive’s own statement. On social media, Junqueira classified the failure as “bizarre”, acknowledged the disruption caused by the improper communication, and explained that the alert stemmed from an internal operational problem, already addressed by the Nubank team.
What Cristina Junqueira said about the error
Cristina Junqueira stated that the notification was sent after an employee submitted a pull request, a common procedure in software development to suggest code changes. According to her, this process accidentally triggered an internal protocol used in emergency situations.
-
Levi’s sees FIFA cover its logo at the 2026 World Cup, joins in the fun without losing style, and turns a white cloth into marketing that goes viral on social media.
-
Bill Gates is called to explain contacts with Jeffrey Epstein in a closed-door deposition that may reveal behind-the-scenes details of one of the most sensitive investigations in the US.
-
Coca-Cola prepares a mega-operation in Brazil with 11 factories and 53 distribution centers to turn the 2026 World Cup into a billion-dollar consumption race.
-
Electrolux emerged from a Swedish merger in 1919 and conquered homes worldwide with innovative refrigerators, stoves, and washing machines.
“Man, really bizarre, but that’s what happened, an operational error,” declared the co-founder while explaining the origin of the failure.
The executive also apologized to the clients who received the incorrect information. In her statement, she said that the message reached a small portion of the user base, estimated at about 20,000 clients, as reported by media outlets such as UOL, Seu Dinheiro, BP Money, and Bloomberg Línea.
Message about liquidation scared clients
The notification sent by mistake mentioned a supposed extrajudicial liquidation of Nubank. The alert also cited guidelines related to the FGC, a mechanism known for guaranteeing certain amounts in specific cases involving financial institutions.
Due to involving sensitive terms, the message immediately raised doubts among users. Nevertheless, Nubank reinforced that the communication did not correspond to the company’s operational reality and that there is no liquidation process involving the institution.
According to the company, services continued to function normally after the mistaken sending. The failure, therefore, was treated as a one-off communication episode, without impact on the bank’s operations.
Apology and Internal Measures
Cristina Junqueira acknowledged the impact of the situation and stated that the episode caused discomfort within the company itself. “We were upset about this,” declared the co-founder when commenting on the internal reaction to the error.
The executive also informed that Nubank acted quickly to correct the problem and adopted measures to prevent similar situations from occurring again. For her, the case served as an internal learning experience to reinforce control processes in sensitive communications sent to clients.
Founder’s Statement Focuses the Repercussion
Cristina Junqueira’s statement became the main point of the repercussion because it brought a direct admission of the failure, a technical explanation of the origin of the problem, and a public apology to the affected clients.
By admitting the error and detailing what happened, the co-founder sought to reduce doubts about the notification and reinforce that the alert did not reflect the real situation of Nubank. The bank, in turn, maintained that operations continue to function normally and that the episode has already been corrected internally.

Be the first to react!