Create a Dynamic Charge with Due Date
Use this endpoint to create a due date Pix collection (cobrança com vencimento) with complex payment rules including fines, interest, discounts, and rebates.
Notes:
- Similar to traditional boletos with Pix payment capability
- Due date defines when payment is expected
- Supports complex amount calculations with fines, interest, discounts, and rebates
- Requires complete debtor and receiver information
- Transaction ID (txId) must be unique across all collections
- Collection remains valid for a configurable period after the due date
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
Account ID (UUID format)
Body
Amount is the amount configuration object (required)
Debtor is the debtor information (required)
DueDate is the due date for the collection in format YYYY-MM-DD (ISO8601)
"2024-12-31"
Pix key that will receive the payment
"+5511999999999"
TxID is the unique transaction identifier for this collection
"TXabcdefghijklmno123456789"
ValidAfterDue is the number of days after the due date that the collection remains valid
x >= 05
AdditionalInfo is a key-value map for additional information
{ "customerId": "67890", "orderId": "12345" }Description is a custom message or description for the collection
"Payment for order #12345"
LocationInformation contains merchant location data for QR code generation
Metadata is an optional map for custom key-value pairs (max 50 keys)
Tags is an array of custom tags for categorization
["ecommerce", "subscription"]Response
Created
AdditionalInfo is a key-value map for additional information (optional)
{ "customerId": "67890", "orderId": "12345" }Amount is the amount configuration object (required)
CreatedAt is the timestamp when the collection was created (required)
"2024-01-15T10:30:00Z"
Debtor is the debtor information (required)
DeletedAt is the timestamp when the collection was deleted (optional, nullable)
"2024-01-25T10:30:00Z"
Description is the custom description of the collection (optional)
"Payment for order #12345"
DueDate is the due date for the collection in format YYYY-MM-DD (required)
"2024-12-31"
EMV is the QR code payload in EMV format (required)
"00020126580014br.gov.bcb.pix..."
ID is the unique identifier of the collection (required)
"550e8400-e29b-41d4-a716-446655440010"
LocationURL is the URL to access the collection location/QR code (required)
"https://api.example.com/qr/550e8400"
Metadata is the custom metadata associated with this collection
Receiver is the receiver information (required)
Pix key that will receive the payment
"+5511999999999"
Review is the revision number of the collection (required)
0
Status is the current status of the collection (required) Valid values: ACTIVE, COMPLETED, REMOVED_BY_RECEIVER, REMOVED_BY_PSP
"ACTIVE"
Tags is an array of custom tags (optional)
["ecommerce", "subscription"]TxID is the transaction identifier (required)
"TXabcdefghijklmno123456789"
UpdatedAt is the timestamp of the last update (required)
"2024-01-20T14:45:00Z"
ValidAfterDue is the number of days after the due date that the collection remains valid (required)
5

