---
title: "Update dynamic COBV QR Code"
method: PATCH
path: "/v1/pix/qrcode/cobv"
tags: ["QR Code"]
---

# Update dynamic COBV QR Code

`PATCH /v1/pix/qrcode/cobv`

Update dynamic COBV QR Code

The entire QR Code is updated. If a parameter is not passed, the current value (if any) is emptied.

## Headers

- `Authorization` string, required

## Request body

- QrcodeQrCodeUpdateCobVRequest — Update COBV QR Code request
  - `id` string, required — Pismo QR Code identifier
  - `status` 'CREATED' | 'PROCESSING' | 'SETTLED' | 'CANCELLED' | 'HOLD', required — - `CREATED` - Payment has been created and is pending processing - `PROCESSING` - P2P balance was impacted and waiting for provider confirmation. For cashin, the transaction means the money will be credited on the next Working Day - `SETTLED` - Transaction completed processing and is settled - `CANCELLED` - Something went wrong and the transaction is cancelled. Refer to `reason` for more details - `HOLD` - The payment is on hold, pending further review
  - `charge` Charge, required
    - `due_date` string, date, required — Payment due date. Format = yyyy-mm-dd
    - `validity_after_expiration_day` integer — How many days QR Code is valid after expiration
    - `discount_type` 'FIXED_VALUE_UNTIL_THE_DATES_INFORMED' | 'PERCENTAGE_DATE_REPORTED' | 'AMOUNT_PER_CALENDAR_DAY_ADVANCE' | 'AMOUNT_ADVANCE_WORKING_DAY' | 'PERCENTAGE_ADVANCE_CURRENT_DAY' | 'PERCENTAGE_ADVANCE_WORKING_DAY' — Discount value type.
    - `discount_value` number — Discount value to be applied when `discount_type` is not `FIXED_VALUE_UNTIL_THE_DATES_INFORMED` or `PERCENTAGE_DATE_REPORTED`.
    - `discount_fixed_dates` QrcodeDiscountDate[] — Maximum dates for payment to apply the discount (fixed value). Use this attribute for `discount_type` = `FIXED_VALUE_UNTIL_THE_DATES_INFORMED`
      - `date` string, date — Last date discount can be applied. Format = yyyy-mm-dd.
      - `value` number — Discount values.
    - `fine_type` 'FIXED_VALUE' | 'PERCENT' — Fine type.
    - `fine_value` number — Fine value.
    - `fine_final_amount` number — Fine total (calculated).
    - `interest_type` 'VALUE_CALENDAR_DAYS' | 'PERCENTAGE_PER_DAY_CALENDAR_DAYS' | 'PERCENTAGE_PER_MONTH_CALENDAR_DAYS' | 'PERCENTAGE_PER_YEAR_CALENDAR_DAYS' | 'VALUE_WORKING_DAYS' | 'PERCENTAGE_PER_DAY_WORKING_DAYS' | 'PERCENTAGE_PER_MONTH_WORKING_DAYS' | 'PERCENTAGE_PER_YEAR_WORKING_DAYS' — Interest type to calculate.
    - `interest_value` number — Value to be applied.
    - `interest_final_amount` number — Interest total (calculated).
    - `settlement_type` 'FIXED_VALUE' | 'PERCENT' — Settlement type.
    - `settlement_value` number — Settlement value (depends on `settlement_type`).
    - `settlement_final_amount` number — Total settlement (calculated as fixed or percentage).
    - `final_amount` number — Total (initial - `settlement_final_amount` - `discount_final_amount` + `interest_final_amount` + `fine_final_amount`)
  - `payee` QrcodePayeeRequest, required — Payee information
    - `address` string, required — Location
    - `city` string, required — City where payment occurred.
    - `key` string, required — Payee Pix key (should have Pismo account)
    - `state` string, required — Brazilian state where payment will occur - two letter ISO 3166 code.
    - `zip_code` string, required — Location postal code.
    - `category` string — Receiver ISO 18245 merchant category code.
  - `payer` PayerInfo, required — Payer information
    - `name` string, required — Name
    - `address` string — Location
    - `city` string — City where payment occurred.
    - `document_number` string — Government ID, such as a CPF (Cadastro de Pessoas Fisicas - individual tax ID in Brazil) or a CNPJ (Cadastro Nacional de Pessoa Juridica - business tax ID in Brazil) number.
    - `state` string — Brazilian state where payment will occur - two letter ISO 3166 code.
    - `trade_name` string — Company name
    - `type` 'LEGAL_PERSON' | 'NATURAL_PERSON' — Person legal type: * `LEGAL_PERSON` - Person * `NATURAL_PERSON` - Company or organization
    - `zip_code` string — Location postal code.
  - `initial_amount` number, required — Initial payment amount
  - `transaction_identification` string, required — Client-generated unique transaction ID for client monitoring and tracking.
  - `payer_solicitation` string — Payee text sent to payer.
  - `qrcode_expiration_time` integer — QR Code's maximum time for presentation (in seconds)
  - `reusable` boolean — Can QR Code be reused? Default is `false`.
  - `allows_value_change` boolean — Can payer change payment values? Default is `false`.
  - `location` QrcodeLocation — Location URL information
    - `url_jwk` string — PSP Receiver's URL that holds key pairs in JSON format. Should be hosted on the same site associated with the CERTQRC certificate. Use the format "JWK Set URL" without the protocol (http/https). The Central Bank uses this field and `url_payload` to register and validate the QR Code. This field **must** be passed if the PSP requires it. The URL format is described in <a href="https://www.bcb.gov.br/content/estabilidadefinanceira/cedsfn/Manual_de_Seguranca_PIX.pdf" target="_blank">Manual de Segurança do PIX</a>.
    - `url_payload` string — PSP Receiver's URL containing the dynamic QR Code's JSON Web Signature (JWS). Should not include the protocol (http/https). The Central Bank uses this field and `url_jwk` to register and validate the QR Code. This field **must** be passed if the PSP requires it. The URL format is described in <a href="https://www.bcb.gov.br/content/estabilidadefinanceira/pix/Regulamento_Pix/II_ManualdePadroesparaIniciacaodoPix.pdf" target="_blank">Manual de Padrões para Iniciação do PIX</a>.
  - `additional_information` QrcodeAdditional[] — Additional remarks
    - `name` string, required — Label name
    - `value` string, required — Value
  - `access_token` string — Access token related to the `url_payload`/`url_payload_rec` fields, used to register and validate a QR code. This field **must** be provided if the PSP requires it. The URL format is described in the Manual of Standards for PIX Initiation.

## Response `202`

Generate COB QR Code response

- QrcodeQrCodeGenerateCobResponse — Generate COB Qrcode response
  - `id` string, required — Pismo QR Code identifier
  - `access_token` string, required — QR Code access token generated and returned at creation.
  - `external_id` string, required — Client-generated record identifier for client tracking and monitoring.
  - `emv` string, required — Base 64 encoded discount QR Code payload. EMV = Europay, Mastercard and Visa, a global standard for credit and debit payment. The EMV might include details required for secure transactions such as cardholder informatipn, transaction amount, merchant information, and other relevant data.
  - `status` 'CREATED' | 'PROCESSING' | 'SETTLED' | 'CANCELLED' | 'HOLD', required — - `CREATED` - Payment has been created and is pending processing - `PROCESSING` - P2P balance was impacted and waiting for provider confirmation. For cashin, the transaction means the money will be credited on the next Working Day - `SETTLED` - Transaction completed processing and is settled - `CANCELLED` - Something went wrong and the transaction is cancelled. Refer to `reason` for more details - `HOLD` - The payment is on hold, pending further review
  - `qrcode_imageb64` string — Base64 encoded QR Code
  - `version` integer — Current version
  - `jws` string — JWS (JSON Web Signature) payload. When a JWT (JSON Web Token) is signed, it becomes a JWS.
  - `creation_date` string, datetime — QR Code creation date/time. RFC 3339 format.
  - `last_update` string, datetime — When QR Code last updated. RFC 3339 format.

## Other responses

- `400` — Bad request
- `401` — Access token is missing or invalid
- `403` — The request has been lost
- `404` — Not Found
- `409` — The specified resource status conflicts with the current request.
- `429` — Too many reqquests
- `500` — Internal server error
- `502` — Bad Gateway
- `504` — Gateway Timeout

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/versions/935b62e16de4/schema)