Install

596installs

Page bridge

Onboarding

The email account opens on yap-pay.xyz. Yap Signer still generates the username on the device. This page does not create the wallet.

What the page does

  • /onboarding is the account page. After the wallet exists, Yap Signer signs a pairing proof and opens /onboarding/pair/<session>. The session value is random. The database stores only its hash, plus the public key and username, for 30 minutes. Yap Signer may also send the account email and account password on POST /api/onboarding/session so yap-pay.xyz can open the second account without a second form. Those values are YapPay account credentials, not a seed or vault secret. The pair and login pages also offer Google and Apple sign-in; after either provider succeeds, the same pairing cookie links the wallet username. An 8-digit code is still emailed for password signup. If signup fails (email taken, mail down), the pairing URL still works and the wallet on the device stays created. A forgotten password is replaced from /login/forgot with another emailed code. That code does not reset the signer vault password.
  • The code is checked on /onboarding/verify. The account and the session start after it matches.
  • When a pairing session is active after verify, the site links the username Signer already proved and opens /onboarding/ready. Otherwise /onboarding/wallet asks for the username. The page reads it from getStatus. The typed name has to match.
  • If Signer has no wallet yet, the person creates or imports it in the extension, then returns and enters the username Signer shows.
  • The operator account pairs the same username on /dev and can clear that pairing there.

POST /api/onboarding/session

Called by Yap Signer after wallet create. Pairing proof is required. Account email and password are optional and best-effort.

{
  "publicKey": "<base58>",
  "username": "swift-fox-ab12",
  "signature": "<base64>",
  "email": "person@example.com",
  "password": "<yappay-account-password>"
}
{
  "ok": true,
  "url": "https://yap-pay.xyz/onboarding/pair/<token>",
  "account": { "status": "pending" | "skipped" | "email_taken" | "invalid" | "offline", "error"?: "…", "email"?: "…" }
}

A 401 means the proof was rejected. A failed YapPay signup never blocks the pairing URL when the proof is valid.

Page request

{
  source: "yap-app",
  type: "YAP_SIGNER_REQUEST",
  requestId: "<uuid>",
  method: "getStatus",
  payload: {}
}

Extension status

Same origin. Source yap-signer-extension.

{
  source: "yap-signer-extension",
  type: "YAP_SIGNER_STATUS",
  requestId: "<same id>",
  installed: true,
  hasWallet: true,
  unlocked: true,
  username: "swift-fox-ab12"
}

After Signer already has a username

Prefer sending email and account password with the pairing proof so the pair page can start the code and skip the password form. The username is linked automatically after the code when the pairing cookie is present. The account password is stored as a hash. The vault password and the 24-word phrase stay on the device.