stripe-cli VS stripe-android

I've always found this to be a very useful practice. Many projects have a few core files (or packages / modules / whatever) where most of the changes happen. Being able to familiarize new contributors (or old returning ones) with those quickly really helps the startup time on a project.

I've added architecture files to projects at multiple jobs now [0], [1] and they've been well received. They're not perfect, but they're better than nothing.

[0]: https://github.com/zapier/zapier-platform/pull/324

[1]: https://github.com/stripe/stripe-cli/blob/master/ARCHITECTUR...

Stripe CLI

Before getting started with this, make sure that you have the Stripe CLI installed. Click me

You'll need the Stripe CLI installed.

The easiest way is to use stripe cli. You can download it here.

​ We use CLIs to perform quick actions from the comfort of our terminals and automate recurring tasks. You might use the GitLab CLI to submit your code in a merge request, so the team can review it and include it in the next release, for example. Many other developer platforms like AWS, Stripe, Sentry, and CircleCI offer CLIs as well. ​ Connecting a CLI to your online account often involves generating API access keys in a browser, then pasting those values into the terminal. Those credentials are usually saved in a plaintext config file that gives the CLI persistent access to your account, even after reboots. But if an attacker or process gains access to your system, they have the same level of access to your account that you do. ​ We built 1Password Shell Plugins so you can securely store all of your access keys in encrypted 1Password vaults, rather than on disk. When you use a Shell Plugin for a particular service, access to the associated API keys is restricted to your specific terminal session. ​ Because they're saved in 1Password, you can securely sign in to any CLI with your fingerprint or another form of biometrics. If the service supports it, MFA codes can be filled automatically – so there’s no need to pull out your phone multiple times every day. ​ In fact, there’s no need to type anything. No plaintext, no typing passwords, no hassle – you can stay in the zone and focus on the task at hand. ​

You’re probably looking for this: https://stripe.com/docs/stripe-cli

The Stripe CLI (command line interface) and Stripe for VS Code extension are essential tools when you’re building, testing and managing your Stripe integration. In this article you’ll learn about the powerful features of the Stripe CLI and how you can leverage those features both on the command line and via the VS Code extension.

You can test locally with the stripe CLI tool https://stripe.com/docs/stripe-cli, that sends the webhook info through localhost.

"I haven't seen excitement around any product and ecosystem launched since 2018 except flutter and Firebase."

Hard disagree, lol. Android Jetpack was launched in 2018. It was basically the second generation of Android development, it was a proper "tech stack" instead of everyone cobbling together third party libraries. Architectures switched over to the one true MVVM, instead of being this mess of MVC, MVP, etc.

Jetpack Compose is pretty amazing, it cut down our LOC by about half because we don't need adapters for every list. Kotlin coroutines & flow is nice. You get reactive programming, no more complex nested if/else conditions. We're not using Fragments or Activities much now either, navigation is via Compose, meaning DI is less necessary. So builds can be much faster too with a 2023 stack, and you can get UI changes rendered in the emulator immediately without even needing to update the build.

Here's a modern stack I made, should be able to spin up an app in an hour, and it shouldn't be too hard to read the code: https://github.com/smuzani/android-minimalist-template

Or if you want something production, Stripe's code is one of my favorites: https://github.com/stripe/stripe-android

Jetpack has some dark moments though, but that's a story for another day.

Ha! I hope not! You can look up my name as a maintainer in the android SDK here: https://github.com/stripe/stripe-android/blob/master/.github/CODEOWNERS and my linkedin here: https://www.linkedin.com/in/jaynewstrom/

Stripe Android SDK: Android SDK versions 20.7.0-20.11.0 were released this month and contain updates and fixes for functionality related to PaymentSheet and Identity.

Stripe Android SDK v20.6.2: Android SDK version 20.6.2 contains several bug fixes for Payments, reduces the size of StripeCardScan, and adds new rememberFinancialConnections features for Financial Connections.

Hi everyone - I'm on the Stripe Mobile SDK team and would love this community's feedback on what you would love to see us improve, namely in stripe-android. Would love to hear things that would make you say "Finally!", would have saved you several hours/days, or even little annoyances. No idea is too farfetched!

The Stripe Android SDK now supports SetupIntents with Google Pay. Use the multipayment UI to gain these features in v17.1.2.

Stripe Android SDK version 17.0.0 and 17.1.0: Android version 17.0.0 introduces GooglePayLauncher and GooglePayPaymentMethodLauncher to simplify Google Pay integration, and version 17.1.0 adds support for WeChat pay. Read more in the release notes.

Android SDK update: The latest version of the Stripe Android SDK (16.5.0) now supports Kotlin coroutines.

Thank you to our top open-source contributors this month: joeltaylor, ybiquitous, gogainda (stripe-ruby); masterjus (stripe-php); westy92, msternow (stripe-android); ees37 (stripe-go); Fonata (stripe-cli); rdsedmundo (stripe-node); hibariya (stripe-samples); risentveber, vinistock, jaredbeck, ryanwilsonperkin, anandvc, RyanBrushett, paracycle (sorbet).

Open-source 3DS2 SDK: We’ve open-sourced our 3DS2 SDK for iOS and Android under the MIT license.