#dpelkey98

1 messages · Page 1 of 1 (latest)

unique hollyBOT
#

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.

vapid wind
#

To clarify -- using the Stripe CLI

#

Want to simulate the individual.verification.document requirement on a specific account to test a webhook

sick iris
#

I don't think you can do that via cli

#

You'd need to create a new account, etc

#

Or just mock the event and send it to your endpoint

vapid wind
#

hmm, so no way to force account requirements either?

#

I've also been unable to find a complete list of possible requirements. Kind of just working in the dark as they arise in test mode.

sick iris
#

Yeah I don't think we maintain a complete list

sick iris
vapid wind
#

What does it depend on? I can trigger the account.updated event generally using the CLI, which my webhook compares new requirements with my own database. However, it would be nice to know if there was a way to manually trigger requirements. Be it on the dashboard or creating new accounts using the API. What kind of requirements should I prepare to handle aside from identity verification?

Just to add, so far this is the only requirement that has popped up while in test mode. It has been roughly 3 months.

#

Well, actually:

stripe trigger account.updated --stripe-account acct_1O8sUJHB3M8BbwhD
Setting up fixture for: account
Running fixture for: account
Trigger failed: Request failed, status=403, body={
  "error": {
    "message": "Connect platforms cannot create new accounts on behalf of their connected accounts.",
    "request_log_url": "https://dashboard.stripe.com/acct_1O8sUJHB3M8BbwhD/test/logs/req_ANxys8uitGq8o8?t=1708013017",
    "type": "invalid_request_error"
  }
}

I guess this is what you meant by not possible?

sick iris
#

I mean you can't set specific requirements to be triggered via the cli

#

You can generate 1 off events

#

But no way to specify a specific requirement to be triggered

#

By "it depends" I just mean it depends on the requirement. Some you can surface just by creating a new account via the api

#

What kind of requirements should I prepare to handle aside from identity verification?
Hard to say. Why does it matter to you though? Are these custom accounts and you are building a UI to handle the requirements?

#

Usually the requirement type wouldn't matter to the platform. An onboarding link or account dashboard (w/ standard accounts) would be the place the account holders would remedy the situaiton