Data Transfer Process
Our preferred data transfer process:
-We will get in touch with your old provider and provide them with a Public Encryption Key.
-Your old provider will encrypt the data with our encryption Key and load the data to Till's SFTP server.
-We will perform the data import.
-Once the import is complete, we will provide you with a newline-delimited JSON, with each line containing the old and the new reference ID of one card.
Sample:
{ “newReferenceId”: ”abcdefghijklmnopqr”, ”oldReferenceId”: “388333B”, customerId: “AT-2938938” }
{ “newReferenceId”: ”8291edi3ndidn393un”, ”oldReferenceId”: “7837373”, customerId: “DE-3838832” }Data Format
The data shall be provided in CSV or JSON with UTF-8 encoding. The provided data must follow the following conventions. Data provided in a different format may cause importing delays. The encrypted file may not exceed the file size of 25 Megabytes. Please split the file into several chunks if it exceeds the file size limit.
| CSV | JSON |
|---|---|
| Text qualifier or encapsulation: none or " Delimiter or field separator: , (comma) or ; (semicolon) A header column which identifies each field must be included. | Newline-delimited JSON (one valid JSON per line) http://jsonlines.org The Key of each field shall match the field names of the tables below, we don’t support nested JSON, data must be provided as String types only. |
The following data fields can be imported during the data transfer processes. Please include the field name in the data migration file:
Required fields
| Field name | Description | Example |
|---|---|---|
| creditcard.number | The primary Account number (PAN) of the card | 4111111111111111 |
| creditcard.expiration_month | The Credit Card's expiration month in the format: M or MM | 1 (M) 01 (MM) |
| creditcard.expiration_year | The Credit Card's expiration year (YYYY) | 2020 |
| reference_id | ID or token representing this card to the Merchant in the former processors system | 83389B |
Optional Fields
| Field name | Description | Example |
|---|---|---|
| creditcard.cardholder_name | The cardholder name of the card (technically this is optional, but usually you will want to know the cardholder name) | John Smith |
| customer.identification | Any Identification representing the User or customer in your shop or ERP system (max. 36 characters, anything beyond is cut off) | AT-2938938 |
| customer.first_name | First name of the customer | John |
| customer.last_name | Last name of the customer. | Smith |
| customer.billing_address1 | Street address line 1 | Shortroad 33 |
| customer.billing_address2 | Street address line 2 | Unit A |
| customer.billing_city | City | Vienna |
| customer.billing_postcode | Postal Code / Zip code | 1060 |
| customer.billing_state | State | Vienna |
| customer.billing_country | 2-letter country code | AT |
| customer.billing_phone | Phone number | +431555000 |
| customer.company | The company associated with the billing address | Example Inc. |
| customer.email | E-mail address of the customer | john.smith@example.org |
| customer.ip_address | IP address of the customer | 1.2.3.4 |
| customer.national_id | The national ID (e.g. social insurance number) of the customer | AT39398881 |
| customer.gender | either M for male or F for female | M |