Skip to content

Solution

Open Banking / API Integration

Post into the same books your accountants close from

A staff REST API with bearer tokens, Stripe-style idempotency keys, duplicate detection and maker-checker enforcement, so your own apps and partners post batches and approvals safely.

The same API that powers the Zenus field app is available to your own applications. It covers customer search, balance and ledger enquiry, field deposit and withdrawal batches, multi-credit and multi-debit batches, journal entries, expense and loan approvals and reference lookups.

Every mutating call accepts an Idempotency-Key header and replays the original response on retry; a same-day duplicate is bounced with a 409 until confirmed; and every approval enforces maker-checker with a 403. Tokens are revoked the moment a staff member is deactivated.

What it does

  • Bearer-token authentication with per-user rate limits
  • Customer search, balance and ledger endpoints
  • Field deposit, field withdrawal and transfer batch endpoints
  • Journal, expense and loan approval endpoints
  • Idempotency-Key header with cached replay
  • Duplicate detection with explicit confirmation
  • Maker-checker enforced on every approve/reject
  • Instant token revocation on deactivation

How it works

  1. 1

    Request API access for your institution.

  2. 2

    Authenticate a staff account and receive a token.

  3. 3

    Post batches with an Idempotency-Key.

  4. 4

    Approve from the web, the app or the API.

Related

Works together with

See Open Banking / API Integration on a live demo

A live demonstration on a sandbox with sample data, then a free two-day data assessment for a fixed go-live date.

Prefer WhatsApp? Chat with us