When to use platform payment infrastructure

When a buyer pays $100, that money immediately belongs to multiple parties — creator, platform, perhaps a referral partner. A general-purpose checkout collects the full amount into one account and leaves the split as a reconciliation problem. Platform payment infrastructure applies the split atomically at checkout time: each wallet is credited in the same database transaction that records the payment. No nightly batch, no manual transfer, no double-counting.

A creator dashboard that shows "your balance" needs a ledger, not a spreadsheet. Every checkout completion, refund reversal, and hold release should move through a double-entry ledger so the balance is always the authoritative sum of all entries — not a cached counter that drifts under concurrent writes. Soledgic's creator_earnings wallet is that ledger account. The balance is always current because it is computed, not stored.

ACH payouts to bank accounts carry regulatory obligations. A creator who hasn't completed identity verification shouldn't be able to trigger a payout — but the right time to enforce that is at eligibility check, not at bank reject. Soledgic's payout eligibility endpoint returns the exact reason a creator can't receive a payout (KYB not approved, no bank account linked, balance below minimum) so your UI can show a clear next step, not a generic error.

Loyalty points, referral credits, gift balances, and prepaid plans all share one shape: value that lives inside your platform and can only be spent within it. A general-purpose payment processor isn't designed for this — you end up building a bespoke credit table that diverges from your payment ledger. consumer_credit wallets in Soledgic are a first-class ledger account type: they participate in the same double-entry system as creator earnings, so credits issued, spent, and refunded are always reconcilable.

A marketplace where buyers pay now but delivery happens later has a trust problem. Soledgic's hold primitive locks funds in a creator's wallet and prevents payout until the hold is explicitly released. The release can be triggered by a webhook from your fulfilment system, a support decision, or a time-based cron — whatever your dispute window requires. Funds are never in limbo: they're on the ledger, just constrained.

Double-entry means every credit has a matching debit on the same ledger. A creator's earnings wallet growing by $85 and the platform fee account growing by $15 are two sides of the same journal entry — traceable back to a single checkout session ID. The wallet activity endpoint returns the full ledger history: credits, debits, holds, releases, reversals, and their originating references. No blind spots.