View as Markdown↗

Order lifecycle

Every order moves through a predictable sequence of statuses as it progresses from creation to payment completion. Understanding these transitions helps you build accurate UI states and debug payment flows with confidence.

Use MCP to investigate order state

An authenticated AI agent can inspect live order state, compare recent orders, show governed order analytics, or render an order card while you debug lifecycle questions.

MCP tools: list_orders, get_order, get_order_analytics or render_order_card

Status transitions

Orders and payments have separate state. Read both after every operation; do not infer one from the other.

Stage	Order	Payment	Next action
Draft or finalized	Inttegro.OrderStatuses.Preparing	Inttegro.PaymentStatuses.RequiresAction	Inttegro.PaymentNextActionTypes.Execute
Payment started	Inttegro.OrderStatuses.RequiresPayment	Inttegro.PaymentStatuses.RequiresAction	Inttegro.PaymentNextActionTypes.ConfirmPayment
OTP confirmed	Inttegro.OrderStatuses.RequiresPayment	Inttegro.PaymentStatuses.RequiresAction	Inttegro.PaymentNextActionTypes.AuthorizePayment
Payment successful	Inttegro.OrderStatuses.Paid	Inttegro.PaymentStatuses.Paid	null
Fulfilled	Inttegro.OrderStatuses.Completed	Inttegro.PaymentStatuses.Paid	null

Move the order forward

Create and finalize

Call Create an order. A draft order has no hosted invoice. Set finalize to true to seal it and generate the invoice, or finalize it later. Before payment starts, use Update an order to replace mutable details.

Start payment

Call Pay for an order, or set

executePayment to

true

during creation. When confirmation is required, collect the OTP and call Confirm a payment.

• Read payment.nextAction.type to decide what the customer must do next.
• Use payment.nextAction.confirmPayment.expiresAt for the OTP countdown.
• After confirmation, wait for provider authorization and continue polling Look up an order.
• Fulfill only when status is Inttegro.OrderStatuses.Paid.

Complete fulfillment

After delivering the goods or service, call Complete an order. The order moves from

Inttegro.OrderStatuses.Paid

to Inttegro.OrderStatuses.Completed

. Completion is terminal.

Handle other outcomes

• If payment.status is Inttegro.PaymentStatuses.Failed, show the failure and let the customer retry. The order normally remains Inttegro.OrderStatuses.RequiresPayment.
• A canceled order has status set to Inttegro.OrderStatuses.Canceled and cannot restart payment.
• An expired order has status set to Inttegro.OrderStatuses.Expired. Create a new order instead of reviving stale prices or inventory decisions.

Related resources

• Orders API - Complete order endpoint documentation
• Accept a payment - Step-by-step payment guide with code examples
• Product: Orders - High-level overview of the Orders API