SEPA operation import - with transaction monitoring

Just so you know, further examples and descriptions apply only to SEPA operation imports with transaction monitoring.

This section provides information how to submit operation (transaction) details to our database and is focused to those operations which require to perform transaction monitoring. It includes examples of API requests with mandatory and optional fields, a comprehensive list of all available fields, common responses and error descriptions.

SEPA (Single Euro Payments Area) operations involve transactions between two or more parties, one of the parties is always the customer. The other party(ies) are called counterparty(ies). Transaction monitoring ensures compliance and helps detect fraudulent activities or anomalies that your risk team is interested in.

HTTP Method: POST

Path: {{baseUrl}}/amlyze-ws-rest/operation

ContentType: application/json

Authorization: Bearer Token

API requests examples

Show Mandatory fields example | SEPA operation import - with transaction monitoring

{
"communicationNumber": "Test_ComNr_SEPA_13",
"requester": "Company Name Amlyze",
"businessUnit": "sandbox",
"operationExtId": "Op_11_SEPA_TEST",
"operationType": "SEPA",
"riskManagementCategory": "OP_TRANSFER",
"sourceOfRiskLevel": "EVALUATE",
"operationDateTime": "2025-06-20T12:09:33+02:00",
"financialFlowDirection": "OUTGOING",
"currency": "EUR",
"amount": 10000,
"euroExchangeRate": 1,
"amountInEuro": 10000,
"description": "Invoice 'Nr.01'",
"listOperationParty": [
	{
		"partyRole": "DEBTOR",
		"accountNumber": "ORG20231117550",
		"entityType": "ORGANIZATION",
		"bic": "SANDLT00XXX",
		"title": "UAB 'BrotherHood'"
	},
	{
		"partyRole": "CREDITOR",
		"accountNumber": "LT9208800274335945522",
		"bic": "AmlyzeXX22",
		"entityType": "INDIVIDUAL",
		"firstName": "Tomas",
		"lastName": "Garcia"
	}
]
}

Show Mandatory fields example | SEPA operation import - with transaction monitoring and screening

{
"communicationNumber": "Test_ComNr_SEPA_15",
"requester": "Company Name Amlyze",
"operationExtId": "Op_12_SEPA_TEST",
"operationType": "SEPA",
"businessUnit": "sandbox",
"riskManagementCategory": "OP_TRANSFER",
"sourceOfRiskLevel": "EVALUATE",
"initializeScreeningProcesses": [
	"SANCTIONS",
	"PEP",
	"ADVERSE_MEDIA",
	"INTERNAL_LIST"
],
"operationDateTime": "2025-06-20T10:09:33+02:00",
"financialFlowDirection": "OUTGOING",
"currency": "EUR",
"amount": 100000,
"euroExchangeRate": 1,
"amountInEuro": 100000,
"description": "Invoice 'Nr.01'",
"listOperationParty": [
	{
		"partyRole": "DEBTOR",
		"accountNumber": "VG50GHJL6649878241059005",
		"bic": "SANDLT00XXX",
		"entityType": "ORGANIZATION",
		"title": "Vending Machines LTD"
	},
	{
		"partyRole": "CREDITOR",
		"accountNumber": "LV11245541148212335",
		"entityType": "ORGANIZATION",
		"title": "LTD 'VivaFocus'"
	}
]
}

Show All fields example | SEPA operation import - with transaction monitoring and screening

{
"communicationNumber": "Test_ComNr_SEPA_20",
"requester": "Company Name Amlyze",
"businessUnit": "sandbox",
"operationExtId": "Op_14_SEPA_TEST",
"operationType": "SEPA",
"riskManagementCategory": "OP_TRANSFER",
"sourceOfRiskLevel": "EVALUATE",
"initializeScreeningProcesses": [
"SANCTIONS",
"PEP",
"ADVERSE_MEDIA",
"INTERNAL_LIST"
],
"operationDateTime": "2025-06-20T15:09:33+02:00",
"financialFlowDirection": "INCOMING",
"currency": "EUR",
"amount": 123,
"euroExchangeRate": 1,
"amountInEuro": 123,
"sourceCountry": "LT",
"destinationCountry": "LV",
"description": "invoice '06'",
"ipAddress": "555.222.4545.144",
"ipAddressCountry": "LT",
"listOperationParty": [
{
	"partyRole": "ULTIMATE_DEBTOR",
	"accountNumber": "LT20240226T133450",
	"bic": "BIC",
	"currency": "EUR",
	"bankTitle": "TBC",
	"entityType": "INDIVIDUAL",
	"firstName": "Hakaka",
	"lastName": "Luka",
	"identifier": "50007102289",
	"address": "Verkių g. 7-8, Vilnius",
	"country": "LT"
},
{
	"partyRole": "DEBTOR",
	"accountNumber": "LV11245541148212335",
	"bic": "BIC22XX",
	"currency": "EUR",
	"bankTitle": "TBC",
	"entityType": "INDIVIDUAL",
	"firstName": "Antonio",
	"lastName": "Murara"
},
{
	"partyRole": "CREDITOR",
	"accountNumber": "VG50GHJL6649878241059005",
	"bic": "SANDLT00XXX",
	"currency": "EUR",
	"bankTitle": "Sandbox",
	"entityType": "ORGANIZATION",
	"title": "Vending Machines LTD"
},
{
	"partyRole": "ULTIMATE_CREDITOR",
	"accountNumber": "LT20240226T133633",
	"bic": "BIC",
	"currency": "EUR",
	"bankTitle": "TBC",
	"entityType": "INDIVIDUAL",
	"title": "Dona Murara",
	"identifier": "60007102289",
	"address": "Kauno g. 9, Vilnius",
	"country": "LT"
}
]
}

Fields

communicationNumber

string

required

Unique number of communication. This field can store up to 256 characters.

Example: ComNr_01_TEST

requester

string

required

Name of the system requesting web service.

Example: Amlyze

businessUnit

string from classifier list

❗Mandatory field for clients utilizing a multi-organizational solution. Omit this parameter unless instructed about it.

It serves to specify the unique identifier for the business unit. Business units are logical groupings of users and data. Each business unit can have its own set of users, permissions, and data access rules.

Example: BUSINESS_UNIT_NAME

Show Path to extract classifier values

HTTP Method: GET

Path: {{baseUrl}}/classifier/businessUnit

operationExtId

string

required

External identifier of operation.

Example: Op_01_SEPA_TEST

operationType

string

required

Notifies about which kind of operation type was performed

Value: SEPA

riskManagementCategory

string from classifier list

required

Code of risk management category of the object. Value must be from a classifier list personalized to your company.

Example: OP_TRANSFER

Show Path to extract classifier values

HTTP Method: GET

Path: {{baseUrl}}/classifier/riskManagementCategory

sourceOfRiskLevel

string

required

The value “EVALUATE” is used for normal business processes - risk assessment will be performed.

Value: EVALUATE

initializeScreeningProcesses

list[]

Defines which lists to check during screening process. Strings of the list are noted in the dropdown below.

Show list[]

   "initializeScreeningProcesses": [
       "SANCTIONS",
       "PEP",
       "ADVERSE_MEDIA",
       "INTERNAL_LIST"
   ]

Example: PEP, ADVERSE_MEDIA

operationDateTime

date

required

The operation date and time show when the operation proceeded.

Example: 2024-08-16T13:00:00Z

financialFlowDirection

string from enum

required

Refers to the movement of money between entities or accounts.

Enum class values: INCOMING, OUTGOING

Example: INCOMING

currency

string from classifier list

required

International currency code.

Show Path to extract classifier values

HTTP Method: GET

Path: {{baseUrl}}/classifier/currency

Value: EUR

amount

BigDecimal

required

Amount of money sent in an operation.

Example: 1499

euroExchangeRate

BigDecimal

❗Mandatory if currency is not EUR. Not Used when currency is EUR.

Euro exchange rate for other than Eur currency.

Example: 0.93

amountInEuro

BigDecimal

❗Mandatory if currency is not EUR. Not Used when currency is EUR.

Amount of money in euro currency.

Example: 1499

sourceCountry

string (ISO 3166-1 alpha-2) from classifier list

Country rom where the operation was initiated.

Show Path to extract classifier values

HTTP Method: GET

Path: {{baseUrl}}/classifier/country

Example: LT

destinationCountry

string (ISO 3166-1 alpha-2) from classifier list

Country of operation’s destination.

Show Path to extract classifier values

HTTP Method: GET

Path: {{baseUrl}}/classifier/country

Example: LT

description

string

required

The purpose of payment is saved under description.

Example: Invoice '02'

ipAddress

string

The IP address of the operation.

Example: xxx.zzz.yyyy.www

ipAddressCountry

string (ISO 3166-1 alpha-2) from classifier list

Country of an IP address of the operation.

Show Path to extract classifier values

HTTP Method: GET

Path: {{baseUrl}}/classifier/country

Example: LT

listOperationParty

list[]

required

List of entities that belong to one operation. Fields of the list are described in the dropdown below.

Show listOperationParty list[] fields

partyRole

string from enum

required

The role of the party in ongoing operation. At least one operation party account must already exist in Amlyze.

Only one operation can be imported per API request which means only one CREDITOR and one DEBTOR could be provided.

Enum class values: DEBTOR, CREDITOR, ULTIMATE_DEBTOR, ULTIMATE_CREDITOR

If financialFlowDirection is INCOMING your customer is CREDITOR. If financialFlowDirection is OUTGOING your customer is DEBTOR.

Example: CREDITOR

accountNumber

string

required

❗Not mandatory if partyRole is ULTIMATE_DEBTOR or ULTIMATE_CREDITOR.

Unique account identification number used in performing operations.

Example: LT038625979279192518

currency

string from classifier list

required

International currency code.

Show Path to extract classifier values

HTTP Method: GET

Path: {{baseUrl}}/classifier/currency

Value: EUR

bic

string

required

❗Mandatory only for your customer. Not mandatory for counterparties.

Bank identifier code for account number.

Example: BICXX22

bankTitle

string

Title of bank at which the operation is happening.

Example: TBC bank

entityType

string from enum

required

Describes client status.

Enum class values: INDIVIDUAL, ORGANIZATION, UNKNOWN

UNKNOWN is valid only for counterparties.

Example: INDIVIDUAL

firstName

string

Individual entity’s first name, used only together with lastName and never alone.

Example: Eduardo

lastName

string

Individual entity’s last name, used only together with firstName and never alone.

Example: Rodriguez

title

string

required

❗Not mandatory if entity is INDIVIDUAL and both firstName and lastName are provided.

Identifies a party (INDIVIDUAL, ORGANIZATION or UNKNOWN) without requiring firstName or lastName.

Example: Moller

identifier

string

❗Mandatory only when “partyRole” = “ULTIMATE_” and no more elements are provided for that party.

Unique identification number (e.g., personal ID, company VAT code) to distinguish the payer and the transaction. Can be used for customer, counterparty and ultimateparty.

Example: 50007153359

address

string

Party’s nformation including street address, city, and possibly other relevant details.

Example: Verkių g. 7-8, Vilnius

Country

string (ISO 3166-1 alpha-2) from classifier list

Two-letter country code specifying the participant’s country.

Show Path to extract classifier values

HTTP Method: GET

Path: {{baseUrl}}/classifier/country

Example: DE

List of possible responses

This part lists common responses after the submission of the request.

200 OK
  "resultType": "REQUEST_ACCEPTED"


400 Bad Request
    "resultType": "REQUEST_REJECTED",
    "errorCode": "O001",
    "errorDescription": "CommunicationNumber already used in amlyze"


404 Not Found
    "timestamp": "2024-05-26T16:49:50.237+00:00",
    "status": 404,
    "error": "Not Found",
    "path": "/amlyze-ws-rest/opeation" --> mistake inside the endpoint


500 Internal Server Error
  "resultType": "REQUEST_REJECTED"
  "status": 500,
  "error": "Internal Server Error"

List of possible errors

This section lists the possible errors that can occur when making a bad operation request to the API. A bad request is a request that somehow does not follow the API specifications.

Error Description
DestinationCountry is mandatory, check country classifier codes for allowed values.
Amount is mandatory and must be greater than 0.
Despite currency = EUR, AmountInEur differs from Amount.
AmountInEur is mandatory and must be greater than 0.
EuroExchangeRate is mandatory and must be greater than 0.
For non-INTERNAL operation, financialFlowDirection value cannot be ‘NULL’.
Description is mandatory.
Invalid MerchantCountryCode.
RiskManagementCategory is mandatory.
RiskManagementCategory does not exist in Amlyze.
RiskManagementCategory does not support Operation.
Account registered to your institution; Account found in Amlyze, but customer not found in Amlyze.
entityType mismatch in operationParty[” + i + ”]: Amlyze customer has different entity type to operation one.
For INCOMING operation, your customer party role must be CREDITOR.
For OUTGOING operation, your customer party role must be DEBTOR.
operationType ” + operationType.getCode() + ” is not defined in Amlyze. Check Operation type classifier for available values.
Problem with operation party (index: ” + i + ”).
Invalid FinancialFlowDirection: Your institution DEBTOR found for INCOMING operation.
Invalid FinancialFlowDirection: Your institution CREDITOR found for OUTGOING operation.
OperationParties must contain CREDITOR.
OperationParties must contain DEBTOR.
Invalid operation party count. Range: min 1, max 4.
Invalid count of operation parties for ” + operationType.getCode() + ” operationType.
For ‘PIS’ operation, only creditor can be provided.
No operation party account related to your institution BIC, or Customer.
Invalid count of your institution operation parties for ” + operationType.getCode() + ” operationType.
Tenant header ’” + securityOwnerService.getHeaderTenantCode() + ”’ is mandatory.
Business unit is mandatory.
Tenant ’” + tenantCode + ”’ business unit ’”+ businessUnitCode +”’ does not exist.
CommunicationNumber is mandatory.
Requester is mandatory.
SourceOfRiskLevel is mandatory, allowed values: IMPORT / EVALUATE.
OperationExtId is mandatory.
OperationType is mandatory.
Problem with OperationType (INVALID): INVALID is not defined in Amlyze. Check Operation type classifier for available values.
Currency is mandatory, check Currency classifier codes for allowed values.
SourceCountry is mandatory, check country classifier codes for allowed values.
Problem with OperationType (SEPA): Problem with OperationParties. No operation party account related to your institution BIC or Customer.
Problem with OperationType (SEPA): Invalid count of your institution operation parties for SEPA operationType.

API Documentation

​API requests examples

​Fields

​List of possible responses

​List of possible errors

API requests examples

Fields

List of possible responses

List of possible errors