🔍 Read the full analysis: What India’s Payment Data Rules Mean For SAP Data Localisation on Rymvard

Before you orderOffer from Amazon

Get the latest gadgets delivered free with Prime

• Fast, free delivery on millions of items
• Prime Video, Amazon Music and more included
• Member-only deals all year

Start your free Prime trial →Free trial for eligible customers · Cancel anytime

As an affiliate, we earn on qualifying purchases.Hide

TL;DR

The Reserve Bank of India’s 2018 circular requires payment-system data to be stored only in India. Rymvard, an early-access product, models SAP HANA memory, site capacity and replica requirements for an illustrative Mumbai hosting-provider scenario; it does not establish that all SAP data must be local or show a customer deployment.

India’s payment-data rule requires payment-system data to be stored only in the country, while Rymvard says its early-access software helps Indian SAP hosting providers plan the HANA memory and replica capacity that expanding workloads may require. The company’s Mumbai scenario is illustrative: it is not a customer deployment, and the rule does not by itself establish that every SAP system or all enterprise data must be hosted in India.

The Reserve Bank of India’s April 6, 2018 circular on storage of payment system data directs that the entire data relating to payment systems be stored in a system only in India. For organisations subject to the requirement, that can affect where relevant payment workloads and their data are hosted. The circular is the regulatory basis; Rymvard’s product is a capacity-planning response to hosting demand, not an RBI tool or interpretation.

Rymvard says its software identifies each SAP system using a combination of system ID, site and customer, because system IDs can recur across different customers. It displays available HANA memory at each site after accounting for replicas and projects planned landscapes into a quarterly memory runway, weighting the pipeline by probability. The model also includes a replica at a second site for each planned landscape.

At host level, the product separates physical memory into an operating-system reserve, current HANA system use, allocated but unused memory, memory reserved for replicas of systems at other sites, and capacity that remains free. Rymvard says system use is based on the 30-day peak. Its default operating-system reserve is 10% of the first 64 GiB and 3% of the remainder, unless a host specifies a different reserve. Allocations above physical memory are shown as overbooking rather than concealed as negative free capacity.

Planning HANA Capacity Across Sites

The rule can make the location of payment-system data a hosting constraint, while the operational challenge is to plan enough infrastructure for the workloads an India-based provider expects to support. HANA memory, replica capacity and host-level overbooking all affect whether a provider can place additional systems at a site without exceeding physical capacity.

Rymvard’s approach is designed to put those demands into one model rather than separate customer spreadsheets. Tracking systems by customer and site can help distinguish similarly named system IDs, while probability-weighted forecasts can show how planned additions might affect capacity over coming quarters. Including second-site replicas makes the projected requirement larger than the primary systems alone.

Those are product capabilities described by Rymvard, not evidence of a measured business outcome. The company has not supplied a customer case, deployment result, or quantified savings. Its example should be read as an illustration of how a provider could inspect capacity, not proof that the software has resolved a particular compliance or infrastructure problem.

The Rule and Rymvard’s Example

The RBI circular dates to April 6, 2018 and concerns data relating to payment systems. Its stated storage requirement is India-only. The supplied information does not set out the circular’s full scope, subsequent regulatory guidance, or how it applies to individual SAP architectures; those questions require reference to the applicable RBI material and an organisation’s circumstances.

Rymvard frames the market issue as a rise in demand for in-country SAP hosting, with providers needing to forecast capacity faster than new hardware can arrive. It presents a scenario involving an in-country SAP hosting provider in Mumbai. The company says the screens are from its running product but use an illustrative estate, not a customer’s systems or actual operational results.

The product is in early access. Rymvard says pricing is agreed with early-access partners and does not publish a standard price. The available description focuses on infrastructure planning for SAP landscapes and HANA memory; it does not claim that the product itself stores payment data or certifies compliance.

“The entire data relating to payment systems is stored in a system only in India.”

— Rymvard

Scope and Customer Evidence

The exact application of the RBI requirement to particular enterprise SAP systems is not established here. The circular concerns payment-system data; the information available does not show that all SAP workloads, all enterprise records, or every replica must be located in India. Organisations should assess the rule’s scope against their payment activities and seek appropriate compliance advice.

There is also no named customer, independent evaluation, or production outcome in the product description. The Mumbai estate is explicitly illustrative, and Rymvard has not published evidence showing how accurately its forecasts match real deployments or whether its planning reduces costs, delays or compliance risk. The company’s early-access status means product availability and commercial terms may also depend on partner arrangements.

Early-Access Product Development

Rymvard says the product is currently running and available through early access, with pricing agreed individually with partners. The next concrete development indicated is therefore further use and evaluation with those partners; no public launch date, customer announcement or product roadmap milestone has been provided.

For hosting providers considering the approach, the practical next steps are to verify the regulatory scope for their workloads, validate host and replica assumptions against their own SAP estates, and test whether the capacity forecasts reflect actual consumption. Rymvard lists contact@rymvard.com for enquiries. Any broader conclusion about adoption or compliance impact will depend on customer deployments and further details that have not yet been made public.

Primary source: Reserve Bank of India · via Rymvard

Key Questions

What does India’s payment-data rule require?

The RBI circular dated April 6, 2018 says the entire data relating to payment systems must be stored in a system only in India. The details of how that requirement applies to a particular organisation or SAP landscape are not established by Rymvard’s product description.

Does the rule require every SAP system to be hosted in India?

Not on the information presented here. The circular described concerns payment-system data; it does not, on its own, establish that every SAP workload or all enterprise data must be localised. Organisations need to assess which systems and data fall within the applicable requirement.

What does Rymvard’s software model?

Rymvard says it tracks SAP systems by customer and site, estimates HANA memory use and free capacity, accounts for replica needs at a second site, and forecasts planned landscapes by quarter. Its description says system use is based on the 30-day peak.

Is the Mumbai example based on a real customer?

No customer deployment is identified. Rymvard says its screens show a running product using an illustrative example estate, and that no customer, site or outcome is implied.

Is Rymvard generally available, and what does it cost?

Rymvard says it is in early access. It does not publish prices; pricing is agreed with early-access partners.

Primary source: Reserve Bank of India · via Rymvard