Submit transaction

Request

Use this endpoint to submit transaction data for screening and monitoring. The system analyzes the payment parameters against your selected ruleset_id and delivers the result asynchronously to your callback_url. To identify the customer, you must provide either an internal applicant_id or your external_applicant_id.

Security

API-Key

Bodyapplication/jsonrequired

applicant_idstring, = 36 characters

A unique identifier of an applicant, that is assigned by our system after an applicant object was created with a “Create an applicant” request

Example:"da0ebf0ade0bfad0ebf0adeb0fade0bfad0e"

external_applicant_idstring or null, [ 0 .. 50 ] characters

A unique identifier of your user in your system

Example:"ad0ebf0a-de0b-fad0-ebf0-adeb0fade0bf"

external_applicant_registered_atstring, = 19 characters

The date and time of user registration in the customer's system. Must be in UTC and follow the YYYY-MM-DD hh:mm:ss format. Cannot be a future date

Example:"2025-12-19 18:44:08"

transactionobject

ruleset_idstring, = 36 characters^[a-fA-F0-9]{36}$

The unique 36-character hexadecimal identifier of the screening ruleset. This ID is automatically generated after you create a ruleset in the Dashboard. It determines which ruleset will be applied to the transaction

Example:"da0ebf0ade0bfad0ebf0adeb0fade0bfad0e"

{
  "applicant_id": "da0ebf0ade0bfad0ebf0adeb0fade0bfad0e",
  "external_applicant_id": "ad0ebf0a-de0b-fad0-ebf0-adeb0fade0bf",
  "external_applicant_registered_at": "2025-12-19 18:44:08",
  "transaction": {
    "direction": "incoming",
    "amount": "16.003892000000000000",
    "asset": "GBP",
    "created_at": "2026-02-01 15:27:15"
  },
  "ruleset_id": "da0ebf0ade0bfad0ebf0adeb0fade0bfad0e"
}

Responses

OK The request was successful, and our system returned an expected response.

Bodyapplication/json

statusstring

Example:"ok"

dataobject

Response

{
  "status": "ok",
  "data": {
    "service_request_id": "6bff21e17da144418b7643267ba4502930a9"
  }
}