> ## 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.

# Request a receivables-anticipation transfer from the câmara

> As the card issuer's bank, asks the câmara to transfer a receivables anticipation negotiated with the acquirer (SLC0004). Asynchronous intake — 202 means the request is committed and nothing has been sent yet. Lerian SILOC sends it on the SILOC connection and the state is read back from GET /v1/lbtr/commands/{commandId}: ANSWERED carries the câmara's SLC0004R1 (numCtrlSLC and the raw sitLancSLC), REFUSED carries the SLC0004E error codes verbatim. Each state change also emits anticipation_request.status_changed. The window and movement-day rules are the câmara's to apply (ESLC1010-ESLC1012), never this API's. X-Idempotency is REQUIRED: a retry carrying the same key replays the stored response, the same key with a different body is 409, and a new request needs a new key. RBAC: lbtr:write; the requesting operator is always taken from the validated request identity, never from the payload.



## OpenAPI

````yaml /en/openapi/v3-current/slc.yaml post /v1/lbtr/anticipation-requests
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/lbtr/anticipation-requests:
    post:
      tags:
        - LBTR
      summary: Request a receivables-anticipation transfer from the câmara
      description: >-
        As the card issuer's bank, asks the câmara to transfer a receivables
        anticipation negotiated with the acquirer (SLC0004). Asynchronous intake
        — 202 means the request is committed and nothing has been sent yet.
        Lerian SILOC sends it on the SILOC connection and the state is read back
        from GET /v1/lbtr/commands/{commandId}: ANSWERED carries the câmara's
        SLC0004R1 (numCtrlSLC and the raw sitLancSLC), REFUSED carries the
        SLC0004E error codes verbatim. Each state change also emits
        anticipation_request.status_changed. The window and movement-day rules
        are the câmara's to apply (ESLC1010-ESLC1012), never this API's.
        X-Idempotency is REQUIRED: a retry carrying the same key replays the
        stored response, the same key with a different body is 409, and a new
        request needs a new key. RBAC: lbtr:write; the requesting operator is
        always taken from the validated request identity, never from the
        payload.
      operationId: submitLbtrAnticipationRequest
      parameters:
        - description: >-
            Required. A retry carrying the same key replays the stored response
            instead of sending a second request; a genuinely new request needs a
            new key.
          in: header
          name: X-Idempotency
          required: true
          schema:
            description: >-
              Required. A retry carrying the same key replays the stored
              response instead of sending a second request; a genuinely new
              request needs a new key.
            type: string
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SubmitAnticipationRequestBody'
        required: true
      responses:
        '202':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CommandAcceptedResponse'
          description: Accepted
        '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:
    SubmitAnticipationRequestBody:
      additionalProperties: false
      properties:
        cnpjNLiqdantCredtd:
          description: 'CNPJNLiqdantCredtd: the acquirer''s CNPJ.'
          examples:
            - '99900003000101'
          pattern: ^[0-9A-Z]{12}[0-9]{2}$
          type: string
        dtLiquid:
          description: >-
            DtLiquid: the payment date. The câmara refuses one that is not its
            movement date (ESLC1010).
          examples:
            - '2026-10-13'
          format: date
          type: string
        dtMovto:
          description: >-
            DtMovto: the movement date. The câmara refuses one that is not its
            own (ESLC1012).
          examples:
            - '2026-10-13'
          format: date
          type: string
        ispbIFCredtd:
          description: >-
            ISPBIFCredtd: the ISPB of the acquirer's settlement bank, the
            institution the transfer credits.
          examples:
            - '60746948'
          pattern: ^[0-9A-Z]{8}$
          type: string
        products:
          description: >-
            Grupo_SLC0004_Prodt, optional and repeatable. Never summed against
            vlrTot here.
          items:
            $ref: '#/components/schemas/AnticipationProductRequest'
          type:
            - array
            - 'null'
        vlrTot:
          description: >-
            VlrTot: the total to settle, a decimal string carried verbatim; the
            câmara refuses a value not above zero (ESLC1009).
          examples:
            - '1500.00'
          pattern: ^-?[0-9]{1,17}(\.[0-9]{1,2})?$
          type: string
      required:
        - ispbIFCredtd
        - cnpjNLiqdantCredtd
        - vlrTot
        - dtLiquid
        - dtMovto
      type: object
    CommandAcceptedResponse:
      additionalProperties: false
      properties:
        commandId:
          description: >-
            The command's id (a UUID minted by this service). It is the key
            every later fact joins on and the id to read the command back by.
          examples:
            - 0199a2e8-7a1c-7c1a-9e5d-2f6a1b3c4d5e
          type: string
        messageType:
          description: >-
            The outbound message this command originates: LTR0002 (result
            answer), LTR0008 (non-liquidante answer), LTR0009 (position query)
            or SLC0004 (anticipation request).
          examples:
            - LTR0002
          type: string
        requestedAt:
          description: When the institution decided (RFC3339, UTC).
          examples:
            - '2026-09-22T13:04:11Z'
          type: string
        sourceAggregateId:
          description: >-
            The announcement this command answers. For a position query or an
            anticipation request it is the command's own id, because neither
            answers an announcement.
          examples:
            - 018f8a3e-4b2c-7c1a-9e5d-2f6a1b3c4d5e
          type: string
        sourceAggregateVersion:
          description: >-
            The version of the announcement this command was authorised against,
            kept so a later reader can see which view of it was answered.
          examples:
            - 1
          format: int64
          type: integer
        status:
          description: >-
            Always REQUESTED here: the command row and its outbound event are
            committed and nothing has been sent yet. Poll the command to see it
            reach ACCEPTED, ANSWERED, REFUSED or FAILED.
          examples:
            - REQUESTED
          type: string
      required:
        - commandId
        - messageType
        - status
        - sourceAggregateId
        - sourceAggregateVersion
        - requestedAt
      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
    AnticipationProductRequest:
      additionalProperties: false
      properties:
        codProdt:
          description: >-
            CodProdt: a card arrangement code live in BACEN's Dicionário de
            Domínios; Lerian SILOC refuses any other.
          examples:
            - VCC
          maxLength: 3
          type: string
        vlrLanc:
          description: >-
            VlrLanc: this arrangement's amount, a decimal string carried
            verbatim.
          examples:
            - '1000.00'
          pattern: ^-?[0-9]{1,17}(\.[0-9]{1,2})?$
          type: string
      required:
        - codProdt
        - vlrLanc
      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.