Step 01
Step 1
Sign in with phone-OTP or magic link; enable TOTP from /settings/security on first visit.
DeveloperB2B
Partner portal.
Self-serve dashboard, API keys, webhooks, usage, cost budgets, MFA, support.
The problem
Why this exists.
Most fintech-API partner portals are read-only and assume the integrator will email support for anything real.
We want every operational action — issue a key, rotate it, pause a webhook, raise a budget alert — to be self-serve, with audit trail and TOTP gate where it matters.
How it works · 3 steps
From input to outcome.
- Step 02
Step 2
Issue and rotate API keys; configure webhook endpoints with signing secrets.
- Step 03
Step 3
Watch usage and cost budgets; respond to WARN and STOP thresholds before they bite.
Under the hood
The models and routes behind it.
Models called
No models cite this feature directly — backing logic is deterministic Python.
API routes
Internal-only — no public route handler.
Compliance posture
- TOTP gate on key rotation, partner-level pause, and budget changes under totp-on-destructive-admin.
- Every write lands in audit-trail with the actor email and timestamp.
- Lifecycle states (pending review, approved, paused, blocked) carry explicit copy and an appeal path.
What it's not
The portal is the operational surface for an existing partnership. It is not the sales channel — first contact is at /partners.
Related · features & stories