> ## Documentation Index
> Fetch the complete documentation index at: https://docs.loyalty.dog/llms.txt
> Use this file to discover all available pages before exploring further.

# Post Signup Setup Intent

> Step 3 (mount): create a Stripe SetupIntent for the pending row and
return the `clientSecret` the frontend uses to mount Stripe's
PaymentElement. The `pending_user_id` is stamped into the SetupIntent's
metadata so the Phase 11 webhook can correlate Stripe events back to the
User.

Only pending rows can advance — active/abandoned/cancelled rows would
create orphan SetupIntents on retry. The Stripe SDK call is wrapped in
`asyncio.to_thread` (it's sync; we don't want to block the event loop).



## OpenAPI

````yaml https://api.loyalty.dog/openapi.json post /v2/signup/pending/{pending_id}/setup-intent
openapi: 3.1.0
info:
  title: LoyaltyDog
  description: >-

    Welcome to the LoyaltyDog API! This API provides access to our loyalty
    program features, allowing you to integrate with various platforms and
    manage your loyalty data.


    Want to query LoyaltyDog via an AI assistant (Claude, Cursor, Windsurf)? See
    the [MCP Integration guide](https://loyaltydog.ai/playground#mcp).
        
  termsOfService: https://loyalty.dog/loyalty-program-terms-service
  contact:
    name: LoyaltyDog Support
    url: https://loyalty.dog/contact-us
    email: support@loyalty.dog
  version: 1.0.1
servers:
  - url: https://api.loyalty.dog
    description: Production
security:
  - bearerAuth: []
paths:
  /v2/signup/pending/{pending_id}/setup-intent:
    post:
      summary: Post Signup Setup Intent
      description: |-
        Step 3 (mount): create a Stripe SetupIntent for the pending row and
        return the `clientSecret` the frontend uses to mount Stripe's
        PaymentElement. The `pending_user_id` is stamped into the SetupIntent's
        metadata so the Phase 11 webhook can correlate Stripe events back to the
        User.

        Only pending rows can advance — active/abandoned/cancelled rows would
        create orphan SetupIntents on retry. The Stripe SDK call is wrapped in
        `asyncio.to_thread` (it's sync; we don't want to block the event loop).
      operationId: >-
        post_signup_setup_intent_v2_signup_pending__pending_id__setup_intent_post
      parameters:
        - name: pending_id
          in: path
          required: true
          schema:
            $ref: '#/components/schemas/PydanticObjectId'
            description: The pending User id from POST /signup/pending
          description: The pending User id from POST /signup/pending
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CreateSetupIntentResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security: []
components:
  schemas:
    PydanticObjectId:
      type: string
      maxLength: 24
      minLength: 24
      pattern: ^[0-9a-f]{24}$
      example: 5eb7cf5a86d9755df3a6c593
    CreateSetupIntentResponse:
      properties:
        clientSecret:
          type: string
          title: Clientsecret
        setupIntentId:
          type: string
          title: Setupintentid
      type: object
      required:
        - clientSecret
        - setupIntentId
      title: CreateSetupIntentResponse
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: JWT access token obtained from POST /v2/token.

````