A seller finished Stripe onboarding, but your marketplace still says "Finish setting up payouts". Or direct charges on a seller's account never unlock anything. Your webhook works for normal payments, so it looks like Stripe isn't sending the event. Usually it's sending it to a different kind of endpoint.
Stripe: "Webhooks for Connect users listen for events in different scopes, depending on the source of the event" (Stripe docs: Connect webhooks).
account.updated events" and direct charges for customers of your connected accounts (source).The scope is a property of the endpoint. In Workbench it's the Events from setting; through the API it's the connect parameter: "If set to true, then a Connect webhook endpoint that notifies the specified url about events from all connected accounts is created; otherwise an account webhook endpoint that notifies the specified url only about events from your account is created" (Stripe API: Create a webhook endpoint).
So an app with only the usual endpoint (the one that receives checkout.session.completed) never sees account.updated for sellers. Many marketplaces need both: Stripe notes you "might also need to register an event destination for Your account", for example for destination charges and separate charges and transfers (Stripe docs: Receive Stripe events).
The return from onboarding doesn't tell you the outcome. For Account Links, "No state is passed through this URL." After the seller lands on your return_url, check details_submitted by retrieving the account or by listening to account.updated with a Connect webhook; and since a seller redirected to your return_url "might not have completed the onboarding process", retrieve the account and check charges_enabled (Stripe docs: Express accounts).
Fields worth storing per seller, from the Account object (Stripe API: The Account object):
charges_enabled: "Whether the account can process charges."payouts_enabled: "Whether the funds in this account can be paid out."details_submitted: "Whether account details have been submitted."requirements.currently_due and requirements.disabled_reason: what Stripe still needs, and why the account is restricted.Requirements can come back later. Stripe: "If verification or validation is unsuccessful, requirements can reappear in currently_due" and to be notified, "set a Connect webhook to listen to the account.updated event" (Stripe docs: Handle verification with the API). A one-time check at the return URL misses that.
/api/stripe/connect-webhook) and its own env var, or every Connect event fails verification with a 400 (see signature verification failed).livemode value (source).account property that identifies the connected account," and you must make API requests for that object as the connected account (source), which server-side means the Stripe-Account header (Stripe docs: Making API calls for connected accounts). Without it, a retrieve for a direct-charge object looks in your platform account and typically fails with a "No such ..." error.// Second endpoint in Stripe: Events from = Connected accounts (connect: true)
// Its own URL and its own whsec_ (env STRIPE_CONNECT_WEBHOOK_SECRET)
export async function POST(req) {
const raw = await req.text(); // raw body, before any JSON parsing
let event;
try {
event = stripe.webhooks.constructEvent(raw, req.headers.get('stripe-signature'),
process.env.STRIPE_CONNECT_WEBHOOK_SECRET);
} catch {
return new Response('bad signature', { status: 400 });
}
if (event.livemode !== (process.env.STRIPE_MODE === 'live')) return new Response('ok');
if (event.type === 'account.updated') {
const acct = await stripe.accounts.retrieve(event.account); // fresh copy, not the payload
await db.sellers.update({
where: { stripe_account_id: acct.id },
data: {
charges_enabled: acct.charges_enabled,
payouts_enabled: acct.payouts_enabled,
details_submitted: acct.details_submitted,
currently_due: acct.requirements?.currently_due ?? [],
},
});
}
if (event.type === 'payment_intent.succeeded') { // direct charge on a seller's account
const pi = await stripe.paymentIntents.retrieve(event.data.object.id,
{ stripeAccount: event.account });
await fulfillOnce(pi.id, pi); // same run-once function your platform endpoint uses
}
return new Response('ok');
}
Rename tables and fields to match your app. Keep your existing platform endpoint and its secret as they are; this is a second route, not a replacement.
My Stripe Connect marketplace never learns when a seller finishes onboarding. 1) Add a second webhook route, /api/stripe/connect-webhook, separate from the existing one. 2) Read the raw body and verify the signature with a new env var STRIPE_CONNECT_WEBHOOK_SECRET; return 400 if it fails. 3) Ignore events whose livemode doesn't match the environment. 4) On account.updated, retrieve the account by event.account and save charges_enabled, payouts_enabled, details_submitted and requirements.currently_due on the seller row. 5) For other connected-account objects (e.g. payment_intent.succeeded on direct charges), retrieve them with stripeAccount: event.account. 6) Gate "can sell" and "can be paid out" on the saved charges_enabled / payouts_enabled, not on the user returning from onboarding. 7) Do not change the existing platform webhook route or its secret.
account.updated (plus any connected-account payment events you use), point it at the new URL and copy its signing secret into production config.stripe listen --forward-to localhost:3000/api/stripe/webhook --forward-connect-to localhost:3000/api/stripe/connect-webhook (Stripe CLI reference: listen).stripe trigger --stripe-account acct_123 payment_intent.succeeded (Stripe's pattern: stripe trigger --stripe-account plus the connected account ID and event name, source). Or finish onboarding for a sandbox seller and watch the delivery log for account.updated with a 2xx.Paste your webhook URL. WebhookProof sends 3 harmless test requests and tells you whether Stripe can reach it and whether it rejects unsigned events. If it finds a problem, the $9 fix pack gives you the exact copy-paste fix for your stack (refundable for 14 days).
Run the free checkaccount.updated for connected accounts is sent to endpoints that listen to Connected accounts (Events from: Connected accounts in Workbench, or connect=true in the API). A normal endpoint only gets events from your own platform account.
Often, yes. Connected-account events (account.updated, direct charges on connected accounts) go to a Connected accounts endpoint, while platform events such as destination charges and separate charges and transfers go to a Your account endpoint. Each endpoint has its own signing secret.
No state is passed to your return_url. Listen to account.updated with a Connect webhook, or retrieve the account, and check details_submitted and charges_enabled.
The object belongs to the connected account named in the event's top-level account property. Retrieve it as that account, using the Stripe-Account header (stripeAccount option in stripe-node).
Stripe webhook not working? Check these 7 things in order · A customer paid but didn't get access. What went wrong? · No signatures found matching the expected signature for payload · Stripe webhook failing with a 307 or 308 redirect
Last reviewed 2026-11-10. WebhookProof is an independent tool, not affiliated with Stripe, Inc.. Quotes are from the linked documentation.