Authorizations

The authorization object and the allowed CRUD operations on the related resource endpoint

When an order is placed a successful authorization transaction is created and the order's payment status becomes authorized (except for async payments, i.e. Stripe)

Fetching an authorization returns all the information and messages provided by the payment gateway. You can update an authorization to capture or void it.

If an authorization gets stuck (for any reason) on our platform but succeeds on the payment gateway, you can unblock 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 by passing the _cancel trigger attribute.

Data model

Check the related ER diagram and explore the flowchart that illustrates how the authorization resource relates to the order and the other transaction APIs.

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.).