A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 6

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 7

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 8

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 9

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 10

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 11

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 284

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 291

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 306

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 316

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 317

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 318

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 319

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 377

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 110

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Session cannot be started after headers have already been sent

Filename: Session/Session.php

Line Number: 143

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

NRIPage | Articles | RBI Launches WhatsApp Channel to Share Verified Financial Info and Fight Fake News | Get Articles For Men. Style, Grooming, and Empowerment - NRI Page
Edit

RBI Launches WhatsApp Channel to Share Verified Financial Info and Fight Fake News

RBI Launches WhatsApp Channel to Share Verified Financial Info and Fight Fake News

The Reserve Bank of India (RBI) has introduced a new initiative to connect more directly with the public by launching an official WhatsApp channel. This development is part of the central bank’s broader commitment to enhancing public awareness and making important financial and banking information accessible to every citizen, particularly those in rural and semi-urban areas who might not have regular access to official websites or traditional media. The initiative falls under the RBI’s ongoing campaign titled ‘RBI Kehta Hai’ (RBI Says), which has been running across various platforms including television, newspapers, digital media, and SMS. With the addition of WhatsApp—a widely used messaging application in India—the RBI aims to reach a broader segment of the population in a quick and user-friendly manner.

This strategic move is designed to offer users verified updates on financial topics through a platform they already use daily. Given the rapid spread of misinformation and financial frauds online, the RBI has recognized the importance of providing authentic content through a channel that is both trusted and easily accessible. The WhatsApp channel will deliver timely updates and information to help users make informed financial decisions and avoid scams. According to the RBI's official statement released on April 4, the primary objective of launching the WhatsApp channel is to disseminate verified content related to banking rules, customer rights, safe digital practices, and debunking common financial myths or rumors.

Through its official WhatsApp account, operated from the verified number 9999 041 935, the RBI will share content that supports financial literacy and digital awareness. The account is verified, which means users will see a green checkmark next to the account name, assuring them of its authenticity. The initiative is expected to boost trust among the public and help build a more secure financial environment. Key areas of focus for this WhatsApp initiative include digital banking safety, fraud prevention tips, understanding customer rights, updates on banking policies and procedures, and factual clarification on any misinformation that might be spreading through unofficial channels. This is especially significant considering the number of fake messages and scams that often make rounds on social media platforms.

For people who are not in the habit of browsing the RBI website or reading financial news regularly, this WhatsApp channel offers a simple yet effective way to stay informed. It enables them to receive concise, actionable information right in their message inbox, which can significantly enhance their understanding of financial systems and safety measures. To subscribe to the RBI’s WhatsApp channel, users can scan a QR code available on the official RBI website or the bank’s social media handles. Scanning the code will lead users directly to the RBI’s WhatsApp channel. They can then tap the “Join” button to begin receiving messages.

By using WhatsApp, the RBI is leveraging one of the most powerful and widely used communication tools in India. With over 500 million users in the country, WhatsApp serves as an ideal platform to spread financial awareness. The move is expected to bring vital financial education into the daily digital habits of millions of Indians, helping them safeguard themselves from digital frauds and misinformation. In a time when digital transactions are becoming the norm, the RBI’s initiative is timely and necessary. It not only aligns with the government’s vision of a digitally empowered society but also strengthens the regulatory ecosystem by promoting transparency and proactive communication.

The Reserve Bank’s effort to embrace digital tools for public outreach reflects its evolving role in a modern financial landscape where communication, accessibility, and trust are more important than ever. The WhatsApp channel will serve as a bridge between the common user and the financial authority, empowering citizens with knowledge and confidence to manage their financial activities securely. This step also signifies a major shift in how central banks around the world can use social messaging platforms to directly engage with the public and reinforce regulatory frameworks. Through initiatives like this, the RBI is setting an example of how institutions can innovate in public communication to address current challenges like financial scams, misinformation, and lack of digital awareness.

What is your response?

joyful Joyful 0%
cool Cool 0%
thrilled Thrilled 0%
upset Upset 0%
unhappy Unhappy 0%
AD
AD