enc_U2FsdGVkX1+EvLby4NyGFQOPF1fJiIQ/5sQPO9wGDp6QQbnJroGxzLgnNF2yq5Mp_enc

By default, any transaction submitted to Go!KYT supports the following information:

enc_U2FsdGVkX1+/wiItsbHC4dR3Pp71/1JJ8P79Ui7Zfws=_enc

Field nameTypeRequiredDescription
external_idstringYesYour unique identifier of the transaction
datestringYesDate of the transaction in ISO format (2023-07-05T08:18:05.661Z)
fromParticipantYesSender of the transaction
toParticipantYesReceiver of the transaction
amountstringYesAmount of the transaction converted to string, ex. "0.01233110"
currencystringYesCurrency of the transaction, ex. "BTC" or "EUR"
cryptoCryptoNo(Crypto only) Specify additional information about a crypto transaction
commentstringNoComment for this transaction
fieldsobjectNoCustom fields for this transaction, key-value object, see ‘custom fields’ section
review_groupsstringNoReview 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_U2FsdGVkX186Y9UVoSZzPKP7492SltFBJdsE36vithLzRnqwo2gQhGyQPYhQoUM1hSavScugKSjlPe8oNWfsAxlBniW5oGuRv2XEwhrYEic=_enc

enc_U2FsdGVkX19Jw5SJT1lCuCps5A7n/dGYdlOMx8OcNGA=_enc

Field nameTypeRequiredDescription
external_idstringYesExternal identifier of the participant, it can match or not a customer already existing in Algoreg
full_namestringYesFull name of the participant, ignored if external_id matches a known customer
account_typestringYes”F” or “N”, Firm (F), Individual (N), ignored if external_id matches a known customer
domicile_codestringNoCountry in ISO3 format, ex. FRA, ignored if external_id matches a known customer
deviceDeviceNoDevice used for the transaction, IP, browser, location etc
payment_institutionPaymentInstitutionNoPayment institution (bank, VASP, etc) of the participant, see below
payment_methodPaymentMethodNoPayment method of the participant, see below
enc_U2FsdGVkX1+CWTBtbtLQVXd4mMxZqULlJ1bIqfs0RDuLrMJ4VLFCSDXNUAuLLaFWtbNdAGre8oDE0EofgjpULVUpcIcgmDVLS0jmFn2qmXVTEy/mB9+Mdz4IBQEi/At+_enc enc_U2FsdGVkX1/VI6U7hrFFCyWncjvZUatSNunL1YNRSkF1zXjLj4B9ZqZXNn6bsaen_enc

enc_U2FsdGVkX1/Pqk6gA5b6BWi/gDwGWsg6413yWBpefG0=_enc

You can define custom fields for transactions in the “Custom fields” page of the backoffice. enc_U2FsdGVkX19pWC+WuBUrmP0TE+Zh8df0CIG/oxS9ntBZOOOAx3f7hNFVhjAd39kPdxQ1up1ehI2TH+5dGNjti24wfjhmY1agwpv0CrTBEIXq/NYPiIOAbD2Z1xj8q9pp_enc

Custom fields

enc_U2FsdGVkX1/ZIBpnQsc3ocdNCkfDT41j3lMerNvjHjuSl82Ksz4FTRQ1kiSj43e/mlKp0upy7iPIJOIh5YhfNA==_enc