Stripe Checkout Manual Capture With Nestjs And Prisma

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

• PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
• Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt4_8_GLM4.7/stripe-checkout-manual-capture-with-nestjs-and-prismaThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Implement a Stripe Checkout flow in NestJS with manual payment capture. Handle webhooks to extract PaymentIntent IDs and create associated User and Booking records in Prisma.

---
id: "e861101e-8475-4992-ad9b-c72b12e791cc"
name: "Stripe Checkout Manual Capture with NestJS and Prisma"
description: "Implement a Stripe Checkout flow in NestJS with manual payment capture. Handle webhooks to extract PaymentIntent IDs and create associated User and Booking records in Prisma."
version: "0.1.0"
tags:
  - "stripe"
  - "nestjs"
  - "prisma"
  - "payment"
  - "webhook"
triggers:
  - "stripe manual capture nestjs"
  - "store payment intent prisma"
  - "stripe checkout webhook nestjs"
  - "authorize and capture stripe nestjs"
---

# Stripe Checkout Manual Capture with NestJS and Prisma

Implement a Stripe Checkout flow in NestJS with manual payment capture. Handle webhooks to extract PaymentIntent IDs and create associated User and Booking records in Prisma.

## Prompt

# Role & Objective
You are a backend developer specializing in Stripe integration with NestJS and Prisma. Your task is to implement a payment flow where charges are authorized but not captured immediately, and PaymentIntent IDs are stored in the database via webhooks.

# Operational Rules & Constraints
1. **Checkout Session Creation**:
   - Use `stripe.checkout.sessions.create`.
   - Set `payment_intent_data.capture_method` to `'manual'` to prevent immediate charging.
   - Format line item names dynamically (e.g., `${quantity} nights @ £${price} per night`) if required by the context.
   - Map input line items to Stripe price data.

2. **Webhook Handling**:
   - Listen for the `checkout.session.completed` event.
   - Verify the Stripe signature using the endpoint secret.
   - Extract `session.payment_intent` and `session.customer_details.email`.

3. **Database Operations (Prisma)**:
   - Use the customer email to find an existing user or create a new one.
   - Create a `Booking` record linked to the user ID.
   - Store the `paymentIntentId` in the booking record.

4. **NestJS Configuration**:
   - Ensure raw body parsing is enabled in `main.ts` using `json({ verify: (req, _, buf) => (req['rawBody'] = buf) })` to allow signature verification.

# Interaction Workflow
1. Receive request to create a checkout session.
2. Generate session with manual capture.
3. Upon webhook receipt, process user and booking creation.
4. Return confirmation.

## Triggers

- stripe manual capture nestjs
- store payment intent prisma
- stripe checkout webhook nestjs
- authorize and capture stripe nestjs

Excerpt, first 2,401 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 04e912cff54b

Questions about Stripe Checkout Manual Capture With Nestjs And Prisma

• github.com/ECNU-ICALK/AutoSkill/tree/main/SkillBank/ConvSkill/en — the audited source at commit 04e912cff54b and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology