Cloud Hosting
Indian Fintech Parked Payment Data in Mumbai S3 Buckets
RBI pins payment data to India, but S3 storage in Mumbai hyperscaler regions took the load, while DPDP lets most SaaS data travel.
PhonePe processed more than 10.33 billion UPI payments in April 2026, according to NPCI’s monthly tables, and the files those payments leave behind now live in object storage inside Indian cloud regions. The Reserve Bank of India’s 6 April 2018 storage circular still requires payment records to stay on systems located in India.
The capacity that met that pin is mostly Amazon S3, and S3-compatible stores, in Mumbai and Hyderabad. India’s first general privacy law, now in force on a phased clock, did not copy the same location test onto ordinary SaaS personal data.
The Compliance Default Is a Bucket in Mumbai
Payment apps, brokers, and Indian SaaS firms did not wake up wanting object storage. They needed a place that could take KYC scans, settlement files, invoices, and chat attachments without a new SAN order every time sign-ups jumped. The S3 API gave them that, with lifecycle rules, presigned upload URLs, and region locks that a compliance officer can point to in an audit.
Amazon publishes S3 Standard at $0.023 per GB-month for the first 50 TB, billed on the region where the bucket lives. Mumbai (ap-south-1) and Hyderabad (ap-south-2) both keep objects inside India. Azure’s India regions and Google’s Mumbai and Delhi locations do the same job for teams already on those clouds.
The durability pitch is the one every vendor repeats, and it is real on the hyperscaler side: Amazon says S3 is designed to exceed 99.999999999% durability, the figure engineers call 11 nines, by spreading objects across at least three Availability Zones unless a customer picks a one-zone class. That is the product Indian fintech actually bought when the 2018 circular made “a disk in Mumbai” a legal requirement rather than a preference.
Hot objects can sit in S3 Standard. Objects nobody has opened for 30 days can drop into Intelligent-Tiering’s infrequent tier, then into Archive Instant Access after 90 days of silence, with an optional deep-archive step after 180 days that Amazon says can cut storage cost by up to 95 percent. The application code does not change. The bill does.
Two Rulebooks Cover the Same Objects
Teams still talk about “data localization” as if India had one switch. It does not. Payment system data is pinned to Indian machines. Most other personal data is not, unless a sector regulator says so.
The Digital Personal Data Protection Act, 2023 lets personal data move across borders by default. The Centre can later name countries that are off limits. That is a negative list, not a Mumbai-only rule. Nikhil Pahwa put the SaaS consequence in plain words when the draft rules appeared: the Act “allowed for global data transfers,” with a note to “all global SaaS customers and Indian SaaS co’s,” except blacklisted destinations.
MeitY then issued the Digital Personal Data Protection Rules, 2025 in the Gazette dated 13 November 2025. Consent-manager registration (Rule 4) takes effect on 13 November 2026. The remaining operational duties, including notice, erasure, and most fiduciary obligations, take effect 18 months after that Gazette date, on 13 May 2027. Penalties under the Act can run to ₹250 crore.
WHERE EXPERTS DISAGREE
- Location first: The Reserve Bank still treats India-only storage of payment records as the test that a system provider must pass.
- Transfer by default: The DPDP Act lets personal data leave India unless the Centre names a banned destination, so a global SaaS product is not automatically a Mumbai-only product.
- The pin is thin: Operators at the India Mobile Congress in October 2026 argued that who holds admin rights and encryption keys matters more than the region name on a bucket.
Bharti Airtel vice chairman Gopal Vittal said at the August 2025 launch of Airtel Cloud that controls would remain “strictly within the country.” GSMA Intelligence’s 2026 survey of 258 Indian enterprises found firms willing to pay an average 13 percent premium for sovereign technology. That premium is being spent, in practice, on public cloud regions that happen to sit on Indian soil.
What the 2018 Circular Still Forces Into India
The circular is DPSS.CO.OD.No 2785/06.08.005/2017-18. It applies to payment system providers authorised under the Payment and Settlement Systems Act, 2007, and to the banks, gateways, vendors, and “other entities” they hire. The authorised provider owns the duty. If a processor stores a copy in Singapore overnight, the Indian principal is still on the hook.
RBI’s FAQ is blunt on the location test: the entire payment data stored only in India, on systems located in the country, with a narrow set of exceptions.
PAYMENT DATA THE CIRCULAR NAMES
- Customer fields: Name, mobile number, email, Aadhaar number, PAN, and similar identifiers gathered in the payment flow.
- Account details: Customer and beneficiary account information treated as payment-sensitive data.
- Credentials: OTP, PIN, passwords, and other payment secrets that travel with the instruction.
- Transaction trail: Originating and destination systems, reference, timestamp, amount, and the rest of the end-to-end message.
Processing abroad is allowed. The data must then be deleted overseas and brought back to India within one business day or 24 hours, whichever is earlier. A copy of the domestic leg of a cross-border payment may also be stored abroad. Foreign banks that were earlier allowed to keep general banking data overseas may continue to do so, but domestic payment transactions still have to live in India.
The 8 May 2025 Digital Lending Directions tightened a related corner. Personal data collected in a digital lending relationship must be stored on servers in India. If it is processed outside, it has to be deleted abroad and brought back within 24 hours. A KYC packet that looks like “just documents in a bucket” can fall under payments, lending, or both, depending on the product.
Hyperscalers Collected the Localization Spend
Gartner’s June 2026 forecast puts India public cloud spend of $17.487 billion in 2026, up from $13.656 billion in 2025, a 28.1% rise. IaaS is the fast line: $4.470 billion to $6.259 billion, a 40.0 percent jump, as firms buy more storage, GPUs, and always-on capacity. PaaS, the largest slice, goes to $6.414 billion.
INDIA PUBLIC CLOUD END-USER SPEND (GARTNER, JUNE 2026)
| Segment | 2025 ($ million) | 2026 ($ million) | 2026 growth |
|---|---|---|---|
| PaaS | 5,114 | 6,414 | 25.4% |
| SaaS | 3,901 | 4,637 | 18.9% |
| IaaS | 4,470 | 6,259 | 40.0% |
| DaaS | 171 | 176 | 2.9% |
| Total | 13,656 | 17,487 | 28.1% |
Ashish Banerjee, a senior principal analyst at Gartner, tied that bill to sovereignty in the same note that recorded the IaaS surge.
This is further fueled by rising demand for application modernization, digital sovereignty, digital service delivery and more scalable, consumption-based IT models, as organizations move toward more advanced and strategic cloud use cases.
Ashish Banerjee, Senior Principal Analyst, Gartner, June 2026 forecast
UPI itself is the volume engine behind a lot of those objects. NPCI’s FY2025-26 figures put the system at 24,162 crore transactions. Each hop still throws off logs, receipts, and dispute files that a PSO cannot park in Frankfurt and forget. The cheapest way to keep them in India, with an API every SDK already speaks, was a bucket in ap-south-1.
That is the twist the 2018 circular never advertised. A rule written to keep payment data on Indian soil became a demand shock for US-owned regions that had already landed here. Indigenous operators such as Yotta, E2E Networks, and AceCloud sell S3-compatible storage in Indian data centers, often with rupee billing and lighter egress. They win the price-sensitive and GPU-adjacent work. They do not yet win the default architecture of a payments app that already runs on IAM, Lambda, and KMS.
Immutable Files Versus a Duty to Erase
Once the objects are in S3, the next fight is whether anyone can change them. Amazon’s write-once-read-many Object Lock freezes an object version for a set period. In compliance mode, even the AWS account root user cannot overwrite or delete it, and the retention period cannot be shortened. Cohasset Associates has assessed that mode for US broker-dealer record rules. Indian PSOs use the same switch for audit packs that have to survive a seven-year ask.
On 8 September 2026 Amazon added event holds, so a retention clock can start when a contract closes or an audit ends rather than on upload day. The feature is in all AWS Regions, with no extra charge. For a fintech, that maps cleanly onto “keep the loan file until the relationship ends, then keep it for the statutory tail.”
DPDP pulls the other way. Fiduciaries will have to erase personal data when the purpose is served, unless another law says keep it. Payment and KYC files that RBI or PMLA already freeze are the easy case: Object Lock and the statute agree. Marketing profiles, device graphs, and support recordings dumped into the same bucket are the hard case. A lifecycle rule that sends everything to Glacier, then locks it, will look tidy in a cost review and ugly in a 2027 erasure request.
The S3 classes built for data residency also include one-zone and Dedicated Local Zone options when a region boundary is not tight enough. Those classes trade price or isolation against the three-AZ default. They do not move key custody. Customer-managed keys in KMS or an external HSM still decide whether “stored in Mumbai” means “controlled in Mumbai.”
MinIO’s Archive and the Lost Local Shortcut
For a decade the private answer to “we need S3 but not AWS” was MinIO. Indian banks and SaaS teams ran it on their own racks, spoke the same API, and told auditors the bits never left the building. In 2026 the open-source Community Edition stopped being maintained and the upstream GitHub repository was archived. Active work moved to MinIO AIStor, a commercial product.
That closes a cheap path just as DPDP turns third-party hosting into a board item. A vendor pitch circulating in mid-October 2026 put it without softness: penalties go to ₹250 crore, and customer data on someone else’s cloud is now a board-level risk. The replacement set is Garage, RustFS, SeaweedFS, and Ceph RGW, plus the India-native S3 endpoints.
WHERE THE OBJECTS CAN LIVE
- Hyperscaler India regions: AWS Mumbai and Hyderabad, Azure’s India regions, Google Mumbai and Delhi, Oracle Cloud in Mumbai and Hyderabad, with the full IAM and event stack attached.
- India-native S3 endpoints: Yotta, E2E Networks, AceCloud, and similar hosts selling rupee-priced, S3-compatible buckets in Indian Tier III and Tier IV halls.
- Self-hosted: Ceph RGW and the MinIO successors, on hardware the firm already controls, at the cost of patching, capacity planning, and 11-nines engineering it now owns.
Portable API is not a portable control plane. Event notifications that kick OCR and fraud models on PutObject are thickest on AWS, GCS, and MinIO. A team that built “S3 plus Lambda plus KMS” can copy objects to Yotta in a weekend. It cannot copy the glue without a rewrite. That is how a localization rule produces lock-in even when the bucket protocol is open.
A Community Cloud for Urban Co-operative Banks
The Reserve Bank did stand up its own answer. Indian Financial Technology and Allied Services, a wholly owned RBI subsidiary, runs IFS Cloud as a community cloud for the regulated financial sector. The Bank’s annual report said a beta with minimum viable services launched, and nine entities have been onboarded. IFTAS has been pitching the same stack to urban co-operative banks as a multi-region, on-demand platform, and it showed IFS Cloud at the Global Fintech Fest 2026 next to INFINET 3.0.
That product is built for smaller banks that cannot staff a cloud team, not for a UPI app clearing billions of payments a month. The large consumer apps already live in the public regions that cleared the 2018 test. IFS Cloud may yet take deposits, core, and co-operative workloads. It is not where PhonePe-scale object stores sit today.
THE STORAGE CLOCK
- 6 April 2018: RBI issues the Storage of Payment System Data circular, giving system providers six months to keep payment data on systems in India.
- 8 May 2025: Digital Lending Directions require lending personal data on Indian servers, with a 24-hour return if processed abroad.
- 13 November 2025: MeitY notifies the DPDP Rules in the Gazette and starts the Data Protection Board clock.
- 8 September 2026: Amazon adds event holds to S3 Object Lock in all Regions, so WORM retention can start on a business event.
- 13 November 2026: Consent-manager registration under Rule 4 takes effect.
- 13 May 2027: Remaining DPDP operational rules, including notice and erasure duties, take effect.
The next audit will not ask whether the bucket’s region code says ap-south-1. It will ask who can delete a KYC object, how fast a consent withdrawal hits the object index, and whether logs of that deletion also stay in India. Consent-manager registration under the DPDP Rules takes effect on 13 November 2026. The large payment apps already know which region holds the files. They still have to prove who holds the keys.
Disclaimer: This article is news reporting and analysis of public cloud storage and Indian data rules. It is informational only and is not legal advice, regulatory advice, or a compliance programme. It does not tell any firm where to host data, which vendor to use, or how to meet RBI, SEBI, IRDAI, or DPDP duties. Readers who must design or sign off storage architecture should consult a qualified data-protection or financial-regulatory lawyer, and read the circulars and rules themselves, before they act. Figures, product prices, and deadlines reflect the official texts and research notes cited here and can change when a regulator or a cloud vendor issues a new schedule.
-
Cloud Hosting4 weeks agoUtho Asks India to Book B300 GPUs Before They Arrive
-
NEWS1 month agoRank Math PRO Joined a 2026 Pattern of Paid Plugin Backdoors
-
AI1 month agoGoDaddy Lets AI Agents Run Hosting, Email and Stores
-
NEWS1 month agoElementor Pro’s Form Bug Left Hosts Holding the Cleanup
-
NEWS4 weeks agoFirstVDS Disk Theft Exposes a Live VMmanager Flaw
-
Email Hosting1 month agoWindows Updates Cap RPC Calls and Stall Exchange Mail
-
Cloud Hosting1 month agoYandex Cloud Bots Moved to Selectel After the Strikes
-
Email Hosting1 month agoTitan Puts a $3 Inbox Beside Google on Squarespace
