1
Evaluate access
Review pricing, included capacity, support level and production approval requirements before requesting credentials.
Financial Operating System for API consumers.
Thenga.io gives approved consumers one versioned API for identity, KYC, payments, messaging, compliance, audit evidence and governed value movement. Your app calls api.thenga.io/v1; Thenga owns provider routing, secrets, callbacks, monitoring, reconciliation and support evidence behind that boundary.
How Consumers Integrate
2
Request approval
Submit organisation, vertical, use case, expected volume and regulated-flow requirements for access review.
3
Sign in after approval
Use api.thenga.io to manage profile, credentials, subscription, usage, remaining capacity, cancellation requests and support.
4
Call the versioned API
Send identity, KYC, payment, messaging and evidence requests through api.thenga.io/v1 with tenant, vertical, correlation and idempotency context.
Core Concepts
Tenants & Verticals
Every request carries tenant and vertical scope so shared infrastructure can serve multiple ecosystems safely.
One API Boundary
Consumers see Thenga states while provider adapters handle PayFast, KYC, messaging, ledger and future integration details internally.
Business Transactions
Controlled value movement becomes a monitored, auditable business event with journal, ledger, payment and case evidence.
Policy & Evidence
Compliance decisions, provider checks, audit records and evidence packs are treated as first-class platform outputs.
First Integration Path
1
Resolve identity
Call POST /v1/identities/resolve-or-create to anchor the consumer's user to a stable Thenga identity.
2
Submit KYC when required
Call POST /v1/kyc/submissions. The consumer sees Thenga review states rather than raw provider output.
3
Start the value flow
Register context, merchant and order, then call POST /v1/transactions/spend-or-pay for ledger spend or external payment orchestration.
4
Notify and inspect evidence
Trigger messaging from Thenga-owned state changes, then inspect transaction state, journal evidence, alerts, cases, outbox and audit records.
Pricing Options
Sandbox
For builders evaluating the API. Includes sandbox credentials, limited monthly capacity, API docs and basic support.
Launch
For pilot consumers. Includes guided onboarding, higher capacity, integration support, evidence exports and compliance review before production value movement.
Scale
For production platforms and enterprise partners. Includes contracted capacity, account management, support commitments, reconciliation and dedicated review workflows.
Request Access
What approval unlocks
- Environment-specific API credentials.
- Default capacity and rate limits.
- Access to profile, subscription, usage and support controls at
api.thenga.io. - Sandbox or production readiness guidance based on the selected plan.
What Thenga reviews
- Organisation, use case and vertical context.
- Expected identity, KYC, payment and messaging volume.
- Regulated-flow exposure and compliance requirements.
- Support needs and launch timeline.
Required Headers
Authorization: Bearer <service-or-user-token>
X-Correlation-Id: corr_...
X-Idempotency-Key: idem_...
X-Vertical: oncor
X-Tenant-Id: thenga
Local Quickstart
1
Run the API profile
docker compose --env-file .env -f deploy/compose/dev.yml up --build
2
Check service health
Call GET /health and GET /ready before moving into contract testing.