// the find
flutter-stripe/flutter_stripe
Flutter SDK for Stripe.
Flutter SDK wrapping Stripe's native Android and iOS SDKs, plus a partial web implementation via stripe-js. Targets Flutter developers who need payment processing without rolling their own Stripe integration from scratch. Covers PaymentSheet, Apple/Google Pay, CardField, regional payment methods, and financial connections.
- The example app is genuinely thorough — there's a working Node/TypeScript backend, per-payment-method screens for 15+ methods (iDEAL, Klarna, Alipay, etc.), and integration tests, which is more than most Flutter plugin repos bother with.
- Package structure is clean: stripe (interface), stripe_android, stripe_ios, stripe_web, stripe_platform_interface all separated with melos, so you can audit or override individual platform implementations without touching everything.
- Actively maintained through mid-2026 and tracks Stripe's own SDK deprecations — the CardField sunset notice and the shift to PaymentSheet are already documented in the README.
- WASM support is present with specific serving instructions, which is ahead of most Flutter payment plugins that still treat web as an afterthought.
- Android setup is genuinely painful — 8 manual steps including proguard rules, theme changes, FlutterFragmentActivity swap, and Kotlin/Gradle version pinning. None of this is automated or validated at build time, so you'll hit cryptic crashes if you miss one.
- Web support is explicitly 'highly experimental' with only 4 API methods implemented. If you're building a cross-platform app expecting feature parity, web will block you on payment sheet, Apple Pay, and most regional methods.
- Test coverage in the core packages is thin — packages/stripe/test/stripe_test.dart exists but is minimal. The integration tests are all in the example app and require a live backend, making CI setup non-trivial.
- The singleton Stripe.instance pattern means you can't easily test code that calls Stripe methods — there's no dependency injection interface, so unit testing payment flows requires mocking at a platform-channel level.