Arcane separates private transaction execution from disclosure review. Your backend owns the product flow and calls the Solana SDK. The SDK builds private payment operations, scans UTXOs, generates proofs, and submits through the relayer. The Auditing Portal is separate from the user transaction path.

​
Execution path

StepComponentResult
1FrontendConnects the user’s external Solana wallet and calls your backend
2Product backendOwns session state, generated private keys, proof signatures, UTXO cache, history, and SDK calls
3DatabasePersists wallet rows, scan progress, decoded UTXOs, encrypted outputs, and operation history
4Privacy Layer SDKBuilds Arcane instructions, scans UTXOs, creates proofs, and submits through a relayer
5Arcane APIProvides indexer and relayer APIs
6Solana RPCReads public balances and confirms transactions

​
Disclosure path

Controlled disclosure is a separate workflow.
LayerVisibility model
Product backendStores your product references, signatures, status history, and support context
Private transaction stateUses commitments, nullifiers, encrypted outputs, proofs, and UTXO state
Auditing PortalGives approved users scoped review and reporting workflows

​
Key boundary

The SDK does not own your product records, backend routes, cookies, sessions, UI, or database schema. Your application keeps those responsibilities and uses Arcane for private transaction execution.

Private payments integration guide

Follow the backend-managed pattern from the SDK integration guide.

Solana SDK reference

See package status, exports, configuration, and SDK examples.