A / 01
৳ 2,480
Checkout that stays on-brand
Use a hosted experience for speed or connect through APIs when your product needs deeper control. Keep choices clear on mobile and desktop.
01 Payment gateway Bangladesh
Payments that move at the pace of your business.
Bring checkout, routing, payment status and reconciliation into one operating layer—built for businesses selling across Bangladesh.
One integrationLive visibilityLocal payment paths
Routing layerEvery payment, visible.
Transaction stateReconciled
✓Checkout →
Authorize →
Route →
Settle →
Reconcile ✓
The operating layer
More than a way to take payment.
A useful gateway should help teams understand what happened after a customer clicked “pay”. That is why the platform connects checkout with day-to-day payment operations.
A / 02
010203↻
Intent-aware routing
Organize attempts by method, state and outcome so your team can respond without disconnected tools.
A / 03
Settlement clarity
Track transaction references, fees, refunds and expected settlement records from one operational view.
A / 04
Risk signals
Controls at each step
Set review rules, capture useful context and keep a traceable record for support and follow-up.
Local choice, one connection
Meet customers where they already pay.
Configure the payment mix that fits your audience and merchant profile. Availability is confirmed during onboarding and partner review.
Discuss your payment mix ↗bKash
Mobile financial service payments shown only when enabled for the approved project.
Nagad
Project-specific Nagad access with current limits checked before display.
Upay
A Bangladesh Bank-licensed wallet flow available according to live project configuration.
TAP Wallet
A wallet route for eligible BDT checkout and withdrawal use cases where activated.
Bangla QR
Interoperable QR payments scanned from supported banking and wallet apps.
Operations, connected
From first attempt to final record.
Keep support, finance and product teams aligned around the same payment timeline.
01—05One traceable lifecycle
A route for every build
Launch with the control you need.
Start with a light integration or design a deeper payment layer around your product. We scope the operating model before implementation.
Hosted payment page
The merchant backend creates a payment, then sends the customer to a provider-controlled page.
- Backend request required
- Customer return URL
- Signed postback confirmation
Payment API
Create BDT payment requests from the server and keep the project credentials out of browser code.
- API key and project ID
- Server-side status handling
- Custom product journey
Test before production
Use a separate test project to prove payment states and signed notifications before production access is activated.
- Approved and failed states
- Duplicate postback handling
- Production credentials kept separate
Create depositPostbackStatus
POST /Remotes/create-deposit
Headers:
apikey: server_secret
project_id: merchant_project
Body:
currency: "BDT"
order_id: "ORDER-2048"Backend required
Create on the server, confirm on the server.
Use the current technical specification for the complete payload, validate signed postbacks, and never treat the browser return as final payment evidence.
BUILT FOR GROWTH
Commerce changes shapeOne payment layer,
One payment layer,
many business models.
Design checkout and operations around the way you sell—not around a generic template.
E-commerce
Clear mobile checkout and state visibility for online orders.
Marketplaces
Payment references and workflows for multi-party commerce.
Education
Structured fee references that reduce manual matching.
Services & travel
Payment requests, booking references and refund-aware support.
CONTROL✓TRACE
Security is operational
Control what happens before, during and after payment.
Security is not a badge in a footer. It combines protected transmission, controlled access, traceable events and disciplined handling of payment data.
01 Encrypted transport02 Role-aware access03 Event traceability04 Data minimisation
Our security approachFrom fit to first payment
A deliberate launch, in five moves.
We align business, risk, finance and engineering early so operational questions do not appear at the end.
- 01
Discover
Business model, journey and payment mix.
- 02
Review
Documents, risk context and partner needs.
- 03
Connect
Choose the route and map payment states.
- 04
Validate
Test success, failure and refunds.
- 05
Operate
Launch with monitoring and support.
Questions, clearly answered
Before you connect.
Payment products involve eligibility, integration and operational choices. These are the points merchants ask about first.
01What is a payment gateway in Bangladesh?+
It connects a merchant backend to a hosted payment page or API, returns signed payment-state notifications, and supports settlement and reconciliation.
02Which payment methods can the platform support?+
Approved BDT projects may enable bKash, Nagad, Upay, TAP Wallet and Bangla QR. The active list, limits and commercial terms are project-specific.
03How long does integration take?+
Timing depends on KYC and AML review, document readiness, backend work, test evidence and production approval; no fixed timetable is promised.
04How are refunds and failed payments handled?+
Keep the merchant reference, accept pending and failed states, verify signed postbacks, and follow the approved refund or withdrawal procedure for the project.
05Does the service guarantee approval?+
No. Merchant acceptance, payment-method access, limits, fees and production activation depend on review and the approved project configuration.
Start with your payment flow
Tell us what you need to move.
Share your business model, current setup and launch goal. The launch desk will use it to shape the first conversation.