> ## 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. # Resolve CobV payload (JWS) > Resolves, by the opaque access token, the signed JSON payload (JWS, application/jose) of a due-date charge (CobVPayload). valor.final is calculated (fine/interest/rebate/discount) for the expected payment date (DPP). The verification key is published at /.well-known/jwks.json. ## OpenAPI ````yaml /pt/openapi/v3-current/spi-brcode.yaml get /api/v1/brcode/payload/cobv/{locator} openapi: 3.1.0 info: contact: email: contact@lerian.studio name: Lerian Studio url: https://lerian.studio description: BR Code service for QR code generation and decoding (EMV QRCPS-MPM). license: name: Lerian Studio General License title: Lerian SPI — BR Code API version: 1.0.0 servers: - url: https://api.example.com description: >- Replace the example host with the URL provided during environment onboarding. security: [] tags: - description: EMV BR Code payload generation, decoding, validation, info, and lookup. name: BRCode - description: >- Pix charges (Cob/CobV/LoteCobV): create, retrieve by TxID, list, cancel, reconcile, and resolve public payloads. name: Charges - description: >- Flow (mandatory order): create cob/cobv → generate QR/payload. A dynamic BR Code payload references a charge, so the cob/cobv charge MUST be created first; the payload links to it by txid/locator. name: charge paths: /api/v1/brcode/payload/cobv/{locator}: get: tags: - CobVPayload summary: Resolve CobV payload (JWS) description: >- Resolves, by the opaque access token, the signed JSON payload (JWS, application/jose) of a due-date charge (CobVPayload). valor.final is calculated (fine/interest/rebate/discount) for the expected payment date (DPP). The verification key is published at /.well-known/jwks.json. operationId: resolveCobVPayload 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 - description: >- Data de pagamento prevista (YYYY-MM-DD) para o cálculo do valor final. Deve estar entre o dia corrente (calendário brasileiro) e o último dia pagável da cobrança (calendario.dataDeVencimento prorrogado + calendario.validadeAposVencimento); uma data anterior ao momento presente ou superior à validade da cobrança é recusada com 400 (CobPayloadOperacaoInvalida). explode: false in: query name: DPP schema: description: >- Data de pagamento prevista (YYYY-MM-DD) para o cálculo do valor final. Deve estar entre o dia corrente (calendário brasileiro) e o último dia pagável da cobrança (calendario.dataDeVencimento prorrogado + calendario.validadeAposVencimento); uma data anterior ao momento presente ou superior à validade da cobrança é recusada com 400 (CobPayloadOperacaoInvalida). type: string - description: >- Código IBGE (7 dígitos) do município do pagador, usado para os feriados estaduais e municipais que deslocam o vencimento e a contagem de juros/multa/desconto. Os dois primeiros dígitos são o código da UF, que é um conjunto fechado (11-17, 21-29, 31-33, 35, 41-43, 50-53); um prefixo fora dele não é município algum e é recusado aqui. Ausente: assume-se que não há feriados estaduais/municipais no período. explode: false in: query name: codMun schema: description: >- Código IBGE (7 dígitos) do município do pagador, usado para os feriados estaduais e municipais que deslocam o vencimento e a contagem de juros/multa/desconto. Os dois primeiros dígitos são o código da UF, que é um conjunto fechado (11-17, 21-29, 31-33, 35, 41-43, 50-53); um prefixo fora dele não é município algum e é recusado aqui. Ausente: assume-se que não há feriados estaduais/municipais no período. pattern: ^(1[1-7]|2[1-9]|3[1235]|4[1-3]|5[0-3])[0-9]{5}$ type: string responses: '200': content: application/jose: {} description: Compact JWS (RFC 7515) signed payload. headers: Content-Type: schema: type: string '400': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Bad Request '404': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Not Found '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 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: -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 ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.