API
Cancel order
Cancel an aggregator order and, when supported by the payment processor, refund the payment.
POST
Cancels an order previously created through Inject order. Fire looks up the order by
account and order_uid, updates the order to CANCELED, and returns the updated order in the standard API envelope.
If the stored payment processor supports refunds (for example, Deuna), Fire attempts the refund and sets payment_status to REFUNDED on success. For other processors, Fire cancels the payment state and sets payment_status to CANCELED.
Bearer token obtained from POST /login. Format:
Bearer <accessToken>.Your Fire API key.
Must be
integration. Identifies the request as coming from an external integration.Account identifier used to find the order.
Use
application/json for the request body.UID of the order to cancel.
Reason for the cancellation or refund request.
Optional. UID of the payment method used to resolve refund credentials when you need to target a specific method.
Vendor UID used to resolve payment credentials.
Customer email sent to the payment processor when required.
Registered customer UID. When present, Fire treats the refund payload as authenticated.
Anonymous customer UID. Used as the payment user identifier when
customer_uid is not present.Store UID used to resolve store-specific payment credentials.
Sales medium used to resolve credentials. Supported values:
APP, WEB.Updated order. Prices in
order_lines, totals, and payment_methods are returned as external, unscaled amounts.HTTP status code from the API envelope.
Trace identifier for support and debugging.
Processing rules
- When provided,
payment_method_uidhelps resolve credentials, but Fire evaluates the payment methods stored on the order. - For Deuna refunds, the order must include
metadata.order_token; otherwise Fire returns400. - After saving the updated order, Fire returns prices transformed for external consumption.
- Fire notifies the cancellation downstream after the order is saved.

