Skip to main content

API-first pattern

Best when your backend orchestrates payment logic.

Frontend-first pattern

Best when you want rapid UX iteration first.

CLI-assisted pattern

Best for scripted demos and local validation.

​
Integration decision tree

​
Pattern 1: API-first

1

Implement key generation and wallet setup

Use /api/keys and persist secrets in your secure key store.
2

Implement create/publish flow

Use /api/stealth and /api/registry in one orchestrated backend flow.
3

Implement recipient discovery

Use /api/stealth scan endpoint in background jobs or user-triggered checks.

​
Pattern 2: Frontend-first

1

Map user journey in the app

Start from /explore/frontend-experience and confirm each user action.
2

Mirror each UI action to API endpoint

Attach each frontend event to one backend endpoint and audit payload contracts.
3

Add fallback CLI scripts

Keep a CLI script pack for support and QA parity checks.
  • Product flow in frontend
  • Deterministic logic in backend API
  • CLI scripts for support, QA, and incident reproduction
For most teams, hybrid gives the best balance of developer speed and operational clarity.