Gathering detailed insights and metrics for @stripe/stripe-react-native
Gathering detailed insights and metrics for @stripe/stripe-react-native
Gathering detailed insights and metrics for @stripe/stripe-react-native
Gathering detailed insights and metrics for @stripe/stripe-react-native
npm install @stripe/stripe-react-native
0.40.0 - 2024-11-20
Published on 20 Nov 2024
0.39.0 - 2024-10-15
Published on 15 Oct 2024
0.38.6 - 2024-09-04
Published on 04 Sept 2024
0.38.4 - 2024-08-02
Published on 02 Aug 2024
0.38.3 - 2024-07-22
Published on 22 Jul 2024
0.38.2 - 2024-07-19
Published on 19 Jul 2024
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
1,287 Stars
637 Commits
263 Forks
47 Watching
26 Branches
317 Contributors
Updated on 27 Nov 2024
TypeScript (41.27%)
Swift (26.8%)
Kotlin (26.26%)
Java (1.48%)
Objective-C (1.39%)
JavaScript (0.68%)
C++ (0.66%)
Shell (0.6%)
Objective-C++ (0.48%)
Ruby (0.22%)
Makefile (0.14%)
C (0.01%)
Cumulative downloads
Total Downloads
Last day
10.2%
21,473
Compared to previous day
Last week
4%
110,145
Compared to previous week
Last month
-0.5%
467,717
Compared to previous month
Last year
85.4%
3,994,841
Compared to previous year
3
20
The Stripe React Native SDK allows you to build delightful payment experiences in your native Android and iOS apps using React Native. We provide powerful and customizable UI screens and elements that can be used out-of-the-box to collect your users' payment details.
Get started with our 📚 integration guides and example project, or 📘 browse the SDK reference.
Updating to a newer version of the SDK? See our changelog.
Simplified Security: We make it simple for you to collect sensitive data such as credit card numbers and remain PCI compliant. This means the sensitive data is sent directly to Stripe instead of passing through your server. For more information, see our Integration Security Guide.
Apple Pay: We provide a seamless integration with Apple Pay.
Payment methods: Accepting more payment methods helps your business expand its global reach and improve checkout conversion.
SCA-Ready: The SDK automatically performs native 3D Secure authentication if needed to comply with Strong Customer Authentication regulation in Europe.
Native UI: We provide native screens and elements to securely collect payment details on Android and iOS.
PaymentSheet: Learn how to integrate PaymentSheet, our new pre-built payments UI for mobile apps. PaymentSheet lets you accept cards, Apple Pay, Google Pay, and much more out of the box and also supports saving & reusing payment methods. PaymentSheet currently accepts the following payment methods: Card, Apple Pay, Google Pay, SEPA Debit, Bancontact, iDEAL, EPS, P24, Afterpay/Clearpay, Klarna, Giropay, Sofort, and ACH.
If you're selling digital products or services within your app, (e.g. subscriptions, in-game currencies, game levels, access to premium content, or unlocking a full version), you must use the app store's in-app purchase APIs. See Apple's and Google's guidelines for more information. For all other scenarios you can use this SDK to process payments via Stripe.
1yarn add @stripe/stripe-react-native 2or 3npm install @stripe/stripe-react-native
Each Expo SDK version requires a specific stripe-react-native
version. See the CHANGELOG for a mapping of versions. To install the correct version for your Expo SDK version run:
1expo install @stripe/stripe-react-native
Next, add:
1{ 2 "expo": { 3 ... 4 "plugins": [ 5 [ 6 "@stripe/stripe-react-native", 7 { 8 "merchantIdentifier": string | string [], 9 "enableGooglePay": boolean 10 } 11 ] 12 ], 13 } 14}
to your app.json
file, where merchantIdentifier
is the Apple merchant ID obtained here. Otherwise, Apple Pay will not work as expected. If you have multiple merchantIdentifier
s, you can set them in an array.
compileSdkVersion
must be 34
. See this issue for potential workarounds.Components
In order to use CardForm component, you need to install and configure Material Components theme in your app.
app/build.gradle
file with specified version1implementation 'com.google.android.material:material:<version>'
styles.xml
file1<style name="Theme.MyApp" parent="Theme.MaterialComponents.DayNight"> 2 <!-- ... --> 3</style>
The Stripe React Native SDK requires Xcode 14.1 or later and is compatible with apps targeting iOS 13 or above. For iOS 12 support, please use @stripe/stripe-react-native@0.19.0
.
The SDK uses TypeScript features available in Babel version 7.9.0
and above.
Alternatively use the plugin-transform-typescript
plugin in your project.
You'll need to run pod install
in your ios
directory to install the native dependencies.
For a complete example, visit our docs.
1// App.ts 2import { StripeProvider } from '@stripe/stripe-react-native'; 3 4function App() { 5 return ( 6 <StripeProvider 7 publishableKey={publishableKey} 8 merchantIdentifier="merchant.identifier" // required for Apple Pay 9 urlScheme="your-url-scheme" // required for 3D Secure and bank redirects 10 > 11 <PaymentScreen /> 12 </StripeProvider> 13 ); 14} 15 16// PaymentScreen.ts 17import { useStripe } from '@stripe/stripe-react-native'; 18 19export default function PaymentScreen() { 20 const { initPaymentSheet, presentPaymentSheet } = useStripe(); 21 22 const setup = async () => { 23 const { error } = await initPaymentSheet({ 24 merchantDisplayName: 'Example, Inc.', 25 paymentIntentClientSecret: paymentIntent, // retrieve this from your server 26 }); 27 if (error) { 28 // handle error 29 } 30 }; 31 32 useEffect(() => { 33 setup(); 34 }, []); 35 36 const checkout = async () => { 37 const { error } = await presentPaymentSheet(); 38 39 if (error) { 40 // handle error 41 } else { 42 // success 43 } 44 }; 45 46 return ( 47 <View> 48 <Button title="Checkout" onPress={checkout} /> 49 </View> 50 ); 51}
To initialize Stripe in your React Native app, use the StripeProvider
component in the root component of your application, or use the initStripe
method.
StripeProvider
can accept urlScheme
, publishableKey
, stripeAccountId
, threeDSecureParams
and merchantIdentifier
as props. Only publishableKey
is required.
1import { StripeProvider } from '@stripe/stripe-react-native'; 2 3function App() { 4 const [publishableKey, setPublishableKey] = useState(''); 5 6 const fetchPublishableKey = async () => { 7 const key = await fetchKey(); // fetch key from your server here 8 setPublishableKey(key); 9 }; 10 11 useEffect(() => { 12 fetchPublishableKey(); 13 }, []); 14 15 return ( 16 <StripeProvider 17 publishableKey={publishableKey} 18 merchantIdentifier="merchant.identifier" // required for Apple Pay 19 urlScheme="your-url-scheme" // required for 3D Secure and bank redirects 20 > 21 // Your app code here 22 </StripeProvider> 23 ); 24}
or
1import { initStripe } from '@stripe/stripe-react-native';
2
3function App() {
4 // ...
5
6 useEffect(() => {
7 initStripe({
8 publishableKey: publishableKey,
9 merchantIdentifier: 'merchant.identifier',
10 urlScheme: 'your-url-scheme',
11 });
12 }, []);
13}
You can find more details about the StripeProvider
component in the API reference.
Certain payment methods require a webhook listener to notify you of changes in the status. When developing locally, you can use the Stripe CLI to forward webhook events to your local dev server.
stripe-cli
stripe listen --forward-to localhost:4242/webhook
whsec_***
) to the console. Set STRIPE_WEBHOOK_SECRET to this value in your example/.env
file.This library includes a built in mock file for Jest. In order to use it, add the following code to the Jest setup file:
1import mock from '@stripe/stripe-react-native/jest/mock.js'; 2 3jest.mock('@stripe/stripe-react-native', () => mock);
To have a more control over the mocks, you can extend and override particular methods e.g.:
1const presentNativePayMock = jest.fn(); 2 3jest.mock('@stripe/stripe-react-native', () => ({ 4 ...mock, 5 presentNativePay: presentNativePayMock, 6}));
See the contributor guidelines to learn how to contribute to the repository or to learn how to run the example app.
This is known limitation of using singleTask
as your launchMode
on Android. See here for a workaround.
Undefined symbols for architecture x86_64
on iOSWhile building your iOS project, you may see a Undefined symbols for architecture x86_64
error. This is caused by react-native init
template configuration that is not fully compatible with Swift 5.1.
Undefined symbols for architecture x86_64:
"(extension in Foundation):__C.NSScanner.scanUpToString(Swift.String) -> Swift.String?", referenced from:
static Stripe.STPPhoneNumberValidator.formattedRedactedPhoneNumber(for: Swift.String, forCountryCode: Swift.String?) -> Swift.String in libStripe.a(STPPhoneNumberValidator.o)
"__swift_FORCE_LOAD_$_swiftUniformTypeIdentifiers", referenced from:
__swift_FORCE_LOAD_$_swiftUniformTypeIdentifiers_$_Stripe in libStripe.a(PKPaymentAuthorizationViewController+Stripe_Blocks.o)
Follow these steps to resolve this:
project -> build settings
, find library search paths
and remove all swift related entries such as:
$(TOOLCHAIN_DIR)/usr/lib/swift/$(PLATFORM_NAME)
and $(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)
.Fix.swift
), check the appropriate Targets and create a bridging header when prompted by Xcode.TypeError: null is not an object (evaluating '_NativeStripeSdk.default.initialise')
on AndroidYou might see error this whilst initializing the StripeProvider
component with Expo. This is caused by using an older version of Expo before stripe-react-native was officially supported. Updating Expo Go from the stores (or locally on simulators installed with expo install:client:[ios|android]
) should fix the problem.
If you're still having troubles, please open an issue or jump in our developer chat.
Apple Pay Is Not Available in "My App Name"
This can occur if you attempt to process an Apple Pay payment on a physical device (even in test mode) without having created and uploaded your Apple Pay Certificate to the Stripe Dashboard. Learn how to do that here.
No vulnerabilities found.
Reason
17 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
security policy file detected
Details
Reason
binaries present in source code
Details
Reason
Found 15/30 approved changesets -- score normalized to 5
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
23 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More