Skip to content

Authentication

How dashboard login, PIN, and secret reveal work.

Dashboard login

Merchants sign in at /login with username and password. Sessions are established through the Perper backend; the portal stores session state for authenticated API calls (project list, create, get, pay). /login

PIN step

If your account requires a PIN, login returns a PIN challenge. Enter the 4-digit passcode on /pin (or inline on login when the flow stays on that page). Failed or expired PIN challenges send you back to login. /pin

Project secret reveal

Viewing a project secret is a sensitive action. The portal:

  1. Redirects you to login with a short-lived verification payload tied to your user and project.
  2. After successful verification, the BFF sets an HttpOnly reveal cookie (`__Host-perper.key` in production) and returns to the project page with ?secret=true.
  3. Calls seeSecret once (server reads the cookie — never document.cookie), then clears the cookie and query param.

Copy the secret when it appears. Treat it as a credential: store in environment variables or a secrets manager, and never commit it to git.

Accounts

New merchant accounts are created in the Perper app, not in this portal. Perper app.

Bank-level security controls are documented under Security. Security (bank-level)