180 Core — Developer Infrastructure
Cryptography & Security Doctrine

Built on Open Standards. Verifiable by Design.

Relying parties never store user passwords, shared JWT secrets, or raw card numbers. Every handshake and ledger entry is cryptographically verifiable.

Asymmetric RSA-256 Signing & JWKS Rotation

Every access and ID token is signed with RS256 private keys. Public verification keys are published at /.well-known/jwks.json with safe rotation grace periods.

Mandatory RFC 7636 PKCE (S256)

All authorization code grants enforce SHA-256 Proof Key for Code Exchange to prevent authorization code interception on SPAs and native mobile apps.

HMAC-SHA256 Signed Webhooks & Replay Defense

Downstream payment, subscription, and verification webhooks are signed using per-application secrets in X-180-Signature with timestamp tolerance checks.

Short-Lived Tokens & Central Revocation

15-minute ephemeral access tokens paired with 7-day rotating refresh tokens and instant session revocation via /api/oauth/revoke or the console.

Zero Hardcoded Secrets & Strict Isolation

Per-application tenant and username isolation, Helmet security headers, distributed rate limiting, and dynamic KMS/environment secret injection.

Sovereign Compliance Architecture

Engineered with consent-first OAuth flows, immutable double-entry ledger auditing, and DPDP Act 2023 & RBI-ready data handling boundaries.