MonduRouteurStable

Create async order (Mondu)

Creates or reuses a Mondu order for an ERP or back-office order, then routes the process according to the result.

Ormuz order

Authorization required

Authorized

Pending

Confirmed

Declined

Canceled

Completed

Other

Ordre Mondu

Vue d’ensemble

Create async order (Mondu) covers sales created outside an interactive web checkout. The node uses the platform.order, its buyer, contact, and lines to present the request to Mondu.

Mondu may respond immediately or indicate that a decision is still in progress. The process must explicitly handle the selected route.

The same order.id identifies the order throughout its Mondu lifecycle.
No checkout session or return URL is required.
A new execution on the same order creates no duplicate.

Typical scenario

An order entered by a salesperson arrives from the ERP. The node submits it to Mondu. The authorization_required route then triggers the configured buyer-authorization channel, while authorized allows continuation to confirmation.

Quick start

Link a complete persisted order. Buyer and lines are derived from the order.

Prepare the order

Buyer and contact populated
Valid amount and currency
Complete addresses
At least one line

Prepare the process

Handle intermediate states
Confirm only the authorized route or an already-confirmed state

Configuration example

Parameter	Binding	Role
`order`	`erp_order`	Persisted order
`payment_method`	`invoice`	Condition commerciale
`net_term`	`30`	Buyer term

Key point This node does not replace Hosted Checkout: choose it when authorization is not performed in the current web journey.

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 pending and authorization_required routes mean the order is not yet authorized.

Data resolution

The node automatically derives required data from linked Ormuz objects.

Data	Source or rule
Mondu reference	`order.id` only
Buyer and contact	Order `buyer_id` and `buyer_contact_id` relationships
Amounts, currency, and addresses	`platform.order` fields with fallback to the company address when needed
Lignes	Persisted order lines
Terms	Node parameters → configuration values → defaults

Parameters 7

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.

Commercial terms

Payment choice, term, and journey settings.

payment_methodOptionnelenum

Payment method requested from Mondu. When omitted, the node uses the configuration default, then invoice.

net_termOptionnelinteger

Payment term granted to the buyer, in days. When absent, the node uses the configuration default, then 30 days.

languageOptionnelenum

Language of the Mondu journey or communication. When absent, the node uses the configuration default, then en.

vendor_external_reference_idOptionnelstring

Seller reference reserved for marketplace mode. It is accepted only when marketplace_mode is enabled on the Mondu configuration.

notesOptionnelstring

Optional business notes sent to Mondu with the order.

Outputs 5

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.

authorization_requiredboolean

true when Mondu indicates that buyer authorization is still required.

createdboolean

Whether the node created a new Mondu object. false means the existing object was found and reused.

selected_routestring

Route chosen from the business result returned by Mondu.

Other outputs

extension_object_mappingextension object mapping

Durable mapping between the created or reused Mondu object and the Ormuz object forming its business anchor.

Behavior

Prepare the order

The node checks that identity, amount, currency, buyer, and lines are sufficient to present the request to Mondu.

Avoid duplicates

An order already sent to Mondu is reused.

Present the request

Mondu receives the commercial data and stable order.id reference.

Route the process

The Mondu result selects one of the eight documented routes.

Limits and responsibilities

The node collects no user action.
It does not automatically confirm an authorized order.
It does not turn an intermediate state into a final decision.
It submits no invoice.

Troubleshooting

Ordre incomplet

Complete buyer, contact, lines, amount, currency, and addresses.

`authorization_required`

Plan the authorization channel appropriate to your asynchronous Mondu integration.

`other`

Analyze the returned Mondu state before adding a new business rule.