bKash vs Nagad: API Structure and Interface Comparison
bKash vs Nagad: Comparative Analysis of API Structure and Interface
introductory
In the field of mobile payment in Bangladesh, bKash and Nagad are the two leading platforms, and their technical architecture, especially API design, is crucial for developer integration. In this paper, we will compare the API structure and interface features of bKash and Nagad from a professional point of view to provide valuable references for technical decision makers.
I. Overview of the infrastructure
The bKash technology stack
Adoption of RESTful API design specifications
Support JSON and XML data format exchange
Authentication mechanism based on OAuth 2.0
HTTPS encrypted transport layer assurance
Nagad's System Architecture
Hybrid API design (REST + some SOAP)
Primary JSON data format
JWT Token Authentication System
Double encrypted communication channels
II. Comparative analysis of core API endpoints
Payment processing interface point of difference:
functional module | bKash endpoints | Nagad endpoint |
---|---|---|
Create a transaction | /checkout/create | /api/v1/payment/initiate |
Implementation payments | /checkout/execute | /api/v1/payment/complete |
Refund processing | /payment/refund | /merchant-api/v2/refund |
Key findings: Nagad uses versioned paths (v1/v2) which are better for long-term maintenance, while bKash keeps a clean path structure.
III. In-depth analysis of authentication mechanisms
bKash security programme:
- API key + merchant wallet ID two-factor authentication
- Access Token valid for 24 hours
- IP Whitelist Enforced Restriction Policy
- SHA-256 signature algorithm
Nagad Security Protocol:
- RSA asymmetric encryption key pair
- JWT tokens with 15-minute short time limit
- OTP Secondary Authentication Optional Configuration