Store settings
Settings connect your store name, VAT rule and notifications to your verified account. Changes are saved on the server for the current user.
On this page
Store name#
Choose a short, recognizable name that your customer expects to see on the order. The name must contain 1–80 characters after trimming surrounding spaces.
A display name does not replace legal details or your customer agreement. Keep secrets, payment credentials and other people’s personal information out of this field.
VAT payer#
The default payer is the customer. VAT applies only to cards and Alipay. Switching the setting does not change SBP or cryptocurrency totals.
Existing invoices keep their saved terms. When creating an invoice, independent customer VAT and fee shares from 0 to 100% can override the defaults. The store preference only supplies a default for future invoices.
A saved preference does not expand gateway capabilities. The current live card and Alipay channels require 100% customer VAT and 0% customer processing fee; other saved allocations remain calculations.
| Value | Rule for a new invoice |
|---|---|
| customer | VAT is added to the customer base price |
| merchant | The merchant covers VAT from the base price |
Telegram notifications#
Select payment, payout, support and security categories. Choosing a category controls notifications; it does not activate a payment channel or generate financial events.
A test message checks delivery to the linked private chat. Its status appears in the notification center and GET /api/notifications. A queued message is not yet delivered; also check Telegram.
Saving and errors#
The form confirms a completed save. If the network fails, your input remains available for a retry; pressing Save alone does not prove the change was stored.
Sign in again when your session expires. The server identifies the account from the session and does not accept another store owner ID from the browser.
Theme and demo data#
The display theme is saved locally on the device. The demo workspace uses separate browser data and does not change the server account.
Resetting the demo removes only test records in that browser. A demo export is not a bank statement or proof of payment.
Multiple stores and one USD base price#
Choose All stores for aggregate analytics and operations, or select a store for its own records. Each store has a separate storeId, name, VAT default, invoices, API keys, webhook endpoints, event history and website application. Notifications and support tickets belong to the account. An account can create up to 100 stores. Existing records remain in its first store.
New workspace invoices use pricingMode="universal" and a USD base price. Any includes card, alipay, sbp and crypto; a merchant may select a subset. Cards and Alipay charge USD. SBP charges RUB using the Bank of Russia USD/RUB reference rate. Crypto charges USDT under the explicit invoice rule 1 USD = 1 USDT. This is an invoice conversion rule, not a market USDT quote. The gateway supplies the selected coin’s rate, exact transfer amount and instructions before transfer.
The reference rate and both amounts are frozen on creation. Invoices involving RUB conversion expire within 24 hours. If the reference rate cannot be obtained, creation fails with FX_UNAVAILABLE; no invented or stale fallback rate is used. The owner response amountMinor and quotes use the USD accounting currency. quotes[method].settlement contains the native charge quote. Public checkout exposes the selected charge currency in currency, the original price in baseAmountMinor/baseCurrency, and the reference rate in fx. Once a payment has been dispatched, its method cannot be changed; an invoice has one gateway operation.
Create an API key inside the intended store and send Authorization: Bearer <key> from your server. Its store binding is immutable; X-Kevmi-Store cannot grant it access to another store. Browser sessions select X-Kevmi-Store: <storeId>; omitting it selects the first store. The all value is accepted only by GET /api/account/dashboard and GET /api/payment-links. Mutations require a selected store, Origin and X-CSRF-Token. Account IDs and store IDs are different identifiers.
For compatibility, API requests without pricingMode="universal" retain native pricing and the original currency restrictions. Existing invoices are never recalculated. Confirmed receipts in analytics reflect verified payments less saved invoice expenses; they are not a withdrawable balance. Legacy invoice currencies remain separate and payouts are arranged with support. Fulfil an order only after checking payment.fulfillmentReady=true and payment.status="succeeded" through the server API, event history or a signed webhook.