SikaaHub API Health Check

Developer Documentation

Endpoints

SikaaHub API Endpoints

Base URL: https://api.sikaahub.com/v1

All responses use:

{"success":true,"message":"Human readable message","data":{},"meta":{}}

Errors use:

{"success":false,"message":"Human readable error","error":{"code":"ERROR_CODE","details":{}}}

Health

Authentication

Login supports X-Device-ID and X-App-Version. Access tokens expire. Refresh tokens are stored hashed and rotated.

Customer and merchant registrations start as pending_verification until OTP verification succeeds.

Customers

Merchants

Merchant QR payloads expose only the merchant code and a SikaaHub type marker, never internal numeric IDs.

KYC

Devices

QR Verification

Payments

Financial creation endpoints require Idempotency-Key. Confirmation requires transaction PIN. Wallet balance updates run inside database transactions with row-level locks.

Payment lifecycle: pending, processing, successful, failed, cancelled, reversed.

Confirmed payments create one transaction record and immutable ledger entries:

Wallets and Ledger

Wallet balances are stored for fast reads. The immutable ledger is the source of truth. Every financial movement writes at least two ledger entries, one debit and one credit. Corrections must use reversal entries, not edits or deletes.

Wallet owner types:

Ledger entry types:

Withdrawals

Statuses: pending_customer_confirmation, pending_merchant_approval, approved, completed, failed, cancelled, reversed.

Withdrawal lifecycle:

1. Customer initiates withdrawal from merchant.

2. Merchant approves.

3. Customer confirms with transaction PIN.

4. Merchant completes after cash payout.

5. Merchant wallet is debited.

6. System settlement placeholder wallet is credited.

7. Commission is calculated and ledgered when applicable.

Transactions

Supported filters: type, status, from, to, cursor, limit. Default limit is 20, maximum is 100.

Cursor format is opaque to clients. Use the next_cursor returned in meta.

{
  "meta": {
    "limit": 20,
    "next_cursor": "MjAyNi0wNS0xMSAwNjowMDowMHwxMjM=",
    "has_more": true
  }
}

Merchant Commissions

Admin Commission Rules

Rules support flat and percentage commissions with optional caps.

Admin Wallet Monitoring

Risk

Basic risk checks currently flag high amounts, velocity, failed PIN attempts, new devices, and suspicious merchant/customer patterns as placeholder hooks for a stronger fraud engine.

Webhooks

Provider Operations

Settlements and Reconciliation

Webhook writes store the raw payload and external event ID to prevent duplicate processing.

Developer API Keys

API keys are hashed in the database and only shown once at creation.

Mobile App APIs

Merchant Dashboard APIs

Disputes, Feedback, and Pilot Operations

Admin

Stage 5 control center additions:

Stage 8 admin operations portal additions:

Stage 9 Operations

Stage 10 Sandbox and QA

Stage 11 Developer Platform

Stage 12 Audit and Readiness CLI