# Authorizations

When an [order](https://docs.commercelayer.io/core-api-reference/orders) is placed a successful authorization transaction is created and the order's payment status becomes `authorized` (except for async payments, i.e. [Stripe](https://docs.commercelayer.io/core-api-reference/stripe_payments))

Fetching an authorization returns all the information and messages provided by the [payment gateway](https://docs.commercelayer.io/core-api-reference/payment_gateways). You can update an authorization to [capture](https://docs.commercelayer.io/core-api-reference/captures) or [void](https://docs.commercelayer.io/core-api-reference/voids) it.

If an authorization gets stuck (for any reason) on our platform but succeeds on the payment gateway, you can [unblock](https://docs.commercelayer.io/core-api-reference/transactions#unblocking-stuck-transactions) it by passing the `_forward` trigger attribute. In this case, the associated order is also placed at the end of the forwarding process, to avoid any possible modifications.

If an authorization associated with a still pending order succeeded and the order is updated (introducing an amount mismatch scenario), you can [reset the transaction](https://docs.commercelayer.io/core-api-reference/transactions#cancelling-transactions) by passing the `_cancel` trigger attribute.

<details>

<summary>Data model</summary>

Check the related [ER diagram](https://commercelayer.io/docs/data-model/orders-management) and explore the flowchart that illustrates how the authorization resource relates to the order and the other transaction APIs.

</details>

{% hint style="info" %}
Create and delete operations are not allowed on this endpoint. You can only fetch a list of authorization or a specific single one, which can also be updated in order to mark it as succeeded, pass specific trigger attributes, or add/change common attributes (metadata, references, etc.).
{% endhint %}