Endpoint responsible for updating a charge already created in Asaas.

Updates are only allowed for charges that are still awaiting payment or are already overdue. After creation, it is not possible to change the customer to whom the charge belongs.

Request parameter

• id — Unique identifier of the charge in Asaas

Main request parameters

Fields that can be updated include:

• billingType
• value
• dueDate
• description
• daysAfterDueDateToRegistrationCancellation
• externalReference
• discount
• interest
• fine
• postalService
• split
• callback

Important rule regarding the charge customer

Once created, the charge remains linked to the original customer.

If the payer needs to be changed, the correct strategy is to create a new charge for the correct customer instead of trying to reuse the previous one.

Split update after charge confirmation

Updating split follows specific rules when the charge has already been confirmed.

This change is only allowed for charges made with credit card or debit card, provided that:

• the charge has the CONFIRMED status
• the charge has not been anticipated
• the change occurs up to 1 business day before the expected payment date

There is an exception when there is a block due to split mismatch at the time of receipt. In that case, updating the split will be allowed for charges with CONFIRMED or RECEIVED status, including when anticipation exists.

However, in this scenario, no field other than split may be changed.

Automatic anticipation with fixed split

In cases of automatic anticipation with split configured by fixed amount when the charge is issued, the split calculation will consider the highest fee applicable to the card used.

This behavior must be taken into account in integrations that reconcile net amounts between multiple recipients.