iOS 27 Beta Reveals Apple's 'Restricted Mode' for Financed Devices Ahead of Klarna-Backed 'Upgrade' Leasing Program

Code discovered in an iOS 27 beta by 9to5Mac on July 21, 2026 describes a "Restricted Mode" that would allow Apple to limit functionality on leased iPhones after missed payments, stripping devices down to Phone, Settings, and the App Store while blocking erasure, resale, or part-stripping. The find landed one day before Bloomberg reported that Apple is preparing to launch an "Upgrade" device-leasing program in partnership with Klarna, planned for July 28, 2026.
The two reports together sketch a coherent picture: Apple is building the OS-level enforcement machinery for a financing program it has not yet publicly announced. The Verge, publishing on July 22, corroborated both threads. Apple did not immediately respond to The Verge's request for comment on either Restricted Mode or the Upgrade program.
9to5Mac's original report, titled "iOS 27 code suggests Apple could restrict leased devices after missed payments," identified a new system called "App Managed Features." This framework allows financing or partner apps to continually check whether a financed device remains in good standing. When a device falls out of compliance, Restricted Mode engages, removing access to nearly all apps except Phone, Settings, and the App Store. The Mac Observer independently confirmed the same mechanism, describing a planned lock system that lets providers place iPhones into Restricted Mode when a financing contract is not in good standing. Macworld, also publishing July 22, reported the same beta code references.
A separate component, dubbed "Partner Finance Lock," is designed to prevent users from erasing the device, reselling it, or stripping it for components. Partner Finance Lock lives within Find My infrastructure but reportedly does not grant financing partners access to the device's location data. That architectural choice matters: it separates the lock-enforcement channel from location-tracking, keeping the finance partner's capabilities scoped to device status rather than user surveillance.
The Upgrade program, as reported by Bloomberg and attributed to unnamed people with knowledge of Apple's plans, would support most iPhone, Mac, iPad, and Apple Watch models. Klarna is named as Apple's financing partner. The planned launch date is July 28, 2026. Neither Apple nor Klarna has officially announced the program.
Notably, Apple's own Xcode 27 Beta 4 release notes on developer.apple.com contain no mention of Restricted Mode, device-financing features, or any partner-based device locking functionality. The absence is consistent with how Apple typically handles unreleased consumer-facing features in developer documentation: the code surfaces in beta builds before the company acknowledges it publicly.
The broader context here is that Apple has operated its own iPhone Upgrade Program in the United States for years, but that program functions as an installment loan with carrier integration. The new "Upgrade" program, with Klarna as the financing partner, appears to be a broader leasing construct spanning multiple device categories and potentially multiple markets. Restricted Mode and Partner Finance Lock would give Apple and its financing partner an OS-level enforcement lever that installment-loan models have never required, because those models have historically relied on carrier-side IMEI blocking or credit-report-based collection rather than direct device functionality throttling.
In my view, the technical design as described in the beta code reflects a deliberate scoping decision. By routing enforcement through a dedicated "App Managed Features" system rather than extending existing MDM or Screen Time frameworks, Apple is creating a purpose-built channel for financial lockout that is architecturally isolated from enterprise device management, parental controls, and Activation Lock. The location-data firewall inside Partner Finance Lock further suggests Apple is aware of the privacy implications of giving a third-party financier any foothold on a device and is constraining that foothold at the system level.
The history worth noting is the precedent of carrier-locked devices and Activation Lock. Activation Lock, introduced with iOS 7 in 2013, proved effective at reducing iPhone theft by making stolen devices functionally unusable without the owner's Apple ID credentials. Restricted Mode applies similar logic to a different problem: not theft recovery, but lease enforcement. The mechanisms differ, but the principle of using OS-level locks to change the economics of device ownership is consistent.
Several unknowns remain. The code was found in a beta version of iOS 27 and could be changed or removed before the official release. The relationship between the July 28 reported Upgrade launch date and the iOS 27 release timeline is unclear: if Restricted Mode requires iOS 27 and iOS 27 has not shipped by late July, the financing program could launch before the enforcement mechanism is available to all users. Alternatively, Apple may restrict the Upgrade program's initial rollout to devices already running iOS 27, or phase in enforcement after launch.
The privacy and trust questions are real but bounded by what the code currently describes. A financing partner app with the ability to continually check device standing, even without location access, still represents a persistent third-party process on a consumer device with the authority to throttle core functionality. How Apple communicates that relationship to users at the point of sale will matter as much as the technical implementation.
For developers and platform watchers, the "App Managed Features" framework is the component to track. If it ships in iOS 27, it establishes a new category of system-level capability that is neither MDM nor Activation Lock but a third enforcement surface designed for commercial relationships. Apple has not documented it. The beta code is the only source, and betas are provisional. But the convergence of a new financing program reported by Bloomberg and purpose-built enforcement code surfaced by 9to5Mac, Macworld, and The Mac Observer suggests the pieces are being assembled for a coordinated launch.


