Designing a Bank-Centric Digital Wallet Architecture for Frictionless and Secure E-Commerce Payments

DOI

https://www.doi.org/10.59256/indjcst.20260502068

Published In

Volume 5, Issue 2 (2026)

Published Online

May-August 2026

Pages

601-606

Article Type

Original Article

Check for updates

The rapid expansion of e-commerce has increased the importance of payment experiences that are simultaneously fast, secure, scalable, and convenient. Conventional online checkout frequently requires consumers to manually provide card numbers, expiration information, security codes, and billing details, creating additional interaction steps and increasing the possibility of transaction abandonment. This study presents an engineering and architectural case study of Paze, a bank-supported digital wallet designed to reduce payment friction while maintaining secure handling of payment credentials.The proposed ecosystem follows a bank-to-wallet model in which eligible payment cards can be provisioned into a centralized wallet through automated services. The architecture combines domain-oriented microservices, automated bulk and real-time provisioning, network tokenization, a configurable business rules engine, and cloud-native infrastructure. The backend implementation uses Java 21 and Spring Boot, while Amazon Web Services provides the scalable cloud execution environment. A Drools-based business rules engine separates changing financial eligibility policies from transactional application logic, allowing rules to be modified without requiring core application redeployment.The provisioning architecture supports large-scale card onboarding through encrypted batch processing, idempotent operations, parallel file processing, retry mechanisms, dead-letter queues, and audit logging. A complementary auto-provisioning mechanism processes bank-originated events to update wallet credentials in near real time. Network tokenization further reduces exposure to sensitive card information by replacing underlying card numbers with network tokens. Official Paze documentation similarly states that the wallet stores network tokens rather than the Funding Primary Account Number (FPAN).The reported implementation supports more than 150 million provisioned credit and debit cards, maintains 99.99% system uptime, and reduces the checkout experience to less than 51 seconds in the reported performance evaluation. Cloud-native modernization produced a reported 30% operational-efficiency improvement, while infrastructure provisioning time decreased from approximately two weeks to two hours. The findings demonstrate how bank-centric wallet architecture, automated credential provisioning, tokenization, configurable business rules, and cloud-native scalability can be combined to create a high-scale payment platform for e-commerce.