Go!KYT
Supported fields
Go!KYT
Supported fields
Transactions and customers supported fields for Go!KYT
Transactions fields
By default, any transaction submitted to Go!KYT supports the following information:
Transaction
| Field name | Type | Required | Description |
|---|---|---|---|
external_id | string | Yes | Your unique identifier of the transaction |
date | string | Yes | Date of the transaction in ISO format (2023-07-05T08:18:05.661Z) |
from | Participant | Yes | Sender of the transaction |
to | Participant | Yes | Receiver of the transaction |
amount | string | Yes | Amount of the transaction converted to string, ex. "0.01233110" |
currency | string | Yes | Currency of the transaction, ex. "BTC" or "EUR" |
crypto | Crypto | No | (Crypto only) Specify additional information about a crypto transaction |
comment | string | No | Comment for this transaction |
fields | object | No | Custom fields for this transaction, key-value object, see ‘custom fields’ section |
review_groups | string | No | Review groups for this transaction separated by ;, ex. A;B, see [/docs/common/review-groups](review groups) |
Internally we will store a converted_amount field, which is the amount converted to EUR at the time of the transaction.
Participant
| Field name | Type | Required | Description |
|---|---|---|---|
external_id | string | Yes | External identifier of the participant, it can match or not a customer already existing in Algoreg |
full_name | string | Yes | Full name of the participant, ignored if external_id matches a known customer |
account_type | string | Yes | “F” or “N”, Firm (F), Individual (N), ignored if external_id matches a known customer |
domicile_code | string | No | Country in ISO3 format, ex. FRA, ignored if external_id matches a known customer |
device | Device | No | Device used for the transaction, IP, browser, location etc |
payment_institution | PaymentInstitution | No | Payment institution (bank, VASP, etc) of the participant, see below |
payment_method | PaymentMethod | No | Payment method of the participant, see below |
More information can be added to a participant by using our general Customers api, any fields
Custom fields
You can define custom fields for transactions in the “Custom fields” page of the backoffice. They will be available when building rules and in the transaction details page.
Custom fields
Learn more about custom fields