Ahadu Lekulu API Integration & OpenBanking Solutions

Account Balance & Real-Time Position

The Lekulu home screen surfaces a live ETB balance tied to hardware-backed device authentication. Via protocol analysis we expose a structured balance endpoint — account number, available balance, ledger balance, last-refreshed timestamp — suitable for treasury dashboards, credit-decision engines, or personal finance aggregators that need verified, real-time position data without manual screen-checks.

Transaction History & Statement Export API

The transaction history view in Ahadu Lekulu stores per-transaction records including amount, direction (debit/credit), counterparty identifier, channel (IPS, QR, bill pay, wallet), and timestamp. Our API wrapper adds date-range filtering, pagination cursors, and export serialization to JSON, CSV, or Excel — enabling monthly accounting closes, ERP reconciliation runs, and audit-log generation without manual data entry.

IPS/ET-SWITCH Interbank Transfer Protocol

Ahadu Bank participates in Ethiopia's Instant Payment Switch (IPS) and the ET-SWITCH national interoperability layer. Each interbank transfer carries a routing reference, beneficiary bank code, and settlement status. Exposing these fields via an integration API makes it possible to build corporate payment status dashboards, compliance AML checks that cross-reference IPS codes, and automated retry logic for failed or pending cross-bank transfers.

Telebirr Wallet Bridge & Multi-Wallet Ledger

Ahadu Lekulu's built-in Telebirr transfer integration creates a bidirectional fund-flow event stream between Ahadu Bank accounts and Ethio Telecom's Telebirr (51.5 million registered users as of early 2026). Capturing both sides of these wallet-to-bank events allows fintech platforms, micro-lending companies, and ERP systems to build a unified transaction ledger that spans both the bank and the mobile wallet — a critical requirement for Ethiopia's blended payment reality.

Bill Payments, SchoolPay & Airtime Top-Up Data

Ahadu Bank added SchoolPay — school fee collection via mobile — in response to direct user demand, and also supports airtime top-up and essential service bill payments in-app. Each of these creates a structured payment event with biller ID, student reference, amount, and confirmation code. Syncing these records to an ERP or school management system eliminates manual cashier reconciliation and provides parents with automated payment confirmation trails.

QR Payment Records & Exchange Rate Feed

Every QR-initiated payment in Ahadu Lekulu generates a transaction record tagged with the QR code origin, merchant identifier, and amount. Separately, the app's exchange rate utility publishes daily National Bank of Ethiopia (NBE) FX rates for major currency pairs. Integrating these two data streams supports merchant analytics dashboards and multi-currency treasury reporting — both increasingly relevant as Ethiopia's banking sector opens to foreign participation under Proclamation No. 1360/2025.

Auth: Biometric Session Token Flow

# Step 1: Device binding verification (hardware-backed)
POST /api/v1/auth/device-verify
Content-Type: application/json

{
  "device_id": "<HARDWARE_BOUND_DEVICE_ID>",
  "biometric_token": "<FIDO2_ASSERTION>",
  "app_version": "2.x"
}

# Response: short-lived session token
{
  "session_token": "eyJ...",
  "expires_in": 900,
  "account_ids": ["ETH-AHADU-XXXXXXXX"]
}

# Step 2: Refresh using secure token rotation
POST /api/v1/auth/refresh
Authorization: Bearer <SESSION_TOKEN>
# Returns new session_token on success
# 401 on expired / revoked binding

Balance Query: Real-Time Account Position

# Query live balance for one or more accounts
GET /api/v1/accounts/balance
Authorization: Bearer <SESSION_TOKEN>
X-Account-Ids: ETH-AHADU-XXXXXXXX,ETH-AHADU-YYYYYYYY

# Response
{
  "retrieved_at": "2026-04-22T08:15:00+03:00",
  "accounts": [
    {
      "account_id": "ETH-AHADU-XXXXXXXX",
      "currency": "ETB",
      "available_balance": 48250.00,
      "ledger_balance": 50000.00,
      "status": "active"
    }
  ]
}

# Error handling
# 403 — account not bound to session device
# 429 — rate limit (max 60 req/min per session)
# 503 — core banking system unavailable (retry after)

Transaction History: Paginated Export

# Fetch transaction history with filters
POST /api/v1/accounts/transactions
Authorization: Bearer <SESSION_TOKEN>
Content-Type: application/json

{
  "account_id": "ETH-AHADU-XXXXXXXX",
  "from_date": "2026-03-01",
  "to_date": "2026-03-31",
  "channels": ["IPS", "WALLET", "QR", "BILL_PAY"],
  "page": 1,
  "page_size": 50
}

# Response (one record shown)
{
  "total": 143,
  "page": 1,
  "records": [
    {
      "txn_id": "IPS20260315XXXXX",
      "date": "2026-03-15T11:22:08+03:00",
      "type": "debit",
      "channel": "IPS",
      "amount": 5000.00,
      "currency": "ETB",
      "counterparty_bank": "CBE",
      "ips_routing_ref": "ETSWITCH-XXXXXX",
      "description": "Staff salary transfer"
    }
  ]
}

National Bank of Ethiopia (NBE) Framework

All Ahadu Bank API integrations we deliver operate within the framework set by the Banking Business Proclamation No. 1360/2025 and associated NBE Directive No. SBB/95/2025, which opened Ethiopia's banking sector to foreign participation and strengthened consumer data standards. The NBE's Phase Two national digital payments strategy (launched March 2025, covering 2025–2029) mandates interoperability and data traceability across licensed payment service providers — requirements that our IPS/ET-SWITCH integration layer is explicitly designed to satisfy.

We apply data-minimization principles: only the fields required for the stated integration purpose are extracted. All sessions operate under customer authorization with device-binding verification, respecting Ahadu Bank's hardware-backed authentication architecture. AML/KYC linkage is preserved — transaction records retain the originating account and counterparty identifiers required for regulatory reporting.

Data Handling & Security Standards

• Customer authorization required before any data extraction begins
• End-to-end encrypted transport (TLS 1.3) for all API calls
• Session tokens are short-lived (15 min) with hardware-bound refresh
• No plaintext credential storage — FIDO2/biometric token patterns only
• Data retention limited to customer-specified periods; automated purge on contract end
• Audit logs retained for AML reporting — NBE-aligned transaction traceability
• NDA available on request; GDPR-equivalent data processing addendums for EU-linked clients