Skip to main content
POST
cURL with fictitious data

Authorizations

Authorization
string
header
required

JWT bearer token issued by the identity provider.

Body

application/json
emvPayload
string
required

EMV BR Code payload to decode

Example:

"00020101021126580014br.gov.bcb.pix0136123e4567-e12b-12d1-a456-4266554400005204000053039865802BR5913Fulano de Tal6008BRASILIA62070503***630448CD"

Response

OK

isReusable
boolean
required

Whether the BR Code may be paid more than once. True for every STATIC payload, including one whose Point of Initiation method is absent.

Example:

true

merchantCity
string
required
Example:

"Goiania"

merchantName
string
required
Example:

"Loja Teste"

type
enum<string>
required

Type embedded in the payload. A payload that names NO Point of Initiation method (EMV tag 01 absent) is reported as STATIC: EMVCo makes the element optional and defines its absence as static, and BCB's own composed QR Code examples omit it. Such a payload was previously rejected as malformed.

Available options:
STATIC,
DYNAMIC_IMMEDIATE,
DYNAMIC_DUEDATE
Example:

"STATIC"

amount
string
Example:

"100.50"

currency
enum<string>
Available options:
BRL
Example:

"BRL"

description
string
Example:

"Pagamento do pedido 12345"

expiresAt
string<date-time>
Example:

"2026-05-06T11:30:00Z"

keyType
enum<string>

Pix key type inferred from keyValue, ABSENT when no type both matches and validates. A CPF/CNPJ must satisfy its Modulo 11 check digits — a document that does not is unregistrable at DICT, so no type is reported. A masked document ("529.982.247-25") IS recognised. A phone is any E.164 number, not only "+55".

Available options:
CPF,
CNPJ,
PHONE,
EMAIL,
EVP
Example:

"EVP"

keyValue
string

Pix key exactly as the payload carries it, punctuation included. It is never normalized: this endpoint reports what was scanned.

Example:

"123e4567-e12b-12d1-a456-426655440000"

txId
string
Example:

"TX12345"