MyCAC API integration services (CAC International Bank · Djibouti)

1. ERP & accounting reconciliation

An import/export trader in Djibouti Port operates Sage or Odoo and needs every CAC International Bank entry to land in the general ledger nightly. We schedule a job that calls the statement API per account, normalises the tx_id, value_date, amount, currency and counterparty fields, and posts journal entries through the ERP webhook. Failures are retried with idempotency keys keyed on tx_id.

2. CACPAY merchant payout dashboard

A franchised retail chain uses CACPAY merchant QR codes at every till. Our integration listens for scan-and-pay confirmation events, aggregates them per merchant_id and store, and pushes a daily settlement report into the franchise headquarters' BI stack. CAC Wallet refunds are matched back to the original transaction in OpenFinance fashion.

3. Cross-border payroll for diaspora teams

A multinational with staff across Djibouti, Ethiopia and the UAE uses MyCAC's bulk file upload to push monthly salaries. We wrap the file upload in an API that accepts a payroll JSON, validates IBANs and mobile numbers, generates the institution-formatted file, submits it, and exposes a polling endpoint for confirmations — mapping naturally onto OpenBanking payment-initiation patterns.

4. Treasury & liquidity dashboard

A corporate treasurer monitors DJF, USD and EUR positions across MyCAC Corporate accounts. We expose a unified /positions endpoint that returns balance per account and currency, plus a 30-day cash-flow forecast derived from standing orders and known loan installments. The same feed powers Slack alerts when the operating buffer crosses a threshold.

5. Compliance & audit log export

For a regulated client, we deliver an immutable export of every authorized API call — request hash, consent ID, scope, response code and retained field set — into S3 with object-lock. Auditors can then trace exactly which MyCAC records were retrieved, when, and under whose consent, satisfying Banque Centrale de Djibouti and EU GDPR record-keeping requirements.

1. OAuth-style login bridge

POST /api/v1/mycac/login
Content-Type: application/json

{
  "username": "ALICE_DJ",
  "password": "<hashed>",
  "device_fingerprint": "fp_3f9a..."
}

// step 1: trigger SMS OTP via MyCAC
// step 2: confirm OTP, mint internal access_token
// step 3: bind biometric token (face / fingerprint) on next call

Response 200:
{
  "access_token": "eyJhbGciOi...",
  "expires_in": 1800,
  "scopes": ["balance.read","statement.read","wallet.read"]
}

2. Statement query (DJF / USD / EUR)

POST /api/v1/mycac/statement
Authorization: Bearer <ACCESS_TOKEN>

{
  "account_id": "DJ81-CAC-...",
  "from_date": "2026-04-01",
  "to_date":   "2026-04-30",
  "channels":  ["WALLET","CACPAY","BANK"]
}

Response 200:
{
  "account_id": "DJ81-CAC-...",
  "currency": "DJF",
  "page": 1,
  "items": [
    {
      "tx_id": "TX-2026...A1",
      "value_date": "2026-04-12",
      "amount": -2500.00,
      "channel": "CACPAY",
      "counterparty": "Merchant: Beyti Cafe",
      "balance_after": 184500.00
    }
  ]
}

3. CACPAY webhook + reconciliation

// CAC Wallet / CACPAY scan event delivered to your endpoint
POST https://yourapp.com/hooks/cacpay
X-Signature: hmac-sha256=...

{
  "event": "cacpay.scan.confirmed",
  "merchant_id": "MERCH-00481",
  "tx_id": "CP-2026-...-Z7",
  "amount": 1200.00,
  "currency": "DJF",
  "scanned_at": "2026-05-09T08:14:22Z"
}

// Verify HMAC, idempotency-check tx_id,
// then post to ERP / BI / accounting system.
// On 5xx from downstream, retry with exponential
// backoff up to 24h before alerting ops.

Regulatory alignment

MyCAC is regulated under Djibouti's central bank framework (Banque Centrale de Djibouti, BCD), which supervises all licensed banks including CAC International Bank, BCIMR, Salaam African Bank and Saba African Bank. Our integrations follow BCD guidance on consent, customer-due-diligence record-keeping, and cross-border transfer reporting. For European or UK counterparties we additionally observe GDPR data-minimization and right-to-erasure obligations, and we can apply PSD2-style strong customer authentication (SCA) when a partner bank requires it.

Privacy & data minimization

We retain only the minimum fields needed for the agreed use case, and we strip sensitive identifiers (full PAN, IBAN tail, biometric template) before they leave the trust boundary. Every API call is signed, every response is logged with a consent ID, and every consent is revocable from a single endpoint. NDAs and data-processing agreements are available on request.

BCIMR Connect

The mobile app of Banque pour le Commerce et l'Industrie – Mer Rouge, the largest bank in the Horn of Africa with roughly 45% market share in Djibouti. Holds account, statement and transfer data that pairs naturally with MyCAC for treasury aggregators.

Salaam African Bank

An Islamic banking institution active in Djibouti since 2008, offering POS, mobile and online banking plus the WAAFI mobile wallet — a typical Sharia-compliant counterpart to MyCAC for unified P2P transfer reporting.

Saba African Bank

One of three fully-fledged Islamic banks in Djibouti, established in 2006. Customers often hold side-by-side accounts with CAC International Bank, making cross-bank statement export a recurring integration request.

WAAFI mobile wallet

Salaam African Bank's wallet, interoperable with Djibouti Telecom's D-mobile. WAAFI ledger entries pair with CAC Wallet entries to give a complete picture of mobile-money flows in the country.

D-money / D-mobile (Djibouti Telecom)

Djibouti's telco-led mobile wallet. Frequently appears on the counterparty side of MyCAC transfers, so unified de-duplication is helpful for analytics and AML.

telebirr (Ethiopia)

Ethio Telecom's mobile-money platform, reporting around 72 million users by mid-2025. Cross-border traders along the Djibouti–Addis corridor often need MyCAC and telebirr movements unified for reconciliation.

CBE Mobile Banking (Ethiopia)

The Commercial Bank of Ethiopia mobile app, a major counterpart for cross-border SWIFT and trade flows out of Djibouti Port — a common neighbour to MyCAC in regional treasury stacks.

East Africa Bank

A regional player offering retail and corporate banking; users sometimes maintain parallel accounts to access different correspondent networks alongside CAC International Bank.

CAC MobileNet

The legacy CAC online-banking front-end (package cac.mobile.net). Many corporate users still operate it alongside MyCAC, so a small bridge keeps both data streams aligned.

MyCAC Corporate & MyCAC Islamic e-Token

Companion apps from the same publisher: MyCAC Corporate adds Trade Finance (letters of credit, letters of guarantee) and bulk salary uploads; the e-Token apps deliver TOTP-style two-factor authentication that integration scripts can emulate under explicit user consent.

Deliverables checklist

• OpenAPI / Swagger specification for every endpoint we ship
• Protocol & auth flow report (login, OTP, biometric, token refresh)
• Runnable source for login, statement and CACPAY webhook in Python or Node.js
• Sample payloads for DJF, USD and EUR transactions
• Postman collection plus end-to-end automated test suite
• Compliance dossier: BCD-aligned consent, GDPR record-keeping, NDA template

Engagement workflow

1. Scope confirmation: pick the data scopes (login, balance, statement, CAC Wallet, CACPAY, loans).
2. Protocol analysis & API design (2–5 business days).
3. Build & internal validation against sandbox or authorized live data (3–8 business days).
4. Documentation, samples and automated tests (1–2 business days).
5. Hand-off, security review and warranty window for fixes.

Typical first delivery: 5–15 business days. Real-time CACPAY webhooks or cross-bank stacks may run longer.

About us

We are an independent technical studio focused on mobile-app protocol analysis, OpenData and OpenFinance integrations. Our engineers come from retail and corporate banking, payment gateways, mobile-money operators and cloud security, and we have shipped integrations covering UPI, PIX, SEPA, SWIFT, GCC bank apps and a growing portfolio of Horn of Africa institutions including CAC International Bank, BCIMR and Salaam African Bank counterparts.

• Full pipeline: protocol analysis → API design → build → validation → compliance
• Custom Python / Node.js / Go SDKs and test harnesses
• Source code delivery from $300 — runnable code plus full documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted MyCAC API and pay only per call, no upfront cost
• Security reviews, threat models, NDAs and DPAs available on request

Contact

Tell us the target app (MyCAC), the data scopes you need (CAC Wallet, CACPAY, statements, standing orders, loan schedule) and the delivery model (source code or pay-per-call). We reply with a fixed quote and a delivery plan.

Contact page

What do you need from me to start a MyCAC integration?

How long does a MyCAC API delivery take?

How do you handle Djibouti banking compliance?

Can you integrate CACPAY QR payments into our merchant stack?