MonduUser action with decisionStable

Create hosted order (Mondu)

Creates or reuses a Mondu order from an Ormuz order, opens hosted checkout, and routes the process according to the buyer-journey result.

Checkout session

Ormuz order

Authorized

Declined

Canceled

Expired

Ordre Mondu

Vue d’ensemble

Create hosted order (Mondu) is the entry point for Mondu financing in e-commerce checkout. The checkout_session carries the user experience and return URL; the platform.order carries amount, currency, lines, buyer, and durable financing identity.

The process remains suspended while the buyer is on the Mondu page. At journey completion, the node resumes on authorized, declined, canceled, or expired according to the Mondu result.

order.id is always used as the canonical external reference.
The checkout session and order must concern the same merchant, buyer, and contact.
A new execution on the same order reuses the existing Mondu order instead of creating a second one.
Successful authorization does not yet confirm the merchant order and does not trigger payout.

Typical scenario

A buyer places a EUR 1,000 order on net-30 terms. Ormuz creates an order draft linked to the checkout session, then this node opens the Mondu journey. After authorization, the authorized route resumes checkout. The CMS then confirms the order and a separate process calls Confirm order (Mondu).

Quick start

Prepare a checkout session linked to a persisted order that is complete enough to be sent to Mondu.

Required objects

checkout_session.url valide
order.checkout_session_id = checkout_session.id
Buyer and contact referenced by the order
At least one order line

Commercial data

Positive total amount in minor units
ISO currency
Complete billing and shipping addresses
Buyer contact first name, last name, and email

Configuration example

Parameter	Binding	Role
`checkout_session`	`checkout_session`	Hosted-journey context
`order`	`draft_order`	Order carrying the financing
`payment_method`	`invoice`	Invoice payment
`net_term`	`30`	Buyer term
`language`	`fr`	Journey language

Key point Do not create a second order at ERP confirmation. The draft used here must be enriched and confirmed as the same Ormuz object.

Decision routes

authorized

Buyer authorized

The hosted journey is complete and Mondu authorized the transaction.

Recommended actionCreate or confirm the final order, then call Confirm order (Mondu).

declined

Request declined

Mondu declined authorization after the buyer journey.

Recommended actionShow an alternative payment method or stop the order according to your policy.

canceled

Journey canceled

The buyer canceled the journey or the order was canceled before authorization.

Recommended actionReturn the buyer to payment-method selection or allow a controlled retry.

expired

Authorization expired

The Mondu authorization window expired without a usable positive decision.

Recommended actionCreate a new journey when the buyer wants to retry and the order is still valid.

Attention Treat each route as a distinct business outcome: only authorized may continue to order confirmation.

Process example

Checkout B2B

Créer une commande avec parcours d’achat hébergé (Mondu)

Authorized

Declined

Canceled

Expired

Create the order

Other payment

Return to checkout

Nouvelle tentative

Create the Mondu order from the order draft, wait for the buyer, then handle the route matching the journey result.

Data resolution

The node automatically derives required data from linked Ormuz objects.

Data	Source or rule
Return URL	`checkout_session.url`
Mondu reference	`order.id` only
Amount and currency	`order.amount_including_tax` and `order.currency`
Buyer	`order.buyer_id` → company ; `order.buyer_contact_id` → contact
Adresses	Order details → company registered address → billing address for shipping
Lignes	Persisted `platform.order` lines
Payment method	Parameter → configuration → `invoice`
Net term	Parameter → configuration → `30`
Langue	Parameter → configuration → `en`

Parameters 12

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.

checkout_sessionRequisCheckout session

Ormuz checkout session linked to the order. It provides the hosted-journey return URL and must concern the same order, merchant, buyer, and contact.

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.

Value	Usage
`invoice`	Deferred invoice payment
`installment_by_invoice`	Invoice installments
`direct_debit`	Direct debit
`installments`	Payment in installments
`billing_statement`	Billing statement

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.

Process resumption

Advanced settings that bound replay of the user action.

allow_replay_from_hereOptionnelboolean

Allows an authorized operator to resume the process later from this user action. Leave disabled unless your resume policy explicitly provides for a new Mondu authorization.

replay_boundaryOptionnelboolean

Marks this action as a replay point of no return. Enable it when replaying earlier steps could recreate an order, change its terms, or duplicate a buyer interaction.

Other parameters

titleOptionnelstring

Title displayed in the hosted experience during Mondu checkout to clearly explain the action expected from the buyer.

descriptionOptionnelstring

Supporting text shown under the title during Mondu checkout. Use it to provide business context without repeating information already present on the provider page.

Outputs 6

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.

hosted_checkout_urlurl

Mondu hosted-journey URL used to redirect the buyer.

createdboolean

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

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.

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

Check checkout consistency

The session and order must concern the same merchant, buyer, and contact.

Prepare order data

The node uses buyer, contact, addresses, amounts, and lines carried by the order.

Create or reuse the Mondu order

The same order.id always corresponds to the same Mondu order for this configuration.

Open the Mondu journey

The buyer is sent to the hosted Mondu page and the process waits for the result.

Route the rest of the journey

Terminal results select a route; Mondu processing still in progress leaves the process waiting.

Limits and responsibilities

The node does not confirm the merchant order: use Confirm order (Mondu) after final creation in the CMS or ERP.
It submits no invoice and does not directly trigger payout.
Closing the tab before journey completion leaves the user action waiting.
A change in amount after authorization will be detected during confirmation.

Troubleshooting

Checkout and order inconsistent

Check order.checkout_session_id, merchant, buyer, and buyer contact on both objects.

Buyer information incomplete

Complete legal name, registration, country, first name, last name, and email before checkout.

Address or lines missing

The order must have a complete address and at least one persisted line.

The journey remains waiting

Mondu has not yet returned a terminal result. Wait for processing to complete or plan state tracking for the order.

Hosted URL missing

Check Hosted Checkout mode and the Mondu configuration being used.