enc_U2FsdGVkX19MhQKDhhfecL7Zg0YtmHQ3P42RUnEmee7qhokoFRW682ek46LnjPid_enc

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

enc_U2FsdGVkX1/cedTD+Zih1f1QbVn/nLWmYLVeA/mJRls=_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_U2FsdGVkX1+FCQ0rDfECgFBZ/dwbuhNOV6/BiIOod3eaUM2ytmKs18bFmkpi8Zb5T8uFyevM/CHY4VC9wb4A5gDFwBb08y0vsxX/S+qEb0I=_enc
Field nameTypeRequiredDescription
blockchainstringNo(Crypto only) Specify network where token was exchanged, ex. "AVAX" or "ETH"
txhashstringNo(Crypto only) Fingerprints of the transaction, ex. "0x1234"

enc_U2FsdGVkX18aPQTm5Z4cNktt5X6TZGy3ZRhYJUL1Tnc=_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_U2FsdGVkX18Dve3J0CAcD2Ikei8CU2TMmu1sNY0I5nXbdHVZPnCU2hTfoDCs8MDRnJF0OyHvGuNBjsxCaERKLl7F4yeJym9kqDegrX0R6uTg3nxXlj1fRSzU3EZC4uJf_enc enc_U2FsdGVkX1+yCjgFHEfCa+U6B9SjZy0SMrw7qpVSQvMj+76wmtUo+848OtcPO0cw_enc
Field nameTypeRequiredDescription
fingerprintstringNoDevice fingerprint
user_agentstringNoUser agent of the device, ex. Mozilla/5.0 ...
languagestringNoAccepted language, ex. en
geolocationstringNoGeolocation in this format: lat;lon;accuracy_km
countrystringNoCountry in ISO3 format, ex. FRA
ipstringNoIP address of the device, ex. 1.2.3.4
session_idstringNoSession identifier, ex. 1234
session_durationnumberNoSession lifetime in ms, ex. 127 means a very rapid session
3dsbooleanNo3DS authentication enabled or not, ex. true
2fabooleanNo2FA authentication enabled or not, ex. true
Field nameTypeRequiredDescription
external_idstringNoIf defined, we will match the institution to a customer defined in Algoreg
codestringNoCode the payment institution, BIC for instance
namestringNoName of the payment institution, ex. BNP Paribas
countrystringNoCountry in ISO3 format, ex. FRA
Field nameTypeRequiredDescription
typestringNoType of the payment method, ex. card, crypto, bank, exchange
codestringNoCode of the payment method, ex. IBAN for bank, hash of the card for card, wallet address for crypto, or crypto pair for exchange
countrystringNoIssuing country in ISO3 format, ex. FRA

enc_U2FsdGVkX19Dm0gqWxn1lo+2wPgX2u2j4ZurBzvH+As=_enc

You can define custom fields for transactions in the “Custom fields” page of the backoffice. enc_U2FsdGVkX19JW089Fv9bYdSrdQUFAG6AX+dIa4Z55jkOUABSm9SHN38NSmnocgVq8UyzG0jTMrMcQlZ4RzvZ3ZhbPOeRnYKDHIYnxGuwBu0h+UIWOYM52va60wfWSjwt_enc

Custom fields

enc_U2FsdGVkX194YiIWqfK8PlBzB3Kq9b12uTrj4JE43gqw9Uc1WCBQ8wKSkWMIYcp907wbf3Cfasewg5PNLeiPtw==_enc