---
title: Review Webhook Events
url: https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-events
applies_to: Advanced Billing
updated: 2026-10-12
---

# Review Webhook Events

Webhook events are triggered by key actions and changes within Advanced Billing, providing notifications about billing, Subscription, payment, and account activity. Each event carries a structured payload with the relevant data, so you can automate workflows, synchronize systems, or log activity for auditing and analysis.

## How events map to actions

A single system event can trigger more than one webhook event. Creating a new Subscription, for example, typically fires both `signup_success` and `payment_success`, if a payment was necessary to start the Subscription.

Which events appear for your site depends on how it is configured. Some events only show up once a related feature is enabled, such as `proforma_invoice_issued` on Relationship Invoicing sites or `prepaid_subscription_balance_changed` on sites using prepaid Subscriptions. The definitive list for your own site is the checkbox list under **Config** > **Settings** > **Webhooks**.

## Event reference

Every event Advanced Billing can send, with what triggers it and the payload it carries.

| Event key | Trigger | Payload |
| :--- | :--- | :--- |
| `allocation_change` | The legacy name for `component_allocation_change`, used on sites with productless subscriptions disabled. Same trigger and payload shape as `component_allocation_change`, below. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#component_allocation_change-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>Same keys as `component_allocation_change` |
| `billing_date_change` | Any change to the billing date initiated explicitly by altering the billing date through the application or the API. Not triggered by a normal renewal and period advancement, or by a migration. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#billing_date_change-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription` (with `previous_billing_date`)<br>The `subscription` object also contains information on the Customer and Product. |
| `chjs_tokenization_failure` | A Maxio.js tokenization attempt fails, for example when the card is declined. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#chjs_tokenization_failure-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `errors`, `payment_profile_params` |
| `chjs_tokenization_success` | Maxio.js successfully tokenizes a payment method on your own page. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#chjs_tokenization_success-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `payment_profile`, `gateway_customer_id` |
| `component_allocation_change` | Any change to a Subscription's quantity-based component allocation, to the enabled status of an on/off component, or a purchase of a prepaid component allocation, made *after* signup.<br>This webhook does not fire if allocations are configured during the initial Subscription creation. It only fires for subsequent changes.<br>`previous_allocation` and `new_allocation` give the allocation values before and after the change. For on/off components these are `0` or `1`, representing *off* and *on*.<br>`timestamp` is the date and time the allocation was recorded, in <a href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank" rel="noopener noreferrer">ISO 8601</a> format in UTC. This format differs from the timestamps in older event types and represents the direction for webhook timestamps. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#component_allocation_change-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `component`, `subscription`, `product`, `previous_allocation`, `new_allocation`, `memo`, `timestamp` |
| `custom_field_value_change` | A change to any custom field value, whether adding a custom field at signup or updating one on an existing Subscription or Customer record. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#custom_field_value_change-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `metafield` |
| `customer_create` | A new Customer is created. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#customer_create-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `customer` |
| `customer_delete` | A Customer is deleted.<br>Not triggered by deleting a Subscription and Customer simultaneously. It fires only when the Customer is deleted as a single action. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#customer_delete-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `customer` |
| `customer_update` | Any change to the following Customer fields: `first_name`, `last_name`, `organization`, `email`, `reference`, `address`, `address_2`, `city`, `state`, `zip`, `country`, `phone`, `vat_number`, `parent_id`, `cc_emails`, `business_type`. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#customer_update-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `customer` |
| `delayed_signup_creation_failure` | A delayed Subscription fails to be created. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#delayed_signup_creation_failure-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription` |
| `delayed_signup_creation_success` | A delayed Subscription is created successfully in an awaiting-signup state. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#delayed_signup_creation_success-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription` |
| `direct_debit_payment_paid_out` | A Direct Debit payment is successfully processed in the gateway. Currently supported for Maxio Payments, Stripe, and GoCardless. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#direct_debit_payment_paid_out-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `transaction` |
| `direct_debit_payment_pending` | A Direct Debit payment is created in the gateway and is waiting to be processed. Currently supported for Maxio Payments, Stripe, and GoCardless. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#direct_debit_payment_pending-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `transaction` |
| `direct_debit_payment_rejected` | A Direct Debit payment is rejected in the gateway, for example for insufficient funds on the Customer account. Currently supported for Maxio Payments, Stripe, and GoCardless. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#direct_debit_payment_rejected-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `transaction` |
| `dunning_step_reached` | A Subscription reaches any step of the dunning process. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#dunning_step_reached-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `product`, `dunner`, `current_step`, `next_step` |
| `expiration_date_change` | Any change to an existing `expiration_date` for a Subscription. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#expiration_date_change-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription` (with `previous_expires_at`) |
| `expiring_card` | A periodic event sent on the 1st, on the 15th, and 7 days before the end of the month. It identifies all cards expiring in the current month. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#expiring_card-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`<br>The `subscription` object also contains information on the Customer and Product. |
| `invoice_issued` | An Invoice is issued against a Subscription on a Relationship Invoicing site. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#invoice_issued-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `invoice`, `message`<br>The `subscription` object also contains information on the Customer and Product. |
| `invoice_pending` | An Invoice transitions into the `pending` state. Available on Relationship Invoicing sites. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#invoice_pending-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `invoice`, `customer`, `subscription` (if applicable), `previous_state`, `new_state`, `timestamp` |
| `item_price_point_changed` | A Subscription's price point changes for a Product or Component. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#item_price_point_changed-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `subscription_id`, `item_id`, `item_type`, `item_name`, `item_handle`, `previous_price_point`, `current_price_point`, `origin`, `acting_user_id`, `acting_user_type`<br>`origin`, `acting_user_id`, and `acting_user_type` are included only when the change is made through custom pricing, including when a Subscription is created with segment-level custom pricing. Other price point changes, such as a Product change or a renewal, don't include them.<br>`origin` is `api` for a change made through the API and `ui` otherwise. `acting_user_id` is the id of the record that made the change, and `acting_user_type` is `User`, `ApiUser`, or `Site` (a site-level API key), which tells you which kind of record the id belongs to. |
| `metered_usage` | Any reported usage for a Subscription's metered components.<br>Does not fire when the unit balance is reset to `0` at renewal.<br>`timestamp` is the date and time the usage was recorded, in <a href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank" rel="noopener noreferrer">ISO 8601</a> format in UTC. This format differs from the timestamps in older event types. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#metered_usage-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `component`, `subscription`, `product`, `previous_unit_balance`, `new_unit_balance`, `usage_quantity`, `memo`, `timestamp` |
| `payment_failure` | Any failed payment attempt.<br>`payment_success` or `payment_failure` is triggered for *every* payment attempted, whether for a normal renewal, a one-time charge, a retry after failure, or a payment applied to an Invoice.<br>In some cases the payment fails later, most commonly with ACH/eCheck and Direct Debit. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#payment_failure-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `transaction` |
| `payment_not_attempted` | Advanced Billing tries to collect from a Subscription and finds no payment method on it at all, so no gateway was ever contacted. Covers a periodic renewal, a dunning retry, a component allocation, a reactivation, a one-time charge, and a payment applied to an Invoice.<br>This is distinct from `payment_failure`, which means a gateway was contacted and declined the attempt. A missing payment method never generates `payment_failure`, so an integration that reacts to `payment_failure` by asking the Customer to update their card does not fire for this case.<br>Opt-in per endpoint: subscribing to this event does not change what any existing endpoint receives. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#payment_not_attempted-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `reason`, `amount_in_cents`, `currency`, `memo`, `account_transaction_id`<br>`reason` is `no_payment_method`. `account_transaction_id` is `null` when the attempt was rolled back, for example a refused reactivation. |
| `payment_success` | Any payment attempt that does not result in an immediate failure.<br>`payment_success` or `payment_failure` is triggered for *every* payment attempted, whether for a normal renewal, a one-time charge, a retry after failure, or a payment applied to an Invoice.<br>In some cases the payment fails later, most commonly with ACH/eCheck and Direct Debit. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#payment_success-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `transaction` |
| `pending_cancellation_change` | A Subscription is canceled with delay (cancel at end of period), or a delayed pending cancellation is cleared. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#pending_cancellation_change-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `cancellation_state`, `cancels_at`<br>The `subscription` object also contains information on the Customer and Product. |
| `prepaid_subscription_balance_changed` | Any change to a prepaid Subscription's usage or prepayment balance. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#prepaid_subscription_balance_changed-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `prepaid_configuration`, `customer`, `product`, `product_family`, `credit_card`, `group` |
| `prepaid_usage` | Any recorded usage for a Subscription's prepaid component.<br>Changes in allocation are reflected in a `component_allocation_change` webhook instead. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#prepaid_usage-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `component`, `subscription`, `product`, `previous_unit_balance`, `usage_quantity`, `previous_overage_unit_balance`, `new_overage_unit_balance`, `overage_usage_quantity`, `price_point_id` |
| `proforma_invoice_issued` | A proforma Invoice is issued for a Subscription. Available on Relationship Invoicing sites. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#proforma_invoice_issued-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `proforma_invoice`, `message` |
| `refund_failure` | A refund attempt fails, or a previously successful refund is later reversed by the bank, for example when the Customer's own bank rejects the returned funds after the fact. For a reversal, `errors` carries "Refund was reversed by the bank" as its first entry, followed by a reason if one was given. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#refund_failure-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `subscription_id`, `amount_in_cents`, `customer_id`, `customer_email`, `customer_name`, `customer_reference`, `errors`, `gateway_transaction_id`, `gateway_order_id`, `gateway_used`, `masked_card_number`, `memo`, `payment_amount_in_cents`, `payment_id`, `timestamp`, `currency` |
| `refund_success` | A refund is processed successfully. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#refund_success-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `subscription_id`, `refund_id`, `amount_in_cents`, `customer_id`, `customer_email`, `customer_name`, `customer_reference`, `gateway_transaction_id`, `gateway_order_id`, `gateway_used`, `masked_card_number`, `memo`, `payment_amount_in_cents`, `payment_id`, `timestamp`, `currency` |
| `renewal_failure` | A failed periodic renewal, for example a declined credit card.<br>At the end of every recurring interval, *either* `renewal_success` *or* `renewal_failure` is triggered once. If a card is declined and `renewal_failure` is triggered, a subsequent payment that brings the account current does *not* generate a `renewal_success`, although it does generate a `payment_success` and a `subscription_state_change`. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#renewal_failure-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `transaction`<br>The `subscription` object also contains information on the Customer and Product. |
| `renewal_success` | A successful periodic renewal.<br>At the end of every recurring interval, *either* `renewal_success` *or* `renewal_failure` is triggered once. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#renewal_success-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `transaction` |
| `signup_failure` | Any failed signup, where a Subscription fails to begin, through the API, the application, or Public Pages.<br>Usually caused by a failure at the payment gateway. Not generated for input validation errors, such as leaving a field blank. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#signup_failure-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`<br>The `subscription` object also contains information on the Customer and Product. |
| `signup_success` | Any successful signup, where a Subscription is created, through the API, the application, or Public Pages. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#signup_success-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`<br>The `subscription` object also contains information on the Customer and Product.<br>Component allocations are not included in the `signup_success` webhook. |
| `statement_closed` | A statement closes at the end of a period without payment being successfully received. See [Statement events](https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-events#statement-events). | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#statement_closed-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `customer`, `statement`, `product`, `product_family`, `payment_profile` |
| `statement_settled` | A statement closes at the end of a period and payment was successfully received, or was not required. See [Statement events](https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-events#statement-events). | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#statement_settled-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `customer`, `statement`, `product`, `product_family`, `payment_profile` |
| `subscription_bank_account_update` | A Subscription adds or updates a bank account. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#subscription_bank_account_update-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `product`, `previous_payment_profile`, `updated_payment_profile`, `customer` |
| `subscription_card_update` | Any change to the active credit card Payment Profile, including partial card and billing address updates.<br>Bank account and ACH Payment Profile changes and deletions generate a `subscription_bank_account_update` webhook instead, not this one.<br>Additions and deletions of PayPal Payment Profiles do not generate any webhook. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#subscription_card_update-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `product`, `previous_payment_profile`, `updated_payment_profile`, `customer` |
| `subscription_group_card_update` | Any change to the active credit card Payment Profile on a Subscription group. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#subscription_group_card_update-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription_group`, `previous_payment_profile`, `updated_payment_profile`, `customer` |
| `subscription_group_signup_failure` | A Subscription group signup fails through the <a href="https://developers.maxio.com/http/advanced-billing-api/api-endpoints/subscription-groups/signup-with-subscription-group" target="_blank" rel="noopener noreferrer">Subscription Group Signup</a> endpoint. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#subscription_group_signup_failure-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription_group`, `customer` |
| `subscription_group_signup_success` | A Subscription group signup succeeds through the <a href="https://developers.maxio.com/http/advanced-billing-api/api-endpoints/subscription-groups/signup-with-subscription-group" target="_blank" rel="noopener noreferrer">Subscription Group Signup</a> endpoint. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#subscription_group_signup_success-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription_group`, `customer` |
| `subscription_plan_change` | The legacy name for `subscription_product_change`, used on sites with productless subscriptions disabled. Same trigger and payload shape as `subscription_product_change`, below. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#subscription_product_change-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>Same keys as `subscription_product_change` |
| `subscription_plan_change_scheduled` | The legacy name for `subscription_product_change_scheduled`, used on sites with productless subscriptions disabled. Same trigger and payload shape as `subscription_product_change_scheduled`, below. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#subscription_product_change_scheduled-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>Same keys as `subscription_product_change_scheduled` |
| `subscription_prepayment_account_balance_changed` | A Subscription prepayment account balance changes. This happens when a prepayment is applied to a Subscription, increasing the balance, or when a prepayment is used to pay an Invoice, decreasing it. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#subscription_prepayment_account_balance_changed-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `transactions` |
| `subscription_product_change` | A successful change from an old Product to a new Product for a Subscription. Also fires for a Product version change. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#subscription_product_change-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `previous_product`, `subscription`<br>The `subscription` object also contains information on the Customer and Product. |
| `subscription_product_change_scheduled` | A delayed Product change is scheduled for a Subscription, taking effect at the Subscription's next renewal rather than immediately. The webhook fires as soon as the scheduled change is created, so you can react to an upcoming Product change ahead of renewal instead of waiting for `subscription_product_change`. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#subscription_product_change_scheduled-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `current_product`, `scheduled_product`, `effective_at`<br>`current_product` is the Subscription's Product today; `scheduled_product` is the Product it changes to at `effective_at`. |
| `subscription_service_credit_account_balance_changed` | Any change to a Subscription's service credit account balance. This happens when a service credit is applied to a Subscription, increasing the balance, or when a service credit is used to pay an Invoice, decreasing it. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#subscription_service_credit_account_balance_changed-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `service_credits`, `event_specific_data` |
| `subscription_state_change` | Any change to the Subscription state. This is the workhorse of the events. Watching it tells you when a Subscription moves into a bad state, such as `past_due`. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#subscription_state_change-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`<br>The `subscription` object also contains information on the Customer and Product.<br>The `subscription` object carries keys for both `previous_state` and `state`, so you can track the change. |
| `three_ds_authentication_failure` | A 3D Secure authentication attempt fails during signup on a Public Signup Page. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#three_ds_authentication_failure-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `public_signup_page_id`, `gateway`, `reason`, `customer_email`, `customer_reference` |
| `trial_end_notice` | A notice is sent ahead of a Subscription's trial ending. Shares the same payload shape as `upcoming_renewal_notice`. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#trial_end_notice-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `customer`, `email_sent`, `estimated_renewal_amount_in_cents`, `message`, `payment_profile`, `product`, `subscription` (condensed) |
| `upcoming_renewal_notice` | A notice is sent ahead of a Subscription renewing. By default this is 3 days before renewal, configurable in **Config** > **Settings** > **Emails** with the **Number of days to notify customers before the invoice issue date** field. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#upcoming_renewal_notice-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `customer`, `email_sent`, `estimated_renewal_amount_in_cents`, `message`, `payment_profile`, `product`, `subscription` (condensed) |
| `upgrade_downgrade_failure` | Any failed upgrade or downgrade. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#upgrade_downgrade_failure-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `target_product`<br>The `subscription` object also contains information on the Customer and Product. |
| `upgrade_downgrade_success` | Any successful upgrade or downgrade. | <a href="https://docs.maxio.com/configuration/advanced-billing/webhooks/review-webhook-payload-examples#upgrade_downgrade_success-payload" target="_blank" rel="noopener noreferrer">Payload example</a><br>`event_id`, `site`, `subscription`, `previous_product`<br>The `subscription` object also contains information on the Customer and Product. |

## Statement events

At the end of every period, such as at renewal, either a `statement_closed` or a `statement_settled` webhook is triggered. `statement_settled` means the statement closed and payment was successfully received, or payment was not required. `statement_closed` means the statement closed but payment was not successfully received.

The two are not mutually exclusive over time. If you receive a `statement_closed` webhook for statement #3, you also receive a `statement_settled` webhook for statement #3 later if that statement becomes paid, for example after a dunning retry or a card update.

## Payloads

The resource objects sent as payloads typically contain the same information as the corresponding API resource. Site payload objects include the site's `id` and `subdomain`.