Regulatory disclosures
These notes describe the limits of this test deployment. They are an engineering checklist, not legal advice.
Test mode
- This deployment is a test environment. It is not a licence to collect payments from the public.
- Collecting or settling third-party payments in Bangladesh generally requires Bangladesh Bank authorisation as a payment service provider or payment system operator, or a written arrangement with a licensed provider. Confirm the current Payment and Settlement Systems rules before any launch.
- Personal bKash, Nagad, Rocket, Upay, TAP, or bank accounts are not a substitute for official merchant accounts. Provider terms usually prohibit using a personal wallet as a commercial collection point.
- Merchant onboarding for a live service needs KYC and AML controls consistent with Bangladesh Financial Intelligence Unit guidance. This test deployment does not perform KYC.
- No funds are held, transferred, or settled here. Settlement stays non-operational until safeguarding, settlement agreements, and licensing are in place.
- Cryptocurrency is locked off. Bangladesh Bank restrictions on crypto transactions have to be reviewed with counsel before that section can ever be considered.
- A submitted transaction ID or screenshot is not payment confirmation. Only an operator approval, after comparison with receiving-account records, can produce a PAYMENT_SUCCESS event.
- Do not use this deployment for real customer funds.
- Sandbox approval is separate from live merchant eligibility. It does not complete KYC or AML review.
- A launch would still need a privacy notice, a data-retention schedule, an incident-response contact, and a decision about who is responsible for funds and consumer complaints.
- Transaction monitoring here is an operator queue plus audit logs. It is not a production AML monitoring programme.
Cryptocurrency
The cryptocurrency section is locked. PayBangla does not accept, process, or activate cryptocurrency payments in this build.