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 checkout, payout, or transfer. 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 block or authorize a transaction during checkout or payout.
  • 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 6

extension_config_idRequisref(extension_config:sumsub)
Active Sumsub provider configuration used to sign the KYT call.
subjectRequisContact
Ormuz holder of the transaction. The node accepts a contact or company already mapped to a Sumsub applicant.
transactionRequisobject
Transactional payload sent to Sumsub according to the Sumsub KYT contract (txnId, txnDate, type, info, applicant, counterparty, etc.).
sumsub_applicantOptionnelSumsub applicant
Sumsub applicant to use when the process already has it. Otherwise the node resolves it through the subject mapping.
payment / psp_payment / supplier_paymentOptionnelobject
Ormuz business object linked to decision context. It is not persisted as a node output; the process decides what to do on each branch.
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 the Sumsub applicant linked to the Ormuz subject, then calls the KYT transaction submission endpoint.

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.