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

# Declare the STR confirmation of a card deposit

> The client declares the LDL0022R1 its own STR connection received for the LDL0022 it sent. The rail checks it against the instruction's current round (409 otherwise), the card product SLC and the exact value of the round (422 otherwise), and a terminal SitLancLDL (a pending one is 422), then keeps it as proof. An effected launch moves the instruction to DEPOSITED; a rejected or cancelled one emits funding.deposit_failed. The same declaration repeated answers the same; the same NumCtrlSTR with other values answers 409. Where Lerian SPB sends the card deposits every declaration answers 409: Lerian SPB reports the LDL0022R1 itself. RBAC: funding:write; declarer from the authorized subject.



## OpenAPI

````yaml /es/openapi/v3-current/slc.yaml post /v1/funding/settlement-instructions/{instructionId}/deposit-confirmations
openapi: 3.1.0
info:
  description: >-
    API for Lerian SLC — the participant-side rail that connects the institution
    to Núclea's SLC card settlement.
  title: Lerian SLC API
  version: 1.0.0
servers:
  - url: https://api.example.com
    description: >-
      Replace the example host with the URL provided during environment
      onboarding.
security:
  - BearerAuth: []
tags:
  - description: >-
      Settlement operation lifecycle — create, list, query, and control the
      NUliquid-tracked card operations (NUliquid = the 21-position id Núclea
      assigns each accepted operation) through the state machine.
    name: Operations
  - description: >-
      Participant catalog — the acquirers, sub-acquirers, IF Domicílio (bank
      where the merchant receives its sales), and settlement FIs (financial
      institutions) that take part in card settlement.
    name: Participants
  - description: >-
      Card arrangements (bandeira/scheme configurations, e.g. Visa/Master/Elo)
      attached to a participant.
    name: Arrangements
  - description: >-
      Regulated transport orchestration to Núclea's SLC — dispatch, recovery,
      retransmission, and connectivity testing over managed file-transfer,
      message-broker, and REST.
    name: Connectivity
  - description: >-
      Multilateral netting clearing positions — the net amount each participant
      settles per STR cycle (STR = Banco Central reserves-transfer system).
    name: Clearing
  - description: >-
      SaaS BYOK (Bring Your Own Key) signing-key provisioning — import
      parameters and register the client's ICP-Brasil server-type certificate
      material used to sign ASLC files (RSA, at least 2048 bits, and valid at
      the moment of import — all three are enforced); the SLC never receives the
      private key in cleartext.
    name: SigningKey
  - description: >-
      ASLC file intake and status — passthrough submission and processing status
      of the official Núclea card-settlement XML files (ASLC = Arquivo do
      Sistema de Liquidação de Cartões).
    name: Files
  - description: >-
      Read-only introspection of the embedded Núclea ASLC/RSFN (National
      Financial System Network) XSD schemas used to validate outbound and
      inbound messages.
    name: XSD Schemas
  - description: Read-only regulatory, compliance, and operational settlement reports.
    name: Reports
  - description: >-
      Outbound business-event webhook subscriptions and delivery management for
      consumers (client ledgers — optional).
    name: Webhooks
  - description: Administrative operations — dead-letter-queue inspection/replay.
    name: Admin
  - description: >-
      LBTR (gross real-time settlement) commands and reads — position requests,
      confirmation or divergence of announced settlement results, and
      receivables-anticipation transfers exchanged with the câmara.
    name: LBTR
  - description: >-
      Card settlement funding — the settlement instructions to be funded in STR
      and the declaration of each deposit's confirmation.
    name: Funding
  - description: >-
      IF Domicílio (the bank where the merchant receives its sales) view — the
      settlements Núclea notified it of and its confirmation or refusal of them.
    name: Domicile
  - description: >-
      Read-only introspection of the settlement time grid (the windows in which
      each message type may be sent).
    name: Schedule
paths:
  /v1/funding/settlement-instructions/{instructionId}/deposit-confirmations:
    post:
      tags:
        - Funding
      summary: Declare the STR confirmation of a card deposit
      description: >-
        The client declares the LDL0022R1 its own STR connection received for
        the LDL0022 it sent. The rail checks it against the instruction's
        current round (409 otherwise), the card product SLC and the exact value
        of the round (422 otherwise), and a terminal SitLancLDL (a pending one
        is 422), then keeps it as proof. An effected launch moves the
        instruction to DEPOSITED; a rejected or cancelled one emits
        funding.deposit_failed. The same declaration repeated answers the same;
        the same NumCtrlSTR with other values answers 409. Where Lerian SPB
        sends the card deposits every declaration answers 409: Lerian SPB
        reports the LDL0022R1 itself. RBAC: funding:write; declarer from the
        authorized subject.
      operationId: declareDepositConfirmation
      parameters:
        - description: Settlement instruction id (UUID).
          in: path
          name: instructionId
          required: true
          schema:
            description: Settlement instruction id (UUID).
            examples:
              - 018f8a3e-4b2c-7c1a-9e5d-2f6a1b3c4d5e
            type: string
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/DepositConfirmationRequest'
        required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DepositConfirmationResponse'
          description: OK
        '413':
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Detail'
          description: Request Entity Too Large
        '422':
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Detail'
          description: Unprocessable Entity
        '500':
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Detail'
          description: Internal Server Error
        '501':
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Detail'
          description: >-
            Not Implemented: this capability is not part of this deployment.
            Operations are registered unconditionally so the published contract
            is identical across deploy shapes; when the capability behind one
            did not compose here (authentication disabled, no database, no
            outbound transport, or the feature switched off) it answers this
            coded SLC-0012 problem. It is definitive for this deployment:
            retrying does not help, and the `detail` is deliberately scrubbed
            (any status >= 500 is).
        default:
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Detail'
          description: Error
components:
  schemas:
    DepositConfirmationRequest:
      additionalProperties: false
      properties:
        amount:
          description: >-
            VlrLanc of the LDL0022 the client sent (Valor; a sign is refused,
            the LDL0022 always pays the câmara). It must equal the value of the
            round.
          examples:
            - '1500.00'
          type: string
        codProdt:
          description: CodProdt of the LDL0022 the client sent; it must be SLC.
          examples:
            - SLC
          type: string
        dtHrSit:
          description: >-
            DtHrSit of the LDL0022R1 (Data Hora, YYYY-MM-DDTHH:MM:SS, Brasília
            time).
          examples:
            - '2026-06-28T07:41:12'
          type: string
        dtMovto:
          description: DtMovto of the LDL0022R1 (YYYY-MM-DD).
          examples:
            - '2026-06-28'
          type: string
        numCtrlIF:
          description: NumCtrlIF of the client's LDL0022 (ControleIF, 1 to 20 characters).
          examples:
            - IF20260628000123
          type: string
        numCtrlSTR:
          description: NumCtrlSTR of the LDL0022R1 (Controle, 20 characters).
          examples:
            - STR20260628000000123
          type: string
        round:
          description: >-
            Round of the settlement instruction the deposit answers; it must be
            the current round.
          examples:
            - 1
          format: int64
          type: integer
        sitLancLDL:
          description: >-
            SitLancLDL of the LDL0022R1, as received. A pending situation (17,
            19) is refused: declare the terminal answer.
          examples:
            - '1'
          type: string
      required:
        - round
        - numCtrlIF
        - numCtrlSTR
        - sitLancLDL
        - dtHrSit
        - dtMovto
        - amount
        - codProdt
      type: object
    DepositConfirmationResponse:
      additionalProperties: false
      properties:
        instructionId:
          description: The settlement instruction the declaration was recorded against.
          type: string
        numCtrlSTR:
          description: The STR launch recorded as proof.
          type: string
        round:
          description: The round the deposit answers.
          format: int64
          type: integer
        sitLancCategory:
          description: >-
            EFFECTED, CANCELLED or REJECTED: the category of the declared
            SitLancLDL.
          type: string
        state:
          description: >-
            The instruction's state after the declaration: DEPOSITED once an
            effected deposit of the current round is recorded.
          type: string
      required:
        - instructionId
        - round
        - numCtrlSTR
        - sitLancCategory
        - state
      type: object
    Detail:
      additionalProperties: false
      properties:
        code:
          description: >-
            Stable, machine-readable domain error code scoped to the emitting
            service (format: <SERVICE>-NNNN).
          type: string
        correlationId:
          description: Request-scoped correlation identifier echoing X-Request-ID.
          examples:
            - req-7a3f9c2e
          type: string
        detail:
          description: >-
            A human-readable explanation specific to this occurrence of the
            problem.
          examples:
            - Property foo is required but is missing.
          type: string
        errors:
          description: Optional list of individual error details
          items:
            $ref: '#/components/schemas/ErrorDetail'
          type:
            - array
            - 'null'
        instance:
          description: >-
            A URI reference that identifies the specific occurrence of the
            problem.
          examples:
            - https://example.com/error-log/abc123
          format: uri
          type: string
        status:
          description: HTTP status code
          examples:
            - 400
          format: int64
          type: integer
        title:
          description: >-
            A short, human-readable summary of the problem type. This value
            should not change between occurrences of the error.
          examples:
            - Bad Request
          type: string
        type:
          default: about:blank
          description: A URI reference to human-readable documentation for the error.
          examples:
            - https://example.com/errors/example
          format: uri
          type: string
        upstream:
          $ref: '#/components/schemas/Upstream'
          description: >-
            RFC 9457 extension member: the error a proxied third-party provider
            reported. Absent unless the emitting service explicitly surfaced
            one.
      required:
        - correlationId
      type: object
    ErrorDetail:
      additionalProperties: false
      properties:
        location:
          description: >-
            Where the error occurred, e.g. 'body.items[3].tags' or
            'path.thing-id'
          type: string
        message:
          description: Error message text
          type: string
        value:
          description: The value at the given location
      type: object
    Upstream:
      additionalProperties: false
      properties:
        code:
          description: The upstream provider's own error code, verbatim.
          examples:
            - E4001
          type: string
        message:
          description: >-
            The upstream provider's own error message, verbatim (bounded, never
            its raw response body).
          examples:
            - account not found at provider
          type: string
      type: object
  securitySchemes:
    BearerAuth:
      bearerFormat: JWT
      description: JWT bearer token issued by the identity provider.
      scheme: bearer
      type: http

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.