1. Payment methods
Browser RUB purchases use YooKassa. The universal Android app offers a choice of YooKassa or RuStore Pay; the app shows actual availability. Russian bank cards and the Faster Payments System (SBP) depend on the methods available for the particular order.
CloudPayments, including possible foreign-card support, is being discussed in parallel. Approval for Sanvimo, supported countries, cards and currencies are not confirmed. This method is not automatically included in the YooKassa launch.
Methods available for an order will be displayed before payment. This is a one-time purchase and does not authorise future automatic charges. YooKassa fees are not added to the Sanvimo Pro price.
RUB orders are placed in a browser or an Android version of Sanvimo with RUB checkout available. Payment methods are checked for each order. The version inside Telegram uses the separate Telegram Stars channel.
2. RuStore Pay on Android
Choose RuStore under Sanvimo Pro. Before confirming, review the account, product, duration, total and currency. Sanvimo offers a one-time Pro duration without automatic renewal; RuStore determines the payment methods available in its screen.
If a purchase is still processing, check or restore its status. Do not create a duplicate payment through another provider: switching providers does not cancel the original purchase or confirm that it failed.
Once payment is confirmed, Pro belongs to your Sanvimo account. If you were charged but have no access, contact support with the date, amount and RuStore invoice or purchase number, if known. Passwords, bank codes and full card numbers are not needed.
Payment confirmation and receipt access follow RuStore rules and the selected payment method. Provide an email in the RuStore payment screen when needed. Receipts from YooKassa and its settlement process do not automatically apply to this purchase.
3. Foreign cards, currency and conversion
A foreign-issued card and a foreign-currency payment are different things. A card account may use one currency while the payment service processes another. RUB prices on this website neither confirm support for every card nor set an exchange rate.
Before launching this method, we will publish supported countries and cards, transaction currency, how the exchange rate is determined and possible fees. The buyer will see the final amount and currency before confirming payment. Foreign cards and currency payments are not offered until those terms are agreed.
If the card account currency differs from the transaction currency, the bank or another payment participant may convert it and charge a fee. Sanvimo does not set the bank’s rate or promise the Bank of Russia rate or an unchanged currency equivalent. Check your bank’s terms before payment.
Future integration details and settlement arrangements with the seller do not change an already-paid order. Adding a provider does not authorise automatic charges or change the separate Telegram Stars rules.
4. How to buy through YooKassa
- Sign in to your existing Sanvimo account in a browser or an Android version with RUB checkout available. If you do not have an account, register first.
- Choose Sanvimo Pro for 30, 180 or 360 days. Check the total, duration and the account that will receive access.
- Provide a valid email address for your electronic receipt. Read the terms and refund policy, then confirm acceptance of the terms.
- Proceed through the payment service available for the order. Enter card details or confirm SBP in that provider’s or bank’s interface. Do not pay if the amount or currency differs from what was agreed.
- After successful payment, return to Sanvimo and check the order status and Pro dates in your account. Closing the bank page does not cancel a confirmed payment.
5. When Pro becomes available after YooKassa payment
Confirmed successful payment starts automatic access delivery. The maximum activation time is 24 hours after the payment provider confirms payment. Newly purchased time is not consumed before access is actually provided.
If Pro is already active, the new period continues paid access without consuming periods in parallel. Exact dates are shown in the account. A rouble purchase also applies to a linked Telegram account after ownership is verified.
6. Charged but no Pro access
Do not pay for the same order again. Check that you are signed in to the purchasing account, then email support@sanvimo.com with the order number, date, amount, account email and what Sanvimo shows. If you have no order number, the other details are enough to start an investigation.
You may attach payment confirmation after hiding unnecessary details. Do not send a full card number, card security code, password, bank code or account sign-in code.
We will check the payment-provider status, match the payment to the correct order, and restore access delivery or make the refund due. We will acknowledge your request within one working day. You may contact us immediately; there is no need to wait 24 hours before reporting an issue.
If access is not provided within the stated time, you may request a refund and use other statutory remedies for delay. A repeated notification for one payment does not create another charge or grant the duration twice.
7. YooKassa electronic receipts
The Receipts from YooKassa service is connected for rouble sales. An electronic receipt or a link to it is sent to the email provided before payment. This service does not deliver receipts by SMS.
Cloud Receipts is being considered for a possible CloudPayments integration: receipts use the cash registers of CloudKassir LLC and identify the seller as the service supplier. This scheme applies to CloudPayments and does not replace Receipts from YooKassa. Setup and applicability to foreign cards are still being discussed.
The receipt identifies the seller, Sanvimo Pro and the chosen period, the payment amount and required fiscal details. VAT is not charged under the seller’s exemption. A purchase produces a receipt for 100% prepayment of the service. Delivered service is settled against that prepayment at the end of each calendar month in Moscow time and when the period ends. The settlement amount is proportional to the paid service period provided, accounting for refunds; rounding is reconciled in the final receipt. These receipts do not charge the buyer again. A refund produces the corresponding receipt.
If no receipt arrives, check the address and spam folder, then email support@sanvimo.com. A missing receipt email does not itself cancel confirmed payment. A bank charge notification is not a fiscal receipt.
8. Data used for payment
Purchases use account details, the receipt email, order number, product and duration, amount and currency, and the statuses and identifiers of payments, refunds, receipts and access delivery. These are needed to perform the contract, process payments, meet record-keeping duties and provide support.
If the account is deleted before settlement is complete, the receipt email is retained separately only while outstanding receipt and refund obligations are fulfilled. It is deleted automatically once those obligations are complete. Deleting an account does not mean that undelivered service is treated as delivered.
Necessary data is shared with the provider for that payment, payment participants and the chosen receipt scheme. The browser uses YooKassa; Android uses the selected available provider, YooKassa or RuStore Pay. RuStore receives technical order and product identifiers and a pseudonymous buyer identifier; account email is not passed in these purchase fields. CloudPayments and Cloud Receipts are being considered separately. Mentioning future services does not mean order data is shared with them. Food logs, weight records and recipes are not shared for payment.
Do not enter card details, card security codes or confirmation codes on the marketing website or send them to Sanvimo support. The payment provider or bank handles them in its own interface. A payment does not constitute consent to marketing email.
Before a new payment method is enabled, the single app policy must describe actual recipients, purposes, data shared, retention and any cross-border processing involved. Mentioning a future integration does not replace the required grounds for processing or constitute user consent.