The Bank of Ghana published a draft Open Banking Directive on Sept. 28, 2026, according to policy analysis of the draft by Bold Lite Agency. The direction is clear: customer data will move between regulated institutions through APIs, and only with the customer's consent.
This did not arrive from nowhere. The Bank's Open Banking Service Initiative launched in 2024, ran a proof of concept in 2025, and a pilot is expected to follow the directive. Banks, payment service providers and fintechs that wait for the final rules before touching their data will be the ones scrambling.
Readiness is mostly unglamorous work. Customer records have to be clean enough to share. Consent has to be captured in plain language a Ghanaian customer actually understands, and stored so it can be shown later. APIs have to be secured like the money systems they are: authenticated, logged and monitored.
There is also a customer-trust side. Open banking asks people to agree that one institution may pass their data to another. Institutions that explain what is shared, with whom and for how long — in the app, in plain words — will earn that consent. Institutions that hide it in fine print will not.
KSPACE TECHNOLOGIES builds software and integrations for businesses that run on shared data: APIs, data exchange and the audit trails that make both safe to operate.
If your institution will sit on either side of an open banking connection, the data work comes first. Talk to KSPACE TECHNOLOGIES about getting your systems ready to share — with consent, and with proof.