Open Banking, API Data-Sharing & Embedded-Finance Arrangements in Bangladesh
Open banking, API data-sharing and embedded-finance agreements for banks, payment providers, aggregators, e-commerce platforms and foreign fintechs in Bangladesh: we allocate consent, data use, security, liability and exit so every connected party knows exactly where it stands.
- Scope the data flows
- Agree the structure
- Draft and negotiate
- Launch and adapt
How open banking and embedded finance work in Bangladesh
Open banking describes arrangements in which a bank or payment institution lets authorised third parties access account data or initiate payments through secure application programming interfaces, usually with the customer's permission. Embedded finance goes a step further, placing loans, wallets, insurance or payments inside non-financial apps such as marketplaces, ride-hailing or supply-chain platforms. Bangladesh does not yet have a single open banking statute, so these relationships rest mainly on contract, Bangladesh Bank directions and data protection law. We draft and negotiate the agreements that hold them together, as part of our technology practice in Bangladesh.
The backdrop is layered. Banks act under the Bank Company Act 1991 and Bangladesh Bank's guidance on outsourcing and ICT security. Payment initiation and wallet features may engage the Payment and Settlement Systems Act 2024 and the licensing regime for payment system operators and payment service providers. The Personal Data Protection Act 2026 now governs the handling of customer personal data. An open banking or embedded finance agreement must work within each of these regimes at once, which means the contract has to identify which party is regulated for which activity and how each one evidences compliance to the regulator.
Consent is central but rarely enough. A customer consent screen may authorise a third party to view balances or transaction history, yet the agreement still has to define the purpose of access, what data fields are shared, how long they are kept, whether they may be used for analytics or credit scoring and what happens when consent is withdrawn. Many open banking disputes arise because the commercial team assumed consent covered a new use that the customer never saw. We draft purpose limitation, data minimisation and withdrawal mechanics that operations teams can implement in the product and audit later.
Technical dependence creates legal exposure. When several parties rely on one interface, an outage, a security breach or a faulty data feed can cause losses for customers, the bank and the platform at once. Open banking agreements therefore need clear API specifications, service levels, security standards, incident notification timelines, testing rights and rules for planned changes and version retirement. We work with in-house technology teams to translate these into enforceable obligations, and coordinate with our data protection team on breach response, cross-border hosting and access by group companies abroad.
Embedded finance also raises commercial and consumer questions. A marketplace offering instalment credit through a partner lender must manage disclosure, pricing, complaints, collections and branding so customers understand who provides the service. Revenue sharing, data monetisation and exclusivity terms must reflect competition and foreign exchange rules where a foreign platform is paid from Bangladesh. Barrister Tahmidur Rahman and Barrister Remura Meheruba Mahbub lead our open banking and embedded finance work, drawing on banking, finance and foreign investment experience, and we coordinate with counsel in the UK, US, UAE, Singapore and India for regional and group-wide programmes.
Core workstreams
Four clear stages
- 01Scope the data flows
- 02Agree the structure
- 03Draft and negotiate
- 04Launch and adapt
Talk to a partner
Consultations in Dhaka or by video. Scope, team and fees are agreed in writing first.
Book →What our API and embedded-finance work covers
Participant map and agreement design
- Scope the data flows
- Agree the structure
- Draft and negotiate
- Launch and adapt
Consent, purpose and access rules
- Scope the data flows
- Agree the structure
- Draft and negotiate
- Launch and adapt
Security, API standards and service levels
- Scope the data flows
- Agree the structure
- Draft and negotiate
- Launch and adapt
Personal data protection compliance
- Scope the data flows
- Agree the structure
- Draft and negotiate
- Launch and adapt
Embedded lending, payments and insurance
- Scope the data flows
- Agree the structure
- Draft and negotiate
- Launch and adapt
Liability, disputes and exit
- Scope the data flows
- Agree the structure
- Draft and negotiate
- Launch and adapt
Participant map and agreement design
We identify each participant, from account provider and aggregator to platform, lender, processor and cloud host, and design an agreement structure that reflects real data and money flows. That may include a master API access agreement, product schedules, data-sharing terms, technical specifications and operating manuals, with a clear hierarchy so conflicting documents are resolved predictably and quickly. Each document has a named owner on both sides.
Consent, purpose and access rules
We define who obtains customer consent, how it is recorded, what each party may access and for which purposes. Our open banking drafting covers scope of data fields, frequency of access, secondary use for analytics or credit decisions, consent dashboards, withdrawal, and how changes to the product are tested against the consent customers originally gave in the app. Consent records are kept in an auditable form.
Security, API standards and service levels
We translate technical expectations into contract terms: authentication and encryption standards, penetration testing, vulnerability management, uptime and response commitments, rate limits, change notices and version retirement. We also cover incident reporting, cooperation with Bangladesh Bank and other authorities, and audit or assessment rights proportionate to the sensitivity of the data and payments involved. Obligations are matched to realistic technical capacity.
Personal data protection compliance
We align each data flow with the Personal Data Protection Act 2026, identifying controllers and processors, lawful bases, retention periods and cross-border transfer requirements. For open banking platforms with regional infrastructure, we address offshore hosting, group access, subcontractors and the documents a sponsoring bank will need before it allows customer data to leave Bangladesh. Transfer documents are kept ready for bank review.
Embedded lending, payments and insurance
For embedded finance features we draft distribution, referral and programme agreements between platforms and licensed providers, covering disclosure, pricing display, complaints, collections, marketing approvals and brand use. We check that the platform does not drift into regulated activity it is not licensed to perform, and that customers can see clearly which entity is responsible for the service. Each disclosure is reviewed against the live product.
Liability, disputes and exit
We allocate liability for data errors, unauthorised access, payment failures and fraud according to each party's control, with caps, carve-outs and indemnities that reflect regulatory exposure. Exit provisions cover suspension for security reasons, regulatory intervention, change of control, data return or deletion, customer notices and orderly migration to a replacement partner where the service continues. These terms are tested against realistic incident scenarios.
Partner-led, on every matter.
Technology, IP & Data matters at TRW are led by partners, supported by associates, with one responsible lawyer from first advice to final outcome.
Meet the firm →01Is there an open banking law in Bangladesh?
There is no single open banking statute equivalent to the regimes in the UK or EU. Instead, open banking style arrangements in Bangladesh are shaped by Bangladesh Bank's directions on banking, payments, outsourcing and ICT security, the Payment and Settlement Systems Act 2024 where payments are involved, and the Personal Data Protection Act 2026 for customer data. Bangladesh Bank continues to issue guidance on digital finance, so we check the current position for each product and build regulatory change provisions into the agreement so it can adapt without full renegotiation. We revisit this as new guidance is issued.
02Can a bank share customer data with a fintech through an API?
It can, but only within limits. Banks owe customers duties of confidentiality and must comply with data protection law and Bangladesh Bank expectations. Sharing usually depends on clear customer consent or another lawful basis, a defined purpose and adequate security at the receiving end. The open banking agreement should restrict what the fintech may do with the data, prohibit onward sharing without permission, require deletion when consent ends and give the bank audit rights. We review the data fields and use cases before advising on the right structure and consent wording. Clear deletion records also help in later disputes.
03Who is liable if an open banking API fails or data is breached?
Liability should track control and fault. If the bank's interface goes down, the bank should usually bear responsibility under agreed service levels; if a fintech's systems are compromised, the fintech should bear the consequences. Shared incidents need a process for investigation, customer communication and allocation of losses once the cause is known. We draft indemnities, caps and carve-outs that reflect this, with specific provisions for regulatory fines, customer refunds and third-party claims, so open banking partners are not left arguing about responsibility while customers wait for answers. Customer refunds should not wait for that allocation.
04Does a marketplace offering instalment loans need a lending licence?
Usually the marketplace does not need its own licence if a licensed bank or financial institution makes the loan and the marketplace only refers or displays the product. Problems arise when the platform starts setting credit terms, collecting repayments or holding funds, which may amount to regulated activity. We review the customer journey, the flow of money and the marketing materials, then structure the embedded finance arrangement so the licensed lender keeps the regulated functions and the platform's role is clearly documented in the agreement and in customer-facing terms. We also review the platform's marketing language.
05How should customer consent be captured for open banking access?
Consent should be specific, informed and easy to withdraw. In practice that means a clear screen showing which party will access which data, for what purpose and for how long, recorded in a way that can be evidenced later. The Personal Data Protection Act 2026 adds formal requirements that consent wording and records must meet. We draft consent language, privacy notices and record-keeping obligations for open banking journeys, and include contractual duties to update them when the product changes, so consent stays valid as features evolve after launch. Consent records should be retained for the agreed period.
06Can customer data from an open banking arrangement be stored outside Bangladesh?
Possibly, depending on the data, the regulated status of the parties and the transfer rules in the Personal Data Protection Act 2026. Banks may also face Bangladesh Bank expectations on where certain records and systems are hosted. A foreign fintech using regional cloud infrastructure should expect the bank to ask for detailed hosting information, security certifications and audit rights. We map the data flows and advise on transfer mechanisms, localisation questions and the contractual protections needed before any data leaves the country, coordinating with overseas counsel where group entities are involved. Transfer terms should be reviewed periodically.
07How are API fees and revenue shares structured?
Models vary: per-call fees, monthly access fees, revenue shares on loans or payments, or free access in exchange for distribution. Where a foreign party is paid, foreign exchange documentation and withholding tax become relevant, and payments for data or technology may be characterised differently for tax purposes. We draft fee mechanics, invoicing, audit and set-off provisions, and coordinate with tax advisers so the open banking commercial model can be implemented and remitted lawfully. We also address price changes, most-favoured terms and any exclusivity requested by either side. Fee changes should require advance written notice.
08What happens when an open banking partner is suspended or exits?
The agreement should allow immediate suspension for security threats or regulatory instructions, with a defined process for restoring access once the issue is fixed. On exit, it should set out notice periods, customer communications, data return or deletion, continuing confidentiality and cooperation with any replacement provider. For embedded finance products, outstanding loans, wallets or policies must be serviced until they end or are transferred. We draft these provisions so exit does not harm customers or expose either party to regulatory criticism, and so disputes can be resolved through our dispute resolution team if needed.
From first call to resolution.
- 01
Scope the data flows
We map the customer journey, API calls, data fields, payment flows and licences of each party, then identify where Bangladesh Bank, payment systems and data protection requirements apply to the open banking or embedded finance model.
- 02
Agree the structure
We recommend the agreement set, consent design and any regulatory engagement needed, and agree a term sheet covering roles, fees, security standards, liability principles and exit before detailed drafting begins. Open points are tracked in one shared list.
- 03
Draft and negotiate
We prepare or review the API access, data-sharing and programme agreements, negotiate with counterparties and coordinate with technology teams, tax advisers and foreign counsel on technical schedules and cross-border points. Technical schedules are reviewed line by line.
- 04
Launch and adapt
We support go-live, consent and privacy documentation, then advise on new features, partners, regulatory guidance and incidents, keeping open banking documents aligned with the live product as it grows. Periodic reviews keep schedules current.
“Demonstrates an extraordinary command over both domestic litigation and international arbitration.”
The Legal 500 Asia Pacific, Bangladesh: Dispute resolution, client feedback
Related reading.

PSO and PSP Licence in Bangladesh 2026: Payment Licensing, E-Money, Digital Banks and the Financial Regulators

Bangladesh Data Protection Law: 2026 Guide

Bangladesh Banking Regulations: A Practical 2026 Guide

Cyber Law Compliance in Bangladesh 2026: A Business Checklist under the Cyber Security Act
All insights →
What is open banking?
How is embedded finance different from open banking?
Do open banking agreements need Bangladesh Bank approval?
Can a foreign aggregator connect directly to Bangladeshi banks?
What security standards should an open banking agreement include?
Can data received through an API be used to build credit scoring models?
What should a platform check before embedding a partner's loan product?
Can TRW help negotiate with a bank's standard API terms?
Connect your financial services with clear, enforceable agreements
Speak with the partners about Open banking in Bangladesh or across borders.
Book a consultation →



