Alexis Yushin

Looks like it would be possible to do this the same way https://github.com/Lyokone/flutterlocation is implemented for both mobile and web. We could create flutter_stripe_payment_platform for platform abstraction and flutter_stripe_payment_web to...

It seems there's a dart wrapper for stripe https://pub.dev/packages/stripe and also there's a fully native https://pub.dev/packages/stripe_sdk Unfortunately I don't have much time to work on this now, but I would...

good news! 1. Managed to generate functional js-interop library with [https://github.com/dart-lang/js_facade_gen](dart-js-facade-gen) 2. Got a few methods working Will post prototype library soon. If anybody else is working on this -...

So I've made a [https://github.com/jonasbark/flutter_stripe_payment/pull/147](pr) initially for native pay but there are quite a few open questions: - native pay supports both Apple and Android so canMakeNativePay requires country, currency...

Well the PR above works for us so far, but it requires a bit of adaptation as per above.

There's this breaking change: `native pay supports both Apple and Android so canMakeNativePay requires country, currency and returns null if not supported or object with applePay = true for apple...

@gorillatapstudio we use this in production: ``` stripe_payment: git: url: https://github.com/apexlabs-ai/flutter_stripe_payment ref: web ``` The only plan we have is to split it into separate `flutter_stripe_payment_web` but on hold due...

that could be - i'll try to have a look at it when i have time, however it can be we are not using that functionality at all

1. See the above: > native pay supports both Apple and Android so canMakeNativePay requires country, currency and returns *null* if not supported or object with applePay = true for...

Well, there's no separate method for "not supported", so that's why you get null to indicate that. We'd need a different interface all together if we don't want null there...