Support stripe connect webhooks

Open
#43 0 comments 17 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
api, backend, payments

Research direction

Start by tracing the existing /webhook endpoint and how STRIPE_WEBHOOK_SECRET is read and validated. Add the requested /webhook/connect path with a separate secret for connected-account events, then verify that both endpoint types can receive and authenticate their respective webhook events.

Written by the indexing model from the issue text.

Description

enhancement

Feature request

As per the stripe docs Connect webhooks the recommended way to use connect webhooks is by creating two webhook endpoints. First one /webhook for own account events and second one /webhook/connect for connected accounts events by setting the connect parameter to true.

Is your feature request related to a problem? Please describe.

  • The webhook secret will be different for own account webhook and connect account webhook, currently only STRIPE_WEBHOOK_SECRET is accepted as env.

A clear and concise description of what you want and what your use case is.

Describe the solution you'd like

A new endpoint as /webhook/connect to receive webhook events for connected accounts.

Dominant language
TypeScript
Stars
1.1k
Forks
117
Avg merge
12m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stripe/sync-engine

All issues in stripe/sync-engine

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.