#chop_ford
rugged shardBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- chop-connect-questions, 4 days ago, 8 messages
native garnet
for some additional reference I'm trying to implement something very similar to what was described here in the message above mine; including the message here for context
"""
Right now my flow is
paymentIntent is created where pre authorization is made (triggering 'payment_intent.amount_capturable_updated'). The idempotencyKey is the payment document ID on my server, which is also saved in the transfer_group
const payment = await stripe.paymentIntents.create(
{
amount,
currency,
customer,
transfer_group: idempotencyKey,
payment_method_types: ['card'],
capture_method: 'manual',
},
{ idempotencyKey }
);
seller confirms the booking and the funds are captured ('payment_intent.succeeded')
await stripe.paymentIntents.capture(paymentIntentID);
service is delivered
24h pass from the delivery, if no disputes are opened, then a transfer is created
let transfer = await stripe.transfers.create({
amount: amount*0.9,
currency: currency,
destination: sellerExpressAccountID,
transfer_group: transfer_group,
});
Now user can decide when to do a payout to his bank account
"""
potent quarry
Are you from the same company with Palminyx above?
native garnet
Are you from the same company with Palminyx above?
No, different company. Apologies for the confusion, just thought it'd be helpful since its similar to the flow I'm looking to implement!
potent quarry
To clarify I believe we ask SSN of the Connected Account, not (the customer = paying user) (depends on the country of Platform and the Connected Account)
native garnet
What exactly is the Connected Account then? Does a paying customer not need one?
my main question is around the onboarding of paying users; let's say a user wants to put up a request for a service and is ready to pay for the service upfront (where we hold the amount until the service is completed). Does the requester always have to provide their SSN to even make this initial payment?
And then a separate question: on the seller's end, is it possible to create a connected account for them upfront that can accept money but cannot spend or cash it out until they have provided the necessary details for their account?
potent quarry
From what I understand you the requester is the customer, the service is the Connected Account, you are the Platform
native garnet
yes that's correct
potent quarry
And we should only ask the Connected Account (service seller) the SSN
native garnet
Ok that makes sense
potent quarry
on the seller's end, is it possible to create a connected account for them upfront that can accept money but cannot spend or cash it out until they have provided the necessary details for their accoun
You are thinking of a Connected Account of a Connected Account. That's only possible if your seller holds a Standard Connected Account. But that's complicated
Platform <--- Standard Connected Account <--- (Express/Custom/Standard) Connected Account
native garnet
why does it require that extra step?
potent quarry
Hmm sorry I may misunderstand you. Okie so your seller service will have a Connected Account for them. Let's forget the extra layer mentioned above
(I thought you meant your seller service needs another service provider layer under them)
native garnet
No sorry let me reiterate
i have requesters that put up requests for gigs they'd like fulfilled, with an amount they would pay a recommender if connected to the right person for the gig.
The requester pays upfront (with the money being held by us until the task is marked fulfilled, otherwise it is returned to the requester); other users in the network can then recommend someone to fulfill the gig.
Once the requester confirms with a gig worker, the recommender gets paid out the amount originally offered by the requester for the recommendation
so my question is, if every user can play the role of a recommender (and therefore has the potential to earn), is it possible to defer the collection of their KYC information to when they would like to withdraw money they have received in their stripe account to their bank account?
As opposed to requiring all users to provide SSN upfront prior to even receiving their first payment. The thinking is that if a user does not KYC by a certain time, then the money held in their account gets reimbursed
potent quarry
Um I kinda understand you but not sure about that ability of delaying KYC timing. Don't think that's possible. But you can reach out to Support team to confirm.
To my understanding it's the transfer capability here https://stripe.com/docs/connect/account-capabilities#transfers
native garnet
Um I kinda understand you but not sure about that ability of delaying KYC timing...
how should I reach out to the stripe team?
still carbonBOT
:question: Have a non-technical question, account issue, or need one-on-one support?
We wish we could help, but this community is focused on developers and technical discussions. Our support team will be able to assist you better than we can: https://support.stripe.com/contact