Mondu
Create Mondu buyers and orders, collect authorization, submit invoices, and reconcile payouts.
Nature and scope
| Integration type | Service extension |
|---|---|
| Business capabilities | |
| Integration mechanisms | rest_apiwebhook |
What this extension lets you build
- Redirect B2B buyers to Mondu for payment authorization.
- Request buyer authorization for back-office and ERP orders.
- Submit legal invoices and track settlement and payouts.
Integrate Mondu into the order-to-cash lifecycle
These journeys show how Ormuz events and objects trigger Mondu operations, then feed their outcomes back into the commercial lifecycle.
1. Deferred payment at checkout
The checkout process creates the hosted Mondu journey and retains the Ormuz order as the business reference.
The checkout session carries user context; the Ormuz order remains correlated with the Mondu order through an object mapping.
2. Confirmation and shipping
Confirmation of the Ormuz order triggers confirmation of the Mondu authorization before logistics processing.
The node notably checks amount and currency consistency before confirming the order.
3. Invoicing and payout tracking
The issued invoice is sent to Mondu. The completed payout is then tracked as a cash movement without being applied to the invoices a second time.
Payout invoice references remain useful for traceability, but the payout does not drive their `settlement_status`.
Browse the documentation
Review the configuration, nodes, events, objects, and access declared by this extension.