Please enable JavaScript.
Coggle requires JavaScript to display documents.
Digital Fraud Service (DFS) - Coggle Diagram
Digital Fraud Service (DFS)
Implementation
ABSA HANIS Proxy
Internal rest endpoint
Design json payload
create & publish client lib
Security
Find Security architecture
Authentication
AWS integration?
Authorisation
Metrics
log internal caller data
create internal billing report / dashboard
Call ABSA service
Implement integration
Credential management
Generate client from WSDL
Error handling
Create mock service for testing
Create integration tests
Build internal-to-external mapping
Metrics
Record metrics for billing
Create billing dashboard / report
Security
Provision secret manager
DFS to read from Secret manager
Create cache
Create DB schema
Set up S3 storage
Create db connector (repository)
implement TTL
Create cache clean up control
CI/CD
Create deployment pipeline
Set up git Trigger
Create build script
Create docker file
IDV integration (assumes lightweight DFS-HC integration)
Create HANIS plugin
Create HANIS trigger
Create HANIS reducers
responce payload
happy path
no face
all datra
invalid number
error
error
service failure
fraud view state reducers
id number not found
no face
happy path
service failure
Lookup request counter
tennant config to register trigger
service client
service endpoint config (application.yaml)
client instantiation (DI / IOC)
add client lib dependancy
unit testing
multiplex current unit test over new provider
else copy test scenarios from xds
Enable new HANIS integration in WFS IDV service Chart
Security
configure secrets
network connectivity
point-to-point security
mutual auth
IDV -> DFS
Trigger on IDV complete
Download fraud scores
Download IDV evidence data
DOB HoneyComb integration
Design IDV integation: either do IDV from DFS and return the various IDV results to HC (full integration) or pass DFS the IDV case ID from HC (lightweight but may need to be replaced later)
Design iovation integration: either pass iovation result to ? or pass the data needed to call iovation from the ? and return success or failure to HC. NOTE: iovation is called again when customer switched to another device
OM4 digital fraud data collection endpoint
Need integration guide for new AIT service, can make do with list of fields, types and values for a mock service initially
Security
Authorisation
Authentication
Currently HC IP addresses are whitelisted in DataPower to access AIT, DFS will need this
Metrics
create internal billing report / dashboard
record metrics
IDV fraud analytics takes several minutes, but IDV is the last process in DOB, so GDC will be called from HC straight after IDV and trigger the OM4 collection request before IDV processing may be complete. This all happens synchronously currently and the customer waits for GDC to complete. There is a 150s timeout.
Does DFS need to transform IDV scores for Blaze?
Reporting
Need clarity on Section 6 of BRS - what data needs to be moved to the DWH by the DFS?
Project management
Confluence setup
Scope & cost sign off
Confirm Fraud UI console out of scope
Decide which service controls IDV integration
Decide which service controls iOvation integration
Is internal fraud file importing in scope?
Updated & confirmed BRS based on agreed scope
Confirm that AVS data is not required for Blaze and can thus be implemented in a later phase?
Confirm that the BRS is for their full Fraud Decisioning platform and UI and that DFS will only implement a part of this initially
Parties: Andy (scope and priorities), Jacques (technical architecture), Tamara (BRS and business processes)
Once all questions answered, produce high level prioritised scope document that WFS must approve in writing
Governance
Architecture
Create process flow diagram
Create detailed sequence diagram
Create integration architecture
Design deployment architecture
Get ARB sign off
AIT integration
Fraud UI
out of scope?
Infrastructure
Provision Database
Create deployment descriptors
VPC design
Redundancy design
Provision SQS queues
Provision environments
DEV
UAT
PROD
Provision git repo
Data
Confirm what HC application data will be required from HC for OM4/Blaze
What are data storage requirements for DFS? Where will artifacts be stored? What data management is required for data stored in DFS? Do we need to integrate with Open Text?
QA
Unit testing
Integration testing (require mock service)
Mock service
Need endpoints for real QA systems
QA test cases and automation need to be written (not us)