digital identity service - code and flow diagrams added

Author: PrasanKumar93

docs/howtos/solutions/fraud-detection/digital-identity-validation/images/code-flow-1-1.png

@@ -7,6 +7,7 @@ authors: [prasan, will]
 ---
 
 import Authors from '@theme/Authors';
+import MicroservicesArchitectureWithRedis from '../../microservices/common-data/microservices-arch-with-redis.mdx';
 
 <Authors frontMatter={frontMatter} />
 
@@ -39,6 +40,23 @@ This is exactly where **Redis Enterprise** fits in transaction risk scoring
 
 Finally, both of the use cases above can be deployed in an Active-Active set-up, allowing for 99.999% uptime.
 
+## Microservices Architecture for an E-commerce Application
+
+<MicroservicesArchitectureWithRedis />
+
+Consider below fraud detection flow where Digital identity is validated before order checkout/ payment.
+
+![Flow](./images/flow.svg)
+
+- Purchase : Item is selected for purchase
+- **Check Digital Identity** : Confirm the user characteristics (like **user session/ cookie, IP address, Browser fingerprint, location, device type**..etc) and calculate **Identity score** from 0.0-1.0
+- Check User Profile : Confirm the user behavior (like purchased from this category and level before?) and calculate **Profile score** from 0.0-1.0
+- AI (Artificial Intelligence) : Score overall purchase patterns ( say basket comparison) and calculate **AI score** from 0.0-1.0
+- Add to cart : Add the selected item in to the cart
+
+Calculate the transaction fraud/ risk score from above identity score, profile score and AI score.
+If the **fraud/ risk score is high**, the customer is sent through a **challenge flow** to provide additional authentication. Challenges typically include a one-time password sent via text, email, or biometric scan.
+
 ## Demo
 
 - [loan prediction - github](https://github.com/RedisVentures/loan-prediction-microservice)

docs/howtos/solutions/fraud-detection/digital-identity-validation/images/code-flow-1-3.png

@@ -4,6 +4,7 @@ The e-commerce microservices application discussed in the rest of this tutorial
 1. `orders service` - handles validating and creating orders
 1. `order history service` - handles querying a customer's order history
 1. `payments service` - handles processing orders for payment
+1. `digital identity service` - handles storing identity and calculating identity score
 1. `api gateway` - unifies your services under a single endpoint
 1. `mongodb` - serves as the primary database, storing orders, order history, products, etc.
 1. `redis` - serves as the stream processor and caching database