Create PSP payment
Creates a canonical PSP-payment intent in `draft` status before a provider establishes the external payment.
Contexte financier
Create PSP payment
Finance
Typed result
Vue d’ensemble
Creates a canonical PSP-payment intent in draft status before a provider establishes the external payment.
Exemple
Prepare a payment intent for an order or invoice before handing it to the selected PSP extension.
Parameters 8
company
Buyer company used as the context for payment intent or reconciliation.
order
Order used to bound or derive the financial context of the operation.
invoice
Invoice used to bound or derive the financial context of the operation.
receivable
Receivable projection whose balance can serve as a basis for the payment intent.
checkout_session
Checkout session whose financial result or lifecycle is updated.
amount
Operation amount in minor monetary units. When optional, the node may use the residual amount defined by its contract.
currency
ISO 4217 currency used to interpret all amounts in the operation.
metadata
Free-form integration metadata associated with the resource according to the flat
common.metadata contract.Outputs 1
psp_payment
Canonical PSP intent created in
draft status before establishment with a provider.Behavior
The node freezes the Ormuz financial context — company, order, invoice, receivable, or checkout — and creates the intent that the provider step can later establish.
Key point Always distinguish the canonical object created by Ormuz from any external effect. A payment or refund intent in
draft status does not prove that a provider executed the movement of funds.Limits and responsibilities
- No provider payment is created by this node.
- Amount and currency must represent the real intent; derive them from an object only when the process contract guarantees that derivation.