TMS import

⚠️ Before you start, please read the prerequisites for depositing files on our SFTP server.

🔐 Create a valid SSH key 

⚠️ We use the AWS managed service Transfer Family for SFTP deposits, and it only accepts ssh1.

You can follow this documentation to create a valid SSH key on Windows, Mac, and Linux: 

Generating a new SSH key and adding it to the ssh-agent - GitHub Docs.

🗄️ SFTP Connection 

Here is the information needed to connect to your SFTP deposit:

📘 Data Formatting

Transactional data must:

• be in .csv format, using a comma , as the separator
• have a filename that does not contain spaces; use underscores _ instead
• adhere to the following data schema:

AMLF_KYC_ID 

• Identifier for a KYC file within AMLF 
• type: string 
• required

LABEL 

• A label to categorize the data 
• type: string

SOURCE 

• A label representing the data source (product, etc.) 
• type: string

CLIENT_ID 

• Unique client identifier (id, email, iban, etc.) 
• type: string

CLIENT_TYPE 

• Identifier for the client type (individual, company, sole proprietorship, etc.) 
• type: string

CLIENT_GEO 

• Residence, legal address, or nationality in ISO 3166-1 alpha-2 format 
• type: string: ISO 3166-1 alpha-2

CLIENT_ACCOUNT_ID 

• Client's account number (or equivalent) (id, iban, credit card, etc.) 
• type: string

CLIENT_ACCOUNT_GEO 

• Bank location of the account or card in ISO 3166-1 alpha-2 format 
• type: string: ISO 3166-1 alpha-2

COUNTERPARTY_ID 

• Unique identifier of the transaction counterparty (id, iban, email, etc.) 
• type: string

COUNTERPARTY_TYPE 

• Identifier for the counterparty type (individual, company, sole proprietorship, etc.) 
• type: string

COUNTERPARTY_GEO 

• Counterparty's residence, legal address, or nationality in ISO 3166-1 alpha-2 format 
• type: string: ISO 3166-1 alpha-2

COUNTERPARTY_ACCOUNT_ID 

• Counterparty's account number (or equivalent) (id, iban, credit card, etc.) 
• type: string

COUNTERPARTY_ACCOUNT_GEO 

• Bank location of the counterparty's account or card in ISO 3166-1 alpha-2 format 
• type: string: ISO 3166-1 alpha-2

TRANSACTION_ID 

• Unique transaction ID (if unavailable, AML Factory will generate an md5 hash of the row) 
• type: string 
• required

TRANSACTION_DATE 

• Transaction date in ISO 8601 (UTC) format 
• type: Date: ISO 8601 required

TRANSACTION_TYPE 

• Transaction type (service, instrument, etc.) 
• type: string 
• required

TRANSACTION_CURRENCY_A 

• Transaction currency ISO 4217 text (e.g., EUR) 
• type: string: ISO 4217 
• required

TRANSACTION_AMOUNT_A 

• Original transaction amount, in standard format (e.g., 10000) 
• type: number 
• required

TRANSACTION_CURRENCY_B 

• Transaction currency ISO 4217 text (e.g., EUR) 
• type: string: ISO 4217 
• required

TRANSACTION_AMOUNT_B 

• Original transaction amount, in standard format (e.g., 10000) 
• type: number 
• required

TRANSACTION_DIRECTION 

• Transaction direction (credit = IN, debit = OUT) 
• type: string: [IN,OUT] 
• required