Decode a Pix EMV payload
Parses a Pix EMV payload and returns the structured payment details. Third-party payloads are accepted, so decoding is more permissive than BR Code creation: a payload without a Point of Initiation method is decoded as STATIC. keyType is inferred from the key value and omitted when no key type defined by the BCB both matches the value and passes validation. See the response schema for the rules that apply to each field.
Authorizations
JWT bearer token issued by the identity provider.
Body
EMV BR Code payload to decode
"00020101021126580014br.gov.bcb.pix0136123e4567-e12b-12d1-a456-4266554400005204000053039865802BR5913Fulano de Tal6008BRASILIA62070503***630448CD"
Response
OK
Whether the BR Code may be paid more than once. True for every STATIC payload, including one whose Point of Initiation method is absent.
true
"Goiania"
"Loja Teste"
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.
STATIC, DYNAMIC_IMMEDIATE, DYNAMIC_DUEDATE "STATIC"
"100.50"
BRL "BRL"
"Pagamento do pedido 12345"
"2026-05-06T11:30:00Z"
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".
CPF, CNPJ, PHONE, EMAIL, EVP "EVP"
Pix key exactly as the payload carries it, punctuation included. It is never normalized: this endpoint reports what was scanned.
"123e4567-e12b-12d1-a456-426655440000"
"TX12345"

