> ## 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.

# SDK Surface Status

> Reviewed public vs draft resource status across the current Zentra SDKs

This page is the source of truth for how to read the current SDKs in this repo.

<Warning>
  Some SDKs still expose generated helpers for compatibility or draft resources such as `customers`, `wallets`, `plans`, or `subscriptions`. Identity is different: it is part of the reviewed gateway surface, but it remains tenant-gated and may not be enabled in every environment.
</Warning>

## Reviewed Public SDK Surface

Treat these as the reviewed public HTTP surfaces across SDK usage today:

* transfers
* payments
* cards
* virtual accounts
* webhooks
* identity when your tenant is enabled for the reviewed identity namespace

When a checked-in wrapper still lags the live gateway for one of those reviewed surfaces, prefer the current reviewed public docs and direct HTTP until the SDK catches up.

## Draft Or Tenant-Specific SDK Helpers

These namespaces may still exist in generated or checked-in SDKs, but they should be treated as draft or tenant-specific unless your tenant explicitly enables them:

* customers
* wallets
* analytics
* plans
* subscriptions

## Current Repo Notes

* `zentra_identity` is part of the reviewed gateway surface today, but it is still tenant-gated and should not be assumed to be enabled everywhere.
* the recurring-billing product flow remains draft/reference even though the reviewed payments surface contains the primitives needed to build it
* JavaScript, Python, Go, Flutter, Ruby, C#, Rust, and PHP now expose reviewed public payment helpers for charges, refunds, and saved payment tokens while retaining legacy initialize or compatibility helpers where they already existed
* the iOS app-side multi-currency consumer has started its asset-aware cutover with compatibility aliases, but some app-side and non-public-API consumers still lag on broader Core Engine asset naming
* the checked-in Java, C#, and Android wrappers are narrower than the broader server SDKs: they currently center on transfers, payments, virtual accounts, logs, and webhook verification rather than the full reviewed namespace set
* the older Go `resources/` package path in this repo has been aligned too

## How To Use This Page

Use this page together with:

* [Reviewed Public Surface](/resources/reviewed-public-surface)
* [SDK Overview](/sdks/overview)
* the SDK-specific README/changelog in the repo when you need language-level caveats

## Current Recommendation

* start new integrations from reviewed public primitives first
* only use compatibility or draft helpers when your tenant explicitly exposes them
* treat identity helpers as reviewed only when your tenant has the identity namespace enabled
* prefer the reviewed payment helpers in JavaScript, Python, Go, iOS, Flutter, Ruby, C#, Rust, and React over older initialize/authorization-only flows
* treat SDK breadth as a compatibility artifact, not proof of reviewed public support