stripe-react-native VS stripe-cli

What is your purpose with the action of opening the payment window? Do you just want to show the cards, or is the user buying a product, or is it for something in the app? The react-native-payment has not seen any updates the past 2 years… I would skip this package for usage. You could use something like https://github.com/stripe/stripe-react-native if you like to use stripe as a payment provider. Or for in app purchases I use https://github.com/dooboolab/react-native-iap So it depends on want you want to accomplish and what kind of payment provider you want to use. Good luck 💪🏽

Example (from stripe github fficial documentation) for Styles.xml: https://github.com/stripe/stripe-react-native/tree/518593e5a64da9e5b7385690a53c9d0cd7395261/android/src/main/res

Stripe React Native: version 0.19 was released, which contains breaking changes required to fit updated brand guidelines from Google for Google Pay and moves the minimum compileSdkVersion to v33.

Stripe React Native: Versions 0.15.0 - 0.18.1 were published this month and include a breaking change: Your compileSdkVersion for android/build.gradle must be set to greater than version 32. There are also updates to confirmPayment, several bug fixes, and the inclusion of Link on PaymentSheet for iOS.

Stripe React Native v0.15.0–0.16.0: Two new releases to our React Native library this month include support for dark mode on the GooglePayButton and CardForm components. These updates also introduced several breaking changes from previous versions.

Stripe React Native v0.12.0–0.14.1: This has been added in the canAddCardToWallet method, for use with Stripe Issuing in combination with Apple and Google Pay wallets. This set of releases also allows devs to set the default country for both the CardField and CardForm components, and includes several bug fixes.

This is an issue that I opened yesterday. I’ve attached my code over here.

We do have a first-party react native library here: https://github.com/stripe/stripe-react-native. Anything specific with it, you'd like to see improved?

Stripe React Native SDK: The official Stripe React Native SDK is now in public beta to help you build delightful payment experiences using React Native. Watch our video guides on adding the SDK to a React Native app and accepting a payment.

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.