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

# Confirm challenge completion

> Confirms that the cardholder has completed the 3DS challenge. The authentication session must be in CHALLENGE_REQUIRED status.




## OpenAPI

````yaml /openapi/payment-acceptance.json post /threeds/{authentication_id}/confirm
openapi: 3.1.0
info:
  title: lite - Payment Acceptance
  version: 1.0.0
servers:
  - url: https://api.lite.sa/api/v1
    description: Production
security:
  - ApiKeyAuth: []
  - BearerAuth: []
tags:
  - name: 3DS Authentication
    description: Standalone payer authentication via the 3DS standard
  - name: Hosted Checkout
    description: Create, manage and deploy hosted checkout pages
  - name: Payment Links
    description: Create, manage and audit shareable payment links
  - name: Server-to-Server Payments
    description: Direct payment API for server-side integrations
paths:
  /threeds/{authentication_id}/confirm:
    post:
      tags:
        - 3DS Authentication
      summary: Confirm challenge completion
      description: >
        Confirms that the cardholder has completed the 3DS challenge. The
        authentication session must be in CHALLENGE_REQUIRED status.
      operationId: lite.3ds.confirmAuthentication
      parameters:
        - $ref: '#/components/parameters/authentication_id'
        - $ref: '#/components/parameters/x-correlation-id'
      responses:
        '200':
          $ref: '#/components/responses/AuthenticationConfirmed'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
        '409':
          $ref: '#/components/responses/AuthenticationConfirmConflict'
        '500':
          $ref: '#/components/responses/InternalServerError'
components:
  parameters:
    authentication_id:
      name: authentication_id
      in: path
      required: true
      description: Unique identifier of the authentication session
      schema:
        type: string
        format: uuid
        example: 9822ffb8-26de-423b-ad15-0d129cf1b4ac
    x-correlation-id:
      name: x-correlation-id
      in: header
      required: false
      description: >-
        Unique identifier for request tracing. Generated by the client or server
        if not provided.
      schema:
        type: string
        format: uuid
        example: 550e8400-e29b-41d4-a716-446655440000
  responses:
    AuthenticationConfirmed:
      description: >-
        3DS challenge confirmed. The response has no body; poll the session
        resource for the authentication outcome.
    Unauthorized:
      description: |
        Authentication failed — missing or invalid token.

        Returned when:
        - The JWT bearer token is missing, expired, or has an invalid signature
        - The API key is missing or invalid
        - The authenticated session token is invalid
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
    NotFound:
      description: |
        The requested resource was not found.

        Returned when:
        - The specified resource ID does not exist
        - The path does not match any known endpoint
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
    AuthenticationConfirmConflict:
      description: Authentication is not in CHALLENGE_REQUIRED status.
      content:
        application/json:
          schema:
            type: object
            properties:
              message:
                type: string
                example: >-
                  3DS authentication is not in CHALLENGE_REQUIRED status.
                  Current status: AUTHENTICATED
    InternalServerError:
      description: >
        An unexpected error occurred on the server.


        Returned when an unhandled exception or infrastructure failure prevents
        the request from being processed. Retry the request with exponential
        backoff.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
  schemas:
    ErrorResponse:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - code
            - message
            - timestamp
          properties:
            code:
              type: string
              description: Error code identifying the type of error
              example: PAYMENT_DETAILS_MISMATCH
            message:
              type: string
              description: Human-readable error description
              example: The request was invalid or malformed
            details:
              type: object
              description: Additional error details
            correlationId:
              type: string
              format: uuid
              description: Correlation ID for tracking the request
              example: 550e8400-e29b-41d4-a716-446655440000
            timestamp:
              type: string
              format: date-time
              description: Timestamp when the error occurred
              example: '2024-12-16T10:30:00.000Z'
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key
      description: API key for service-to-service or merchant authentication.
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        JWT Bearer token obtained from user authentication. Passed as
        Authorization: Bearer <token>.

````