🚨 This library is no longer maintained 🚨

If you're building apps with React Native, please use Stripe's official React Native library.

tipsi-stripe

If for some reason you cannot migrate to it now. And you can offer with testing new beta versions, please reach me in discord (name: cybergrind#4625). Just PM with github account name + platforms you can check will be enough. I will ping you when we have something to check.

React Native Stripe binding for iOS/Android platforms

Join our Discord channel to access the beta, to get support from the contributors, and to help us be aware of any issues you find. Here is the invite link: https://discord.gg/vmBxnBw

We'll make notifications on that channel as new beta releases are published, along with sharing documentation and handling questions.

p.s. if you are skilled at writing Appium tests, please raise your hand on the channel!

Cheers!

Documentation

https://tipsi.github.io/tipsi-stripe/docs/index.html

# help us with docs!
npm install docusaurus

# to run docs locally
npm run start-docs

# and open http://localhost:3000/tipsi-stripe/docs/index.html

# upgrade existing docs website in repo
npm run build-docs

Changelog

Full changelog

[9.0.0 - 2021-03-16 Bumped ios sdk and fixed xcode 12.5]

[8.0.0] - 2021-01-16 Breaking changes

[7.0.0] - 2019-01-08 Breaking changes

[6.0.0] - 2018-10-24 Breaking changes

[5.0.0] - 2018-03-21 Breaking changes

Documentation

https://tipsi.github.io/tipsi-stripe/

# help us to upgrade docs locally
npm run start-docs

# upgrade existing docs website in repo
npm run build-docs

Community

Discord

License

tipsi-stripe is available under the MIT license. See the LICENSE file for more info.

Changelog

[11.0.0] - 2023-03-31

Breaking changes:

• 863 Update stripe-ios dependency to support building against iOS 16 SDK

To support this change, the minimum iOS version has been increased from 11 to 12.

[10.0.0] - 2022-06-22

• 840 Add deprecation notices to: library, readme, docs, CLI

[9.2.0] - 2021-10-19

• 554 Android: forward error code & message on failed confirmPaymentIntent

[9.1.1] - 2021-06-18

• 792 fix 3ds crash after upgrade to 16.10.0

[9.1.0] - 2021-06-17

• 790 android: bump stripe-android to 16.10.0

[9.0.0] - 2021-03-24

• 741

• 730 ios: bump stripe-ios to v21

[8.0.1] - 2021-01-17

• 710 Android: japanese translation

[8.0.0] - 2021-01-16

Android

• Compile SDK Version increased from 26 -> 28
• Target SDK Version increased from 26 -> 28
• Min SDK Version increased from 16 -> 19
• Support libraries increased from 27.1.0 to 28.0.0
• stripe-android upgraded from 8.1.0 to 10.4.0

iOS

• Minimum compatible stripe-ios sdk -> 16.0.7, but recommended 17.0.1 or later (update your Podfile or vendored stripe-ios!)
• Xcode version: recommended 10.3.1 or later

New SCA-ready APIs

• stripe.createPaymentMethod(…)
• stripe.confirmPaymentIntent(…)
• stripe.confirmSetupIntent(…)
• stripe.authenticatePaymentIntent(…) (only used with manual confirmation mode)
• stripe.potentiallyAvailableNativePayNetworks(…)

Common

• Breaking The Card form now returns a PaymentMethod. The Card form will no longer return a token (or Source)
• Warning Supports React Native 59.x (other versions at your own risk)
• JSDoc-annotated API Descriptions for the new APIs
• Helper methods stripe.slugForCardBrand(…) and stripe.presentableStringForCardBrand(…) to normalize Card Brand Strings that change values depending on which API you're working with. (Stripe API oddity)

Bug fixes

• Prevented toErrorCode from itself causing an error

Examples

• The example app has new PaymentIntent and SetupIntent screens that can be used to test various card scenarios
• The example app requires a backend for those screens, which can be forked and one-click deployed to Heroku from:
  • mindlapse/example-tipsi-stripe-backend
  • You need to set the environment variable BACKEND_URL to the location it is deployed

Dev tooling

• Added .circleci config
• Added eslint & prettier config

[7.5.0] - 2019-04-22

• Google pay: capture email
• Add translations for German, Dutch, Italian and Spanish.
• android: update CreditCardEntry:1.5.1

[7.4.0] - 2019-02-25

• Switch from compile to implementation in gradle file

[7.3.0] - 2019-02-15

• Call reject directly in createSourceWithParams

[7.2.0] - 2019-01-29

• Remove broken imports

[7.1.0] - 2019-01-14

• Fixed issue #232 Added card type for source creation (#261)

[7.0.0] - 2018-10-28

• Update iOS Stripe SDK to 14.0.0
• Update Android Stripe SDK to 8.1.0
• Fix unassigned promise rejector bug

[6.1.0] - 2018-10-28

• Update CreditCardEntry to 1.4.10

[6.0.0] - 2018-10-24

• Update iOS Stripe SDK to 13.2.0
• Update iOS deployment target to 9.0
• Update Android Stripe SDK to 8.0.0

[5.6.0] - 2018-08-22

Added

• Common error codes. Part of them provided by tipsi-stripe, another part by Stripe itself.

[5.5.1] - 2018-08-10

Added

• paymentRequestWithAndroidPay now supports boolean phone_number_required field to ask a user for phone number

[5.5.0] - 2018-08-08

Added

• tipsi-stripe now respects project-level GMS version on Android

[5.4.0] - 2018-07-27

From this release we are starting unify our Public API.
There was a difference between iOS and Android API, now we've created new methods that currently work as a proxy.
So, we have marked deprecated methods inside src/Stripe.js, and yes there is no more Stripe.${platform}.js files.
But, you won't see any changes. Breaking changes will be introduced in version 6.

DEPRECATED METHODS

• deviceSupportsAndroidPay and deviceSupportsApplePay => deviceSupportsNativePay
• canMakeAndroidPayPayments and canMakeApplePayPayments => canMakeNativePayPayments
• paymentRequestWithAndroidPay and paymentRequestWithApplePay => paymentRequestWithNativePay
• completeApplePayRequest => completeNativePayRequest (Android implementation doesn't exist)
• cancelApplePayRequest => cancelNativePayRequest (Android implementation doesn't exist)
• openApplePaySetup => openNativePaySetup (Android implementation doesn't exist)

As you can see all platform specific methods are now unified.
We called them Native Methods because Google/Android Pay and ApplePay are native payments systems unlike Credit Cards.

Changed

• Stripe.ios.js and Stripe.android.js => Stripe.js
• Native iOS TPSStripeManager renamed to StripeModule
• Example App now uses new unified methods

[5.3.0] - 2018-07-23

Changed

• REACT_CLASS for Native Android implementation of PaymentCardTextField renamed CreditCardForm => TPSCardField
• PaymentCardTextField merged into one compoment. It's a first step to clearing the difference between iOS and Android
• Android Pay => Google Pay in android/src/main/res/values/strings.xml
• prop-types in example updated 15.5.10 => 15.6.1, appium 1.8.0 => 1.8.1

Added

• Default string value for Cancel button in Card Form gettipsi_card_enter_dialog_negative_button
• Support overflow style property on PaymentCardTextField (now it has <View /> wrapper inside)

Removed

• Obsolete AndroidPay flow

[5.2.4] - 2018-06-28

Added

• Added missing {number|expiration|cvc}Placeholder fields to iOS' <PaymentCardTextField />

[5.2.3] - 2018-06-07

Changed

• Removed package.json from tipsi-stripe's podspec preserve_paths (to enable adding this pod via a :git key without hitting npm/yarn considering it a js package)

[5.2.2] - 2018-06-01

Changed

• Fixed int LOAD_PAYMENT_DATA_REQUEST_CODE in GoogleApiPayFlowImpl.java (< 65535)

[5.2.1] - 2018-05-05

Added

• Fixed an error with PropTypes

[5.2.0] - 2018-04-04

Added

• Method stripe.canMakeAndroidPayPayments() checks if gpay supported and user has existing payment method

Changed

• Method stripe.deviceSupportsAndroidPay() doesn’t require anymore user to have existing payment method

[5.1.0] - 2018-03-28

Changed

• Method deviceSupportAndroidPay() now also checks if google pay has at least one existing payment method (for example user attached his card before)

[5.0.0] - 2018-03-21

Breaking changes:

1) Initialization

before 5.0.0:

// somewhere in the app start section

stripe.init({
  merchantId: '<MERCHANT_ID>',
  publishableKey: '<PUB_KEY>',
  androidPayMode: 'test',      
})

stripe.paymentRequestWithAndroidPay(paymentOptions)

after 5.0.0:

single-step initialization

// same as above except used method name

stripe.setOptions({
  merchantId: '<MERCHANT_ID>',
  publishableKey: '<PUB_KEY>',
  androidPayMode: 'test',      
})

stripe.paymentRequestWithAndroidPay(paymentOptions)

multi-step initialization

// somewhere in the app start section
// make sure you've set androidPayMode before using androidPay related methods i.e.
// stripe.deviceSupportsAndroidPay()
// stripe.paymentRequestWithAndroidPay()
// or runtime exception will be thrown

stripe.setOptions({
  androidPayMode: 'test',      
})

// somewhere else later i.e. near store cart code
stripe.setOptions({
  publishableKey: '<PUB_KEY>',
})

// make sure you've set *all* needed options before, both androidPayMode and publishableKey
// or exception will be thrown

stripe.paymentRequestWithAndroidPay(paymentOptions)

2) billing/shipping address requirement

before 5.0.0:

// you couldn't before set billing_address_required, shipping_address_required options
// to require user filling that data. shipping_address_required was true by default
// and such data was missing in the method response (useless user input)

stripe.paymentRequestWithAndroidPay(paymentOptions)

after 5.0.0:

// explicitly set required input from user by
// setting billing_address_required, shipping_address_required props,
// omitted values are false by default

const addressRequirements = {
  billing_address_required: false,
  shipping_address_required: true,
}

stripe.paymentRequestWithAndroidPay({
  paymentOptions,
  ...addressRequirements,
})

Added

• Modern GooglePay api was used by default
• shippingContact, billingContact appear are in results of paymentRequestWithAndroidPay()
• Firebase dependency appears
• More strict runtime argument checks

Changed

• Method setOptions() performs multi-step initialization and used instead of init(). Options publishableKey, androidPayMode are settable at runtime. If method requires presence of options that are unset, runtime exception will be thrown. Special case: androidPayMode re-init is forbidden and leads to runtime exception.
• Wallet api version bump
• AndroidPay flow extracted from StripeModule
• Better naming
• Only create api client on demand
• Extract commons to utils
• Avoid copy and paste in old code

Removed

• Obsolete AndroidPay flow is disabled by default and will be removed soon

Fixed

• Fix of Android Pay Shipping address not working
• Avoid StripeModule Activity NPE
• Avoid bugs regarding options default values
• Fix leaked promise bug