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

# /AnswerMFAQuestions

> The `AnswerMFAQuestions` endpoint allows you to submit responses to multi-factor authentication questions in order to complete the authentication process and refresh the associated financial card.

**Availability:**
This endpoint is supported only in Canada and only for institutions using simple security questions as their MFA method.

**Note:** This endpoint is specific to the Enhanced MFA flow, which preemptively collects simple security question answers to improve Nightly Refresh success. It does not handle advanced MFA types such as two-step verification, push notifications, or other specialized authentication mechanisms — those are fully supported through Flinks' standard authentication flow via the [/Authorize](/api/authorize/endpoints/authorize) endpoint and Flinks Connect.


The `AnswerMFAQuestions` endpoint allows you to submit responses to multi-factor authentication questions in order to complete the authentication process and refresh the associated financial card.

**Availability:**
This endpoint is supported only in Canada and only for institutions using simple security questions as their MFA method.

**Note:** This endpoint is specific to the Enhanced MFA flow, which preemptively collects simple security question answers to improve Nightly Refresh success. It does not handle advanced MFA types such as two-step verification, push notifications, or other specialized authentication mechanisms — those are fully supported through Flinks' standard authentication flow via the [/Authorize](/api/authorize/endpoints/authorize) endpoint and [Flinks Connect](/guides/connect/flinks-connect/widget).


## OpenAPI

````yaml PATCH /v3/{customerId}/BankingServices/AnswerMFAQuestions
openapi: 3.0.3
info:
  title: Flinks API
  description: >
    Flinks API provides financial data connectivity, enrichment, and payment
    solutions.


    ## Authentication

    Endpoints require authentication using `flinks-auth-key` header (Bearer
    token).


    For more information, visit: https://docs.flinks.com
  version: 3.0.0
  contact:
    name: Flinks Support
    url: https://www.flinks.com/contact/sales
  termsOfService: https://www.flinks.com
servers:
  - url: https://{instance}-api.private.fin.ag
    description: Flinks API Environment
    variables:
      instance:
        default: toolbox
        description: The environment instance (e.g., toolbox, sandbox, production)
security: []
tags:
  - name: Authorization
    description: Endpoints for generating authorization tokens and authenticating requests
  - name: Enrich - Consumer Attributes
    description: Consumer financial attribute analysis and credit risk assessment
paths:
  /v3/{customerId}/BankingServices/AnswerMFAQuestions:
    patch:
      tags:
        - Authorization
      summary: Answer MFA Questions
      description: >
        The `AnswerMFAQuestions` endpoint allows you to submit responses to
        multi-factor authentication questions in order to complete the
        authentication process and refresh the associated financial card.


        **Availability:**

        This endpoint is supported only in Canada and only for institutions
        using simple security questions as their MFA method.


        **Note:** This endpoint is specific to the Enhanced MFA flow, which
        preemptively collects simple security question answers to improve
        Nightly Refresh success. It does not handle advanced MFA types such as
        two-step verification, push notifications, or other specialized
        authentication mechanisms — those are fully supported through Flinks'
        standard authentication flow via the
        [/Authorize](/api/authorize/endpoints/authorize) endpoint and Flinks
        Connect.
      operationId: answerMFAQuestions
      parameters:
        - name: customerId
          in: path
          required: true
          description: >-
            Key that grants access to the environment specified in the instance
            field. By default, the value is set to the toolbox environment key.
          schema:
            type: string
            default: 43387ca6-0391-4c82-857d-70d95f087ecb
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                loginId:
                  type: string
                  description: >-
                    The loginId you received after successfully connecting a
                    customer account.
                Questions:
                  type: array
                  description: >-
                    Your MFA questions. This is an array of objects, where each
                    object contains a Question and Answer field.
                  items:
                    type: object
                    properties:
                      Question:
                        type: string
                        description: The security question text.
                      Answer:
                        type: string
                        description: The answer to the security question.
              example: {}
      responses:
        '200':
          description: >-
            Confirmation message indicating that the answers were updated
            successfully.
          content:
            application/json:
              schema:
                type: object
                properties:
                  Message:
                    type: string
                    description: >-
                      Confirmation message indicating that the answers were
                      updated successfully.
              example:
                Message: Answers updated
        '400':
          description: Error message describing the issue.
          content:
            application/json:
              schema:
                type: object
                properties:
                  HttpStatusCode:
                    type: integer
                    description: HTTP status code of the response.
                  Message:
                    type: string
                    description: Error message describing the issue.
                  FlinksCode:
                    type: string
                    description: 'Flinks-specific error code: `INVALID_REQUEST`.'
              example:
                HttpStatusCode: 400
                Message: The login 'bb8b8569-3bfc-43c1-ae31-08d6de7f1675' is invalid.
                FlinksCode: INVALID_REQUEST

````