Agreement on joining the recurrent payment system

This Agreement (the “Agreement”) is entered into between the Nash service operator, the owner of the website https://nashconnect.me (the “Contractor”), and any capable natural person (the “Client”) who accepts the public offer (the “Main Agreement”) through the Contractor’s website and who intends to pay for Nash services by bank card with automatic debits from the card provided when paying under the Main Agreement.

Placing an order and enabling auto-renewal constitutes the Client’s full and unconditional acceptance of this Agreement. Where Russian law applies, this Agreement is an adhesion contract within the meaning of Article 428 of the Civil Code of the Russian Federation. Clicking the payment button means that the Client has read this Agreement, understood it, and agrees to be legally bound by it.

For this Agreement: “Website” means https://nashconnect.me. “Recurring payment service” means automatic charges in favour of the Contractor to renew a Nash subscription, in the amount and on the schedule set by the selected plan. “Bank card” means a payment card issued by a financial institution and accepted on the Website. “Processing environment” means the bank and/or payment provider infrastructure (including, where available, YooKassa, CloudPayments, acquiring banks, and other lawful payment methods offered on the Website) through which card transactions are processed. “Personal data” has the meaning under applicable data protection law.

3.1. The recurring payment service allows the Client to pay for Nash services under the Main Agreement by automatic debits from the bank card to the Contractor, on the terms chosen with the plan and as set out in the Terms of Service / offer on the Website.

3.2. Settlements under this Agreement are made in the currency shown on the Website at the time of payment (typically RUB for relevant payment methods), unless otherwise expressly stated at checkout.

3.3. The Contractor does not charge a separate fee for enabling or disabling recurring payments, except for third-party fees (bank, payment system) that may apply under the Client’s agreement with the bank.

3.4. Activation: the Client subscribes on the Website or in the app, confirms the information and acceptance of the Main Agreement and this Agreement, is redirected to the payment provider (depending on the method), enters card details, and completes payment. After successful payment and acceptance of this Agreement, recurring payments are deemed enabled, and the Contractor may initiate automatic debits to renew the subscription under the Main Agreement.

4.1. After auto-renewal is enabled, charges may occur no earlier than 3 (three) days and no later than 15 minutes before the end of the current paid period, and after it ends, in the amounts and timeframes needed to renew services under the Main Agreement, unless a different schedule is expressly shown on the Website or in the Client’s account.

4.2. The actual debit is performed by the card issuer; the Contractor sends requests through the processing environment and does not store full card data on its own systems.

4.3. The Contractor does not guarantee that every card transaction will succeed; authorisation decisions rest with the bank and payment infrastructure.

4.4. The Client warrants that they are the cardholder and enters details correctly when enabling the service.

4.5. Activation is subject to technical availability for the Contractor, the processor, and the bank. The parties are not liable for inability to enable the service for reasons beyond their reasonable control.

4.6. Disabling: the Client may turn off auto-renewal in the online account on the Website (subscription management) and/or send a request to support@nashconnect.me with a subject line that clearly identifies the message as a “recurring payment cancellation”. The Contractor will handle such requests within a reasonable time, typically within up to 48 hours of receiving a complete request.

4.7. If the card account has insufficient funds, the Contractor may retry debits within the rules of the payment system and processing settings.

4.8. The Client is responsible for monitoring charge dates and amounts. The Contractor is not obliged to send a separate reminder before each upcoming charge unless required by applicable law or expressly provided on the Website.

5.1. The Contractor may refuse to enable recurring payments without stating reasons where required for security, compliance, or technical constraints.

5.2. The Contractor may amend this Agreement; the new version takes effect when published on the Website unless a different effective date is stated. If the Client disagrees, they may disable auto-renewal and stop using recurring payments. If the Client does not send a disablement request within 10 (ten) days of publication and continues to use paid features with auto-renewal, the changes may be deemed accepted to the extent permitted by mandatory law.

5.3. The Contractor is not liable for temporary unavailability of recurring payments for reasons outside its control; the Client may use other payment methods offered on the Website.

5.4. If the card is lost or replaced, the Client must promptly update the payment method in the account and/or notify the Contractor via support@nashconnect.me to reduce the risk of erroneous or unwanted transactions.

5.5. The Client must use only their own card; if a third party’s card is used, the Client bears the risks and liability towards the cardholder and towards the Contractor within the limits permitted by law.

5.6. The Contractor may disable recurring payments after repeated failed authorisations or if the Client breaches the Main Agreement, using notice channels available for the account (e-mail) where technically feasible.

5.7. Neither party is liable for failure to perform due to force majeure, provided timely notice is given to the other party where possible.

6.1. This Agreement remains in effect for the duration of the Main Agreement and auto-renewal; it ends when auto-renewal is disabled, the Main Agreement is terminated, or acceptance is withdrawn as permitted by law.

6.2. Disputes shall first be resolved through negotiations; if no agreement is reached, they shall be submitted to a court or other competent authority as determined by applicable law and the Main Agreement.

6.3. The Contractor’s legal details and contacts are published on the “Contacts” page (https://nashconnect.me/support). The current support email is support@nashconnect.me.

We also recommend reading the Terms of Service and Privacy Policy of Nash.