bazylh

[lucid falcon]

Hi there

Are you asking specifically if there is a way to always request card_capability on your Connected Accounts?

[unborn iron]

Basically we use stripes connect account maker wizard, so itd be cool if we could flip something on the dashboard to make every made connect account have this turned on.

[lucid falcon]

I'm not familiar with "stripes connect account maker wizard"

[unborn iron]

Our api doesnt touch accounts or capabilities currently.

[lucid falcon]

Is that a third party?

[unborn iron]

No we have a button that takes users to stripe to make a connect account.

Its by stripe.

[lucid falcon]

Oh I see

Are you using OAuth?

[unborn iron]

Yes.

[lucid falcon]

Got it. And these are Express accounts?

[unborn iron]

yeah

req_kWdTsdSvBI0ct9

[lucid falcon]

Cool. So you can set the default capabilities you will request in your Dashboard here: https://dashboard.stripe.com/settings/connect

[hidden sparrow]

Hello! I'm taking over and catching up...

The Dashboard is the recommended way to do this, but you can also include suggested_capabilities[] in your OAuth link as well: https://stripe.com/docs/connect/oauth-express-accounts#specify-capabilities-for-an-account

[unborn iron]

How do we do this through the dashboard.

[hidden sparrow]

Using the link @lucid falcon provided above.

Do you need specific instructions, or did you find the setting?

[unborn iron]

Everywhere I look its on.

[hidden sparrow]

Those are payment methods, not capabilities. What do you see if you go here? https://dashboard.stripe.com/settings/connect/express

[unborn iron]

Ah i think i found it

Its the Payments Product that needs turned on

[hidden sparrow]

Yep, that's correct.

[unborn iron]

Okay but still getting the same reesponse

Turned on for both test and prod

[hidden sparrow]

Same response?

[unborn iron]

{
"detail": "Request req_fxF0dVXIdV30Vr: You cannot create a charge on a connected account without the card_payments capability enabled."
}

[hidden sparrow]

To clarify, this setting only applies to new accounts going forward, not existing accounts.

[unborn iron]

Ohh okay how do we turn on specific ones

I think i found it

[hidden sparrow]

You can update the Account in question and request the capability you want. For card_payments, for example: https://stripe.com/docs/api/accounts/update#update_account-capabilities-card_payments-requested

[unborn iron]

Can i do this through the dashboard

I turned on card payments and now the account is restricted

[hidden sparrow]

You can do it though the Dashboard, yes. The account being restricted is expected; requesting new capabilities typically requires review and sometimes requires the account holder to provide more information.

Have you seen our Account capabilities guide? https://stripe.com/docs/connect/account-capabilities

[unborn iron]

"detail": "Request req_KV5lbFub2VJcQz: Your account cannot currently make charges. To find out why charge creation is currently disabled, look at the requirements.disabled_reason property on this account (/v1/accounts/acct_1LOQRTDGAsxGWWJC)."
}

[hidden sparrow]

What do you see in requirements.disabled_reason on the Account?

[unborn iron]

where is that in the dashboard?

This is always greyed out..

[hidden sparrow]

I don't know that it's displayed in the Dashboard, but you can see it if you fetch the Account from the API.

https://stripe.com/docs/api/accounts/retrieve

[unborn iron]

stripe.Account.retrieve("acct_1LOQRTDGAsxGWWJC").requirements.disabled_reason

'requirements.past_due'

[hidden sparrow]

Okay, so the account has requirements which are past due. The next step is to check which requirements are needed and fulfill them.

[unborn iron]

okay

I just went to the login link and filled out the info again.

[hidden sparrow]

Okay, what's the status of the Account now?

[unborn iron]

same thing

[hidden sparrow]

No, using the API.

[unborn iron]

Oh i did that before i showed the response

So no change.

  "alternatives": [],
  "current_deadline": null,
  "currently_due": [
    "individual.address.line1",
    "individual.verification.document"
  ],
  "disabled_reason": "requirements.past_due",
  "errors": [
    {
      "code": "invalid_street_address",
      "reason": "The provided street address cannot be found. Please verify the street name and number are correct in \"829 North Bishop Street\"",
      "requirement": "individual.address.line1"
    },
    {
      "code": "verification_failed_keyed_identity",
      "reason": "The identity information you entered cannot be verified. Please correct any errors or upload a document that matches the identity fields (e.g., name and date of birth) that you entered.",
      "requirement": "individual.verification.document"
    }
  ],
  "eventually_due": [
    "individual.address.line1",
    "individual.verification.document"
  ],
  "past_due": [
    "individual.verification.document"
  ],
  "pending_verification": []
}```

Heres the full object

[hidden sparrow]

Okay, so individual.verification.document is past due. You need to supply that.

[unborn iron]

But the link form never asks for that.

[hidden sparrow]

individual.address.line1 is also currently due, so you should likely supply that as well.

What is "the link form"?

[hidden sparrow]

How are you generating that link?

[unborn iron]

With the Stripe connect link functionality

I think this is what needs solved

[hidden sparrow]

I'm not sure what you're referring to. Can you provide more details?

To clarify, I'm still not understanding where the link you're using to get to the form above is coming from.

[brisk thicket]

@unborn iron Did you still need help?

[unborn iron]

I think we are good now.