Decode and Create Pix Payment by Pix Key
POST/pix/payments/by-key/decode-instant-billing
Initiate a new pix payment using a pix key. Enter the decode and pix payment's information in the request body and execute.
Request
Header Parameters
- If there's no value: The default protection checks that the values in this request are equal: { method, params, path, query, body, userId }. This means that if a request repeats the same values, it will be blocked.
- 'nonce': The nonce and { method, params, path, query, body, userId } value are checked. When the protection schema is this, requests will be OK if this nonce value is different in each request.
- 'x-transaction-uuid': The transactionId and { method, params, path, query, body, userId } value are checked. Requests will be OK if this x-transaction-uuid value is different in each request.
- 'x-transaction-uuid&nonce' or 'nonce&x-transaction-uuid': The nonce, transactionId value and { method, params, path, query, body, userId } are checked, i.e. if requests are repeated the same value in both fields, they will be blocked. But if any field has a different value, the request is OK.
The replay-protection-schema allows the user to choose between 3 options:
The transaction ID is a UUID (v4) used to uniquely identify the object that will be created. All objects must have an identifier.
Sender Wallet UUID (if empty, your default Wallet UUID will be settled)
The nonce ID is a UUID (v4) used to uniquely identify the requisition. All requisitions must have an identifier.
- application/json
Body
required
- CPF: Key type CPF.
- EVP: Key type EVP.
- EMAIL: Key type EMAIL.
- PHONE: Key type PHONE.
- CNPJ: Key type CNPJ.
Pix key.
Possible values: [CNPJ
, CPF
, PHONE
, EMAIL
, EVP
]
Pix Key state:
Value in R$ cents.
Payment date.
User defined payment description.
User defined allowed document.
User defined bank allowlist.
User defined bank blocklist.
Responses
- 201
- 400
- 401
- 422
Decoded Pix Key and Payment accomplished.
- application/json
- Schema
- Example (from schema)
Schema
- CPF: Key type CPF.
- EVP: Key type EVP.
- EMAIL: Key type EMAIL.
- PHONE: Key type PHONE.
- CNPJ: Key type CNPJ.
decoded_pix_key object
Unique decoded pix key UUID.
Possible values: [CNPJ
, CPF
, PHONE
, EMAIL
, EVP
]
Pix Key state:
Possible values: [NATURAL_PERSON
, LEGAL_PERSON
]
Pix key.
Owner document number.
Owner name.
Company's trade name.
Bank ISPB
payment object
Payment UUID.
Operation UUID. Used to get receipt and track the transaction. This will not be returned if the payment has been scheduled.
Possible values: [PENDING
, WAITING
, WAITING_DELAYED
, CONFIRMED
, ERROR
, FAILED
, CANCELED
, SCHEDULED
]
Payment state.
Value in R$ cents.
Schedule a day to execute payment. Use null to send payment right now.
User defined payment description.
Payment created date.
Possible values: [DOCUMENT_NOT_ALLOWED
, BANK_NOT_ALLOWLIST
, BANK_IN_BLACKLIST
]
Reason that decoded pix key is invalid. Check this field to know if decoded and payment are valid.
{
"decoded_pix_key": {
"id": "d5e0bec8-8695-4557-b0dd-021788cd83ef",
"type": "EMAIL",
"person_type": "LEGAL_PERSON",
"key": "string",
"document": "string",
"name": "string",
"trade_name": "string",
"end_to_end_id": "string",
"ispb": "string"
},
"payment": {
"id": "f6e2e084-29b9-4935-a059-5473b13033aa",
"operation_id": "f6e2e084-29b9-4935-a059-5473b13033aa",
"state": "PENDING",
"value": 1299,
"payment_date": null,
"description": "string",
"created_at": "2024-12-26T10:36:25.767Z"
},
"failed_code": "DOCUMENT_NOT_ALLOWED"
}
If any required params are missing or has invalid format or type.
User authentication failed.
If any required params are missing or has invalid format or type.