PayBangla
Get Started

PayBangla

Payment made
beautifully simple.

Create payment requests, manage checkout experiences, and verify transactions from one powerful workspace.

Get StartedExplore PayBangla

Products for the full review path

Checkout, merchant operations, and verification share one record. A submitted reference stays pending until an operator decides.

1 / 6

Hosted Checkout

A hosted BDT checkout shows only methods with an active receiving account.

Payment Verification

A submitted transaction ID stays pending until an operator checks the receiving record.

Merchant Dashboard

Payment links, request history, and webhook deliveries for that merchant only.

Payment Links

Set the amount, description, and expiry, then share the checkout URL.

Developer API

Sandbox keys, idempotent payment creates, and signed webhooks.

Transaction Management

The admin desk lists stored submissions. It does not invent volume.

One checkout. Multiple payment methods.

Customers only see a method when it is enabled and has an active receiving account. PayBangla does not claim a partnership with these providers.

Swipe on a phone. Use the arrows on a larger screen.

bKash

Mobile wallet

Shown in checkout

Nagad

Mobile wallet

Shown in checkout

Rocket

Mobile wallet

Shown in checkout

Upay

Mobile wallet

Shown in checkout

TAP

Mobile wallet

Shown in checkout

Bank Transfer

Bank transfer

Shown in checkout

Merchant workspace

The signed-in dashboard reads the database. The panel below is an example preview, not a live balance.

Example previewFigures on this panel are illustrations
Pending12Approved48Links6

Create payment link

Amount · example
Create Payment Link

API · pb_test_ prefix only

OrderStatus
EX-1008Pending verification
EX-1004Approved
EX-1002Rejected

Payment orchestration

One request becomes a checkout URL, a status, and a webhook. The amount stays fixed after the customer submits.

Read the create call

Manual verification

Approval needs an independently checked receiving account. A second decision on the same submission is rejected.

Open the review desk

Developer integration

The examples match the local API. PAYMENT_SUCCESS is sent only after a manual approval, and livePayment stays false. Read the API reference.

POST /api/v1/payments
Authorization: Bearer pb_test_...
Idempotency-Key: demo-1001-key

{
  "orderId": "DEMO-1001",
  "amount": "1250.00",
  "currency": "BDT"
}
201
{
  "paymentId": "…",
  "status": "AWAITING_PAYMENT",
  "checkoutUrl": "/checkout/…",
  "livePayment": false
}
event: payment.approved
type: PAYMENT_SUCCESS

{
  "data": {
    "status": "APPROVED",
    "verification": "MANUAL_INDEPENDENT",
    "livePayment": false
  }
}

Security and auditability

Sessions, API keys, and review decisions stay on the server. The interface cannot mark a payment successful by itself.

  • AccessSeparate admin and merchant sessions, CSRF checks, and optional admin MFA.
  • VerificationDuplicates stay flagged. Approval records the operator and the time.
  • AuditThe audit table rejects updates and deletes.

Company

PayBangla is a local manual-review workspace for Bangladesh payment methods. It is not a licensed payment institution, and it does not hold customer funds.

  1. 1A merchant creates a payment request.
  2. 2The customer submits a reference on the hosted checkout.
  3. 3An operator verifies the receiving record and approves or rejects it.

Pricing

PayBangla does not publish a fee schedule and does not sell payment collection. Compliance limits are on the disclosures page.

Help and merchant questions

Does a transaction ID mark the payment paid?

No. The status becomes pending verification until an operator records an independent check.

Can a new merchant collect live payments?

No. Registration starts as pending approval. Sandbox approval does not enable live collection.

Where is support?

This build runs on your computer. Use the merchant desk, the admin review queue, and the documentation at /docs.

Regulatory information · Developer resources