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

# Conjunto de claves JWK del payload de BR Code

> Publica el conjunto de claves JWK (JWK Set, RFC 7517) del PSP recebedor. Un PSP pagador resuelve la clave de verificación JWS de un payload público cob/cobv/rec haciendo coincidir el kid del encabezado JWS del payload con el kid de una entrada aquí. Devuelve 404 cuando la firma de payloads JOSE no está configurada.



## OpenAPI

````yaml es/openapi/v3-current/spi-brcode.yaml get /api/v1/brcode/.well-known/jwks.json
openapi: 3.1.0
info:
  contact:
    email: contact@lerian.studio
    name: Lerian Studio
    url: https://lerian.studio
  description: >-
    Servicio de BR Code para la generación y decodificación de códigos QR (EMV
    QRCPS-MPM).
  license:
    name: Lerian Studio General License
  title: Lerian SPI — BR Code API
  version: 1.0.0
servers:
  - url: https://spi.sandbox.lerian.net
security: []
tags:
  - description: >-
      Generación, decodificación, validación, información y consulta de payloads
      de BR Code EMV.
    name: BRCode
  - description: >-
      Cobranzas Pix (Cob/CobV/LoteCobV): crear, consultar por TxID, listar,
      cancelar, conciliar y resolver payloads públicos.
    name: Charges
  - description: >-
      Flujo (orden obligatorio): crear cob/cobv → generar QR/payload. Un payload
      dinámico de BR Code hace referencia a una cobranza, por lo que la cobranza
      cob/cobv DEBE crearse primero; el payload se vincula a ella mediante
      txid/locator.
    name: charge
paths:
  /api/v1/brcode/.well-known/jwks.json:
    get:
      tags:
        - BRCode
      summary: Conjunto de claves JWK del payload de BR Code
      description: >-
        Publica el conjunto de claves JWK (JWK Set, RFC 7517) del PSP recebedor.
        Un PSP pagador resuelve la clave de verificación JWS de un payload
        público cob/cobv/rec haciendo coincidir el kid del encabezado JWS del
        payload con el kid de una entrada aquí. Devuelve 404 cuando la firma de
        payloads JOSE no está configurada.
      operationId: getBRCodeJWKS
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/JWKSet'
          description: OK
        default:
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Detail'
          description: Error
components:
  schemas:
    JWKSet:
      additionalProperties: false
      properties:
        keys:
          items:
            $ref: '#/components/schemas/JWK'
          type:
            - array
            - 'null'
      required:
        - keys
      type: object
    Detail:
      additionalProperties: false
      properties:
        code:
          description: >-
            Stable, machine-readable domain error code scoped to the emitting
            service (format: <SERVICE>-NNNN).
          examples:
            - ERR-0001
          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
      type: object
    JWK:
      additionalProperties: false
      properties:
        e:
          type: string
        key_ops:
          items:
            type: string
          type:
            - array
            - 'null'
        kid:
          type: string
        kty:
          type: string
        'n':
          type: string
        x5c:
          items:
            type: string
          type:
            - array
            - 'null'
        x5t:
          type: string
        x5t#S256:
          type: string
      required:
        - kty
        - 'n'
        - e
        - key_ops
        - kid
        - x5t
        - x5t#S256
        - x5c
      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

````