Design a Credit Card Application Page and Its Confirmation Page
Try the prompt first
Design the frontend of a credit card application page and the confirmation page after it. An applicant enters identity, address, income and housing costs, reviews the terms and submits. The decision can be approved, declined, pending review or a request to verify identity. Walk through the components, where form state and validation live, how sensitive fields are protected, and what the confirmation shows after a refresh.
Constraints
- Sensitive fields never reach logs, URLs or storage.
- One submit creates one application.
- A decision can take minutes.
Challenge summary
Design a credit card application page and its confirmation page where one form store owns the fields, a retried submit creates one application, and a refresh never posts the form again.
What you'll practice
- Keep every field and its errors in one form store and validate in three layers.
- Keep sensitive values out of logs, URLs, analytics and browser storage, and mask them on the confirmation.
- Send each submit with an idempotency key and render all five outcomes.
- Make the confirmation a status read, so a refresh or a second tab never resubmits.
What Premium unlocks
Premium unlocks the worked example of a double click during a slow submit, the typed form and gateway contracts, the application API semantics and the failure playbook.
Free related practice
Public interview reports: Taro (July 2024), Taro (August 2024) · Capital One frontend interview questions
Upgrade to FrontendAtlas Premium to access this system design scenario. Already upgraded? Sign in to continue.