payment.record

To record a payment with an audit trail, you register the payment event on an existing order using a mandatory payment_status field and an operation_id to ensure traceability and idempotent execution. Explicit confirmation is required before mutating the order's payment state.

Idempotent payment processing prevents duplicate mutations by using a unique operation_id for each request. If a network failure causes a retry, the same operation_id ensures the payment is only recorded once, allowing safe recovery without corrupting the order's payment status.

Yes, you can update a payment status to paid, pending, or partial without duplicating the transaction. The idempotent workflow uses the operation_id to recognize repeated requests, ensuring the partial payment is registered safely and only alters the state once.

You link a payment confirmation to a specific order by providing the order folio or an operation_id_ref. This reference compatibility ensures the payment event is accurately attached to the correct existing order before the explicit confirmation step mutates the payment state.

Yes, recording a payment requires explicit confirmation before changing the order state. The pending_confirm workflow ensures that payment statuses are not mutated automatically, maintaining security and providing a verifiable audit trail for every operation.