MonduRouteurStable

Confirm order (Mondu)

Confirms with Mondu that an authorized order has become firm in the CMS or ERP.

Ormuz order

Confirmed

Mismatch

Not authorized

Ordre Mondu

Vue d’ensemble

Confirm order (Mondu) translates the merchant's business commitment: the order now genuinely exists in the CMS or ERP and can enter its execution lifecycle.

The node confirms only an order that still matches the Mondu authorization. If amount, currency, or reference changed, it selects the mismatch route.

external_order_id is always order.id, with no fallback to an ERP reference.
An already-confirmed order can be processed again without creating a second confirmation.
Confirmation does not trigger payout: the invoice must then be submitted.

Typical scenario

The CMS confirms an order initially authorized for EUR 1,000. The order.confirmed process calls this node. If the ERP recalculated the order to EUR 1,050, the mismatch route blocks confirmation and exposes both amounts.

Quick start

Trigger this node when the same Ormuz order becomes firm in the CMS or ERP.

Before confirmation

Order already authorized by Mondu
Same order.id as during authorization
Amount and currency unchanged

After the result

Treat mismatch as a business blocker
Invoice only from the confirmed route

Configuration example

Parameter	Binding	Role
`order`	`confirmed_order`	Same object as during checkout
`buyer_confirmed_at`	`event.occurred_at`	Optionnel

Key point An amount difference must never be ignored. The Mondu authorization applies to the exact terms sent at creation.

Decision routes

confirmed

Order confirmed

Amount, currency, and external identity match the Mondu authorization, and the order is then confirmed or was already in a compatible later state.

Recommended actionContinue to shipping and invoicing.

mismatch

Order changed

The Ormuz order no longer matches the Mondu authorization on amount, currency, or canonical reference.

Recommended actionBlock confirmation, analyze discrepancies, and cancel or recreate the Mondu order as appropriate.

not_authorized

Order cannot be confirmed

The Mondu order is neither authorized nor already confirmed in a compatible state.

Recommended actionHandle the returned state: wait, offer an alternative, cancel, or restart a journey according to its value.

Attention mismatch means the order no longer matches authorized terms. Provide a visible branch to block and handle it.

Process example

order.confirmed event

Confirmer une commande (Mondu)

Confirmed

Mismatch

Not authorized

Ship and invoice

Block and analyze

Handle the Mondu state

Confirm the order only when it exactly matches the Mondu authorization.

Data resolution

The node automatically derives required data from linked Ormuz objects.

Data	Source or rule
Mondu order concerned	`order.id` identifies the authorized order
Expected identity	`external_reference_id = order.id`
Current amount	`order.amount_including_tax`
Current currency	`order.currency`
Confirmation reference	`external_order_id = order.id` uniquement

Parameters 3

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.

buyer_confirmed_atOptionneldatetime

Date and time when the buyer confirmed the order, when available. Use an ISO 8601 datetime.

Outputs 8

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_routeenum

Route chosen from the business result returned by Mondu.

selected_valuestring

Mondu value that led to routing. It may be more precise than the route, for example an advanced state grouped under authorized or confirmed.

Consistency diagnostics

Details available when the order no longer matches the Mondu authorization.

mismatch_fieldsOptionnelstring[]

List of fields that no longer match the Mondu authorization: external_reference_id, amount, and/or currency.

expected_amountOptionnelamount

Amount in minor units carried by the Mondu authorization.

actual_amountOptionnelamount

Amount in minor units carried by the Ormuz order at confirmation time.

expected_currencyOptionnelcurrency code

Currency carried by the Mondu authorization.

actual_currencyOptionnelcurrency code

Currency carried by the Ormuz order at confirmation time.

Behavior

Identify the authorized order

The node starts from the same Ormuz order used for the Mondu request.

Compare commercial terms

Reference, amount, and currency must match the authorization.

Route discrepancies

Any discrepancy produces mismatch with expected and current values.

Handle the Mondu state

A non-authorized order produces not_authorized. An already-confirmed order produces confirmed.

Confirm the order

When the order is still authorized and consistent, Mondu treats it as firm.

Limits and responsibilities

The node does not change the authorization when the amount changes.
It creates no new Mondu order.
It submits neither invoice nor proof of delivery.
By itself, it does not guarantee merchant payout.

Troubleshooting

Route `mismatch`

Review mismatch_fields and expected/current values. Cancel or recreate the journey if commercial terms changed.

Route `not_authorized`

Review selected_value to distinguish waiting, rejection, cancellation, or expiration.

Mondu order not found

Check that Hosted Checkout or the asynchronous order was created from the same order.id.