---
title: "Get QR Code information and calculate payment"
method: GET
path: "/v1/pix/qrcode/jws/{access-token}"
tags: ["QR Code"]
---

# Get QR Code information and calculate payment

`GET /v1/pix/qrcode/jws/{access-token}`

Get QR Code information and, at the same time, calculate payment information depending on query parameters passed.

## Path parameters

- `access-token` string, required

## Query parameters

- `desired-payment-date` string, date
- `payer-city-id` string

## Headers

- `Authorization` string, required

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