#mesudev
swift plover
Hi 👋
I don't think we have an API -only way to simulate the completion of that. I think you need to go through the onboarding process using test data
dark cypress
Not even for testing? Would be crazy helpful for our integration tests
swift plover
Unfortunately that isn't something we have an automation for. However, you can simulate the webhook event that will fire when the KYC process occurs by triggering the account.updated event using the CLI: https://stripe.com/docs/cli/trigger#trigger-event-account_updated
You can even write your own fixtures to configure different versions of this webhook events with different statuses of the requirements property, thereby simulating different stages of the KYC process
dark cypress
So we're providing a return URL that authenticates a user who successfully completed the KYC-procedure when arriving back on the platform.
After a successful authentication, we then send an API request to Stripe's connected account API to check on the details_submitted property. If it is true, we then consider the KYC to be completed. Hence: Can I, using your mentioned strategy, simulate that a subsequent API request to stripe's connected account API returns true for the details_submitted property of a given connected account, even if the onboarding flow remained untouched after being initiated by generating an account link?
That would already be enough for the integration testing. Or can I manually update the details_submitted using the Account API in testing only to simulate this (Of course we would never do that in prod).
swift plover
Yes you can configure a custom fixture to return an Account in that state when you trigger that event
I would recommend you investigate the requirements hash as well, not necessarily for initial onboarding but at different points as accounts begin to generate transactions, additional KYC is required and that hash will give you good information about those upcoming requirements
dark cypress
Meaning verifying that details_submitted=true does not indicate a completed KYC for a newly initiated connected account ?
swift plover
It means they have sumitted all the necessary initial information
What I was referring to was a way to track all potential KYC requirements over time
dark cypress
Yes
But do you agree that for the initial onboarding, verifying that details_submitted is true is enough?
And that only at a later moment, more info may be required, and that info "requirement state" should be checked via webhook as indicated here https://stripe.com/docs/connect/connect-onboarding ?
swift plover
Yes that will work
dark cypress
Okay and manually updating the details_submitted property via https://stripe.com/docs/api/accounts/update seemingly does not work for the details_submitted property, according to your docs?
that property is read-only?
swift plover
Correct
dark cypress
Yes you can configure a custom fixture to return an Account in that state when y...
You can configure a custom fixture to return an Account whose value for details_submitted is true? Could you elaborate on that please?
swift plover
Wait, sorry. I wasn't thinking about this correctly. You can provide all the necessary details via the API.
dark cypress
Wait, sorry. I wasn't thinking about this correctly. You _can_ provide all the...
Such that in the end, the details_submitted property will have a value of true ?
swift plover
If you are creating an Account with business_type = individual you provide the complete individual parameter:
https://stripe.com/docs/api/accounts/create#create_account-individual
That should but I would test to be sure
dark cypress
Ah so you don‘t even need to provide sample bank account numbers etc ?
swift plover
I am testing this currently
dark cypress
Cheers, please let us know
swift plover
So far I have not returned an Account with details_submitted: true
dark cypress
Because the thing is that we already provide all that info when creating the account directly, so I don’t think you’ll get “true”
Yeah
The KYC completion would need to be simulated completely too, so I guess your fixture solution is also not an option, as we have to be able to test the execution of test transactions in the testing environment with the concerned connected account
swift plover
In that case you might try manually going through onboarding and saving the objects that are returned as JSON, and then using them as mock API responses during your integration testing
dark cypress
Concluding that manual KYC and then later use of that account for the integration tests is the only real solution..?
Yesyes ok thx!
Would be a huge plus to have that for testing though, any plans on implementing such a thing?
Because otherwise, everytime the onboarding is changed on our platform, we’d have to go through the manual setup again..
To execute tests which are always up-to-date
swift plover
Yes I understand the difficulty that causes. I can raise this as a feature request
ivory salmonBOT