Payment and Order statuses serve as operational state indicators. They provide visibility into the progression of a transaction but do not independently trigger automated system behaviour.
The behavior of checkout and payment orchestration depends on the payment model configured for the marketplace and the call-to-action (CTA) defined in the buyer journey.
| Status Type | Examples | Behaviour |
|---|---|---|
| PaymentStatus | WaitingForPayment, Paid, Refunded | Represents financial state progression. |
| FulfilmentStatus | Created, Acknowledged, Shipped, Delivered | Represents operational state after payment confirmation. |
| Note: Neither status advances automatically. All changes to financial components or payment states must be updated explicitly via API or gateway callbacks, including when integrating external payment or fulfilment systems. |
Arcadier provides controlled endpoints that allow modification of specific order-level attributes, subject to role-based authorization. These APIs allow updates to:
- Freight (shipping charges), Discount Amount, Surcharge, PaymentStatus
Merchant-level updates: Authenticated merchants can update Orders they own (freight, discount, surcharge, PaymentStatus). A Merchant may only update Orders associated with their own merchant account. Cross-merchant updates are not permitted.
Admin-level updates: Authenticated admin tokens allow updates across any merchant's Orders within the marketplace, including bulk updates across multiple merchants simultaneously.