Overview
Submitting a transaction means sending the transaction data to Sigma so it can be analysed for fraud and risk. Every transaction your customers make (transfers, deposits, withdrawals, payments) can be submitted to Sigma in real time. Sigma evaluates the transaction against your configured rules and returns a decision: approve, review, or reject.Submission Methods
There are two ways to submit a transaction:
For most integrations, instant is recommended. It lets you act on the result immediately, for example blocking a transaction before it settles.
What to Send
When submitting a transaction, include as much data as you have. The more context Sigma receives, the more accurate its analysis. Key fields include:
You don’t need to send every field. Send what your system has and Sigma adapts its analysis to the data available.
For a complete list of accepted fields and their formats, see the Historical Data page which documents the full transaction data structure.
Understanding the Response
Sigma returns three key values in the transaction result:action: what Sigma recommends you do with the transaction:
risk_level: the overall risk score assigned to the transaction (low, medium, high).
triggered_rules: a list of any rules that fired on this transaction, helping you understand why a decision was made.
How to Handle Each Outcome
- APPROVE: proceed with the transaction as normal
- REVIEW: hold the transaction and queue it for a compliance team member to investigate. You can view flagged transactions in the Sigma dashboard under Transaction Monitoring
- REJECT: block the transaction and notify the user. Log the decision for audit purposes
API Reference
Instant Submission
Submit a transaction and receive a synchronous decision.
Webhook Submission
Submit a transaction and receive the result via webhook callback.