Hi Revathy,
That configuration sounds roughly right.
When a merchant changes account information, your connect application
webhook endpoint should receive an account.updated webhook.
Additionally, when a merchant disconnects from your application, your
connect application webhook endpoint should receive an
account.application.deauthorized webhook.
To debug what might be happening right now, I have a few recommendations:
1) Make sure you confirm whether you're testing with your
"Development" connect application or your "Production" connect
application. If you only have the webhook URL entered on your
Development application, but in your testing you're connecting users
to your Production application, you'll be missing the webhook.
2) To eliminate variables, you might try using a service such as
Requestbin (
http://requestb.in/) to spin up an endpoint that you can
use as your test webhook endpoint to ensure that you're getting our
webhooks. Basically this will help you make sure that if there's an
issue, it's an issue with the Stripe account configuration rather than
anything with your own server configuration.
3) If you haven't already done so, it might also be worth making sure
that you're able to get the "vanilla" webhook use case working
end-to-end. You can add a webhook endpoint and
https://dashboard.stripe.com/account/webhooks, try making a charge in
your own dashboard, and make sure that you get a charge.created
webhook at your URL.
Just a few ideas for how to debug to get you started -- happy to help
dig on this further.
Cheers,
Jim
> --
> You received this message because you are subscribed to the Google Groups
> "Stripe API Discussion" group.
> To post to this group, send email to
api-d...@lists.stripe.com.
> Visit this group at
>
http://groups.google.com/a/lists.stripe.com/group/api-discuss/.
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
api-discuss...@lists.stripe.com.