RBI: A solution looking for more problems: Here’s why RBI’s data localisation mandate must be reviewed.

Share via:


Synopsis

The mandate was issued without inputs from stakeholders and the lack of customary consultation meant that alternative solutions to enable regulatory access remain unexplored. Further, it puts the NCPI, Indian banks, and fintech firms operating in foreign jurisdictions at the risk of reciprocal measures.

In the summer of 2018, the Reserve Bank of India (RBI) said payment firms in India should ensure that their data is stored exclusively on local servers. The banking regulator also set a six-month deadline to comply with its April circular aimed at gaining access to payments data that may be territorially beyond its jurisdiction. But more than half a decade since that announcement, RBI’s data localisation mandate continues to be a subject of

  • FONT SIZE
  • SAVE
  • PRINT
  • COMMENT

New Feature
Refer & Earn

Uh-oh! This is an exclusive story available for selected readers only.

Worry not. You’re just a step away.



Source link

Disclaimer

We strive to uphold the highest ethical standards in all of our reporting and coverage. We StartupNews.fyi want to be transparent with our readers about any potential conflicts of interest that may arise in our work. It’s possible that some of the investors we feature may have connections to other businesses, including competitors or companies we write about. However, we want to assure our readers that this will not have any impact on the integrity or impartiality of our reporting. We are committed to delivering accurate, unbiased news and information to our audience, and we will continue to uphold our ethics and principles in all of our work. Thank you for your trust and support.

Team SNFYI
Hi! This is Admin.

Popular

More Like this

RBI: A solution looking for more problems: Here’s why RBI’s data localisation mandate must be reviewed.


Synopsis

The mandate was issued without inputs from stakeholders and the lack of customary consultation meant that alternative solutions to enable regulatory access remain unexplored. Further, it puts the NCPI, Indian banks, and fintech firms operating in foreign jurisdictions at the risk of reciprocal measures.

In the summer of 2018, the Reserve Bank of India (RBI) said payment firms in India should ensure that their data is stored exclusively on local servers. The banking regulator also set a six-month deadline to comply with its April circular aimed at gaining access to payments data that may be territorially beyond its jurisdiction. But more than half a decade since that announcement, RBI’s data localisation mandate continues to be a subject of

  • FONT SIZE
  • SAVE
  • PRINT
  • COMMENT

New Feature
Refer & Earn

Uh-oh! This is an exclusive story available for selected readers only.

Worry not. You’re just a step away.



Source link

Disclaimer

We strive to uphold the highest ethical standards in all of our reporting and coverage. We StartupNews.fyi want to be transparent with our readers about any potential conflicts of interest that may arise in our work. It’s possible that some of the investors we feature may have connections to other businesses, including competitors or companies we write about. However, we want to assure our readers that this will not have any impact on the integrity or impartiality of our reporting. We are committed to delivering accurate, unbiased news and information to our audience, and we will continue to uphold our ethics and principles in all of our work. Thank you for your trust and support.

Website Upgradation is going on for any glitch kindly connect at office@startupnews.fyi

Team SNFYI
Hi! This is Admin.

More like this

Is the 2025 Altseason Here? Experts’ Insights 

Bitcoin (BTC) price has recorded a new all-time...

Google’s worst nightmare? OpenAI’s new AI web browser is...

OpenAI is preparing to roll out an artificial...

AI gone too far: xAI’s Grok draws flak for...

Elon Musk-led xAI's artificial intelligence chatbot Grok was...

Popular

Upcoming Events

iptvdfgdfs iptvdfgdfs iptvdfgdfs iptvdfgdfs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs fgs