raghuveerdiyyala wrote:
We are not requesting all the fancy features right. Just one feature to support UPI
NPCI could have said "We'll use the new security feature when we can, but when we can't, we'll make do without the feature."
The feature seems to be "United Payments Interface (UPI) device validation", and part of the implementation is a Message UI method called "setUPIVerificationCodeSendCompletion." There is also a property list item, called "com.apple.developer.upi-device-validation," whose value indicates whether that validation method is available on the current device.
They didn't. They decided they would rather lock out your phone than do without the feature. They could still change their policy and allow UPI transactions on older versions of iOS that do not have the new feature, if they wanted to do so. But I bet that they won't.
Let's say that you could convince NPCI to relent. That wouldn't automatically mean that you could start making UPI payments on older iPhones. You'd need to go to the UPI payment app vendors and say, "Now that NPCI has relented, could you do the work to support older iPhones?" Same thing if you could convince Apple to back-port the feature to iOS 16. Apple does not control NPCI or UPI payment app vendors. If an app requires a minimum of iOS 17 now, you would need to convince the app vendor to release a new version with a lower requirement.
As a practical matter, when was the last time you ever seen any app developer decrease the minimum version of iOS required to run their app?