StableNexus
Cases

Choose a case

Pick a case, start the run, and continue the lifecycle inside cabinet.

Families

Run release, redemption, and issuer-grade stablecoin control flows.

Case

2 cases

Geo

4 stages in the lifecycle

SG reserve-backed USD cycle

Allows Singapore issuers and treasury teams to run a reserve-backed USD stablecoin cycle across DBS reserve setup, issuer-core mint and release, Independent Reserve or Finery market execution, and DBS payout close.

Setup

Reserve currency

USD

Redeemer wallet

Matches holder wallet in demo

Payout bank path

DBS reference generated on run

Lifecycle

Flow

• StableNexus verifies the SG perimeter through ACRA / Bizfile, issues the DBS reserve path, and records issuer-core reserve match before issuance.

• Reserve recognition stays explicit before any mint or wallet release step.

Actors

ACRA / Bizfile — Issuer verification

DBS — Reserve and payout bank path

Issuer core — Reserve matching and issuance control

Artifacts

reserve path notereserve confirmation
Responsibilities

Responsibilities

StableNexus coordinates policy, workflow, and evidence. Appointed parties execute regulated functions.

What StableNexus coordinates

Policy, workflow, approvals, and evidence across each route.

Route packaging, operating posture, and buyer-visible handoff logic.

Wallet delivery, servicing controls, and managed route orchestration where the lane requires it.

What appointed parties execute

Issuance, custody, settlement, conversion, payout, registrar, and paying-agent functions.

Reserve handling, redemption, and legal issuer obligations for separate activation tracks.

Partner-operated treasury, payout, and bridge-market execution once those stages go live.

What you receive

A visible route map with the operating posture shown at each stage.

Exportable evidence, lifecycle objects, and named operating parties where they matter.

A clear split between the demo asset, restricted activation, and placeholder production tracks.

System tracks

Demo asset, issuer-controlled activation, and production placeholder tracks stay visible without becoming separate audience stories.

SNXUDemo asset trackGSPTSeparate activation trackProduction assetPlaceholder track
API and evidence

Integrate once and receive route events, outputs, and evidence for every run.

Use one API contract across wallet delivery, payout, bridge routing, and asset servicing / sukuk flows while keeping route posture and evidence explicit.

Read docsOpen routes
curl -X POST https://api.stablenexus.dev/v1/program-runs \
  -H "Authorization: Bearer sn_test_..." \
  -H "Idempotency-Key: 7a3307a8-bbd4-4d17-a4de-3be0db4f0ad7" \
  -H "Content-Type: application/json" \
  -d '{
    "scenario_id": "my_local_balance_to_snxu_wallet_standard_v1",
    "inputs": {
      "amount": "1000.00",
      "destination_wallet_address": "DESTINATION_SOLANA_WALLET"
    }
  }'

What the integration returns

Policy and control outputs

Keep route scope, approvals, and control posture visible without relying on screenshots or side-channel explanation.

Lifecycle updates

Receive deterministic webhook events as a case moves from intake to result.

Exportable evidence bundle

Return lifecycle records, route selections, and delivery objects in machine-readable form.

Request access

Request Pilot Access

Tell us the route, markets, and outputs you need. We scope the pilot around that flow.

Tell us what you need to run

Start with the route, markets, and outputs that matter. Scope, readiness, and team detail can stay behind the advanced section.

Advanced scope and readiness