#adam-sct-checkout

1 messages ยท Page 1 of 1 (latest)

somber geyser
#

So you say "to the Checkout" so I thought you used our Checkout product but then you show code where you create the PaymentIntent yourself.
Are you using Checkout or not?

jade kernel
somber geyser
#

Okay, so which part are you curious about, I'm not sure I understand. You control that part of the code and the loop and it's not really Stripe-specific

#

though usually you shouldn't trust that information from the client as it's unsafe and anyone could modify it

jade kernel
#

We're basically hoping the transfers allow us to create as many transfers as there are sellers involved in the transaction. Like if Amazon or Etsy needed to distribute transfers to each Seller involved in the customer's Cart Purchase

jade kernel
somber geyser
#

not really

#

Sorry I'm just confused by the question

#

But yes you can create 1, 2, 20, 4000 transfers, it's all supported

#

Note that the way you approach this you are floating the funds entirely from your own balance

jade kernel
jade kernel
somber geyser
#

nope

#

but really you want the flow I just linked you to

#

almost no business wants to "float the funds". You're unlikely to charge me $1000 today, and then immediately pay $900 to an etsy seller out of your own company's money and then wait 2 days to get the $1000 back from the banking network

#

almost everyone wants the funds to be released together so you basically want source_transaction: 'ch_123' in this flow (what I linked you to) but it still works the same beyond that

jade kernel
#

Okay we'll read up more on source transactions and floating

jade kernel
hasty lava
#

hello Adam

#

I'm on here now

jade kernel
#

Especially since you can only have 1 destination for Destination charges

#

@hasty lava ๐Ÿ‘‹

hasty lava
#

so no Destination Charges create the Transfer immediately, what you described here

Its probably not feasible to use Destination Charges to our platform account right and then Transfer to each connected account manually?
that is Separate Charges & Transfers

jade kernel
hasty lava
#

no

#

or maybe I misunderstood you

jade kernel
#

Oh wait Separate Charges... allows for many destinations

#

But Destination charges only supports 1 destination..?

hasty lava
#

yes

#

Destination supports only 1 destination acct

#

and Separate Charges & Transfers supports n destinations

jade kernel
#

Okay, and its not scalable to manually payout connected accounts from our Platform Dashboard so I guess we'll continue with Sep Chg Tfr

#

just going to read on Source Transactions really quick

jade kernel
#

Can these Stripe paymentIntent's be maybe integrated with Spreedly's Apple Pay?

somber geyser
#

We don't know anything about Spreedly so you'd have to ask them directly what their API supports

jade kernel
#

Okay, I was just referring to prev threads, Apple Pay is available on Safari, but would it work on an iOS app and Android app?

somber geyser
#

Apple Pay never works in Android. And yes it works in an iOS app if you integrate it

jade kernel
somber geyser
#

I'm honestly confused by the ask

#

what does "Not transfers" have to do with mobile?

#

Transfer creation always has to happen server-side where you safely use your Secret API key

#

Unfortunately, I'm not sure what you're calling "we're publishing ReactJS code" and how your integration is built overall

#

yes Apple Pay works on iOS devices in Mobile Safari, whether you write vanilla JS or React or other frameworks

#

same for Android + Chrome

#

but you also mentioned Spreedly on top of it (which has their own integration separate from Stripe as far as I know)

jade kernel
#

Oh I dont know, gotcha, yes. I think Google Signin has not worked on iOS, although I dont remember if thats server side or not

somber geyser
#

google signin has nothing to do with Stripe or server-side

#

you've lost me completely ๐Ÿ˜…

jade kernel
somber geyser
#

what does Spreedly have to do with Apple/Android pay?

#

Spreedly is a "card vault" that aggregates numerous payment processors such as Stripe or Braintree

jade kernel
jade kernel
somber geyser
#

yeah it makes no sense to use Spreedly just for Apple and Google Pay ๐Ÿ˜…

#

like Stripe supports it, if you don't use Spreedly in general, please don't use them just for mobile wallets it'll make your integration extremely complex

jade kernel
somber geyser
#

yeah I worry you're mixing up a lot of things right now all mushed together

#

but yes Apple Pay works in iOS apps, either written straight in Swift of Objective C or with a webview + JS

#

same for Google Pay / Android / Chrome

jade kernel
somber geyser
#

sounds good