Hosted checkout
Your logo, your colors, your domain allowlist. Customers never have to type a transaction ID into a form you built by hand.
Confirm the payment when the SMS lands.
Hosted checkout for Bangladesh wallets and gateways — flat plans, your brand, your domain.
bKash You have received Tk 500.00 from 017•••1234. TrxID 8H2K9X. Ref ORD-1001.
Completed. Webhook queued to your server.
Three steps
Your server posts the amount, return URLs, and a webhook. Redirect the customer to the hosted checkout on your brand.
They use a wallet, a gateway API, or a payment link. Personal wallets pay the number you configured.
The companion app forwards trusted SMS, or the gateway callback arrives. When the facts match, the webhook fires.
Methods you can turn on
A method appears on checkout only after you switch it on and add your own number or API keys. Names are the products you connect — not an endorsement.
What the panel actually does
Your logo, your colors, your domain allowlist. Customers never have to type a transaction ID into a form you built by hand.
The Android app keeps only configured wallet senders. Unknown messages stay in review. Amount and reference must match.
Send a payment link or an invoice when there is no storefront. Useful for social-commerce, services, and subscriptions.
Mark an order paid only when status is completed. If a webhook is missed, call verify-payment with the charge id.
Tokenized bKash, Nagad merchant API, and aggregators such as SSLCommerz sit beside personal wallets. Use both when a method needs it.
Separate brands, staff roles, domain and IP allowlists, and a monthly transaction quota you can see before you hit it.
Security, without the certificate wallpaper
We do not claim PCI DSS, ISO, or a central-bank license on this page. Those belong to the card networks and licensed operators you connect. What this panel enforces is listed here.
Auth cookies are HttpOnly, Secure on HTTPS, and SameSite=Lax, with a one-day life. Sessions are bound to the browser fingerprint. Optional email codes and authenticator apps sit on login.
Every private call needs mh-guaranteepay-api-key, and the caller must be on your domain or IP allowlist. Do not put the key in a website or an app.
A screenshot is not proof. Completion requires a trusted sender plus a matching amount and reference. CSRF tokens rotate after each validated browser POST.
Responses send HSTS on HTTPS, nosniff, frame protection, a content security policy, and a public security.txt. Asset URLs on this page reject javascript: and off-site hosts.
How this differs
| Topic | Typical aggregator | SMS-only tools | Guarantee Pay |
|---|---|---|---|
| Where the money lands | Their settlement account, then yours | Your wallet number | Your wallet, or the gateway you connected |
| Price | About 1.5–2.5% per sale | Monthly fee, wallets only | Flat plan. Gateway fees still apply if you use one |
| Proof of payment | Their callback | Forwarded SMS, often after the customer types a TrxID | SMS match or official API, then webhook and verify |
| Paperwork | Trade license and bank account | A handset is enough | A handset for wallets. Licensed rails still need their own KYC |
Plans from this install
Standard includes 1,000 transactions / month. Need more volume? Unlimited plans start at ৳50 with 5 brands.
৳0 Forever
৳30 1 month
৳80 3 months
৳300 1 year
৳50 1 month
৳130 3 months
৳500 1 year
৳100 1 month
৳260 3 months
৳1,000 1 year
Standard (৳30 line) includes 1,000 transactions / month. Unlimited starts at ৳50. Paid plans activate after a verified payment. Upgrade later from the dashboard if you outgrow a quota.
Developers
Keep the API key on your server. Whitelist the domain or IP before the first live call. Docs cover verify, webhooks, and the Android app.
POST https://payment.yamin.bd/api/create-charge
mh-guaranteepay-api-key: YOUR_API_KEY
{
"full_name": "Rahim Uddin",
"email_mobile": "rahim@example.com",
"amount": "500",
"currency": "BDT",
"metadata": { "order_id": "ORD-1001" },
"redirect_url": "https://shop.example.com/pay/success",
"cancel_url": "https://shop.example.com/pay/cancel",
"webhook_url": "https://shop.example.com/hooks/guaranteepay",
"return_type": "GET"
}
Fee calculator
Enter a volume and compare. This is arithmetic, not a quote, and it ignores gateway fees on API methods.
Not for personal or agent wallets. Those payments land on the number you own. Merchant APIs and licensed aggregators still need their own accounts and keys.
Only that handset receives the wallet SMS. The app forwards trusted senders and ignores the rest. Official API methods do not need the phone.
A matching SMS from a trusted sender is required for wallet methods. A typed id alone is not enough, and unknown senders stay in review.
No. Personal-wallet payments go to your number. If you connect SSLCommerz, aamarPay, or a card gateway, settlement follows that provider’s rules.
Create a brand, whitelist your server, keep the API key off the browser, and confirm webhooks on an HTTPS endpoint you control. The docs cover the exact fields.