#Pravin-connect

1 messages · Page 1 of 1 (latest)

oak token
cedar whale
#

no actually , let me provide you example . Let support connected account user status is complete on stripe dashboard . and after some time stripe will notice some fraud activity happening with that account so stripe has right to reject that account.

#

i want to simulate this scenario for testing

#

e.g. req_YkAyxDSf67jd9t, this request id is from stripe live account . i want to reproduce same kind of scenario on stripe test account as well for testing

#

hope you got what i want @oak token

oak token
#

so there's no way to trigger this in test mode, but what you can do is to mock the account.updated event (like what you're getting in live mode) and watch the requirements[disabled_reason]

cedar whale
#

Unfortunately i don’t have data for mock

oak token
#

as a platform, are you listening for the account.updated webhook events from your connected accounts?

cedar whale
#

Actually there are lots of webhook events

#

how can i find only specific event

#

and also i need pass valid signatures . i think its also difficult

#

do you have any examples of mocking

oak token
#

I can't provide a specific example since it depends on how your application processes the event / wants to implement the logic. My reccomendation here would be to look for the account.updated event and then your application can action accordingly based on requirements[disabled_reason]

cedar whale
#

above url is really helpful for me

#

but before going into prod i need test this flow in stage

#

i am facing challenges at this position

oak token
#

you can try discussing this internally with your team and retrieve production event data to modify and use for mocking the event in test

cedar whale
#

ok thank you