Customer file descriptions
Customer file
| Field Name | Field Type | Mandatory | Details |
|---|---|---|---|
| REPORTING_DATE | DATE | Yes | YYYY-MM-DD.The data has been extracted end of day of this date. Files are provided next day. |
| INSTITUTION_ID | NUMBER(6,0) | Yes | The institution ID setup in Enfuce Payment Platform, “Branch code” in API. |
| ADD_INFO | VARCHAR2(3900) | No | Additional field which contains miscellaneous data of the customer. Data is marked with tags. Contact Enfuce for tags relevant to you. |
| ID | NUMBER(18,0) | No | |
| BRANCH_ID | NUMBER(18,0) | Yes | Foreign key to Customer. Enfuce payment platform generated id for the customer, customerId in API calls |
| CUSTOMER_REG_NO | VARCHAR2(32) | YES* | *Mandatory if agreed to be included in files, otherwise, this field is always empty. |
| CUSTOMER_NUMBER | VARCHAR2(255) | Yes | |
| CUSTOMER_CATEGORY | VARCHAR2(16) | Yes | Possible values: Private, Corporate |
| COMPANY_NAME | VARCHAR2(255) | No | |
| CREATION_DATE | DATE | Yes | YYYY-MM-DD. Date when the customer was created. |
| DECEASE_DATE | DATE | No | YYYY-MM-DD. |
| FIRST_NAME | VARCHAR2(255) | No | |
| LANGUAGE | VARCHAR2(32) | No | ISO 639-2/B |
| LAST_NAME | VARCHAR2(255) | No | |
| RECORD_DATE_FROM | DATE | Yes | YYYY-MM-DD. Date from which record version is effective |
| RECORD_DATE_TO | DATE | Yes | YYYY-MM-DD. Expiry date of record version effective term |
| BANK_OFFICER_ID | NUMBER | No | Latest officer that updated the record. |
Customer Address
| Field Name | Field Type | Mandatory | Details |
|---|---|---|---|
| REPORTING_DATE | DATE | Yes | YYYY-MM-DD.The data has been extracted end of day of this date. Files are provided next day. |
| INSTITUTION_ID | NUMBER(6,0) | Yes | The institution ID setup in Enfuce Payment Platform, “Branch code” in API. |
| ID | VARCHAR2(32) | Yes | Foreign key to Customer. Enfuce payment platform generated customer ID, customerId in API calls. |
| BRANCH_ID | NUMBER(18,0) | Yes | Foreign key to Customer. Enfuce payment platform generated id for the customer, customerId in API calls |
| CUSTOMER_NUMBER | VARCHAR2(255) | Yes | Foreign key to Customer |
| CUSTOMER_REG_NO | VARCHAR2(32) | No | |
| NAME | VARCHAR2(255) | Yes | Possible values: Statement |
| CODE | VARCHAR2(32) | Yes | Possible values: STMT |
| ADDRESS_LINE_1 | VARCHAR2(255) | No | |
| ADDRESS_LINE_2 | VARCHAR2(255) | No | |
| ADDRESS_LINE_3 | VARCHAR2(255) | No | |
| ADDRESS_LINE_4 | VARCHAR2(255) | No | |
| ADDRESS_ZIP | VARCHAR2(32) | No | |
| REGION_CODE | VARCHAR2(32) | No | |
| STATE | VARCHAR2(32) | No | |
| CITY | VARCHAR2(32) | No | |
| COUNTRY | VARCHAR2(32) | No | ISO 3166-1 Alpha-3 code |
| DATE_FORM | DATE | No | |
| DATE_TO | DATE | No | |
| E_MAIL | VARCHAR2(255) | No | |
| PHONE1 | VARCHAR2(32) | No | |
| PHONE2 | VARCHAR2(32) | No | |
| RECORD_DATE_FROM | DATE | Yes | YYYY-MM-DD. Date from which record version is effective |
| RECORD_DATE_TO | DATE | No | YYYY-MM-DD. Expiry date of record version effective term |
Customer Properties
| Field Name | Field Type | Mandatory | Details |
|---|---|---|---|
| REPORTING_DATE | DATE | Yes | YYYY-MM-DD.The data has been extracted end of day of this date. Files are provided next day. |
| INSTITUTION_ID | NUMBER(6,0) | Yes | The institution ID setup in Enfuce Payment Platform, “Branch code” in API. |
| ID | VARCHAR2(32) | Yes | Foreign key to Customer. Enfuce payment platform generated customer ID, customerId in API calls. |
| CUSTOMER_NUMBER | VARCHAR2(255) | Yes | Foreign key to Customer |
| CUSTOMER_REG_NO | VARCHAR2(32) | No | Foreign key to Customer |
| VALUE_DATE_FROM | DATE | Yes | YYYY-MM-DD. Date when the property was applied. |
| VALUE_DATE_TO | DATE | Yes | YYYY-MM-DD. YYYY-MM-DD. Expiry date of the applied property. |
| DETAILS | VARCHAR2(3900) | No | Original message received. Can include for example the source (API), timestamp and bank date |
| PROPERTY_TYPE_NAME | VARCHAR2(255) | Yes | See possible values and descriptions from below table. |
| PROPERTY_TYPE_CODE | VARCHAR2(32) | Yes | See possible values and descriptions from below table. |
| PROPERTY_VALUE_NAME | VARCHAR2(255) | Yes | See possible values and descriptions from below table. |
| PROPERTY_VALUE_CODE | VARCHAR2(32) | Yes | See possible values and descriptions from below table. |
Customer properties - names and codes
| PROPERTY_TYPE_NAME | PROPERTY_TYPE_CODE | PROPERTY_VALUE_NAME | PROPERTY_VALUE_CODE | Description |
|---|---|---|---|---|
| Client Locale | CLIENT_LOCALE | As per ISO 639-1 | ISO 639-1 and ISO 3166-1 alpha-2 Example_ en_G | Indicating the customer locale as set by issuer. |
| Client Classification | CLIENT_CLASS | Staff – Regular | STAFF – REGULAR | Indicating the customer classifier if set by issuer. |