walkOrders iterates pages using the server cursor.
listAllOrders collects available pages where the application requires the full result.
For direct API pagination, start with an explicit empty cursor query parameter.
Preserve each returned nextCursor unchanged.
Verify that the installed SDK sends this parameter when starting cursor pagination.
Remove repeated rows by orderId.
See order pagination for the stopping condition and legacy behavior.
Keep upstream, Infinity Hub, and on-chain identifiers as distinct fields.
Use onchainOrderId for contract observation and refund helpers.
Do not infer an order’s contract identifier from an unrelated transaction hash.
Display state
Display actual source spend and destination output evidence. Separate destination delivery from origin settlement. UseisChainOnlyStatus, statusOutcome, or chainStatusOutcome where supported by the client.
Do not require upstream history when upstreamUnavailable is true.
History rows preserve the initial upstream state.
Use lifecycle and chain.status for current progress.
Infinity Hub’s status endpoint remains at CREATED for openFor orders.
Use upstream status with its chain projection or the on-chain fill view instead.
The API’s chain projection can include refund eligibility and an extended deadline.
Pass the effective deadline into refund checks where the helper supports it.
Confirm escrow state before sending a refund.