What shapes custom software for Bahrain
Bahrain's economy is more regulated and more regional than its size suggests. Both facts show up in requirements.
| Topic | What it means for your software | Decide early |
|---|---|---|
| Supervision by the central bank | Banks, insurers, investment firms and payment companies are licensed by the Central Bank of Bahrain. Technology they buy is subject to their own obligations on outsourcing, security and record keeping | What your compliance team needs from a supplier, stated before the proposal |
| Open banking | The central bank issued open banking rules in 2018, and a published framework describes the interfaces for account information and payment initiation. Access is for licensed providers, or through one | Whether account data or payments are needed, and through which licensed party |
| The regulatory sandbox | Since 2017 the central bank has run a sandbox in which new financial products can be tested under supervision before a full license | Whether the product will enter the sandbox, and what must be demonstrated there |
| Regional headquarters | Companies manage Gulf operations from Bahrain. One system may serve entities in several countries, each with its own currency, tax and reporting | The entities and countries the software must cover, now and later |
| Data protection and location | The data protection law sets conditions on moving personal data out of the kingdom, and regulated firms may have further rules on where records sit | Where data will be hosted, agreed with legal and compliance |
| Arabic and English records | Customer documents and regulatory filings may need Arabic, while internal work is largely in English | Which outputs need Arabic, and who approves the terminology |
| Audit and evidence | Supervisors and auditors ask for proof of who did what and of the controls in place | The events to record, how long to keep them, and who may read them |
Workflows we build for Bahraini companies
The first two are specific to financial firms. The others apply to any regional operation.
Customer onboarding with checks
For licensed financial firms taking on customers.
- Applicant submits details and documents
- The system runs the checks your policy requires through your chosen providers
- Results are shown to a compliance officer
- The officer approves, declines or asks for more
- The decision and its evidence are stored together
- The customer is told the outcome
Account data with consent
For products that read a customer's bank data.
- Customer is shown what will be accessed and why
- Gives consent with their bank through the licensed provider
- Data arrives over the approved interface
- The product uses it for the stated purpose
- Consent can be withdrawn from the app
Group reporting across countries
For regional headquarters.
- Each entity records transactions in its currency
- Rates are applied by an agreed rule
- Figures consolidate for the group
- Managers see each country and the total
- Reports are exported for auditors
Client portal for a professional firm
For law, audit, advisory and corporate services firms.
- Client signs in securely
- Sees open matters and requests
- Uploads documents to the right matter
- Receives updates and invoices
- Every access is logged
What we build
Financial products and back offices
Customer-facing products and the internal tools behind them, designed with your compliance team from the first workshop.
Client and partner portals
Secure access for customers, brokers or suppliers to their own records and requests. Our client portal development page shows what these include.
Connections to banks and systems
Integration through licensed open banking providers, core systems, ERPs and document stores, using documented interfaces.
Multi-entity operations
One system for several companies, currencies and tax treatments, with consolidated reporting.
Records and audit trails
Tamper-evident logs of decisions and access, with retention and export designed for reviewers.
Documentation for your regulator
Architecture, data flow and control descriptions written as the system is built, for your own submissions.
What we need from you
- Whether the firm or the product is licensed, and by whom
- Your compliance team's requirements for technology suppliers
- The entities, countries and currencies involved
- The systems and banks the software must connect to
- A product owner with authority across business and compliance
Ownership and licensing terms are defined in the project agreement.
A readiness checklist for custom software in Bahrain
Before development starts
0 of 8 checkedWhat to do next
Tell us what the firm does, whether it is licensed and which process or product you have in mind. We will reply with a first release, the compliance questions we would raise early and the documentation the build would produce. Start a conversation or book a 30-minute call.
Comparing suppliers? Our software vendor evaluation checklist gives every proposal the same questions.
Common questions
Can you build for a firm licensed by the central bank?
Yes, working to the requirements your compliance team sets. Licensed firms carry obligations on outsourcing, security testing, record keeping and data location, and those shape how the system is built and hosted. We ask for them in writing at the start and produce the documentation your team needs for its own submissions. We do not give regulatory advice.
How does open banking work for a product built in Bahrain?
Under the central bank's rules, account information and payment initiation services are provided by licensed firms over defined interfaces, with the customer's consent. A product that is not itself licensed reaches bank data through a licensed provider. We integrate with that provider's interface and design the consent screens. The central bank's current rules should be checked before the model is fixed.
Should a new financial product go through the sandbox?
That is a decision for the founders and their advisers. The central bank's sandbox lets a firm test a new product with real customers under supervision before full licensing. If you plan to apply, the software should be able to limit users, record everything a supervisor might ask about and be changed quickly during the test period.
Can one system serve our companies in several Gulf countries?
Yes. The system is designed with entities as a core concept: each has its own currency, tax settings, numbering and users, and the group sees consolidated figures. What must stay separate, for legal or data protection reasons, is agreed at the start, because that determines whether one database or several is appropriate.
Where to go from here
Related serviceCustom Software DevelopmentSoftware that fits the process you already run