Skip to main content
Operation, also referred to as a transaction, represents the financial activity. Every Operation sent must be linked to at least one Account that already exists in the system. This ensures that every transaction is associated with a specific Customer, which is a critical requirement for effective monitoring. This linkage applies to at least one party in the transaction. Each transaction can have up to four participants — two direct parties (sender and receiver) and two ultimate parties. At least one direct party must be your customer; the others may be customers or external counterparties. To keep integration simple, we use a single endpoint for all transaction data. The specific details required depend on the type of operation you are reporting.

Operation Types

You can always retrieve the full list of available operation types via Classifier API.

Financial Flow Direction

Financial flow direction refers to the movement of money between entities or accounts. It dictates which party role must be a customer and helps to determine which direction is used for money.

Incoming

Outgoing

Internal

Flexible Fields

While most operations share basic fields (like amount and currency), some require specific data to ensure accurate risk scoring:
  • Card Operations: Include merchant details, MCC codes, and terminal info.
  • SEPA/SWIFT: Focus on sender/receiver IBANs and intermediary bank details.
If a field is not relevant to a specific operation type (for example, a merchant name for a SEPA transfer), you can simply leave it blank.

Additional Properties

Use additionalProperties to send operation data that has no dedicated field, for example a risk score calculated in your own system. Each property is a code with a typed value, stored with the operation so that your monitoring rules can take it into account. The list is optional and is accepted by Evaluate operation, Batch import of operations and Validate Batch Operations. A property that breaks these rules rejects the operation with error code A001 (see Errors). In a batch, only the operation that carries the property is rejected. When you update an operation (action UPDATE), send the complete list again. An update without additionalProperties removes the properties stored for the operation. The example below shows the field inside an operation request, with the other operation fields left out:

Device Data

Use deviceData on an operation party to send the device your customer acted from, for example the device that initiated an outgoing payment. It is optional and is accepted by the same three endpoints as additional properties. Device data is allowed only on a party that is your customer: the party’s account must be in AMLYZE and belong to a customer. In an outgoing payment, that is the DEBTOR. The operation is rejected when:
  • deviceData has no id, including an empty object or one with only eventId: error code OP07.
  • deviceData is sent on a party that is not your customer, for example the counterparty: error code OP08.
The example below shows the field on the customer’s party of an outgoing payment, with the other operation fields left out:

Other Caveats

If operation party does not contain currency, the currency is inherited from operation currency. Exception in CRYPTO_EXCHANGE where creditor does not inherit operation currency even if the currency is absent.