# Authorizations

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

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

If an authorization gets stuck (for any reason) on our platform but succeeds on the payment gateway, you can [unblock](/core-api-reference/transactions.md#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](/core-api-reference/transactions.md#cancelling-transactions) by passing the `_cancel` trigger attribute.

<details>

<summary>Data model</summary>

Check the related [ER diagram](/data-model/orders/orders-management.md) 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 %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.commercelayer.io/core-api-reference/authorizations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.