ormuz
Home/Integrations/Mondu/Nodes/Get order (Mondu)
MonduRouteurStable

Get order (Mondu)

Retrieves the Mondu state of an Ormuz order and routes the process to the corresponding branch.

Vue d’ensemble

Get order (Mondu) retrieves the current Mondu state using only the platform.order used at creation.

Use it after a delay, after a Mondu event, or before an operation that depends on order authorization or confirmation.

  • The designer supplies only the Ormuz order.
  • Retrieval modifies neither the Ormuz order nor the Mondu order.
  • If no unique Mondu order matches this order, the node fails explicitly.

Typical scenario

A process retrieves an order still pending. When Mondu returns authorized, the process moves to commercial confirmation.

Quick start

Link the Ormuz order used during Mondu creation.

Terms

  • Same Mondu configuration as at creation
  • Same order.id as in the financing request
Configuration example
ParameterBindingRole
orderorderTracked Ormuz order
Key point Always use the original Ormuz order; do not ask the designer to provide a separate Mondu identifier.

Decision routes

authorization_required

Autorisation acheteur requise

Mondu is still waiting for buyer action or validation before returning a usable decision.

Recommended actionKeep the order pending and start or continue the configured authorization journey.
authorized

Order authorized

Mondu authorized the transaction, but the merchant has not yet confirmed that the final order exists.

Recommended actionCreate or finalize the order in the CMS or ERP, then call Confirm order (Mondu).
pending

Decision in progress

The order is still being processed or reviewed by Mondu.

Recommended actionPut the process on hold and resume when a new Mondu state becomes available.
confirmed

Order confirmed

Mondu recognizes the merchant order as committed and it can enter the shipping and invoicing lifecycle.

Recommended actionContinue commercial execution, then submit issued invoices with Create invoice (Mondu).
declined

Financing declined

Mondu did not authorize the transaction based on available information.

Recommended actionOffer another payment method or stop the order according to your commercial policy.
canceled

Order canceled

The Mondu order was canceled and can no longer continue its normal lifecycle.

Recommended actionCancel the associated journey or recreate a new Mondu order when a new attempt is legitimate.
completed

Lifecycle complete

The Mondu order lifecycle is complete.

Recommended actionRetain the result for tracking, reconciliation, and audit.
other

Unknown state

Mondu returned a state that does not match any business route known to the node.

Recommended actionDo not continue automatically. Analyze the returned Mondu state and define the appropriate business rule before resuming.
Attention The other route prevents a new or unexpected Mondu state from being treated as authorized.

Data resolution

The node automatically derives required data from linked Ormuz objects.

DataSource or rule
Retrieved Mondu orderorder.id identifies the order concerned
RouteCurrent Mondu result

Parameters 2

Contexte principal

Objects and configuration that determine the Mondu operation.

extension_config_idRequisref(extension_config:mondu)
Active Mondu configuration used for the operation. It notably defines environment, default payment method, net term, language, and optional marketplace settings.
orderRequisOrder
Persisted Ormuz Order carrying the entire Mondu lifecycle. Its order.id is used as external_reference_id and then external_order_id.

Outputs 2

Objet Mondu

Primary Mondu object produced or refreshed by the node.

orderMondu order
Mondu order including identifier, state, amounts, currency, external references, and dates.

Decision and control

Information used to direct the next process step.

selected_routestring
Route chosen from the business result returned by Mondu.

Behavior

Identify the order

The node uses the Ormuz order identifier.

Retrieve its Mondu state

Mondu returns the order's current state.

Select the route

The process is routed to the branch matching that result.

Limits and responsibilities

  • The node does not create a missing Mondu order.
  • It confirms, cancels, and invoices nothing.
  • It does not guarantee that an intermediate state will change within a given time.

Troubleshooting

Mondu order not found

Check that the order was created with the same Mondu configuration and that you supply the same order.id.

Plusieurs correspondances

Correct duplicates so one Ormuz order corresponds to one Mondu order.

`other` state

Analyze the returned Mondu state and define the appropriate business rule before continuing.