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.

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.

Last updated