Customer Portal and Automated Mobile Payment Verification Architecture

In telecommunications and digital service delivery, billing friction and manual payment reconciliation represent significant operational pain points for both subscribers and accounting personnel [3]. Historically, customers paying broadband invoices via mobile financial services had to manually call support desks or send SMS screenshots of transaction IDs, requiring staff to manually verify records before renewing accounts [3].

To eliminate manual bottlenecks, Deprogit engineered an automated payment verification pipeline within our integrated customer portal [3]. By integrating directly with Bangladesh's leading Mobile Financial Service (MFS) providers—including bKash, Nagad, Rocket, and Upay—our billing architecture achieves real-time transaction reconciliation and instantaneous service renewal [1, 3]. In this technical analysis, we dissect the architecture of the customer portal and examine the end-to-end automated payment verification flow [1, 2, 3].

1. The Customer Portal Architecture

The Deprogit customer portal functions as a secure, self-service management gateway for residential and commercial subscribers [3]:

• Identity & Session Management: Built on modern tokenized session architectures, ensuring subscribers can securely review account details, active subscription tiers, renewal dates, and historical invoices [1, 3].
• Transport Security: All communication between customer browsers, our billing servers, and external fintech gateways is encrypted strictly over TLS 1.3 (RFC 8446) [2].
• Role-Based Access Control: Commercial accounts support multi-user roles, allowing corporate finance officers to view invoices and process payments while network engineers manage bandwidth allocations and support tickets [3].

2. The Automated Mobile Payment Verification Flow

The automated verification workflow connects customer actions, payment gateway APIs, and core billing databases in real time [1, 3]:

+--------------------+        1. Initiate Payment        +---------------------+
|  Customer Browser  | --------------------------------> |  Deprogit Billing   |
|   (Portal View)    | <-------------------------------- |       Engine        |
+--------------------+   2. Redirect to MFS Gateway      +---------------------+
          |                                                         |
          | 3. Authenticate & Authorize PIN                         |
          v                                                         v
+--------------------+        4. Webhook / Callback      +---------------------+
| MFS Provider API   | --------------------------------> | Billing Webhook     |
| (bKash/Nagad/etc.) |   5. Cryptographic Signature Match| Handler (Idempotent)|
+--------------------+                                   +---------------------+
                                                                    |
                                                         6. Settle Invoice &
                                                            Provision Bandwidth
                                                                    v
                                                         +---------------------+
                                                         | RADIUS / Core Router|
                                                         | (Active Subscriber) |
                                                         +---------------------+

Step-by-Step Transaction Stages:

1. Invoice Generation & Initiation: When a monthly billing cycle matures, the billing engine generates a cryptographically hashed invoice token. The subscriber selects their preferred payment method: bKash, Nagad, Rocket, or Upay [3].
2. Gateway Redirection & Payment: The portal securely redirects the customer to the official, verified checkout gateway of the chosen provider over an encrypted HTTPS connection. The user authorizes the transaction directly with their provider [2].
3. Cryptographic Webhook Notification: Upon successful authorization, the MFS provider makes an outbound asynchronous HTTP POST webhook call to Deprogit's billing listener [1, 3].
4. Signature & Hash Verification: The webhook listener cryptographically validates the message signature and verifies that the transaction ID, amount, and invoice token match an outstanding internal invoice record [1].
5. Idempotent Settlement: To prevent double-crediting if an MFS provider retries a webhook callback, the database transaction enforces strict idempotency using unique transaction reference constraints [1, 3].
6. Instant Service Provisioning: Once settled, the billing engine automatically communicates with core network RADIUS servers via API, updating the subscriber's account balance and extending internet access immediately without human intervention [3].

3. Supported Mobile Financial Services

Our portal supports the full spectrum of standardized digital payment rails in Bangladesh [3]:

• bKash: Direct API checkout integration supporting tokenized quick payments and one-time verification.
• Nagad: Integrated digital checkout rail for postal digital financial service subscribers.
• Rocket (Dutch-Bangla Bank): Direct bill payment integration for DBBL mobile banking accounts.
• Upay (UCB): Real-time automated QR and digital payment processing.

Security Controls and Fraud Prevention

To protect financial integrity and subscriber privacy, the portal enforces rigorous security controls [1, 2]:

Practical Subscriber Guidance

For the smoothest billing experience:

1. Pay Directly via the Portal: Always initiate payments through the official Deprogit customer portal to ensure instant automated reconciliation [3].
2. Retain Transaction IDs (TrxID): Although verification is automated, save the provider's SMS TrxID as a reference for your financial records.
3. Verify Official Domains: Ensure your browser address bar displays https://deprogit.com with a valid TLS certificate before entering account credentials [2].

For customer support inquiries, invoice verification, or account assistance, visit our Contact Page.

Key Takeaways

• Deprogit's customer portal automates billing reconciliation, eliminating manual payment confirmation delays.
• Full API integration with bKash, Nagad, Rocket, and Upay enables instantaneous service renewals.
• Transactions are secured via TLS 1.3 encryption, tokenized checkouts, and cryptographic webhook signatures.
• Database idempotency controls guarantee accuracy and eliminate duplicate billing errors.

Need help with this? Contact us.

Sources

[1] IETF, "RFC 6749: The OAuth 2.0 Authorization Framework", 2012. URL: https://www.rfc-editor.org/rfc/rfc6749.html (Standards-track specification for delegated authorization, access tokens, and third-party payment handshakes).

[2] IETF, "RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3", 2018. URL: https://www.rfc-editor.org/rfc/rfc8446.html (Authoritative standards specification defining TLS 1.3 encryption, handshake integrity, and cipher suites).

[3] Deprogit, "Deprogit Billing and Customer Service Architecture", 2026. URL: https://deprogit.com/ (Official operational guidelines on customer account management, billing cycles, and automated payment receipting).

Last reviewed: October 2026