We’ve been using the Flutter plugin for about six months now (UK), and we’re experiencing a lot of difficulty adding cards on file in our app. We can confirm that about 70% of the cards tried are being successfully added but the rest aren’t, they fail at the verfication step. We’ve upgraded to the latest version of the Plugin, but noticed that fewer cards were working with that version and reverted back to 1.7.6.
There’s nothing we’re able to do to improve this and ideally don’t want to change providers. Can you comment on whether this is going to improve? Do you know if it’s strictly a flutter problem or whether these issues are platform dependent? It’s a big source of frustration with our customers and completely out of our hands.
What difficulties are you seeing? Is it buyer verification errors? Do you have some examples that we can look into?
I’ve posted the details of the issue on GitHub:
I can’t give exact details because they’re customer cards. They’re all English cards. The they don’t seem to trigger the verify steps and fails. This all happens within the plugin.
What version of In-App Payment SDK is the Flutter plugin running?
The version is 1.7.6. As mentioned before, we seem to have less card coverage with 1.7.7. The same card tested by a Dev works with in 1.7.6 but not in 1.7.7.
That’s the Flutter version. At this time the current In-App Payment SDK iOS version is 1.6.2. What version is your plugin using?
This is what the documentation says. The versions of the SDKs are defined by the Flutter Plugin. We don’t change this.
Okay, if you update it to the latest version does it resolve the issue? We do recommend that you update the plugin on a regular cadence.
I mentioned earlier that updating the Flutter plugin results in fewer cards working… There are more details in the posted git issue I referenced. This is why we reverted back to 1.7.6. Making changes within the plugin isn’t ideal because we’d have to fork to keep the changes.
What’s your application ID?
application id is sq0idp-THIqoyMaSYA1fXUrNNoZ5A
The team tried to reproduce this and was able to both generate a nonce as well as go through
verifyBuyer successfully. Whats the
location_id and the timestamps of when you saw the issue?