For developers

Mass payouts, via API.

SOLnova is primarily a no-code product for finance teams. When you need programmatic disbursement — marketplaces, gig platforms, high-volume cycles triggered by your own platform's events — the same controls are available via REST API.

Request API access → See an example
Same controls as the UI · audited end-to-end
$ curl -X POST https://api.solnova.co.za/v1/batches \
  -H "Authorization: Bearer $SOLNOVA_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "reference": "gig-week-42",
    "approval_policy": "auto",
    "lines": [
      { "beneficiary_id": "ben_8124",
        "amount": 124800,
        "rail": "payshap" }
    ]
  }'
→ 201 Created · batch_01H9XK...
→ webhook: batch.released → 1,420 payouts settled
When the API fits

For teams that pay programmatically at scale.

Marketplaces & gig platforms

Trigger payouts from your own platform events — job completed, milestone passed, weekly cycle closed. Thousands of payouts per cycle, controlled.

Embedded payment workflows

Build SOLnova into your operational pipeline. Your code creates the batch; SOLnova handles review, audit, and settlement.

High-volume disbursement

EFT, RTC, eWallet, and prepaid cards — including card issuance for unbanked recipients — accessible from a single API surface.

What the API exposes

The same controls, from your code

  • Batch creation, line management, and submission for approval
  • Approval state machine — submit, approve, reject, release
  • Webhook callbacks for batch lifecycle and per-line events
  • Multi-rail routing — EFT, RTC, eWallet, prepaid cards in one call
  • Approval-rule definitions for auto-pass on trusted beneficiaries
  • Audit-log retrieval, scoped to your tenant
What stays the same

API is not a bypass

Every payout created via API still flows through SOLnova's review, change tracking, and audit. The default policy is maker-checker; you decide what to auto-approve via rules.

This is what separates SOLnova from a raw payment API. Programmatic disbursement gets the same human-grade controls that finance teams use in the UI — your engineering scale without losing your operational trust.

A bank's payment API hands you a rail. SOLnova hands you the workflow that runs the rail safely.

Typical integration

Four steps from event to settled payout

  • Your platform fires an event (gig job completed, marketplace seller paid out, contractor invoice approved).
  • A POST to /v1/batches/lines adds the line to a pending batch — or starts a new one keyed by your reference.
  • SOLnova applies your approval rules. Lines outside the rule queue for human review; the rest auto-release.
  • Webhook fires on settlement (per line and per batch). Reconciliation data flows back into your platform.
Full API reference, OpenAPI spec, and SDKs (Node, Python, Go) on request. We onboard developer teams personally — every integration gets a dedicated engineer for the first two cycles.

Build mass payouts on SOLnova

REST APIWebhooksSame controls as the UI
Schedule a Demo Or email [email protected]

[email protected] · solnova.co.za