Sharvari96 | Stripe Developers | Page 1

whole jacinthBOT Jun 21, 2023, 12:04 AM

#

hollow echo Jun 21, 2023, 12:05 AM

#

What type of connected account do you use (Standard, Express or Custom)?

sharp solar Jun 21, 2023, 12:06 AM

#

Express

#

Platform Account - US, Connect Account India

hollow echo Jun 21, 2023, 12:07 AM

#

Thanks for sharing!

#

For Separate Charges and Transfers, the fund on the invoice will go to the platform first, then your system calculate the funds after deducting the application fee and transfer to connected account accordingly. Since it's a Separate Charges and Transfers, your system should manage to Transfer yourself instead of through invoices

#

If you wish to transfer the funds automatically, Destination Charges should be used instead: https://stripe.com/docs/connect/destination-charges

#

To use Destination Charges on Invoicing, you will set transfer_data.destination as the connected account and application_fee_amount to be collected when creating an invoice.

transfer_data.destination: https://stripe.com/docs/api/invoices/create#create_invoice-transfer_data-destination
application_fee_amount: https://stripe.com/docs/api/invoices/create#create_invoice-application_fee_amount

sharp solar Jun 21, 2023, 12:13 AM

#

I have tried Destination Charges - and its not working for India. The support team is working on resolving the query I had - because for US platform account and india connect account - the documentation says its allowed.

sharp solar Jun 21, 2023, 12:14 AM

#

hollow echo For Separate Charges and Transfers, the fund on the invoice will go to the platf...

ok thanks for clarification

hollow echo Jun 21, 2023, 12:15 AM

#

Can you share the request ID (req_xxx) that threw error for Destination Charges on India connected account for US platform?

From https://support.stripe.com/questions/stripe-india-support-for-marketplaces, it should be supported.

#

If you are already in the conversation with Support team, then I'd recommend following with them

sharp solar Jun 21, 2023, 12:17 AM

#

Let me share the reqID..

#

req_nee6R3RctCQrQZ

hollow echo Jun 21, 2023, 12:34 AM

#

In https://dashboard.stripe.com/test/logs/req_LApYqylBM6c14H, the connected account acct_1NKaquSB3C5v0NdW is a Standard account, not Express. Destination Charges isn't recommended to use on Standard account. If you try on Express account, does it work?

sharp solar Jun 21, 2023, 12:36 AM

#

my bad I have tried both... and its not working. Let me share teh correct req_ID

#

req_IUlt1sSWa0YlUg

#

can you check this one instead?

hollow echo Jun 21, 2023, 12:48 AM

#

In https://dashboard.stripe.com/test/connect/accounts/acct_1NJDOPPxtJyeJZXO/activity, the connected account only has transfer capability. With on_behalf_of, it should also have card_payments capability. Can you try enabling card_payments capability to check if it works?

From https://stripe.com/docs/connect/destination-charges#settlement-merchant:

The on_behalf_of attribute is supported only for connected accounts with the card_payments capability

sharp solar Jun 21, 2023, 12:51 AM

#

because - I have enabled - tos_acceptance={"service_agreement": "recipient"}. I cannot enable card_payments

#

I also tried removing - on_behalf_of parameter - I am still getting the same issue. - req_fdIZeaiKOVGLqe

hollow echo Jun 21, 2023, 1:01 AM

#

Thanks for sharing! I'm afraid I can't find any reason why Destination Charges can't be performed on India connected account. Since you are already in discussion with Support, I'd recommend following up with them, so that they can check with the relevant team

sharp solar Jun 21, 2023, 1:02 AM

#

Ok thanks will do the same.
Can I ask one more question?

#

What are the different account statuses for a connect account?

hollow echo Jun 21, 2023, 1:07 AM

#

You can find the explanation of connected account status here: https://stripe.com/docs/connect/dashboard#status-badges

sharp solar Jun 21, 2023, 1:08 AM

#

I want to manage it via a API...

#

I tried retrieve account API- but account status is not a key in the response

hollow echo Jun 21, 2023, 1:09 AM

#

Connected account status is not available through API. You can refer to the guide above to determine which parameters are used to determine those status. For example, Restricted status means the account has payouts or payments disabled

sharp solar Jun 21, 2023, 1:10 AM

#

then, how I can check for example the onboarding using the link was complete or not?

#

https://stripe.com/docs/api/account_links/create

here -

refresh_url
REQUIRED
The URL the user will be redirected to if the account link is expired, has been previously-visited, or is otherwise invalid. The URL you specify should attempt to generate a new account link with the same parameters used to create the original account link, then redirect the user to the new account link’s URL so they can continue with Connect Onboarding. If a new account link cannot be generated or the redirect fails you should display a useful error to the user.

return_url
REQUIRED
The URL that the user will be redirected to upon leaving or completing the linked flow.

#

I understand that a refresh_url means - failure

hollow echo Jun 21, 2023, 1:12 AM

#

To check if the onboarding is completed, you should check if there's anymore requirements under requirements parameter: https://stripe.com/docs/api/accounts/object#account_object-requirements

Stripe API reference – The account object – curl

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

#

If there is, your system will create a new account link for connected account holder to complete the onboarding

#

https://stripe.com/docs/connect/express-accounts#handle-users-not-completed-onboarding

sharp solar Jun 21, 2023, 1:14 AM

#

let me have a look and get back to you...

#

here's the comparision of the requirements parameter:

before onboarding

before onboarding
"requirements": {
    "alternatives": [],
    "current_deadline": null,
    "currently_due": [
      "tos_acceptance.date",
      "tos_acceptance.ip"
    ],
    "disabled_reason": "requirements.past_due",
    "errors": [],
    "eventually_due": [
      "individual.verification.document",
      "tos_acceptance.date",
      "tos_acceptance.ip"
    ],
    "past_due": [
      "tos_acceptance.date",
      "tos_acceptance.ip"
    ],
    "pending_verification": []
  },

  -------------------------------------------
after onboarding

  "requirements": {
    "alternatives": [],
    "current_deadline": null,
    "currently_due": [],
    "disabled_reason": null,
    "errors": [],
    "eventually_due": [
      "individual.verification.document"
    ],
    "past_due": [],
    "pending_verification": []
  },

#

I am guessing we need to use - currently_due key?

or is it anything else?

#

I mean - what exactly do I need to check within the requirements parameter?

hollow echo Jun 21, 2023, 1:18 AM

#

Under requirements, past_due, currently_due and eventually_due are the parameters to be completed

sharp solar Jun 21, 2023, 1:20 AM

#

ok -about this - "individual.verification.document"

this wasn't asked to be uploaded in the onboarding link - what's the flow to get it from the connect account user?

hollow echo Jun 21, 2023, 1:22 AM

#

Can you share the connected account ID (acct_xxx)?

sharp solar Jun 21, 2023, 1:23 AM

#

ok

#

acct_1NL4QXPxl6FaXZsX

hollow echo Jun 21, 2023, 1:28 AM

#

Requirements in eventually_due isn't required at the moment as other requirements have been completed to process charges and payout, so it might be why "individual.verification.document" isn't collected. I'd recommend listening to account.updated event and ensure past_due and currently_due are empty

sharp solar Jun 21, 2023, 1:55 AM

#

Ok you mean - using a web hook?

hollow echo Jun 21, 2023, 1:56 AM

#

Yup! eventually_due may move to currently_due at later time, so account.updated should be listened in this case

sharp solar Jun 21, 2023, 1:56 AM

#

Ok, cool thank you

#Sharvari96