Order, payment, documents and consents

This page covers ordering and paying for a cloud instance, and the documents and consents that appear in the process.

Placing an order, step by step

If you are doing this for the first time, the whole path is six steps (the first few are usually already done in onboarding):

Verify your e-mail — ordering is unavailable without it.
Fill in your requisites (individual or company/sole proprietor) — needed for the invoice and act, and filled in before payment.
Pick a plan and period (monthly/yearly) on the plans storefront.
Choose a subdomain name — the address will be <name>.cloud.aihummer.ru; the system shows “Free/Taken” instantly.
Pay — by card (individuals and companies) or by invoice (companies/sole proprietors only).
Wait for provisioning — the status on the dashboard turns “Your assistant is running” and the “Open panel” button appears.

Each step is detailed below.

Choosing a subdomain

When ordering you choose a subdomain name for the instance — the address will be <name>.cloud.aihummer.ru. The name is checked live: 3–30 characters from a-z, 0-9 and a hyphen (no leading/trailing or double hyphen), not on the stop-list and not already taken. A “Free/Taken” pill and a preview of the full address are shown; the pay button is enabled only for a free name.

Order and payment

Ordering requires a verified e-mail. In v1 a customer may have one active managed instance. On order you pick a plan and period (monthly/yearly), the subdomain is re-validated and a subscription is created; the first payment runs. Possible subscription statuses: pending, active, past_due, canceled, expired. After a successful payment the instance begins provisioning — track it on the instance dashboard.

Payer requisites (individual or company) are filled in before payment — on the requisites step of onboarding or on the Profile screen.

Free trial — 10 days free

The cheapest cloud plan (“Personal Helper”) starts your first order with a 10-day free trial. Terms:

the offer applies once — on your first cloud order;
a card is required (the invoice flow for companies does not open a trial) — the card is linked right away; for verification the bank charges ₽1 and refunds it immediately (the plan price is not charged during the trial);
for all 10 days the instance runs as usual, for free;
when the trial ends, the plan price is charged automatically to the linked card and the subscription continues as paid;
you can cancel any time before the trial ends on the Subscription screen — then nothing is charged.

On the pricing page the cheapest cloud plan’s price is shown accordingly: “Free for 10 days, then <price>/mo”.

Paying by card

Payment runs on the secure page of a payment gateway (T-Bank acquiring). Card details are never stored in the portal — they stay with the bank; the portal receives only the payment result. Every payment issues a fiscal receipt (54-FZ). For a yearly period or auto-renewal the card is bound for recurring charges — you can unbind it and manage auto-renewal on the Subscription screen.

Paying by invoice (companies)

Companies and sole proprietors always have invoice payment available — the payment method is a toggle on the payment step (including during onboarding); individuals pay by card only. With an invoice:

The subscription is created in the pending status with auto-renewal off.
An invoice is issued (visible right away on the waiting screen and under documents) — pay it from the company bank account or via the SBP QR code printed on the invoice itself.
Once the operator records the payment, the subscription activates, an act is issued and instance provisioning starts — the waiting screen updates by itself.

Payment history

The “Payments” screen is a table: date, kind (initial / recurring / refund), amount and status (pending / paid / failed / refunded). It shows how charges go through. If the payment provider passed a fiscal receipt link, the payment row shows a “Receipt” link.

Documents and consents

The “Documents” screen:

Invoices and acts — strictly yours, scoped to your account. A row shows the number (С-YYYY-NNNN for invoices, А-YYYY-NNNN for acts), kind, date and amount; the button downloads a ready A4 PDF with the logo, stamp and signature. The invoice is created when a payment is created, the act (transfer of rights) when it settles. The payer details come from your requisites.
The invoice carries a QR code for paying via SBP (GOST R 56042 / ST00012 format) — the invoice can be paid by scanning the code in a banking app.
Amounts are quoted with VAT included in the price: the invoice and the act carry an “Including VAT (22%) …” line (the rate is set by the vendor and frozen into the document at issuance).
The list supports filters (kind and period), sorting and pagination.
Consents — records of consent to personal-data processing and to the offer, captured at registration (with a date), marked “Given”.

If it didn’t work

The pay button is disabled — most likely the subdomain name is taken or failed validation (3–30 chars a-z, 0-9, no leading/trailing hyphen). Pick a free one — a “Free/Taken” pill is shown next to it.
Card payment failed — payment runs on the bank’s secure page; check your card limits and details, go back and retry. The subscription status on the dashboard shows the reason.
I’m a company but don’t see invoice payment — the operator must first confirm your requisites (required for companies/sole proprietors before the first payment); wait for the “Requisites confirmed” e-mail, see Profile and requisites.
Paid by invoice but the instance isn’t provisioning — with an invoice the subscription activates once the operator records the payment; the waiting screen updates by itself.
No receipt arrived — the fiscal receipt is issued by the payment provider; the “Receipt” link appears on the payment row on the Payments screen once the provider passes it.

Instance dashboard — lifecycle after payment.
Subscription management — auto-renewal and plan change.
Profile and requisites — the details on documents.