Default notifications
Understand the default notifications
When you register a customer, Asaas automatically creates a set of notifications to follow the charge lifecycle.
Each notification has its own id and can later be configured to change channels, recipients or sending time.
Automatically created notifications
By default, all of them are created with enabled: true and deleted: false.
WhatsApp is disabled in all initial settings.
| Notification | event | scheduleOffset | Default sending |
|---|---|---|---|
| Charge created | PAYMENT_CREATED | 0 | Customer: email and SMS |
| Due date | PAYMENT_DUEDATE_WARNING | 0 | Customer: email and SMS |
| Charge received | PAYMENT_RECEIVED | 0 | Customer: email and SMS; provider: email |
| Digitable line on the due date | SEND_LINHA_DIGITAVEL | 0 | Customer: email and SMS |
| Charge overdue | PAYMENT_OVERDUE | 0 | Customer: email, SMS and phone call; provider: email |
| 7 days after the due date | PAYMENT_OVERDUE | 7 | Customer: email, SMS and phone call |
| 10 days before the due date | PAYMENT_DUEDATE_WARNING | 10 | Customer: email and SMS |
| Charge updated | PAYMENT_UPDATED | 0 | Customer: email and SMS |
Charge created
PAYMENT_CREATED is sent when the charge is created, except for charges generated by subscriptions.
Digitable line
SEND_LINHA_DIGITAVEL is sent on the due date when the invoice or bank slip (boleto) has not yet been viewed by the customer.
Charge updated
PAYMENT_UPDATED is sent when the amount or the due date of the charge is changed.
Understand scheduleOffset
scheduleOffsetThe same event can have more than one notification.
For example, PAYMENT_DUEDATE_WARNING is created with:
scheduleOffset: 0for the due date;scheduleOffset: 10for 10 days before the due date.
The same applies to PAYMENT_OVERDUE:
scheduleOffset: 0for the notice when the charge becomes overdue without payment;scheduleOffset: 7for the periodic notice after the due date while the charge remains unpaid.
Each configuration has its own id, even when it uses the same event.
Example:
{
"object": "notification",
"id": "not_EDaloT543tss",
"customer": "cus_Y4AEif5zrMGK",
"enabled": true,
"emailEnabledForProvider": false,
"smsEnabledForProvider": false,
"emailEnabledForCustomer": true,
"smsEnabledForCustomer": true,
"phoneCallEnabledForCustomer": true,
"whatsappEnabledForCustomer": false,
"event": "PAYMENT_OVERDUE",
"scheduleOffset": 7,
"deleted": false
}Retrieve the customer's notifications
The IDs shown on this page are examples. Retrieve the customer's notifications to obtain the identifiers created for them:
GET /v3/customers/{id}/notificationsSee the Retrieve notifications from a customer endpoint.
Notifications are created by Asaas and have a fixed structure. You can change the existing settings, but you cannot create or delete notification types through the API.
To customize channels, recipients or sending time, see Changing notifications of a customer.
Next steps
Updated 13 days ago
