Positive register: functional specification: Difference between revisions
No edit summary |
No edit summary |
||
(6 intermediate revisions by 2 users not shown) | |||
Line 9: | Line 9: | ||
= Definitions = | = Definitions = | ||
* '''Data''' – information about existing obligations of a private person that allows the Member to assess creditworthiness of the individual | * '''Data''' – information about existing obligations of a private person that allows the Member to assess creditworthiness of the individual. | ||
* '''Data exchange system''' – the IT solution used by the Member to exchange the Data; | * '''Data exchange system''' – the IT solution used by the Member to exchange the Data; | ||
* ''' | * '''Manager of the data exchange system''' – Creditinfo Eesti AS; | ||
* '''Codebtor''' – a private person together with whom the Applicant applies for credit and who is taken into account while making the Credit decision; | * '''Codebtor''' – a private person together with whom the Applicant applies for credit and who is taken into account while making the Credit decision; | ||
* '''Credit decision''' – the decision made by the Member with regard to concluding the Consumer credit contract with the Applicant; | * '''Credit decision''' – the decision made by the Member with regard to concluding the Consumer credit contract with the Applicant; | ||
Line 17: | Line 17: | ||
* '''Applicant''' – a private person who turns to the Member with the wish to conclude the Consumer credit contract and provides his/her Agreement for using the Data possessed by the Members; | * '''Applicant''' – a private person who turns to the Member with the wish to conclude the Consumer credit contract and provides his/her Agreement for using the Data possessed by the Members; | ||
* '''Guarantor''' – a person who assumes the obligation before the Member to be liable for performance of the Consumer credit contract obligations of the Applicant; | * '''Guarantor''' – a person who assumes the obligation before the Member to be liable for performance of the Consumer credit contract obligations of the Applicant; | ||
* ''' | * '''Consent '''– consent of the Applicant for providing the Member making the inquiry with the Data of the Members being the recipients of the inquiry; | ||
* '''Member''' – an Estonian | * '''Member''' – an Estonian that joins the Data exchange system and shares the Data about the Applicant with other Members; | ||
* '''Consumer credit contract''' – the contract on the basis of which the Member issues the credit to the Applicant; | * '''Consumer credit contract''' – the contract on the basis of which the Member issues the credit to the Applicant; | ||
* '''Subject''' – a party to the contract; | * '''Subject''' – a party to the contract; | ||
* '''Consumer credit''' – the credit issued to the Applicant by the Member. | * '''Consumer credit''' – the credit issued to the Applicant by the Member. | ||
* Users of the system are the Members. | = Business rules = | ||
* A Member must join X- | |||
* Users of the system are the ''Members''. | |||
* The Member inputs | * A ''Member'' must join X-road. | ||
* The Member updates the Data by sending to | * The ''Member'' inputs ''Data'' to the database of ''Data exchange system'' or provides ''Manager of the data exchange system'' with an IT-based solution to obtain the ''Data'' from him's database. | ||
* The Member updates the Data every 24 hours. | * The ''Member'' updates the ''Data'' by sending to the ''Data exchange system'' all current ''Data or Consumer credit contract data one by one''. | ||
* The Member | * The ''Member'' updates the ''Data'' every 24 hours. At least every 7 days. | ||
* | * The ''Member'' requests the ''Data'' only with the ''Applicant'' prior ''Consent''. If the ''Consent'' is not assigned digitally, then the requester has no permission to request ''Data'' from databases of other Members, who has a condition of existence of digitally signed ''Consent'' for data requesting and forwarding. | ||
* The | * The ''Consent'' document is stored in the ''Data exchange system'' for 3 years. | ||
* The response to the ''Data'' request does not reflect information about the ''Member''. | |||
* Composition of the | * Composition of the response to the ''Data'' request is described in “Data composition” chapter. | ||
* The ''Members'' share the ''Data'' with other Members in equal data composition. | |||
* The Members share the Data | |||
= Data composition= | = Data composition= | ||
# Date of updating; | # Date and time of updating data; | ||
# | # Person identity code; | ||
# Role of the person within the scope of the contract; | # Role of the person within the scope of the contract; | ||
# Contract number | # Contract number; | ||
# Type of consumer credit; | # Type of consumer credit; | ||
# Effective date of credit agreement – date of commencement of the Consumer credit contract; | # Effective date of credit agreement – date of commencement of the Consumer credit contract; | ||
# End date of credit – the date of repayment of the Consumer credit; | # End date of credit – the date of repayment of the Consumer credit; | ||
# Consumer credit sum – the maximum sum of the Consumer credit | # Consumer credit sum – the maximum sum of the Consumer credit paid or payable to the Applicant; | ||
# Currency – currency of the Consumer credit | # Currency – currency of the Consumer credit; | ||
# | # Schedule payments – the sum and the due date of the next or the closest three payments; | ||
# Balance – the amount of the obligation of the consumer before the Member; | # Balance – the amount of the obligation of the consumer before the Member; | ||
# Overdue balance – the sum of payments overdue for more than 7 days; | # Overdue balance – the sum of payments overdue for more than 7 days; | ||
# Requests – dates of requests made with regard to the Data of the Applicant made during the past three years. | # Requests – dates of requests made with regard to the Data of the Applicant made during the past three years. | ||
'''Roles of the person''' | |||
#Borrower | |||
#Codebtor | |||
#Guarantor | |||
'''Types of credit''' | |||
#Secured loan | |||
#Hire-purchase | |||
#Unsecured loan | |||
#Lease | |||
#Credit card | |||
#Other | |||
= Use cases = | = Use cases = | ||
[[File: | [[File:Positive register use cases.jpg]] | ||
== Members list request == | |||
'''Prerequisite:''' <u>Data exchange system manager</u> has given a permission to <u>Member</u> to make a request. | |||
Member requests the list of other Members for using it while consent document creation. | |||
== Consent document creation == | |||
'''Prerequisite:''' <u>Data exchange system manager</u> has given a permission to <u>Member</u> to make a request. | |||
Member requests the consent document of the Applicant for inquiring hims/hers Data possessed by the Members; | |||
== Credit report request == | |||
'''Prerequisite:''' <u>Data exchange system manager</u> has given a permission to <u>Member</u> to make a request. | |||
'''Prerequisite:''' If the consent document is an input of the request, this should had been generated in the Data exchange system. | |||
# Member sends a request to the Data exchange system to get Applicant's credit obligations; | |||
# Data exchange system queries the Data from the database; | |||
# Data exchange system responses to the requester with the Data. | |||
Extension | |||
* Member has a condition of existence of the digitally signed ''Consent'' for data requesting from repository and the digitally signed consent is not an input of the request | |||
::2a. Data Exchange System does not request the Data from Member's repository; | |||
::3a. Data Exchange System response includes information about undone request. | |||
* Data repository of the member is stored in Member's system | |||
::2a. Data exchange system queries the Data from Members' systems | |||
* Quering of the Data from Member's system fails | |||
::3a. Data exchange system responses to the requester with the Data and with the error message that includes the number of failed queries. | |||
== Credit data management == | |||
'''Prerequisite:''' <u>Data exchange system manager</u> has given a permission to <u>Member</u> to make a request. | |||
'''Prerequisite:''' The <u>Member</u> has concluded the authorization agreement with Data exchange system manager, under which the Member issues to Data exchange system manager the rights of authorized data processor with regard to the database held by the Member. | |||
The Member forwards credit data from the database held by the Member to Data exchange system. | |||
[[File:Credit data management use case.jpg]] | |||
'''Scenarios''' | |||
'''A)''' The <u>Member</u> forwards all current data on consumer credits to the Data exchange system. | |||
''' | '''B)''' The <u>Member</u> changes the consumer credit data in the Data exchange system database. | ||
== Manager data management == | |||
<u>Data exchange system manager</u> registers information about the Member in the Data exchange system / removes such information from the Data exchange system. | |||
= Sequence diagram = | = Sequence diagram = | ||
The following diagram describes the process of credit decision when | |||
::1. the Applicant signes the consent digitally | |||
::[[File:Credit decision using digi consent.jpg]] | |||
::2. the Applicant do not sign the consent digitally | |||
::[[File:Credit decision using digi consent.jpg]] | |||
= Links = | = Links = | ||
[[X-road interface | [[Data exchange system X-road interface|Data exchange system X-road interface]] |
Latest revision as of 12:45, 10 April 2017
eesti keeles |
Overview
The Positive Register (Positiivne Register) is the data exchange system, through which creditors that are members of the register are able to share information about person’s credit obligations with consent of the person in question. The Positive Register allows a creditor to fulfill statutory requirements of responsible lending and to ensure a person’s ability to fulfill his or her debt obligations. Loan applicants will no longer have to collect documents from other creditors. Customer will also be better protected from the problems associated with making emotional decisions about loans and excessive debts.
Definitions
- Data – information about existing obligations of a private person that allows the Member to assess creditworthiness of the individual.
- Data exchange system – the IT solution used by the Member to exchange the Data;
- Manager of the data exchange system – Creditinfo Eesti AS;
- Codebtor – a private person together with whom the Applicant applies for credit and who is taken into account while making the Credit decision;
- Credit decision – the decision made by the Member with regard to concluding the Consumer credit contract with the Applicant;
- Borrower – a private person to whom the Member issues the credit based on the Consumer credit contract;
- Applicant – a private person who turns to the Member with the wish to conclude the Consumer credit contract and provides his/her Agreement for using the Data possessed by the Members;
- Guarantor – a person who assumes the obligation before the Member to be liable for performance of the Consumer credit contract obligations of the Applicant;
- Consent – consent of the Applicant for providing the Member making the inquiry with the Data of the Members being the recipients of the inquiry;
- Member – an Estonian that joins the Data exchange system and shares the Data about the Applicant with other Members;
- Consumer credit contract – the contract on the basis of which the Member issues the credit to the Applicant;
- Subject – a party to the contract;
- Consumer credit – the credit issued to the Applicant by the Member.
Business rules
- Users of the system are the Members.
- A Member must join X-road.
- The Member inputs Data to the database of Data exchange system or provides Manager of the data exchange system with an IT-based solution to obtain the Data from him's database.
- The Member updates the Data by sending to the Data exchange system all current Data or Consumer credit contract data one by one.
- The Member updates the Data every 24 hours. At least every 7 days.
- The Member requests the Data only with the Applicant prior Consent. If the Consent is not assigned digitally, then the requester has no permission to request Data from databases of other Members, who has a condition of existence of digitally signed Consent for data requesting and forwarding.
- The Consent document is stored in the Data exchange system for 3 years.
- The response to the Data request does not reflect information about the Member.
- Composition of the response to the Data request is described in “Data composition” chapter.
- The Members share the Data with other Members in equal data composition.
Data composition
- Date and time of updating data;
- Person identity code;
- Role of the person within the scope of the contract;
- Contract number;
- Type of consumer credit;
- Effective date of credit agreement – date of commencement of the Consumer credit contract;
- End date of credit – the date of repayment of the Consumer credit;
- Consumer credit sum – the maximum sum of the Consumer credit paid or payable to the Applicant;
- Currency – currency of the Consumer credit;
- Schedule payments – the sum and the due date of the next or the closest three payments;
- Balance – the amount of the obligation of the consumer before the Member;
- Overdue balance – the sum of payments overdue for more than 7 days;
- Requests – dates of requests made with regard to the Data of the Applicant made during the past three years.
Roles of the person
- Borrower
- Codebtor
- Guarantor
Types of credit
- Secured loan
- Hire-purchase
- Unsecured loan
- Lease
- Credit card
- Other
Use cases
Members list request
Prerequisite: Data exchange system manager has given a permission to Member to make a request.
Member requests the list of other Members for using it while consent document creation.
Consent document creation
Prerequisite: Data exchange system manager has given a permission to Member to make a request.
Member requests the consent document of the Applicant for inquiring hims/hers Data possessed by the Members;
Credit report request
Prerequisite: Data exchange system manager has given a permission to Member to make a request.
Prerequisite: If the consent document is an input of the request, this should had been generated in the Data exchange system.
- Member sends a request to the Data exchange system to get Applicant's credit obligations;
- Data exchange system queries the Data from the database;
- Data exchange system responses to the requester with the Data.
Extension
- Member has a condition of existence of the digitally signed Consent for data requesting from repository and the digitally signed consent is not an input of the request
- 2a. Data Exchange System does not request the Data from Member's repository;
- 3a. Data Exchange System response includes information about undone request.
- Data repository of the member is stored in Member's system
- 2a. Data exchange system queries the Data from Members' systems
- Quering of the Data from Member's system fails
- 3a. Data exchange system responses to the requester with the Data and with the error message that includes the number of failed queries.
Credit data management
Prerequisite: Data exchange system manager has given a permission to Member to make a request.
Prerequisite: The Member has concluded the authorization agreement with Data exchange system manager, under which the Member issues to Data exchange system manager the rights of authorized data processor with regard to the database held by the Member.
The Member forwards credit data from the database held by the Member to Data exchange system.
Scenarios
A) The Member forwards all current data on consumer credits to the Data exchange system.
B) The Member changes the consumer credit data in the Data exchange system database.
Manager data management
Data exchange system manager registers information about the Member in the Data exchange system / removes such information from the Data exchange system.
Sequence diagram
The following diagram describes the process of credit decision when