#halbertj

1 messages · Page 1 of 1 (latest)

fleet turtleBOT
spark tendon
#

hello! who will be the merchant displayed on the customer's credit card statement - will it be you the platform, or the connected account? Also, will you be transferring a single payment to multiple connected accounts?

inland niche
#

The merchant would be the platform

#

So assuming the connect account is enabled, we'd be using destination charges

#

So even if we do the first charge to our account, we could eventually transfer it to the connect account

#

For now, the payment would be transferred to the connect account (minus our service fees)

spark tendon
#

ah yeah, then it should be totally fine to use destination charges and you don't need to wait till the connected account is fully verified for payments. For Destination Charges, the charge/payment occurs on the platform, and a Transfer is made to the connected account

inland niche
#

Ahh, so a destination charge will still work even if the connect account is not yet verified?

spark tendon
#

yep, you can test this out in test mode

inland niche
#

That is great news

#

Thank you

#

Also, just to confirm my understanding:

verification of connect accounts can take 1-3 days?

#

And SSN is required in every case? (assuming we're dealing with individuals)

spark tendon
#

i think that would be in the worst case scenario. In most cases, as the connected account user goes through the onboarding form, the form verifies most of the information synchronously. It's only if additional info is necessary, like ID document uploads whereby it may take a bit more time for the verification. You can take a look at the required verification info here based on your use case : https://stripe.com/docs/connect/required-verification-information

Learn what required verification information you need to collect for each country when using Connect.

inland niche
#

Okay that is good to know, thank you

#

"error": {
"code": "insufficient_capabilities_for_transfer",
"message": "Your destination account needs to have at least one of the following capabilities enabled: transfers, crypto_transfers, legacy_payments",
"request_log_url": "https://dashboard.stripe.com/test/logs/req_qPjA2FurmihJnf?t=1704852104",
"type": "invalid_request_error"
}

#

I got this error when trying to make a charge to a connect account that is not enabled

#

Note I did include the following in the POST request to create the Connect account:

"capabilities": {
"us_bank_account_ach_payments": {
"requested": "true"
},
"card_payments": {
"requested": "true"
},
"transfers": {
"requested": "true"
}
},

spark tendon
#

did the connected account user go through the hosted onboarding form?

inland niche
#

Not yet

spark tendon
#

i probably should have clarified, that you'd at least want the connected account to go through the onboarding form

inland niche
#

Got it

#

Let's look at this another way - say we want to collect money from a customer before a vendor completes their connect account

#

Can we do a direct charge to the platform account and then later do a transfer to the connect account?

spark tendon
#

hrm, then you would need to look into Separate Charges and Transfers

inland niche
#

But wouldn't we run into the same issue if the connect account is not yet set up?

#

let's say the connect account doesn't exist at all at the time we collect the payment

spark tendon
#

Separate Charges and Transfers as it's name implies mean creating a Charge and Transfer separately. So you would collect the charge/payment on your platform. Later, when the connected account is setup, you can create a Transfer to it

#

Destination charges have the transfer "baked" into the payment/charge (for lack of a better term off the top of my head right now)

#

Are all of your connected accounts in the same region as your platform account? e.g. US and US

inland niche
#

So we would do an initial call to collect the money, and once the connect account is set up (maybe days or weeks later), we'd do a separate call to transfer the funds?