Use Pakana's non-custodial, read-only Satellite API plus browser-generated proofs to integrate private payments into apps, agents, and services without moving private keys to a server.
The public Satellite surface is read-only and designed for integration monitoring. It exposes ledger state, proof status, and transaction confirmations.
| Endpoint family | Returns | Usage |
|---|---|---|
/api/satellite/ledger-state |
Current chain context (network, latest indexed ledger, ingest timestamp). | Health checks, telemetry, and read-side sync. |
/api/satellite/proof-status/{proofId} |
Proof lifecycle status (queued, verified, failed) plus related tx identifiers. | Track proof processing after client submission. |
/api/satellite/tx-confirmations/{txHash} |
Confirmation depth/finality for a submitted Stellar transaction hash. | Update app UX once payment settlement is confirmed. |
Satellite APIs are read-only integration endpoints. Wallet secrets and proving keys stay in the client; the server never takes custody of user signing material.
Per BROWSER_PROVER_IMPLEMENTATION_RUNBOOK_2026-03-13, proofs are generated in the browser and private witness data remains local to the user session.
Use the active TestNet environment at https://staging.pakana.net to send a private test payment and confirm settlement.
https://staging.pakana.net./api/satellite/proof-status/{proofId}./api/satellite/tx-confirmations/{txHash}.Start with runbooks, then request access for private SDK and contract integration materials.