Soledgic Documentation
Treasury infrastructure for platforms. Model participants, balances, holds, checkout sessions, payouts, refunds, reconciliations, fraud checks, compliance monitoring, and tax workflows on top of a ledger-native core.
curl -X POST https://api.soledgic.com/v1/participants \
-H "x-api-key: slk_test_your_api_key" \
-H "Content-Type: application/json" \
-d '{
"participant_id": "creator_456",
"display_name": "Jane Creator",
"email": "jane@example.com",
"default_split_percent": 80
}'Resource Flow
participant -> checkout_session -> wallet balance / hold -> payout -> refund reconciliations -> fraud evaluation -> compliance monitoring -> tax documents / summaries
The public API is resource-first. Edge functions validate and route requests into shared treasury services, and those services commit balanced ledger writes through PostgreSQL RPCs.See the architecture details
Shared identity, participant linking, ecosystems, and fixture cleanup are operator control-plane features. They require authenticated dashboard sessions and are intentionally excluded from the public `/v1` API reference and the TypeScript SDK.
Quickstart
Create a participant, launch checkout, inspect balances, and send payouts
Authentication
Authenticate resource requests with API keys and environment isolation
Core Concepts
Understand the resource layer, ledger guarantees, holds, and replay safety
API Reference
Generated reference for treasury resources and supporting accounting APIs
Webhooks
Receive checkout, payout, and refund events from the platform
SDKs & Libraries
Use the TypeScript SDK or integrate directly over REST
Why Soledgic?
Resource-First Treasury API
Participants, wallets, holds, checkouts, payouts, refunds, reconciliations, fraud evaluation, compliance monitoring, and tax resources are the canonical public surface for new integrations.
Ledger Guarantees
Money movement maps to balanced entries and atomic database writes. The ledger either commits the full state change or nothing.
Built for Platform Economies
Model delayed release policies, creator balances, internal transfers, and payout schedules without bolting treasury logic onto a checkout API.
Need help?
Start with the quickstart, then move into the API reference once your participant and checkout model is clear.