Create Split PIX QR Code Static
POSTTag: api-paas-post-split-payments-pix-qr-codes-staticDescription: Generate a new static QR Code with split payment configuration./split-payments/pix/qr-codes/static
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:
Sender Wallet UUID (if empty, your default Wallet UUID will be settled)
The transaction ID is a UUID (v4) used to uniquely identify the object that will be created. All objects must have an identifier.
The nonce ID is a UUID (v4) used to uniquely identify the request. All requests must have an identifier.
Possible values: [pt-BR, en-US]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
UUID (v4) of the product that the request should use. Send it explicitly when the authenticated user has more than one product or when the integration must select a specific product. If omitted and the endpoint does not require it, the API uses the authenticated user's default product.
UUID (v4) of the user on whose behalf the request should run within the selected product. If omitted, the request runs as the authenticated user. Requires x-product-uuid.
- application/json
Body
required
- Array [
- ]
Associated key ID.
Value in R$ cents.
User friendly static QR Code identifier.
User defined payment description.
Expiration date to pay static QR Code. Max date is 3 months ahead.
If it is true, static QR Code can be paid many times. When it is false, expiration date is required.
User defined payment merchant ID.
split objectrequired
Possible values: [PERCENTUAL, ABSOLUTE]
Split type (PERCENTUAL or ABSOLUTE).
accounts object[]required
Array of accounts to receive split payments.
Possible values: [NATURAL_PERSON, LEGAL_PERSON]
Person type (NATURAL_PERSON or LEGAL_PERSON).
Name of the account holder.
CPF or CNPJ of the account holder.
Bank ISPB code.
Branch number.
Account number.
Possible values: [CACC, CASH, CHAR, CISH, COMM, CPAC, LLSV, LOAN, MGLD, MOMA, NREX, ODFT, ONDP, OTHR, SACC, SLRY, SVGS, TAXE, TRAN, TRAS, CC, PG, CD, CG, CI, PP]
Account type.
Split value. For PERCENTUAL: percentage (0-100). For ABSOLUTE: value in cents.
Responses
- 201
- 400
- 401
- 422
The split QR Code returned successfully.
- application/json
- Schema
- Example (from schema)
Schema
Split QR Code ID.
Associated key ID.
Possible values: [PENDING, READY, ERROR]
Split QR Code state.
User defined payment ID.
User defined payment description.
Expiration date to pay static QR Code. When it is false, expiration date is required.
Split QR Code created at.
{
"id": "9a1c2d3e-4f56-4789-8abc-def012345678",
"key_id": "f6e2e084-29b9-4935-a059-5473b13033aa",
"state": "PENDING",
"summary": "party-payment",
"description": "User defined description",
"expiration_date": "2026-03-27T20:36:28.663Z",
"created_at": "2026-03-27T20:36:28.663Z"
}
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.