Bird
Raised Fist0
HLDsystem_design~10 mins

Payment integration architecture in HLD - Interactive Code Practice

Choose your learning style9 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to identify the component responsible for receiving payment requests.

HLD
The [1] handles incoming payment requests from users.
Drag options to blanks, or click blank then click option'
APayment Gateway
BDatabase
CNotification Service
DUser Interface
Attempts:
3 left
💡 Hint
Common Mistakes
Confusing the database with the component that receives requests.
Choosing the notification service which only sends alerts.
2fill in blank
medium

Complete the code to specify the component that securely stores payment details.

HLD
The [1] stores sensitive payment information securely.
Drag options to blanks, or click blank then click option'
ACache
BAPI Gateway
CPayment Database
DLoad Balancer
Attempts:
3 left
💡 Hint
Common Mistakes
Choosing cache which is temporary storage.
Confusing API Gateway with data storage.
3fill in blank
hard

Fix the error in the description of the component that routes payment requests to processors.

HLD
The [1] is responsible for directing payment requests to the correct payment processor.
Drag options to blanks, or click blank then click option'
APayment Router
BUser Interface
CNotification Service
DCache
Attempts:
3 left
💡 Hint
Common Mistakes
Confusing the user interface with routing logic.
Choosing notification service which only sends alerts.
4fill in blank
hard

Fill both blanks to complete the description of the payment flow components.

HLD
The [1] validates payment data, while the [2] handles communication with banks.
Drag options to blanks, or click blank then click option'
APayment Validator
BUser Interface
CBank Connector
DCache
Attempts:
3 left
💡 Hint
Common Mistakes
Mixing up user interface with validation.
Choosing cache instead of bank communication.
5fill in blank
hard

Fill all three blanks to complete the payment integration architecture description.

HLD
The [1] manages user requests, the [2] processes payments securely, and the [3] sends transaction status updates.
Drag options to blanks, or click blank then click option'
APayment Gateway
BPayment Processor
CNotification Service
DDatabase
Attempts:
3 left
💡 Hint
Common Mistakes
Confusing database with notification service.
Mixing roles of gateway and processor.