Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.usezentra.com/llms.txt

Use this file to discover all available pages before exploring further.

Zentra functions as a financial infrastructure control plane. Rather than hiding our operations behind black-box facades, Zentra makes each transaction inspectable. When your application triggers an API request, Zentra validates tenant-scoped policy rules, routes the request through verified primitives, logs deterministic ledger entries, and delivers signed, signature-verifiable webhooks. This control plane serves as the single source of truth for engineering, compliance, finance, and operations teams to inspect state transitions, retry attempts, and raw evidence.

​
Core Architectural Boundaries

The control plane isolates and governs our financial operations across four critical layers:

Reviewed API Contracts

The reviewed public API surface represents stable contracts. Only these namespaces are guaranteed to maintain backward compatibility under production traffic.

Tenant-Scoped Isolation

API keys, webhook endpoints, fee models, daily transaction velocity, and risk parameters are structurally isolated per tenant to prevent cross-contamination.

Deterministic Ledger writes

No money moves without a matching ledger mutation. Ledger entries use strict idempotency keys to ensure duplicate submissions are rejected safely.

Operational Evidence Logs

API request signatures, provider callbacks, timing logs, and compliance verifications are packed and stored as permanent audit trails.

​
The Operational Request Path

The following diagram illustrates how an API invocation moves through Zentra’s gatekeeping layers, policy engines, and evidence loggers before communicating with underlying bank or scheme partners.

​
Scoped Key Verification

API keys enforce namespace restrictions at the gateway boundary. A tenant can generate multiple sandbox or live secret keys with specific permissions to protect their environment:
  • Sandbox Keys (sk_sandbox_...): Restricted to virtualized bank rails and mock responses. Perfect for local integration tests and CI pipeline verification.
  • Live Keys (sk_live_...): Bind to production funds. Live keys require active tenant policies and compliance approval before the gateway starts passing real transactions.
  • Granular Scopes: Create separate keys for analytics ingestion (GET only) and card operations to isolate risk surfaces.
If a route or endpoint is marked draft or reference in our documentation, it exists as a design reference. Do not route live traffic through these namespaces. Always design production flows around Zentra’s stable, reviewed primitives.