AiHummer
English▾
Sign inAccount
v1.1.x▾
v1.2.xstablev1.1.xstablev1.0.xstable
{ }Swagger
Customer portal/Profile and requisites

Profile and requisites

v1.1.x · updated 2026-07-27

The “Profile” screen holds your personal details and payment requisites. It is built from cards for personal data, requisites, password, e-mail and account security.

Personal data

You can edit the last name, first name and patronymic (the patronymic is optional), date of birth and gender. The e-mail is read-only in the profile — it changes via a separate confirmed step (below).

Changing password and e-mail

  • Change password — current and new (at least 8 characters). After the change all sessions are ended and you are signed out.
  • Change e-mail — two-step: a code is sent to the new address, then you enter it to confirm. An already-used address is rejected.

Two-factor authentication

The “Security” card adds a second sign-in factor. It is entirely optional: you can turn two-factor on and off at any time — it protects the account even if someone learns your password. A badge at the top shows the state (“on” / “off”). Three tools are available:

  • Authenticator app (TOTP). One-time codes from Google Authenticator, 1Password, Aegis and any compatible app. Click “Enable” — a QR code appears: scan it in the app (or enter the shown secret key manually) and confirm with the six-digit code. From then on, sign-in asks for the app code in addition to your password. To disable it you need a current app code, a recovery code, or the account password.
  • Passkeys. Sign in with a fingerprint, Face ID or a hardware key (YubiKey) via the WebAuthn standard — no password or codes. Click “Add passkey”, give the key a clear name and confirm creation on your device. Added keys are listed (when added, when last used); each can be renamed or removed. You can register several keys (for example, a phone and a hardware key).
  • Recovery codes. One-time codes for when you don’t have your phone or key at hand. Click “Generate codes” — the set is shown once: copy it or download the .txt right away and keep it somewhere safe (a password manager, say). Each code works once; “Regenerate” creates a new set and voids the old one.

The “Disable two-factor authentication” button removes every second factor — sign-in goes back to password only (this requires a code or the password).

[!NOTE] With two-factor on, after your login and password you get a “Second factor” screen: enter the app code, a recovery code, or sign in with a passkey. If the confirmation has expired, start the sign-in again.

Requisites

The “Requisites” block holds the billing details used on invoices and acts. Requisites are first filled in before payment — on the requisites step of onboarding. The person type is a segmented switch:

  • Individual — full name (required), INN (optional, exactly 12 digits), address.
  • Legal entity / sole proprietor — company name (required), INN (10 digits or 12 for a sole proprietor), KPP (9), OGRN/OGRNIP (13/15), legal address, bank, account (20), correspondent account (20), BIK (9).

Every save sets the requisites to “pending”. An operator can confirm them — then the requisites are locked (read-only, a 🔒 badge) and used on documents; a confirmation e-mail is sent to you. Statuses: “not filled” / “pending” / “🔒 confirmed”. Typed values are preserved when you toggle individual/legal.

[!NOTE] For companies / sole proprietors operator confirmation is required before the first payment: onboarding stops on the “requisites awaiting confirmation” step and resumes after the confirmation e-mail. The person type (individual/company) chosen during onboarding cannot be changed after onboarding completes — contact support to change it.

Next