#braydensterrett
eternal scarab
Hi there
gritty raptor
I'm passing an email field to the Stripe::Account.create call that I'm making, but I still see the need for a user to enter an email into the KYC forms.. is there a way I can pre-fill this info so the user doesn't have to enter it?
eternal scarab
What type of Connected Accounts are you working with?
eternal scarab
Gotcha, are you collecting bank accounts here via the onboarding form?
gritty raptor
Yes we are
{
type: "custom",
country: "US",
email: @member.email,
business_type: "individual",
individual: {
first_name: @member.first_name,
last_name: @member.last_name,
email: @member.email
},
business_profile: {
url: @member.default_onboarding_business_url
},
settings: {payouts: {debit_negative_balances: true, schedule: {interval: "manual"}}},
requested_capabilities: [:transfers, :tax_reporting_us_1099_misc, :tax_reporting_us_1099_k],
metadata: {member_id: @member.id, member_username: @member.username}
},
api_key: ENV["STRIPE_MARKETPLACE_API_KEY"]
)
That's our Account creation call. Those @member fields are just being filled with data from our database
brave pawnBOT
eternal scarab
Okay yeah
So with bank account collection you can't prefill that email/phone
The reason is that your user can log in and update the bank account themselves
Since that is sensitive data, they control their login here and it isn't shared with you.
gritty raptor
Oh interesting.. do they access their account with just an email? Is it possible for me to test that?
I'd like to see how that looks for the user.
Or is this when they would do an AccountLink with type: "account_update"
Is that how they would access it?
eternal scarab
Yep exactly
They would access via an account_update Account Link
You should be able to test this I believe
gritty raptor
Yeah I can do that for sure. So that email that I'm pushing into the Stripe::Account creation process, is that actually being used for anything?
Like is that the email that an automated email would go to? Or is the one they fill out in the form the one?
Just trying to understand how the information we're putting on the Account will be used down the line
eternal scarab
One sec let me double check on something related to that
Okay @gritty raptor yeah that email is only used for your own identification (we describe this here: https://stripe.com/docs/api/accounts/create#create_account-email) and I just had to verify when we would send emails to that email and it is only relevant for 1099 tax form delivery (https://stripe.com/docs/connect/deliver-tax-forms) if you are utilizing that.
gritty raptor
Yes, we will be. That's good information. Thanks for that.
I've got another question here that I'd love to get an answer on.
We're creating accounts with a "manual" payout schedule. In the Stripe dashboard I'm seeing this:
What exactly does the 2 day rolling basis mean?
From what I'm seeing in the docs, all payouts will have to be inacted by us via an API call (this is what we want). I just want to understand what this 2 day rolling basis part means and if it has any implications into what we're trying to do.
eternal scarab
That means how long until the funds become available to be paid out
But yes, the payout itself will only be initiated via your explicit API request
gritty raptor
Okay so in a scenario, let's say we would transfer funds into the user's account from our platform account on Monday. The customer would not be able to action those funds into their actual bank account until Wednesday?
Is that what you're saying?
eternal scarab
Depends on the charge flow you are using really
If you are moving funds from your platform available balance into the Connected Account then no, those would already be available
But if you use Destination Charges for instance then the funds would not be available for 2 days
gritty raptor
Is a Destination Charge where this user would be accepting like credit card payments from customers in like a POS type situation?
We won't have anything like that. We'll always be paying these users out from our platform account, so it sounds like that bit of information isn't really a concern of ours.
eternal scarab
No a destination charge means the funds are transferred immediately on payment to your Connected Account. See: https://stripe.com/docs/connect/destination-charges
Do you know which charge flow (Direct, Destination, Separate Charges & Transfers) you are going to be using?
gritty raptor
I believe just transfers
The setup is basically a marketplace where this account owner lists a product, a buyer pays for it and we hold the funds until the item is shipped and authenticated by us. Then we release the funds to the seller
So we'll just be topping up our platform account as the items are authenticated, and then transfer from that platform account to the connected account whenever we have confirmation of authentication.
Tell me if I'm way off base in thinking that transfers is all we need to support that situation.
As well, Stripe will not be the platform that is accepting payment from the buyers. This is happening in a Shopify store which seems to eliminate the need for Destination Charges from what I'm reading
eternal scarab
Gotcha then you can mostly ignore the two days there
And it will just be dependent on the funds being available in your platform
Then they can be paid out immediately
gritty raptor
Perfect, thanks for the info!