Accept
Present the payment methods approved for your merchant profile through a focused hosted or integrated checkout.
Commercial payment infrastructure
Accept online payments through one merchant flow—built around local checkout expectations, practical integration and the work that happens after every transaction.
Payment methods, pricing and settlement terms are confirmed during merchant review.
A payment gateway should do more than display a checkout. It should give your team a clear path from payment attempt to confirmation, refund and reconciliation.
Present the payment methods approved for your merchant profile through a focused hosted or integrated checkout.
Connect your store or application with documented requests, return URLs and server-side payment verification.
Follow transaction states, use consistent references and keep refunds and settlement records understandable.
03 — CHECKOUT COVERAGE
Your final checkout mix depends on merchant approval and the live project configuration. Show only methods currently available for the requested amount.
Discuss payment coverageBDT payment route where enabled for the approved project
01Local checkout flow with project-specific limits and availability
02Additional BDT route activated according to merchant configuration
03Wallet-based deposit or withdrawal route where the approved setup enables it
04Interoperable QR standard scanned from supported banking and wallet apps
0504 — INTEGRATION
Choose a hosted payment page, direct API, or both. Every path requires a merchant backend and assigned project credentials.
Share your legal entity, website, products, expected volume and customer locations.
We align eligibility, payment coverage, commercial terms, settlement requirements and integration route.
Your team implements the approved flow and tests success, failure, cancellation and verification states.
Production access follows completed KYC and AML review, technical checks and final written service terms.
06 — AFTER THE CHECKOUT
Search and review payments using references your product, support and finance teams can share.
Keep refund requests linked to the original transaction and communicate status clearly.
Separate abandoned, declined, pending and technically failed attempts before taking action.
Match gateway records with orders and settlement information using consistent identifiers.
07 — QUICK ANSWERS
These answers describe the intended commercial service. Provider availability and binding terms are confirmed during onboarding.
It is presented as a commercial payment gateway service for eligible merchants. The website collects merchant enquiries and explains the intended payment, integration and operating flow; a separate agreement confirms the actual service.
Approved Bangladesh projects may enable bKash, Nagad, Upay, TAP Wallet and Bangla QR in BDT. The exact mix, limits, fees and availability are confirmed for the merchant project.
There is no universal timeline. Document readiness, business review, commercial approval and technical complexity all affect launch. We confirm milestones after reviewing the enquiry.
The approved setup can use a hosted payment page, direct API, or both. Backend implementation, assigned credentials, signed postbacks and test access are required.
No fixed price or settlement promise is shown because terms vary by payment method, risk profile, volume and operating partner. Merchants should receive the full commercial schedule in writing before launch.
08 — MERCHANT ENQUIRY
Tell us what you sell and how you want customers to pay. We will review the fit before discussing integration and commercial terms.
Do not send card numbers, passwords, one-time codes, identity documents or API credentials through this form.