#riptired-reactnative-paymentsheet

1 messages ยท Page 1 of 1 (latest)

simple bayBOT
iron otter
#

๐Ÿ‘‹ Hey @golden halo ! Sorry about that! We try to help in real time in this server and we have to quickly close inactive threads are we often help 20+ people in parallel.
I'm happy to help you further though! Can you clearly summarize your question/issue?

golden halo
#

Hey

#

this is the thread

#

My follow up questions were what is the payment sheet, I only see one reference to that in the docs

#

and why would I need to pass a client secret over API requests?

iron otter
#

PaymentSheet is our UI component in our iOS SDK

#

Let's try a step back: which exact doc are you following and what is the problem?

golden halo
#

Ah I am talking about react native

iron otter
#

Sure but our React Native SDK will rely on our iOS or Android SDK under the hood

golden halo
#

is payment sheet a reference to the mobile payment element shown in the docs I sent above?

iron otter
#

If you are using Stripe Checkout as a product, none of this matters at all. That product only works in a browser. So in React Native you wouldn't do anything specific other than redirecting your customer to a browser instead.

#

riptired-reactnative-paymentsheet

golden halo
#

wait so there is no way to use stripe checkout in the app?

#

just to be clear by stripe checkout I mean the single page UI stripe provides that handles sales tax and payment

iron otter
#

Checkout is a web-based hosted payment flow

#

So in a mobile app you simply redirect to Checkout in a browser

golden halo
#

okay what if I want to keep the user in the app -- does stripe tax work with the implementation in the docs I sent above?

iron otter
#

No it won't work

#

Stripe Tax is only compatible with products like Checkout or Invoicing. So really your best bet is to use a browser for this

golden halo
#

๐Ÿ˜ฆ

#

yikes

#

so how do people calculate sales tax when using this implementation?

iron otter
#

Also what are you selling? Because Apple/Google have strict rules around payments in mobile apps

golden halo
#

We are selling physical products, i.e. clothing

iron otter
#

Gotcha, so yeah in that case the best option is really to keep Checkout and open a webview. That's what most people do and that will make your life way easier

golden halo
#

okay, lets say I wasn't using checkout and followed the implementation in the guide i linked, what do those customers use for sales tax?

iron otter
#

In the past, they used a third-party and calculated it entirely themselves. Now you can use https://stripe.com/docs/tax/custom and integrate this in your own logic. None of this is built in though, you collect the information, so that you ask us to calculate tax and then you do the math

golden halo
#

okay so if I want to keep the payment flow entirely in the app I would need to use my own components for shipping, hit stripes api for the sales tax and then use the payment sheet for completing the transaction

iron otter
#

yes

golden halo
#

So its possible to keep the transaction in the app, I would just need to build the requisite infrastructure to make requests to the stripe custom tax api and handle collecting the shipping info and any related information beforehand

iron otter
#

yes

golden halo
#

whats the most commonly selected flow between keeping payment in app vs using stripe checkout in a web view?

iron otter
#

I would assume 95% use Checkout. Our API for standalone tax calculation is brand new and only shipped a month ago so before that anyone would use Checkout or their own tax calculation logic I assume

golden halo
#

Interesting, alright thanks for your advice! I'll have to look into this alternative to checkout webview