Crédit Municipal Open Banking & API Access

Pulling your Crédit Municipal (France) balances and transactions into your own tools no longer means chasing bank certificates or building a PSD2 stack from scratch. open-banking.io links to Crédit Municipal on your behalf and hands the raw account data straight back to you — decrypted only on your device, with a key nobody else holds. It covers 2,600+ EU and UK banks, so Crédit Municipal sits alongside the rest of your financial connections in one place.

How to connect Crédit Municipal

Connecting happens entirely in the open-banking.io dashboard — there is no code, endpoint, or key involved at this stage:

  1. Sign up for open-banking.io and set your encryption passphrase. Your keys are generated locally on your own device, so the service never sees them.
  2. In the dashboard, search for Crédit Municipal and choose the account type you want to link — both business and personal accounts are supported.
  3. You are redirected to Crédit Municipal's own secure login, where you approve access under PSD2. open-banking.io never sees your banking credentials.
  4. Your accounts sync into the dashboard. The consent you grant lasts up to 180 days, after which you simply re-approve on Crédit Municipal's screen.

Note that Crédit Municipal does not publish a public BIC in our records (BIC: n/a); selecting the bank by name in the dashboard is all you need.

Access your data

Once Crédit Municipal is connected, developers can optionally read the data programmatically. Open the Developers page, create an API key, and export a credentials.json — this bundles the API key together with your private decryption key. From there use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Requests carry the X-Api-Key header, and every response is decrypted locally with your own key. There is no connect command — the CLI and SDK only read or refresh connections you already approved in the dashboard.

Because open-banking.io is zero-knowledge, its servers store only your public key. An API key on its own returns ciphertext; without your private key it stays unreadable. That is the privacy trade at work — certificate-free setup, ~EUR 3/month, and data only you can decrypt.

FAQ

Do I need an API key to connect Crédit Municipal?

No. Connecting is done in the dashboard and approved on Crédit Municipal's own login. API keys are only for reading data afterwards.

Can open-banking.io read my Crédit Municipal transactions?

No. Data is decrypted locally with a key only you hold; the service keeps just your public key.

Up to 180 days, then you re-approve directly with Crédit Municipal.

Ready to start? Visit open-banking.io.