Stripe webhooks on NestJS: capture the raw body with the body-parser verify hook

TL;DR

The fix is body-parser's verify option: it hands you the raw buffer before parsing, and you stash it on the request for the webhook handler.

Steps

1. NestJS on the Express adapter runs body-parser before your controller, so @Body() is already parsed. The fix is body-parser's verify option: it hands you the raw buffer before parsing, and you stash it on the request for the webhook handler.
2. - This applies to the Express adapter (the default). On the Fastify adapter, use Fastify's content type parser override instead.

• @Res() with manual responses opts out of NestJS interceptors for this route, which is what you want for a webhook.
• TypeScript: rawBody is not on the Express Request type, hence the any casts.

When to use

You are seeing this: NestJS on the Express adapter runs body-parser before your controller, so @Body() is already parsed. Use this skill when you run into "Stripe webhooks on NestJS: capture the raw body with the body-parser verify hook".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

body-parser's verify option hands you the raw buffer before JSON parsing, and NestJS on the Express adapter runs this middleware before controllers reach the request. Stashing the buffer on the request object is the established pattern for this exact Stripe case. Stripe requires the raw body for constructEvent (docs.stripe.com/webhooks/signature). Verified against live docs 2026-09-26.