D1.6 Incorrect Payments Data

Header Image
Project:
D1.6 Incorrect Payments Data : Public <<FRAME_Datastore>> FRAME_Datastore
Created: 24.10.2019 12:47:06
Modified: 10.09.2021 10:38:52
Project:
Advanced:
This Data Store shall be used within the Provide Electronic Payments Facilities Functional Area.  It shall contain information objects that provide details of the incorrect payments that have been detected and recorded plus a list of accounts from which these payments were attempted to be made, i.e. a "black list" of users.<br/><br/>The incorrect payments (i.e. failure by the user to provide the correct payment that is required for the service) shall be those that have been detected through the use of services paid by electronic means.  The information objects shall contain the following data objects:<br/><br/>(1) Date of incorrect payment detection (date string),<br/>(2) Date of message to enforcement bodies (date string),<br/>(3) Location at which the incorrect payment was made (characters and/or numbers, e.g. GPS/Galileo data),<br/>(4) User ID, if identified (number),<br/>(5) Service ID (number),<br/>(6) What made the payment incorrect (characters - descriptive text),<br/>(7) If overdraft account:<br/>    (7a) Account ID (number),<br/>    (7b) Amount of overdraft (number - in currency),<br/>    (7c) Access control systems breaching, ID of these systems (number),<br/>    (7d) Result (user blocked / user passing through) (characters).<br/><br/>The "black list" of users shall identify those who have made a payment that is incorrect in some way, e.g. non-payment. Their structure within this part of the Data Store shall be as follows:<br/>- User ID (number),<br/>- What made the payment incorrect (characters - descriptive text)?<br/><br/>Note that it shall be possible for there to be more than one incorrect payment that has been made by each user in the black list.<br/>
  • Associations To
  • Associations From
  • Tagged Values
  • Advanced
Element Source Role Target Role
«FRAME_High_Level_Data_Flow» pepf_incorrect_payment_input
FRAME_High_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» pepf_incorrect_payment_history
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» pepf_black_list
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» pepf_incorrect_payment_notification_L2
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» pepf_black_list_update
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» pepf_incorrect_payment_notification_L1
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» pepf_black_list_request
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_High_Level_Data_Flow» pepf_incorrect_payment_output
FRAME_High_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
Tag Value
DataStore_SecurityLevel None
Details:
Default: None
isUnlimited false
Details:
Values: true,false
Default: false
itemKind Information
Details:
Values: Physical,Information
Default: Information
Maximum acceptable request times per application and/or service 1000
Details:
Default: 1000
Number of Users supported 1
Details:
Default: 1
Physical Capacity 1 Byte
Details:
Default: 1 Byte
Planned data storage duration over time 1 Year
Details:
Default: 1 Year
Planned Service level per application and partner None
Details:
Default: None
transaction numbers over time 10
Details:
Default: 10
Property Value
isControlType: false
ordering: FIFO