Skip to main content
POST
Create a Dynamic Charge with Due Date

Autorizações

Authorization
string
header
obrigatório

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Cabeçalhos

X-Account-Id
string
obrigatório

Account ID (UUID format)

Corpo

application/json
amount
object
obrigatório

Amount is the amount configuration object (required)

debtor
object
obrigatório

Debtor is the debtor information (required)

dueDate
string
obrigatório

DueDate is the due date for the collection in format YYYY-MM-DD (ISO8601)

Exemplo:

"2024-12-31"

receiverKey
string
obrigatório

Pix key that will receive the payment

Exemplo:

"+5511999999999"

txId
string
obrigatório

TxID is the unique transaction identifier for this collection

Exemplo:

"TXabcdefghijklmno123456789"

validAfterDue
integer
obrigatório

ValidAfterDue is the number of days after the due date that the collection remains valid

Intervalo obrigatório: x >= 0
Exemplo:

5

additionalInfo
object

AdditionalInfo is a key-value map for additional information

Exemplo:
description
string

Description is a custom message or description for the collection

Exemplo:

"Payment for order #12345"

locationInformation
object

LocationInformation contains merchant location data for QR code generation

metadata
object

Metadata is an optional map for custom key-value pairs (max 50 keys)

tags
string[]

Tags is an array of custom tags for categorization

Exemplo:

Resposta

Created

additionalInfo
object

AdditionalInfo is a key-value map for additional information (optional)

Exemplo:
amount
object

Amount is the amount configuration object (required)

createdAt
string

CreatedAt is the timestamp when the collection was created (required)

Exemplo:

"2024-01-15T10:30:00Z"

debtor
object

Debtor is the debtor information (required)

deletedAt
string

DeletedAt is the timestamp when the collection was deleted (optional, nullable)

Exemplo:

"2024-01-25T10:30:00Z"

description
string

Description is the custom description of the collection (optional)

Exemplo:

"Payment for order #12345"

dueDate
string

DueDate is the due date for the collection in format YYYY-MM-DD (required)

Exemplo:

"2024-12-31"

emv
string

EMV is the QR code payload in EMV format (required)

Exemplo:

"00020126580014br.gov.bcb.pix..."

id
string

ID is the unique identifier of the collection (required)

Exemplo:

"550e8400-e29b-41d4-a716-446655440010"

locationUrl
string

LocationURL is the URL to access the collection location/QR code (required)

Exemplo:

"https://api.example.com/qr/550e8400"

metadata
object

Metadata is the custom metadata associated with this collection

receiver
object

Receiver is the receiver information (required)

receiverKey
string

Pix key that will receive the payment

Exemplo:

"+5511999999999"

review
integer

Review is the revision number of the collection (required)

Exemplo:

0

status
string

Status is the current status of the collection (required) Valid values: ACTIVE, COMPLETED, REMOVED_BY_RECEIVER, REMOVED_BY_PSP

Exemplo:

"ACTIVE"

tags
string[]

Tags is an array of custom tags (optional)

Exemplo:
txId
string

TxID is the transaction identifier (required)

Exemplo:

"TXabcdefghijklmno123456789"

updatedAt
string

UpdatedAt is the timestamp of the last update (required)

Exemplo:

"2024-01-20T14:45:00Z"

validAfterDue
integer

ValidAfterDue is the number of days after the due date that the collection remains valid (required)

Exemplo:

5