When developing an application that uses a third-party service - like logging in with a social media account or processing a payment - it's common to use Software Development Kits (SDKs) provided by that third-party service. These SDKs are essentially a bundle of features and configurations that enable and securely connect to the third-party service.

We have recently been notified by Google that recent versions of Stripe's SDK were not compliant with their latest disclosures policy. Stripe SDKs up to version 14.2.1 contained unused code that breached the policy, and though it was deprecated it wasn't deleted. The unused code was removed starting in versions 14.3.0 and up of the SDK (https://github.com/stripe/stripe-android/blob/master/CHANGELOG.md#1421---2020-03-26).

Version updates like this require significant testing and have dependencies on other libraries or SDKs. Our upgrade to Flutter 2.0 is a good example of this, a fork in our development that requires all SDKs and Libraries to be compliant. The latest Stripe SDK designed for Flutter is in Beta, now at version 1.3.0, and would offer improvements to our user experience with better native implementations of Stripe's features.

Until we release an updated version of the app with an updated version of the Stripe SDK, the current release of our app is no longer available for download on Google Play. 

If you already have the app installed, you can continue to use it. The app was approved by Google and the non-compliant code is not being used in the Stripe SDK. 

There are no issues with the iOS version of our app and it remains available on the App Store.