H2H API
Your developers build the customer interface and server-side requests. Present the instructions required by your enabled Nagad configuration, then process transaction results on your backend.
Nagad Payment Gateway for Businesses in Bangladesh
Accept Nagad payments from customers in Bangladesh through A-Pay. Connect the method to your payment setup with integration support and transaction results delivered to your backend.
Whether you are planning your first Nagad connection or adding the method to an existing A-Pay project, begin with your business requirements and the customer payment experience. Our team will help establish the available configuration, implementation steps, and commercial terms.
Bangladesh / local payment acceptance
Accept Nagad as a Local Payment Option
Give customers in Bangladesh another familiar way to pay. Nagad is a mobile financial service that can sit alongside the payment methods your business already offers.
Connect through A-Pay with a payment flow configured for your project. Your team works with A-Pay’s integration requirements and receives transaction results through its backend.
Start with your audience: which methods do customers ask for, and how should they move from choosing Nagad to seeing a clear payment result?
LOCAL METHOD
BD
Nagad
Customer market
Bangladesh
Payment currency
BDT
Payment acceptance through an A-Pay project
Payment request / transaction result
How a Nagad Payment Reaches Your Platform
Follow the payment request, then the result coming back. A-Pay processes the transaction; your platform updates its own customer records.
01 · Start
The customer chooses Nagad. Your backend creates the request and presents the instructions for the enabled configuration.
02 · Confirm
A-Pay sends the result through a postback. Your backend verifies the transaction status and amount.
03 · Update
Your platform matches the result to the order or account, updates its records, and shows the outcome to the customer.
Illustrative lifecycle, not a live transaction. Motion shows direction, not processing speed. Customer payment steps depend on the enabled Nagad configuration.
Integration / interface ownership
Choose How Nagad Fits Your Platform
A-Pay provides H2H API and Hosted Payment Page integration approaches. Agree on the available setup for your Nagad project, based on your interface and backend resources.
Hosted Payment Page
Customers use an A-Pay-hosted page. Your backend still creates the required requests and handles results, while your platform displays the customer’s payment outcome.
One method. Different documented configurations.
The nagad_a and nagad_b deposit specifications provide a payment-page URL. The nagad_api_v and nagad_p2p specifications use a payer account number and return recipient details. Follow the configuration agreed for your project.
Interface diagrams are schematic. Exact screens and enabled configurations are established during integration.
Merchant settlements
T+0
Sent on the same day.
A-Pay sends merchant settlements on the same day. The receiving payment channel determines when the funds arrive.
Merchant funds
→
Settlement sent
Customer payment confirmation and merchant settlement are separate events.
Agree before launch
Nagad Processing Terms and Merchant Settlements
Fees & transaction limits
Share your platform, business model, expected activity, and typical transaction amounts. Agree on the processing fees and limits for your project.
Payment & settlement currencies
Documented Nagad payment configurations use BDT. Establish the merchant settlement currency separately.
Customer payouts
If your business needs payments to users, discuss availability and conditions for your selected Nagad setup separately from payment acceptance.
From discussion to production
Prepare Your Nagad Integration for Launch
A clear setup, tested result handling, and an agreed production plan. Build each into your Nagad integration from the start.
Start with three details
Your website or platform.
Your customers in Bangladesh.
The payment operations you need.
01
Agree on your setup
Establish eligibility, the available Nagad configuration, and commercial terms. Identify who will implement requests and handle transaction results.
02
Implement and test
Use a test project with separate credentials. Ask support to send the required test callback statuses and verify how your platform handles each outcome.
03
Prepare production
Check customer instructions, transaction matching, and successful and unsuccessful results. Complete the agreed checks before switching to production credentials.
Illustrative launch sequence; timing is agreed for your project. Your backend verifies payment results and updates its customer records.
Beyond one payment method
Build Your Bangladesh Payment Mix
Nagad can be part of a wider local setup. Review bKash, Rocket, and Upay alongside the methods your customers already use, with availability confirmed for your project.
ON THIS PAGE
Nagad
More supported methods. No extra connection fee.
Existing A-Pay merchants can add supported payment methods at no additional connection cost. The number of connected methods does not change the connection price. Processing fees and enabled operations remain separate.
Nagad Payment Gateway FAQ
Discuss your platform, customers in Bangladesh, and required operations with A-Pay. The team will help establish the available configuration, integration requirements, and terms. Your developers then implement and test the agreed setup before production.
Account requirements are established for the Nagad setup agreed with A-Pay. Ask the team which accounts and credentials your project needs before applying instructions written for direct Nagad integration or another provider.
For integration through A-Pay, use A-Pay’s start-integration, deposit-creation, and postback documentation linked above. Request fields depend on the selected Nagad configuration; direct Nagad specifications are not a substitute for A-Pay’s request formats.
Processing fees and limits are agreed for your merchant project. Share your business model, expected payment activity, typical transaction amounts, and required operations. The team can then discuss the commercial conditions relevant to your proposed setup.
Timing depends on merchant verification, the selected configuration, and your development and testing requirements. Agree on the implementation steps and launch plan with A-Pay rather than relying on a universal deadline.
Existing merchants can discuss adding supported methods without an additional connection fee. The number of connected methods does not affect the connection price. Availability and any implementation changes are confirmed for your current setup; transaction processing fees remain separate.
Discuss Nagad Payments for Your Business
Tell us about your platform, customers in Bangladesh, and the payment operations you need. Our team will help establish the available Nagad setup, integration requirements, and commercial terms.
Your website, expected payment activity, and required operations are a useful starting point. You can discuss a first connection or adding Nagad to an existing A-Pay project.