The UpdateLead
Flexible Finance, Inc.'s version 3.59.0 update to its Flex app, released August 28, 2026, introduced a critical payment bug. The app is now charging users their full rent amount at once, overriding the split-payment plans that form its core service.[2]
Vague Release NotesRelease Summary
The official release notes for version 3.59.0 on the App Store state, "Every update to the Flex app includes performance improvements like speed, reliability, and bug fixes." There is no mention of changes to the payment system. This generic description contrasts sharply with the severe issues reported by users, suggesting the malfunction was an unintentional regression introduced during a routine maintenance release.
Payment System FailureBreaking Changes
The primary issue in v3.59.0 is a failure of the app's central promise: splitting rent payments. Users report that the app is ignoring their established two-part payment schedules and instead withdrawing the entire rent sum in a single transaction. This has caused significant financial distress for users who rely on the service to manage cash flow.
Additional problems have also appeared since the update. Users describe slow processing speeds and card payment errors. One 2-star review on v3.59.0 noted the app stalls with a "slow down it’s processing!" message. Another user reported their card was charged despite the app showing a processing failure, though they were able to resolve it themselves.
Additional problems have also appeared since the update. Users describe slow processing speeds and card payment errors. One 2-star review on v3.59.0 noted the app stalls with a "slow down it’s processing!" message. Another user reported their card was charged despite the app showing a processing failure, though they were able to resolve it themselves.
Rating DropUser Reception
The impact on user sentiment was immediate and severe. Following the release, the app's average rating on the App Store fell from 4.64 to 3.55 stars. Reviews for the previous version, 3.58.0, were largely positive, with one 5-star reviewer calling the service a "godsend" for budgeting. In contrast, post-update reviews capture the sudden failure. In a review paradoxically rated 5-stars on v3.59.0, a user expressed this frustration, stating, "Was very happy using flex until today when all of my rent was paid at once instead of following my 2 step plan." This highlights the direct contradiction between the app's function and its promise.
Pattern of InstabilityRoot Cause
This event is not isolated. Analysis of the publisher's help center and community forums shows a pattern of reliability issues, including payment processing failures, app freezes, and login problems. This history, combined with recurring user complaints about increasing fees, suggests underlying platform instability.
The app's fee structure has evolved, with an April 2026 Los Angeles Times article noting a monthly fee up to $14.99 at the time. The current App Store listing cites a $5.99 monthly fee plus processing and split fees. This sensitivity to cost likely makes functional failures even more damaging to user trust.
The app's fee structure has evolved, with an April 2026 Los Angeles Times article noting a monthly fee up to $14.99 at the time. The current App Store listing cites a $5.99 monthly fee plus processing and split fees. This sensitivity to cost likely makes functional failures even more damaging to user trust.
VerdictExpert Verdict
The v3.59.0 update and its subsequent payment failures impacted a substantial user base, with over 174,000 downloads on US iOS in the 30 days prior.[3] Given that Flex targets renters who may require assistance with monthly cash flow, the unexpected withdrawal of a full month's rent poses a serious financial risk to its customers.
The publisher will likely be forced to ship an emergency hotfix to correct this critical bug. However, regaining user trust will be a significant challenge, suggesting a need for more rigorous quality assurance in its release process to prevent future financial errors and user churn.
The publisher will likely be forced to ship an emergency hotfix to correct this critical bug. However, regaining user trust will be a significant challenge, suggesting a need for more rigorous quality assurance in its release process to prevent future financial errors and user churn.