# Status transitions and finalization

Learn about invoice status transitions and finalization.

The following graphic shows the different ways that an invoice can transition from status to status:

![](images/billing/invoice_states_diagram_simplified.svg)
Status transitions and finalization


## Transitions and endpoints 

The following table outlines the status transitions and their endpoints. It also lists the *webhooks* that are emitted by the endpoint, and the resulting status for each:

| Status          | API Endpoint                                                                                           | Emitted Webhook                | End Status      |
| --------------- | ------------------------------------------------------------------------------------------------------ | ------------------------------ | --------------- |
| `draft`         | [DELETE /v1/invoices/:id](https://docs.stripe.com/api/invoices/delete.md)                              | `invoice.deleted`              | (Deleted)       |
| `draft`         | [POST /v1/invoices/:id/finalize](https://docs.stripe.com/api/invoices/finalize.md)                     | `invoice.finalized`            | `open`          |
| `open`          | [POST /v1/invoices/:id/pay](https://docs.stripe.com/api/invoices/pay.md)                               | `invoice.paid`                 | `paid`          |
| `open`          | [POST /v1/invoices/:id/pay](https://docs.stripe.com/api/invoices/pay.md)                               | `invoice.payment_failed`       | `open`          |
| `open`          | [POST /v1/invoices/:id/send](https://docs.stripe.com/api/invoices/send.md)                             | `invoice.sent`                 | `open`          |
| `open`          | [POST /v1/invoices/:id/void](https://docs.stripe.com/api/invoices/void.md)                             | `invoice.voided`               | `void`          |
| `open`          | [POST /v1/invoices/:id/mark_uncollectible](https://docs.stripe.com/api/invoices/mark_uncollectible.md) | `invoice.marked_uncollectible` | `uncollectible` |
| `uncollectible` | [POST /v1/invoices/:id/pay](https://docs.stripe.com/api/invoices/pay.md)                               | `invoice.paid`                 | `paid`          |
| `uncollectible` | [POST /v1/invoices/:id/pay](https://docs.stripe.com/api/invoices/pay.md)                               | `invoice.payment_failed`       | `uncollectible` |
| `uncollectible` | [POST /v1/invoices/:id/void](https://docs.stripe.com/api/invoices/void.md)                             | `invoice.voided`               | `void`          |

[You can configure a longer grace period](https://docs.stripe.com/billing/subscriptions/usage-based/configure-grace-period.md).

## Post-finalization 

Finalizing an invoice does the following:

- It allows the invoice to be paid.
- It ensures that an invoice number is present.
- It makes certain properties [immutable](#immutable) on the invoice.
- It creates an incomplete payment intent for the invoice.
- It generates a unique URL where someone can pay the invoice, and a link to download a [PDF of the invoice](https://docs.stripe.com/api/invoices/object.md#invoice_object-invoice_pdf).

If an invoice isn’t finalized, you can’t collect payment.

### Finalized invoice restrictions 

After you finalize an invoice, you can’t change certain fields that pertain to the amount and customer. This is to satisfy the common tax-compliance requirement that finalized invoices be retained—as they were finalized—for a legally required minimum time period.

In some jurisdictions, editing fields that modify the total amount due on an invoice could render the invoice invalid. These are typically fields associated with your account, customer, line items, or taxes. It’s your responsibility to make sure that the invoices you create comply with all applicable laws.

If you require updates to the invoice amount after it finalizes, use [credit notes](https://docs.stripe.com/invoicing/dashboard/credit-notes.md). Credit notes allow you to modify the invoice amount by specifying an adjustment in money owed by the customer. You can issue credit notes for any invoice in an `open` or `paid` status. Finalizing the invoice copies the following customer fields to it and makes them immutable:

- [invoice.customer_address](https://docs.stripe.com/api/invoices/object.md#invoice_object-customer_address)
- [invoice.customer_email](https://docs.stripe.com/api/invoices/object.md#invoice_object-customer_email)
- [invoice.customer_name](https://docs.stripe.com/api/invoices/object.md#invoice_object-customer_name)
- [invoice.customer_phone](https://docs.stripe.com/api/invoices/object.md#invoice_object-customer_phone)
- [invoice.customer_shipping](https://docs.stripe.com/api/invoices/object.md#invoice_object-customer_shipping)
- [invoice.customer_tax_exempt](https://docs.stripe.com/api/invoices/object.md#invoice_object-customer_tax_exempt)
- [invoice.customer_tax_ids](https://docs.stripe.com/api/invoices/object.md#invoice_object-customer_tax_ids)

If you want to change a customer-related property on an invoice:

1. Void the current invoice.
1. [Duplicate](https://docs.stripe.com/invoicing/dashboard.md#modify-invoice) the voided invoice.
1. Update the customer information on the new invoice.

### Emails after finalization 

By default, Stripe automatically sends invoices when you set [collection_method](https://docs.stripe.com/api/invoices/object.md#invoice_object-collection_method) to `send_invoice`. Stripe doesn’t email invoices in the following cases:

- When [charged automatically](https://docs.stripe.com/invoicing/automatic-charging.md).
- When [automatic collection](https://docs.stripe.com/invoicing/integration/automatic-advancement-collection.md) is turned off for the invoice.
- When the [Email finalized invoices to customers](https://dashboard.stripe.com/settings/billing/automatic) option is turned off.

If you turn off the **Email finalized invoices to customers** option, automatic or manual finalization doesn’t send an invoice.

## Asynchronous payments 

For more details on using the *Payment Intents API* to complete *3D Secure* authentication, refer to the [3D Secure guide](https://docs.stripe.com/payments/3d-secure/authentication-flow.md#when-to-use-3d-secure).

Some payment methods require customer interaction to complete the payment—for example, a European card or bank transfer may require *Strong Customer Authentication* (SCA).

Use the invoice’s [payment_intent](https://docs.stripe.com/api/invoices/object.md#invoice_object-payment_intent) parameter to choose how to handle the response from the payment attempt, which may be either `success` or `requires_action`.

When the status of the PaymentIntent is `requires_action`, you must have your user complete a [3D Secure authentication](https://docs.stripe.com/billing/migration/strong-customer-authentication.md#scenario-4) to complete the payment.

Instead of building this yourself, you can rely on Stripe to handle it for you. [Enable reminder emails](https://dashboard.stripe.com/settings/billing/automatic) in the Dashboard so that Stripe can automatically send emails to your customers whenever `requires_action` occurs. These emails include a link to the [Hosted Invoice Page](https://docs.stripe.com/invoicing/hosted-invoice-page.md), where a customer can perform all of the actions required to pay the invoice. To learn more about these emails and how to customize them, see [Sending email reminders](https://docs.stripe.com/invoicing/send-email.md).