Supported fields
enc_U2FsdGVkX1/Z9N4BekJezfhQVOP2gmbJ9MpqRI/GnKKc0eUqDN/mD7IfuOn2TIJA_enc
By default, any transaction submitted to Go!KYT supports the following information:
enc_U2FsdGVkX18X25S/SbWUuoBzX2zKM/c74BDToVlSw/E=_enc
| 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 enc_U2FsdGVkX19rrZXNa/CgoMOVJbdNRJOCKLXCVXAa+HDmBVs+nowCpuovvoMbO5IQpL8LyZWDiBwIBhLjfNi5JRfxykfeyQWSy9ogrSlQSUI=_enc
enc_U2FsdGVkX1/vkpKGB1yGpl8PvzRujjq/rf3v8R4zIpE=_enc
| 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 |
enc_U2FsdGVkX1/QRwkdbyfNY8EKurmiIsPvIQ591xP7msxuyUIlJYvubacg+4W+x+uxyBnu9HkDoaa52HwgnhMWaLYsZxZUuUuCq83a1lcWBOWVjx0owGthoCwy14AhpcYq_enc enc_U2FsdGVkX1/OcCp/7Xfm9BzFLegTo0eufePzmwCoFKUVx8ZYMXlftDnmdEN6bDfK_enc
enc_U2FsdGVkX19TPt8TTzCHkwmW05i/VMOSR1vR13QFSTU=_enc
You can define custom fields for transactions in the “Custom fields” page of the backoffice. enc_U2FsdGVkX1+LXRfmH+h/LkZNfClCnPt3ZISBrWcspye/iqdtvZLAQvRP6Kjswc1OrDumccIUJ6g4OPxdjTKKBCNL8tSMaws3isg7owerjmT8WzdjiZjpN+E6b94qagJf_enc
Custom fields
enc_U2FsdGVkX1/zeIdzCziGVQKzXasT8PFnfY5M8srpw1leKtoDaoMyy42Ndtdokvl08UNicQcLTowtUTTScw/f5A==_enc