Dictionaries

Dictionaries	Scope	Description
FTOS_BP_BankingProduct	Data	This entity holds the data defined in Product Factory and usually synchronized from Core Banking in order to know how to label the products received through APIs in a category or another. This enables later in the application to display specific information by type.
FTOS_BP_Category	Data	This entity holds the data of the banking product category to categorize the products in order to be able to treat correctly different types of accounts.
FTOS_BP_SubCategory	Data	This entity is responsible to keep all the data regarding the subcategory.
FTOS_CMB_AccountType	Data	This entity holds the data regarding the types of accounts, e.g., retail, legal entities.
FTOS_CMB_BulkFieldType	Parametrization	It is a parametrization entity that holds the types of bulk files that the Financial Institutions offers to its customers.
FTOS_CMB_BulkPaymentFormat	Parametrization	It is a parametrization entity that holds the types of files that a Financial Institution allows its users to upload bulk files for payments.
FTOS_CMB_Country	Data	This entity holds the data regarding the countries used for users registration, but also for some other small use cases in the application.
FTOS_CMB_Culture	Data	This entity holds the data regarding the culture.
FTOS_CMB_Currency	Data	This entity is an extension for FTOS_CMB_Currency, which contains the cut off time and the "FCY Payment Allowed" flag.
FTOS_IB _ParticipantBanksSchemas	Data	This dictionary holds the information related to the payment schemas that a beneficiary bank has implemented, thus, allowing to establish which schemas are available for the user to choose from.
FTOS_IB_BankAccountTransactionType	Parametrization
FTOS_IB_BankNameIBAN	Data	This dictionary holds the IBAN related data for financial institutions in SEPA and non-SEPA countries that have adopted IBAN.
FTOS_IB_BGBudgetDocumentTypes	Parametrization	This entity dictates which fields should be mandatory for a certain Budget Type payment and the corresponding document type.
FTOS_IB_BGBudgetRule	Parametrization	This entity dictates how a payment is identified as being a budget payment and which type of budget payment.
FTOS_IB_BICSWIFT	Data	This entity holds the data regarding the BIC A BIC (Bank Identifier Code) is the SWIFT Address assigned to a bank in order to send automated payments quickly and accurately to the banks concerned. It uniquely identifies the name and country, (and sometimes the branch) of the bank involved. and SWIFT The Swift Code (also known as SWIFT-BIC, BIC code or SWIFT ID) is needed every time you want to make an international money transfer. codes and the financial institutions. It helps validate the correct input of the BIC/SWIFT and also automatically fill in the Beneficiary Bank’s details in the Make a payment screen as explained in .
FTOS_IB_Category	Parametrization
FTOS_IB_CountryExt	Parametrization
FTOS_IB_CurrencyExt	Parametrization	It is a parametrization extension for FTOS_CMB_Currency that contains the cut off time and the "FCY Payment Allowed" flag. From this dictionary a Financial Institution can control which currencies they accept for international foreign currency. The information can be either parametrized at application level through dedicated screen for admin user in the Settings dashboard or syncronized from Core Banking through APIs.
FTOS_IB_HolidayCalendar	Data	This entity holds the data regarding the holiday calendar. The information sincronized from Core Banking in order for the application to know which dates to allow certain payment schemas to be initiated and processed.
FTOS_IB_IBANStructure	Data	This entity holds the data for the IBAN and how it must be structured. It holds the extensive rules for validating the IBANs and can easily be updated to support any information change and maybe new countries that would adhere to the IBAN standard.
FTOS_IB_InstantPymtErrorCodes	Data & Parametrization	It is both a data and parametrization entity that holds the status, code and message in case of an error for instant payments. It holds the messages for SEPA Instant Payments returned to the customer, as well as indication (parametrization) on how the system should treat the respective response code from the payment system.
FTOS_IB_PaymentCategory		This entity holds the data regarding the payment category available for a certain payment schema.
FTOS_IB_PaymentFieldLength	Parametrization	It is a parametrization entity that holds the values with the length of the editable fields from the Make a payment screen in . The length of each field from the payments screen can be controlled from this screen. The default value cover the standards of SEPA payment fields, but each Core Banking might have different field lenghts for certain schema types and the Financial Institution can set up this without any code modification.
FTOS_IB_PurposeOfPayment	Data	This entity holds the purpose available for a certain payment schema type.
FTOS_IB_PymtTypes	Parametrization	It is a parametrization entity that holds the option set values for a certain payment, and enables to add certain codes that might be required to be synchronized in the financial institution’s Core Banking. It keeps the payment schemas, applicability for the financial institution, cut-off times for each schema, naming and more.
FTOS_IB_SecurityProfilesid	Parametrization	This entity holds the financial limits. Each financial institution can define its security profiles (e.g. retail, retail opened online (no visit to the branch with the exception of KYC, SME, Corporate, etc.) and set up the limits (per transaction, per week, per month, per week and over each channel - online/mobile).
FTOS_IB_SubCategoryExt	Parametrization	It is a parametrization entity that enables the Financial Institution to set up for which type of accounts the balances to be added in the total balance presented in the Homepage, which types of accounts allow statement generation.
FTOS_IB_TypeOfRole		This entity holds the data regarding the types of roles (Viewer, Initiator and Authorizer). These can be customized as per the need of any financial institution.
FTOS_IB_TypeOfRoleTransactions	Parametrization	It is a parametrization entity that holds the data regarding the transaction types and the types of roles. For the defined type of roles (e.g., Viewer, Initiator, Authorizer) a Financial Insitution can map as a parametrization which Transaction Types (e.g: Viewer -> Account Balance & Transactions + Account Statement; Authorizer -> Account Balanace & Transactions +Account Statment + Iniitiate payments + Own Account transfer + Domestic Transfer + etc.) to be automatically granted in the Back-Office Administration.
FTOS_IB_Utility3rdPartyPaymentProvider	Data	This entity holds the data regarding the third party payment provider. If there are multiple providers, they can be defined here.
FTOS_IB_Utility3rdProviderBankAccount	Data	This entity holds the data regarding the third party provider bank account to which the bill payments are initiated. They are usually internal account in the financial institution.
FTOS_IB_UtilityPaymentService	Data	This entity holds the utility service data (e.g., gas, electricity, telco, etc.). If a 3rd party is involved, then the information is brought from an integration or if no third party is involved, then it can be either synchronized from the Core Banking or other application of the financial institution or manually inputted and administrated.
FTOS_IB_UtilityPaymentServiceProvider	Data	This entity holds the data regarding the service provider. One provider can cover multiple services. This connects the providers with the services they offer.
FTOS_IB_UtilityServiceProvider	Data	This entity holds the data regarding the service provider either from the integration or manually inserted.

FTOS_BP_BankingProduct

Data

This entity holds the data defined in Product Factory and usually synchronized from Core Banking in order to know how to label the products received through APIs in a category or another. This enables later in the application to display specific information by type.

FTOS_BP_Category

Data

This entity holds the data of the banking product category to categorize the products in order to be able to treat correctly different types of accounts.

FTOS_BP_SubCategory

Data

This entity is responsible to keep all the data regarding the subcategory.

FTOS_CMB_AccountType

Data

This entity holds the data regarding the types of accounts, e.g., retail, legal entities.

FTOS_CMB_BulkFieldType

Parametrization

It is a parametrization entity that holds the types of bulk files that the Financial Institutions offers to its customers.

FTOS_CMB_BulkPaymentFormat

Parametrization

It is a parametrization entity that holds the types of files that a Financial Institution allows its users to upload bulk files for payments.

FTOS_CMB_Country

Data

This entity holds the data regarding the countries used for users registration, but also for some other small use cases in the application.

FTOS_CMB_Culture

Data

This entity holds the data regarding the culture.

FTOS_CMB_Currency

Data

This entity is an extension for FTOS_CMB_Currency, which contains the cut off time and the "FCY Payment Allowed" flag.

FTOS_IB _ParticipantBanksSchemas

Data

This dictionary holds the information related to the payment schemas that a beneficiary bank has implemented, thus, allowing to establish which schemas are available for the user to choose from.

FTOS_IB_BankAccountTransactionType

Parametrization

FTOS_IB_BankNameIBAN

Data

This dictionary holds the IBAN related data for financial institutions in SEPA and non-SEPA countries that have adopted IBAN.

FTOS_IB_BGBudgetDocumentTypes

Parametrization

This entity dictates which fields should be mandatory for a certain Budget Type payment and the corresponding document type.

FTOS_IB_BGBudgetRule

Parametrization

This entity dictates how a payment is identified as being a budget payment and which type of budget payment.

FTOS_IB_BICSWIFT

Data

This entity holds the data regarding the BIC

A BIC (Bank Identifier Code) is the SWIFT Address assigned to a bank in order to send automated payments quickly and accurately to the banks concerned. It uniquely identifies the name and country, (and sometimes the branch) of the bank involved. and SWIFT

The Swift Code (also known as SWIFT-BIC, BIC code or SWIFT ID) is needed every time you want to make an international money transfer. codes and the financial institutions. It helps validate the correct input of the BIC/SWIFT and also automatically fill in the Beneficiary Bank’s details in the Make a payment screen as explained in .

FTOS_IB_Category

Parametrization

FTOS_IB_CountryExt

Parametrization

FTOS_IB_CurrencyExt

Parametrization

It is a parametrization extension for FTOS_CMB_Currency that contains the cut off time and the "FCY Payment Allowed" flag. From this dictionary a Financial Institution can control which currencies they accept for international foreign currency. The information can be either parametrized at application level through dedicated screen for admin user in the Settings dashboard or syncronized from Core Banking through APIs.

FTOS_IB_HolidayCalendar

Data

This entity holds the data regarding the holiday calendar. The information sincronized from Core Banking in order for the application to know which dates to allow certain payment schemas to be initiated and processed.

FTOS_IB_IBANStructure

Data

This entity holds the data for the IBAN and how it must be structured. It holds the extensive rules for validating the IBANs and can easily be updated to support any information change and maybe new countries that would adhere to the IBAN standard.

FTOS_IB_InstantPymtErrorCodes

Data & Parametrization

It is both a data and parametrization entity that holds the status, code and message in case of an error for instant payments. It holds the messages for SEPA Instant Payments returned to the customer, as well as indication (parametrization) on how the system should treat the respective response code from the payment system.

FTOS_IB_PaymentCategory

This entity holds the data regarding the payment category available for a certain payment schema.

FTOS_IB_PaymentFieldLength

Parametrization

It is a parametrization entity that holds the values with the length of the editable fields from the Make a payment screen in . The length of each field from the payments screen can be controlled from this screen. The default value cover the standards of SEPA payment fields, but each Core Banking might have different field lenghts for certain schema types and the Financial Institution can set up this without any code modification.

FTOS_IB_PurposeOfPayment

Data

This entity holds the purpose available for a certain payment schema type.

FTOS_IB_PymtTypes

Parametrization

It is a parametrization entity that holds the option set values for a certain payment, and enables to add certain codes that might be required to be synchronized in the financial institution’s Core Banking. It keeps the payment schemas, applicability for the financial institution, cut-off times for each schema, naming and more.

FTOS_IB_SecurityProfilesid

Parametrization

This entity holds the financial limits. Each financial institution can define its security profiles (e.g. retail, retail opened online (no visit to the branch with the exception of KYC, SME, Corporate, etc.) and set up the limits (per transaction, per week, per month, per week and over each channel - online/mobile).

FTOS_IB_SubCategoryExt

Parametrization

It is a parametrization entity that enables the Financial Institution to set up for which type of accounts the balances to be added in the total balance presented in the Homepage, which types of accounts allow statement generation.

FTOS_IB_TypeOfRole

This entity holds the data regarding the types of roles (Viewer, Initiator and Authorizer). These can be customized as per the need of any financial institution.

FTOS_IB_TypeOfRoleTransactions

Parametrization

It is a parametrization entity that holds the data regarding the transaction types and the types of roles. For the defined type of roles (e.g., Viewer, Initiator, Authorizer) a Financial Insitution can map as a parametrization which Transaction Types (e.g: Viewer -> Account Balance & Transactions + Account Statement; Authorizer -> Account Balanace & Transactions +Account Statment + Iniitiate payments + Own Account transfer + Domestic Transfer + etc.) to be automatically granted in the Back-Office Administration.

FTOS_IB_Utility3rdPartyPaymentProvider

Data

This entity holds the data regarding the third party payment provider. If there are multiple providers, they can be defined here.

FTOS_IB_Utility3rdProviderBankAccount

Data

This entity holds the data regarding the third party provider bank account to which the bill payments are initiated. They are usually internal account in the financial institution.

FTOS_IB_UtilityPaymentService

Data

This entity holds the utility service data (e.g., gas, electricity, telco, etc.). If a 3rd party is involved, then the information is brought from an integration or if no third party is involved, then it can be either synchronized from the Core Banking or other application of the financial institution or manually inputted and administrated.

FTOS_IB_UtilityPaymentServiceProvider

Data

This entity holds the data regarding the service provider. One provider can cover multiple services. This connects the providers with the services they offer.

FTOS_IB_UtilityServiceProvider

Data

This entity holds the data regarding the service provider either from the integration or manually inserted.