#Josh!
versed tree
Hello! I'm guessing you want a way of collecting payment details and charging them at later points (when the tasks aren't complete), right?
livid ice
Hello! I'm guessing you want a way of collecting payment details and charging th...
yep!
conditionally
versed tree
Gotcha - then I'd recommend starting here: https://stripe.com/docs/payments/save-and-reuse?platform=react-native&ui=payment-sheet
livid ice
Are there any policies we should be aware of? How do we ensure it is clear that the user is signing off to these conditional transactions?
it is important to us that we are able to dispute any card chargebacks
versed tree
I don't believe we show anything extra for cards in the payment sheet - if you need the fact that these cards may be charges later to be really clear to your users you'd need to show that in your own UI (and I'd definitely recommend talking to support !https://support.stripe.com/contact to see if there are any other compliance/policy obligations)
livid ice
ok! looking through the link you sent rn, please do not close the thread
This is the design we envisioned for payment input. It's our impression that the payment sheet is all coded by Stripe, and then we can modify the CSS.
Is this correct?
We based it off of other apps using Stripe
versed tree
I belive there's some styling you can do (https://stripe.dev/stripe-react-native/api-reference/modules/PaymentSheet.html#AppearanceParams) but I haven't messed around with it myself
livid ice
ok!
do you know how this all interacts with Apple in-app purchase policies?
we don't believe it is within the scope but we were wondering how conflicts between Stripe utilization and apple policies typically go
versed tree
They shouldn't really be interacting at all - they should be completely separate flows
livid ice
They shouldn't really be interacting at all - they should be completely separate...
ah i mean is there any boilerplate terms for Stripe that we need to put in our privacy policy/elsewhere when submitting our app
versed tree
Ah gotcha - I don't think we have any specific boilerplate terms, I think you just have to make it clear when submitting your app what the stripe flows are for (so that they know you're not using them for things that should be in-app purchases)
livid ice
alright! thank you so much for the insight!
one more thing!
some of our transactions may be very small ($1). Stripe's 2.9% + 30¢ charge would take a significant chunk of that. Any recommendations on avoiding this?
versed tree
There isn't really a way around this - we have our own limitations in place (we have a minimum charge amounts for each currency https://stripe.com/docs/currencies#minimum-and-maximum-charge-amounts in place to help with this)
The only thing I could think of is batching your charges together so that instead of 5, $1 charges you just do a singlr $5 charge (but that may not work for your business model)
glad muralBOT
livid ice
There isn't really a way around this - we have our own limitations in place (we ...
oh ok! we figured
how do we accomodate different currencies? Is that handled through the payment sheet?
or is that handled completely on our side?
shadow hemlock
you would handle this completely on your side today
livid ice
ok thank you!