digi.ai.in
← digi.ai.in / blog
2026-09-138 min readReliability

Why Every Integration Is a Promise You Have to Keep

Every API, script or payment gateway you add is a commitment you're on the hook for, even when the vendor breaks it first.

When you add a payment gateway, a maps widget, an analytics tag or a KYC API to your website or app, you are making a promise to your customers and, in India, to your regulators. That promise is that the thing will keep working, keep data safe, and keep loading fast. The vendor behind that integration has made no such promise back to you, at least not for long. This gap is where a lot of Indian businesses get hurt, and it is worth working through exactly why.

The vendor's promise is weaker than you think

Businesses tend to assume that once an integration is live, it stays stable unless they touch it. Vendors don't operate that way. Google's own developer blog documented a 2012 policy change where several major services, including App Engine, Maps and Earth APIs, and YouTube, had their deprecation notice period cut from three years down to one year, which Google called "a common industry practice among similar APIs." For a longer list of other products, including Checkout, Picasa, Orkut and Prediction, Google removed the deprecation policy altogether — meaning no guaranteed notice at all before something breaks source.

This isn't ancient history. Google's current documentation shows the same inconsistency still exists within a single vendor's own product line. Its Merchant API guarantees a firm 12-month window before a version is sunset source. Its Kubernetes Engine documentation, by contrast, runs deprecations on a rolling, feature-by-feature schedule tied to release versions, with no single fixed calendar you can plan around source.

If you're a founder or ops manager, the takeaway is blunt: don't assume "Google" or "Razorpay" or any big name means uniform stability. Ask, for each specific API you depend on, what the deprecation policy actually is, in writing, before you build around it.

Performance is part of the promise, not a bonus

A slow site isn't a cosmetic problem. It's a broken promise measured in conversions. Google's web.dev has documented that Redbus, the ride-hailing and bus booking platform, cut its Cumulative Layout Shift score from 1.65 down to 0 by optimising third-party scripts, and that this work "contributed to 80-100% mobile conversion rates (mCVR), and significant domain ranking uplift" source.

The mechanism is well understood. Analysts studying Core Web Vitals put it plainly: "one sluggish third-party script can delay everything that comes after it," directly hurting both Largest Contentful Paint and Cumulative Layout Shift source. One specific example is stark: Chrome data shows that "YouTube embeds alone block the main thread for 4.5 seconds on 10% of mobile sites," and Lighthouse flags any third-party script that blocks the main thread for more than 250ms source.

None of this code is yours. You didn't write the YouTube embed script or the chat widget's tracking pixel. But your visitor experiences the slowdown as your site being slow, and your Core Web Vitals score reflects it regardless of whose code caused it.

What downtime actually costs

Outage cost estimates vary a lot depending on who is measuring and when, which is itself a useful signal that nobody has a tidy answer. Pingdom's figures put the historical average cost of downtime at roughly $5,600 per minute across industries, rising to about $9,000 per minute in more recent studies, with small businesses averaging around $427 per minute source. A more recent 2026 report cited by Gatling puts the number far higher, at close to $15,000 per minute on average, with enterprises reporting over $1 million per hour of outage and even firms under 25 employees averaging about $1,670 per minute. The same data shows financial services firms losing an estimated $72 million a year in direct revenue from outages, plus another $91 million in contractual and legal costs source.

The gap between $5,600–9,000 and $15,000 a minute is large, and there's no single agreed figure across sources. But every source agrees the trend runs upward, and that transaction-heavy integrations (payments, checkout, KYC) are hit hardest. This is confirmed at the API level too: one analysis of fintech APIs specifically found that "API downtime increased by 60% between Q1 2024 and Q1 2025, with average uptime falling from 99.66% to 99.46%," a change that sounds small but works out to roughly eight extra hours of unavailability a year source.

Metric Figure Source
Average downtime cost, historical ~$5,600/minute Pingdom
Average downtime cost, recent ~$9,000/minute Pingdom
Average downtime cost, 2026 estimate ~$15,000/minute Gatling
Small business (under 25 employees) downtime cost ~$1,670/minute Gatling
Fintech API uptime, Q1 2024 to Q1 2025 99.66% to 99.46% ResolvePay

The Indian legal layer: outsourcing the work doesn't outsource the responsibility

Indian regulation makes explicit what other markets leave implicit: you cannot hand off legal accountability just because you handed off the code. Under the Digital Personal Data Protection Act, 2023, a business acting as "Data Fiduciary" retains responsibility for data protection "even when third parties process the data on their behalf" source. Legal commentary is direct about the logic: the Act "establishes accountability on the entity that determines the purpose and means of processing," not the vendor that merely executes it source. The penalties for getting this wrong are not trivial: businesses can face fines of up to INR 2.5 billion for failing to take reasonable security safeguards to prevent a breach of personal data source.

Payment integrations carry a further, India-specific obligation. Since an RBI directive from April 2018, all payment system providers must store payment-system data only on servers located in India, and where any processing happens abroad, that data must be deleted from the overseas system "within 1 business day or 24 hours after payment processing, whichever is earlier" source. Firms were originally given a six-month window to come into compliance source. If your payment gateway vendor isn't handling this correctly, the RBI holds you, not just them, responsible.

UPI adds one more concrete example of how quickly this can turn operational. After a run of outages, NPCI directed banks and payment service providers on 21 May 2025 to moderate ten high-frequency UPI APIs, giving them until 31 July to comply, "failing which they may face penalties, API restrictions, or suspension of customer onboarding" source. This is a system processing over 14 billion monthly transactions source, which means even a small compliance failure at the API level has consequences at national scale, and the regulator's response is to restrict the offending business's ability to onboard new customers.

A practical checklist before you add any integration

Before committing to a new API, widget or payment processor, it's worth running through a short list of questions rather than assuming the vendor has already thought about them for you.

  • What is the vendor's actual deprecation policy for this specific API, in writing, not the marketing page. Google's own APIs range from a firm 12-month notice to no guarantee at all source source.
  • Does the script load synchronously and block the main thread. Third-party embeds have been measured blocking rendering for as long as 4.5 seconds on a meaningful share of mobile sites source.
  • If this integration touches payment data, is it storing anything outside India, and if so, is deletion happening within the RBI's 24-hour window source.
  • If this integration processes personal data on your behalf, have you confirmed in the contract that you remain the Data Fiduciary and retain accountability under the DPDP Act source.
  • What does an hour of downtime on this specific integration cost you. Even conservative estimates put small businesses at over $400 a minute, and some recent estimates put it far higher source source.
  • If this is a UPI-related integration, is your PSP compliant with NPCI's API moderation guidelines, given that non-compliance can mean suspension of new customer onboarding source.

What this means for how you commission a build

None of this argues against integrations. A business without payment gateways, maps, or analytics is not more reliable, it's just less useful. The argument is that every integration should be treated as a dependency with its own risk profile, not a plug-and-play feature you add and forget. That means asking vendors direct questions about deprecation timelines before signing anything, testing script load behaviour under real mobile network conditions rather than office wifi, and writing data-handling responsibilities into contracts explicitly rather than assuming the vendor's terms of service cover you. The RBI and the DPDP Act are both explicit that the business commissioning the work carries the legal weight, not the vendor executing it. Build accordingly.

Questions people also ask

Can I just switch payment gateways if RBI compliance becomes an issue?

You can, but the switch itself needs to satisfy the same data localization rule from day one, including making sure any data processed by the old vendor outside India is deleted within the required 24-hour window as it's being wound down source.

Is a small business really at risk from downtime costs quoted in the millions?

The largest headline figures (like $1 million per hour) are enterprise numbers, but even the small-business-specific figures are significant: Gatling's data puts firms under 25 employees at around $1,670 a minute of downtime, and Pingdom's more conservative historical estimate puts small businesses at about $427 a minute source source.

If a third-party vendor causes a data breach, am I still liable under the DPDP Act?

Yes. The Act places accountability on the entity that determines the purpose and means of processing, which is the business, not the processor, and this holds even when the processing was carried out by a third party source.

Written by the studio behind digi.ai.in. Questions? hi@digi.ai.in or WhatsApp +91 98605 96905
WhatsApp us