Stripe Signed Webhook Receiver

What does this kit do?

Generate one bounded raw-body Stripe signature-verification boundary for an exact clean Next.js App Router target.

Who should use it?

• The target is a clean Next.js 16.2.6 App Router application.
• You need a Stripe webhook receiver with bounded raw-body handling.
• A human can configure the Stripe endpoint and application-specific event handling.

What will it change?

• The exact Stripe dependency when absent and explicitly approved.
• Four bounded receiver files in a clean supported target without overwrite.

What will the human approve?

The human approves the exact dependency and file plan, configures the Stripe endpoint and three-event subscription, and supplies the signing-secret reference.

What does it verify?

• Raw bytes are bounded and signature-verified before handler dispatch.
• Only the declared Checkout event types can reach the application handler.

What can it remove?

• Unchanged files created by that exact run when their authenticated hashes still match.

What does it deliberately not do?

• The target uses another framework, router, or unsupported dependency version.
• A webhook route already occupies the delivered path.
• The agent would need to design payment-side business semantics.
• Package-manager changes, a human-created Stripe destination, delivered events, business data, or deployment state.

How does an agent use it?

1. Open the BoxFetch Original in the BoxFetch app.
2. Let the kit inspect the target without making changes.
3. Review the plan, target, and human checkpoint.
4. Approve only the changes you intend to make.
5. Read the verification result and run record.

How do I use it?

Create a BoxFetch account and open the app to see current beta availability. The six current Originals are free during the controlled beta, while the application remains the authority for live access.