Developer Diary: Journey of a payment integration
summary
Built a Stripe payment flow for a B2B mobility app, first as a native plugin using Flutter method channels and manually bundled Android/iOS SDKs (fragile, frequent breaking updates), then pivoted to a web checkout served from Firebase Cloud Functions and Firebase Hosting. Banks reject WebViews so integration uses external in-app browsers (flutter_inappwebview/URL launcher), requires universal/app links and Apple Pay assets, and ends up working but costs far more dev time than expected; plugin refactor remains on the roadmap.
AI-written summary · about
chapters (17)
- 0:00Payment integration journey
- 1:07Speaker and Urite platform
- 2:30Developer diary setup
- 3:59Native SDK integration challenges
- 5:03Native SDK pain points and plugin
- 9:24Visa SDK breaking changes
- 11:54Switch to web-based payment
- 14:52Web view integration failure
- 15:57Mandatory in-app browser
- 17:24Firebase Cloud Functions for form
- 19:53Choosing in-app browser plugin
- 22:23Deep link requirements
- 23:05Custom URL schemes vs universal links
- 24:51Firebase Hosting for deep links
- 27:17Lessons from web integration
- 28:21Third-party provider costs
- 29:03Summary and Q&A
related talks
29mHow to build for and market to developers
32mBuilding for Builders: Designing APIs for the Internet Economy
14mHow to drive conversions with Google Pay for Android
36mcontribute to the Flutter ecosystem.
21mCollision 2015 - John Collison of Stripe with Alexandra Suich of The Economist
44mBuilding Pieces for Developers Our Journey with Flutter and Dart
34mFrom Plug-and-Play to Fully Custom
16mSign-in and Payments without Forms