ormuz
Home/Integrations/Sumsub/Nodes/Evaluate transaction (Sumsub)
SumsubRouteurBeta

Evaluate transaction (Sumsub)

Submits a transaction to Sumsub Transaction Monitoring and returns an operational routing decision without creating an Ormuz business object.

Vue d’ensemble

Objectif

This node is a decision gate for a commercial sales or purchase operation. It produces neither compliance_check, nor risk_score, nor a draft to persist.

The node pushes the transaction to Sumsub KYT, reads an immediate decision when available, and suspends the process only when Sumsub puts the transaction into review.

transaction_evaluation is the main business output: it carries the decision, score, triggered rules, and raw provider response.

The node routes directly on transaction_evaluation.decision with approved, rejected, review_required, and awaiting_user branches.

awaiting_user does not embed a hosted experience in this node: the process may branch to a dedicated node afterward, for example sumsub.step_up_liveness.

Quand l’utiliser

  • You want to assess a checkout, sales order, invoice or purchase operation before continuing the process.
  • You want to submit a transaction to Sumsub fraud, transaction-AML, or monitoring rules without creating a compliance result for every transaction.
  • You want to handle manual-review cases with a provider wait encapsulated in the same node.

Parameters 5

extension_config_idRequisref(extension_config:sumsub)
Active Sumsub configuration used to evaluate the transaction.
subjectRequiredContact
Evaluated participant: an Ormuz contact, company or a Sumsub applicant already mapped to an Ormuz participant. Use sumsub.ensure_applicant to prepare missing identity.
transactionRequiredCheckout session
Typed Ormuz commercial object: checkout_session, order, invoice, purchase_order or supplier_invoice. The node adapts it to Sumsub; raw provider JSON is not accepted.
paymentOptionalPSP payment
One optional associated psp_payment, payment or supplier_payment. It enriches context without replacing the transaction amount; parties, currency and available links are checked.
device_access_token / session_id / device_contextOptionnelobject
Device Intelligence context to attach to a financial transaction. Collection happens client-side with the fisherman SDK; the transaction node remains the entry point for financial events.

Outputs 3

sumsub_transactionSumsub transaction
Normalized Sumsub KYT transaction, correlated through id / transaction_id to kytTxnId.
transaction_evaluationSumsub transaction evaluation
Provider-native business result of the transaction assessment. It carries decision, score, triggered_rules, review_answer, review_status, and raw_response.
selected_routeenum
Route selected by the node, derived from transaction_evaluation.decision.

Behavior

Submit the transaction

The node resolves one applicant mapping, checks the subject and optional payment, adapts the typed transaction and submits it to Sumsub. Retries reuse the same submission ID.

Route the immediate decision

When Sumsub returns a final decision, the node completes with selected_route: approved or selected_route: rejected.

Wait only for review

When Sumsub puts the transaction into review, the node suspends the process on extension.sumsub.applicant_kyt_txn_reviewed, correlated by kytTxnId.

Process example

Business object + Transaction
Évaluer une transaction (Sumsub)
Approuvé
Rejeté
Revue requise
Action utilisateur requise

Transaction Monitoring is an operational decision on a transaction, not persisted compliance evidence.