TwoConnecteurStable

Create checkout order (Two)

Creates or reuses a Two order for an Ormuz order attached to a checkout session.

Vue d’ensemble

Creates or reuses a Two order for an Ormuz order attached to a checkout session.

Exemple

After a positive pre-assessment, create the Two order and present buyer verification when required.

Parameters 7

extension_config_idRequisref(extension_config:two)
Two configuration used for this operation. It determines provider identifiers, capabilities, and environment.
checkout_sessionRequisCheckout session
Ormuz checkout session carrying interactive sales context.
orderRequisOrder
Ormuz Order used as business source and durable mapping anchor for the Two order.
order_intentOptionnelTwo order intent
Optional Two pre-assessment whose tracking connects the order intent to final creation.
payment_terms_daysOptionnelenum
Payment term requested from Two for the financed sale.
invoice_typeOptionnelenum
Billing/financing mode requested from Two for the order.
notesOptionnelstring
Optional business notes sent to Two when the operation accepts this field.

Outputs 5

orderTwo order
Latest normalized state of the relevant Two order.
payment_urlOptionnelurl
Two URL intended for the buyer for verification or payment initiation when provided by Two.
extension_object_mappingextension object mapping
Durable mapping between the Two object and its Ormuz anchor object.
createdboolean
Whether execution created a new Two resource/mapping instead of reusing an existing one.
selected_routestring
Normalized business state selected by the node; the route must be explicitly handled by the process.

Behavior

The Ormuz order remains the canonical mapping anchor. When Two requires verification, the node exposes a hosted URL and routes verification_required.

Limits and responsibilities

  • Do not create several Two orders for the same order to bypass a provider state.
  • Creating the order does not mean the sale is fulfilled.