Access control
Role-aware permissions and protected administrative actions.
Security first
Trust is an architecture decision.
BiliPay makes no certification or regulatory claim on this preview. What it does commit to is a security-minded architecture, documented before anything goes live.
Webhook safety
Signed events, replay awareness and idempotent processing.
Environment separation
Test and production concerns kept strictly distinct.
Secret handling
Credentials stored server-side only, never exposed to the browser.
Auditability
Operational events designed to be traceable and reviewable.
Controlled activation
Live processing enabled only after verified readiness.
Defence in layers
Every request passes through the same checks.
Authorization is enforced on the server for every protected action. Nothing in the browser can grant access it does not already have.
- 1
Identity
Authenticated sessions with verified email and optional second factor.
- 2
Authorization
Server-side role checks; the browser never decides permissions.
- 3
Data isolation
Row-level rules keep each merchant's records separated.
- 4
Audit
Append-only status and review events for sensitive actions.
Ready to build with BiliPay?
Merchant onboarding and developer access roll out in controlled phases.