Security Roles

FintechOS security architecture is a unified security design aimed at empowering FintechOS clients to address the necessities and potential risks involved in a certain scenario or environment. The Security Roles are an inbuilt part of the Core DPA Platform security architecture, designed to help you mitigate cybercrime-related risks and keep data secure across all your business flows. Consequently, you use Security Roles to protect sensitive data and configure various organization layers to allow for better communication, collaboration, or reporting.

On top of the platform's default security roles, the Billing and Collection solution comes with three pre-defined Security Roles which allow you to:

• Control the level of user access to various actions, functions or operations.

• Maintain compliance with security standards with regard to processing sensitive information.

• Safeguard end-to-end ownership over your billing and collection operations.

The following are the defined security roles for the Billing and Collection solution:

Security role	Description
Operations user	This is the user role for performing imports in the system. For example you use this role for uploading bank statements, notification files from online payment processors and direct debit notification or instruction files. Please see the table below for the available access privileges for this user role.
Operations superUser	This is the user role for operating with payment data. For example you use this role for allocating or deallocating payments, initiating outgoing payment requests, or delete installments. Please see the table below for the available access privileges for this user role.
Operations manager	This is the user role for approving payment requests. Please see the table below for the available access privileges for this user role.

 

The following are the defined security privileges per every role:

Functionality	Operations User	Operations SuperUser	Operations Manager	Operation
Invoices
	x	x	x	V View
				I (Insert)
		x		E (Edit)
Installments
	x	x	x	V
				I
		x		E - can remove installment
Premiums collected - Payments
	x	x	x	V
	x	x		I
		x		E
Bank statements
	x	x	x	V
	x			I
				E
Payments - Incoming and Outgoing
	x	x	x	V
	x	x		I
		x		E
Payment returns and Unallocated payments
		x	x	V
		x		I
		x		E
Outgoing Payment Request Approval
			x	V
			x	I
			x	E
Payments Allocation
	x	x	x	V
		x		I
		x		E
Outgoing Payment Requests
	x	x	x	V
		x		I
		x		E
DIDE Mandates
	x		x	V
	x			I
	x			E
DIDE Notification file
	x		x	V
	x			I
				E
DIDE Payment Instructions file
	x		x	V
				I
				E
DIDE Payment Confirmations
	x		x	V
	x			I
				E
DIDE Payment Denied
	x		x	V
	x			I
				E

For the UK flow:

Security role	Description
Operations user	This user has the rights to see the DIDE files (External Reports) menu, lists and forms, also having the possibility to import new files: ADDACS and ARUDD files. FTOS_PYMT_ADDACSReasonType - read FTOS_PYMT_DIDE_ADDACSDetail - read FTOS_PYMT_DIDE_ADDACS - crate, read, update FTOS_PYMT_ARUDD - create, read, update FTOS_PYMT_ARUDDDetail - create, read, update FTOS_PYMT_DIDEMandateInstruction - read FTOS_PYMT_DIDEMandateInstructionDetail - read FTOS_DFP_FlowSettings - read
Operations manager	View rights for all new DIDE entities: FTOS_PYMT_ADDACSReasonType - read FTOS_PYMT_DIDE_ADDACSDetail - read FTOS_PYMT_DIDE_ADDACS - read FTOS_PYMT_ARUDD - read FTOS_PYMT_ARUDDDetail - read FTOS_PYMT_DIDEMandateInstruction - read FTOS_PYMT_DIDEMandateInstructionDetail - read