Charlie Cruzan
complete
Integrated into SDK 41 in our most recent patch release with the release of @stripe/stripe-react-native : https://docs.expo.io/versions/latest/sdk/stripe/
You will need to use the most recent versions of Expo Go to use this library by the way!
Sahil Jaidka
Any update on this? I don't want to eject from expo :(
Md. Al-Amin
Can we have any update on this?
Brian Sztamfater
I just published an npm module that implements Stripe Checkout through a WebView, so you can use it on Expo apps without detaching. The link to the repo: https://github.com/briansztamfater/expo-stripe-checkout
I hope it helps!
Sahil Jaidka
Brian Sztamfater: Is this PCI complaint?
Iagor Moraes
By having native form and not a alert screen form with a input is more acceptable, also we can manage the language of the texts based on device language. +1
Brent Vatne
i'm moving this back to open. you can use https://github.com/expo/stripe-expo but i imagine that people want some native integration and that is probably what this feature request is for.
Andreas Lindahl
Brent Vatne: stripe-expo is not longer a valid way for use with Stripe. At least not if you build your own order page within the app. You can still use it within a web browser with Stripe Elements or Checkout. But it would be really nice to have it "native" in the app. So this feature is more then ever requested!
Bradley Huber Jr.
Brent Vatne: I'm under the impression that stripe-expo is no longer PCI compliant, though, right? I thought any CC fields had to be provided by the same party creating the token, hence their DOM-based Elements API. So we cant build our own CC fields in the app and pass them to the stripe API, but since there's no DOM we also can't use Elements to inject a Stripe CC form.
Brent Vatne
open
Viktor Nagy
Do you mean to solve this FR together with https://expo.canny.io/feature-requests/p/apple-pay--android-payments?
Jesper Madsen
Clarification of what is "In Progress" would be great
Jesper Madsen
Brent Vatne , could you clarify please? :-)
Whynot
Jesper Madsen: +1
Brent Vatne
Whynot Jesper Madsen: payments api itself is not actively in development -- we're working on supporting opt-in modules when building standalone apps, so you will be able to opt-in to using the payments api and not have to detach.
Whynot
Thanks for the clarification Brent Vatne ! Great to hear that. I would love to get an ETA for 'opt-in modules when building standalone apps'. Expo 25.0? 26.0?, because depending on this feature I may leave expo to pure react native... But I'd love to stay with expo because of the streamlined processes and short setup -time :)
Brent Vatne
Whynot: not in 25 or 26, unsure about when exactly sorry
Whynot
Brent Vatne: Okay, good luck guys, expo is great! This is gonna be a very valuable thing for Expo. P.S. I'd love to see the Sources functionality too (tipsi-stripe has createSourceWithParams(params) -> Promise
to handle iDEAL, SOFORT, and other european payment methods), but I didn't find this function in your payment API...
Seriously, this may be the most valuable add on for expo EVER because it will make it possible to make PROFITABLE APPS in expo way more easy!
C
Chris
Brent Vatne: Just to confirm, once added, this Payment API will either directly support IAP as an Expo service, or support 3rd-party IAP libs like the ones below, correct? And if yes, which?
Viktor Nagy
Chris: as Brent wrote it above, they plan to add support to the payments api. That api is unrelated to the packages you've mentioned.
arcom
Brent Vatne: opt in modules would be HUGE. I can't believe I missed this comment. Months later now, does it seem like it is still coming in 28?
Brent Vatne
arcom: we have a 37,000 line diff for the first part of this internally.. might ship that in a week. then we need to build infrastructure to take advantage of that
arcom
Brent Vatne: cool. great to hear.
Dylan Falconer
Can someone from Expo clarify what exactly you guys are planning on adding? Can't we just create a form and send a request over HTTP to Stripe to perform pretty much anything?
Load More
→