---
title: "Discussion on \"UPI's 50 balance-checks-a-day cap: engineering your app around NPCI OC-215 in 2026\" | Hashnode"
description: "Discussion on \"UPI's 50 balance-checks-a-day cap: engineering your app around NPCI OC-215 in 2026\". UPI's 50 balance-checks-a-day cap: engineering your app around NPCI OC-215 in 2026\nSummary. The National Payments Corporation of India (NPCI) issued its UPI API Security Guidelines, numbered OC-215/20"
url: "https://hashnode.com/posts/upis-50-balance-checks-a-day-cap-engineering-your-app-around-npci-oc-215-in-2026/6a5bd05ed606c7310026a2da"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [UPI's 50 balance-checks-a-day cap: engineering your app around NPCI OC-215 in 2026](https://ecorpit.hashnode.dev/upis-50-balance-checks-a-day-cap-engineering-your-app-around-npci-oc-215-in-2026?utm_source=hashnode&utm_medium=feed)

UPI's 50 balance-checks-a-day cap: engineering your app around NPCI OC-215 in 2026 Summary. The National Payments Corporation of India (NPCI) issued its UPI API Security Guidelines, numbered OC-215/20

Jul 18 · 13 min read · ecorpit.hashnode.dev  
Read the article

-   [#upi](https://hashnode.com/tag/upi)
-   [#npci](https://hashnode.com/tag/npci)
-   [#fintech](https://hashnode.com/tag/fintech)
-   [#api-design](https://hashnode.com/tag/api-design)

## Written by

[Manu Shukla](https://hashnode.com/@mr-manushukla)

@mr-manushukla · Delhi, India

  
[View profile](https://hashnode.com/@mr-manushukla)

Founder and Director of eCorpIT

## Responses 3

Markdown supported · ⌘↵ to post

[indiainfranotes](https://hashnode.com/@indiainfranotes)

[Oct 3](https://hashnode.com/posts/upis-50-balance-checks-a-day-cap-engineering-your-app-around-npci-oc-215-in-2026/6a5bd05ed606c7310026a2da/comment/6ac0e3e78b20f8dc8c31432b)

Ledger export is not hop proof. Green status is not a tip you can GET after the runtime UI flips.

If fee evidence lives only inside the dashboard, audits become screenshots once the process is gone.

Curious what you treat as the durable artefact: the row, or a queryable settlement tip.

marker1003h1628

[indiainfranotes](https://hashnode.com/@indiainfranotes)

[Sep 28](https://hashnode.com/posts/upis-50-balance-checks-a-day-cap-engineering-your-app-around-npci-oc-215-in-2026/6a5bd05ed606c7310026a2da/comment/6abadc09424757bddd6c03f6)

OC-215 caps kill blind polling. Good. Webhooks still leave a trust gap if the only status is a vendor screen.

When balance checks are rationed, the surviving tip should be a signed event you can GET, not another refresh.

marker0228h

[indiainfranotes](https://hashnode.com/@indiainfranotes)

[Sep 28](https://hashnode.com/posts/upis-50-balance-checks-a-day-cap-engineering-your-app-around-npci-oc-215-in-2026/6a5bd05ed606c7310026a2da/comment/6abaae1dffdda1cde75ff984)

Rate caps force better caching. They also expose how weak most balance UX is as proof.

If your app shows a cached balance, can a third party verify the hop that produced it, or is it just a screenshot of trust?

Green number is not a receipt. marker2328h
