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

# Resolver payload de Cob (JWS)

> Pré-requisito: a cobrança Cob/CobV referenciada já deve existir (consulte postCob e putCobV). Resolve, pelo token de acesso opaco, o payload JSON assinado (JWS, application/jose) de uma cobrança imediata (CobPayload). O valor.original é projetado verbatim. A chave de verificação é publicada em /.well-known/jwks.json.



## OpenAPI

````yaml pt/openapi/v3-current/spi-brcode.yaml get /api/v1/brcode/payload/{locator}
openapi: 3.1.0
info:
  contact:
    email: contact@lerian.studio
    name: Lerian Studio
    url: https://lerian.studio
  description: >-
    Serviço de BR Code para geração e decodificação 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: >-
      Geração, decodificação, validação, informações e consulta de payloads de
      BR Code EMV.
    name: BRCode
  - description: >-
      Cobranças Pix (Cob/CobV/LoteCobV): criar, consultar por TxID, listar,
      cancelar, conciliar e resolver payloads públicos.
    name: Charges
  - description: >-
      Fluxo (ordem obrigatória): criar cob/cobv → gerar QR/payload. Um payload
      dinâmico de BR Code faz referência a uma cobrança, portanto a cobrança
      cob/cobv DEVE ser criada primeiro; o payload é vinculado a ela por
      txid/locator.
    name: charge
paths:
  /api/v1/brcode/payload/{locator}:
    get:
      tags:
        - CobPayload
        - charge
      summary: Resolver payload de Cob (JWS)
      description: >-
        Pré-requisito: a cobrança Cob/CobV referenciada já deve existir
        (consulte postCob e putCobV). Resolve, pelo token de acesso opaco, o
        payload JSON assinado (JWS, application/jose) de uma cobrança imediata
        (CobPayload). O valor.original é projetado verbatim. A chave de
        verificação é publicada em /.well-known/jwks.json.
      operationId: resolveCobPayload
      parameters:
        - description: Token de acesso opaco do payload (capability URL).
          in: path
          name: locator
          required: true
          schema:
            description: Token de acesso opaco do payload (capability URL).
            type: string
      responses:
        '200':
          content:
            application/jose: {}
          description: Compact JWS (RFC 7515) signed payload.
          headers:
            Content-Type:
              schema:
                type: string
        default:
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/Detail'
          description: Error
      security: []
components:
  schemas:
    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
    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

````