Terms of Use of the API Traffic Fines Service
1. General Provisions
1.1. This document (hereinafter, the Agreement) constitutes an offer by YooMoney Non-Banking Credit Organization Limited Liability Company, OGRN (Primary State Registration Number) 1127711000031 (hereinafter, the NBCO), to Internet users (hereinafter, the Developers) to use the API Traffic Fines Service (hereinafter, the Service) under the terms and conditions as follows.
1.2. By starting to use the Service or any of its individual functions, or by registering, the Developer is considered to have accepted all the terms of the Agreement in full, without any reservations or exceptions.
The NBCO may propose amendments and/or additions to this Agreement by publishing a new version of the Agreement on the NBCO website. The Developer accepts such an offer by taking conclusive actions to use the Service under the new terms and conditions. Amendments shall take effect immediately after the new version of the Agreement is posted on the Internet, unless otherwise specified in the new version of the Agreement.
If the Developer disagrees with any provision of the Agreement or with any amendments made in accordance with this clause, the Developer shall cease using the Service.
1.3. The use of the Service is governed by this Agreement and:
- the Agreement on General Terms of Registration and Use of Services, available at https://yoomoney.ru/page?id=525698;
- the Privacy Policy of "YooMoney", NBCO LLC, available at: https://yoomoney.ru/page?id=527708.
1.4. The laws of the Russian Federation shall apply to this Agreement and relations between the NBCO and Developer arising in connection with the use of the Service.
2. Terms and Definitions Used in the Agreement
2.1. The API Traffic Fines Service/ the Service shall mean a software interface that enables interaction with YooMoney service to search and pay traffic fines by Clients, including the ability to use certain functions of the service and/or place forms that allow interaction with YooMoney service on the Developer’s website(s) or mobile applications (hereinafter, the Developer’s Service). The traffic fines are searched and paid for within YooMoney Service based on information about the Client’s access to YooMoney Service, obtained through the use of the API Traffic Fines Service. To search for traffic fines, YooMoney Service interacts with the Public Information System for Regional and Local Payments (GIS GMP).
2.2. YooMoney Service shall mean services provided by the NBCO to the Clients to transfer funds without opening any account and provide electronic payment instruments, which description and other details are posted on the NBCO's website.
2.3 Client shall mean an individual serviced by the NBCO.
3. Terms of Use of the Service
3.1. For the purpose of using the Service as a set of computer software, the NBCO shall provide the Developer with a simple (non-exclusive), royalty-free license to use the API Traffic Fines Service by integrating it with the Developer’s Service to enable Clients to search and pay for traffic fines upon their request for the purposes. The Developer may only use the Service within its functionality in the manners and under the conditions set forth in this Agreement, and subject to the limits and restrictions fixed by the Service.
3.2. Limits and Restrictions
3.2.1. The NBCO reserves the right to set any limits and restrictions related to the use of the Service, including but not limited to limits on the number of requests made through the Service, and may change them at its sole discretion without prior notice to the Developers.
3.2.2. Information about the limits and restrictions in the Service shall be communicated to the Developer at the NBCO’s discretion by one or more of the following methods:
by setting appropriate technical limits in the Service’s functionality,
by including relevant information in the technical documents,
by posting such information on the NBCO website,
by communicating the relevant information to the Developer using any contact details provided by the Developer during registration or further use of the Service.
3.2.3. No use of the Service in violation of the limits or restrictions fixed in the Service is allowed.
3.3. The Developer may not:
3.3.1. Directly or indirectly charge a fee for end user’s / Client’s access to the Service functions.
3.3.2. Use the API Traffic Fines Service as part of services that may disrupt the normal operations of the NBCO’s or third parties’ websites and services, cause harm to the NBCO, Clients, or third parties, violate the laws of the Russian Federation or the laws applicable to the Developer’s Service, or otherwise infringe the rights and legitimate interests of the NBCO, Clients, or third parties.
3.3.3. Alter, decompile, and/or otherwise modify the software code obtained through the Service.
3.3.5. Delete, rearrange, hide, or modify any information contained in the Service and/or data transmitted using the Service, including information about the Service and its usage, advertising and informational materials, any indications of the rights holder (trademarks, logos, links, etc.), any indications of the person providing the Service, as well as any other notices and/or information transmitted by the Service.
3.4. The NBCO may approve the information (including its content, required format, layout, placement, and method of communication to third parties) that is to be communicated to third parties when the Developer’s Service interacts with the API Traffic Fines Service and/or is placed on forms of the Developer’s Service that enable interaction with YooMoney Service.
The information may include, but is not limited to, information about the Service, its usage and operation, any indications of the rights holder (trademarks, logos, links, etc.), any indications of the person providing and/or interacting with the Service, and advertising or informational materials.
Such information may be included in the data transmitted using the Service by technical means or delivered via the applicable technical protocol. The NBCO may also notify the Developer of the requirement to post such information by one or more methods provided in clause 3.2.2 of the Agreement.
The use of the Service without distributing the mandatory information in cases specified by the NBCO, and the deletion, modification, and/or concealment of mandatory information, is prohibited.
3.5. Developer Registration in the Service
3.5.1. To begin using the API Traffic Fines Service, the Developer shall complete the registration procedure. The registration method/ type of identifiers required to interact with the API Traffic Fines Service shall be approved by the NBCO and communicated to the Developer by posting the relevant information on the NBCO website and/or in the applicable registration forms.
3.5.2. The NBCO may:
unilaterally change the registration procedure/ applicable type of identifiers,
require the Developers to re-register by any method chosen by the NBCO, change identifiers required for communication with the Service, or confirm the information provided in the registration form,
request additional information about the Developer and Developer’s Service,
unilaterally withdraw from the Agreement in whole or in part without compensating the Developer for any losses resulting from such withdrawal
3.5.3. If the Developer refuses to re-register, change the identifier, provide additional information, or confirm information, the NBCO may refuse the use of or access to the Service or any part thereof.
3.6. The Developer agrees that the NBCO may monitor all activities related to the use of the API Traffic Fines Service, such as collecting and analyzing statistics on actions performed by the Developer and/or third parties with the API Traffic Fines Service, and other information that can be technically obtained through the Service.
The NBCO may use the above information at its discretion, in particular transfer the collected data to third parties, use it to generate reports on the Software, and make it publicly available.
3.7. The Developer is solely and fully responsible for the use of information about third parties, including personal data, that may be obtained with the Service.
If, during interaction with the API Traffic Fines Service, the Developer’s Service may receive/receives any information about a third party (including the Client/ user of the Developer’s Service), the Developer shall, in an accessible format and before its use, notify the third party intending to use the service developed with the API Traffic Fines Service about potential receipt of such information, the types of information that may become available to the Developer as a result of using such service, and the person who will have access to such information. The Developer shall also (if so required by the applicable laws) obtain the third party’s consent to receive or process such information, or to comply with other procedures required by the applicable laws.
The Developer is independently liable to the third party for the use and processing of the information and undertakes to resolve all third-party claims related to the use of such information independently and at its own expense, and if such claims are made against the NBCO, reimburse the NBCO for all resulting trial/pre-trial expenses.
4. Disclaimer
4.1. The Service is provided “as is,” without any warranties, including but not limited to warranties of continuous availability, stability, uninterrupted or error-free operation, or fitness for the Developer’s purposes and expectations. The NBCO shall not be liable for the actions of the Developer and/or third parties performed through the Service.
4.2. The NBCO shall not compensate for any direct or indirect damages caused to the Developer as a result of using or being unable to use the API Traffic Fines Service, changes to its functionality, or the NBCO’s refusal to maintain the Service.
4.3. The Developer is solely responsible to third parties for its actions when using the Service, such as ensuring compliance with the applicable laws and the rights and legitimate interests of third parties. The Developer independently and at its own expense undertakes to resolve all third-party claims related to the Developer’s actions when using the Service, and if such claims are made against the NBCO, reimburse the NBCO for all resulting trial/pre-trial expenses.
5. Means of Individualization
5.1. The Developer is not granted any rights to use the trademarks or trade names of the NBCO or third parties. The Developer may not distribute the results of its development using the above means of individualization.
5.2. By using the Service, the Developer grants the NBCO the right to use the logo, trademark, and/or trade name of the Developer and/or the Developer’s Service for informational, advertising, and marketing purposes related to YooMoney Service and/or the API Traffic Fines Service, in particular, without the need to obtain additional consent from the Developer and without payment of any compensation for such use.
6. Final Provisions
6.1. The NBCO reserves the right to modify, correct, update, or discontinue the Service at any time, without prior notice to the Developer.
6.2. The NBCO may suspend or completely terminate access to the Service or its individual functions, change access protocols and methods, types of identifiers required for communication with the Service, or cancel the Developer’s registration in the Service without explanation, including if the Developer violates the requirements of this Agreement.
6.3. The Developer shall be solely responsible for safekeeping of the Developer’s identifier required for communication with the Service and may not transfer/ give it (or information thereof) to third parties. Any actions performed within the Service using the Developer’s identifiers are considered to have been performed by the Developer.
6.4. The Developer may not transfer its rights and/or obligations to third parties without the NBCO’s written consent.
6.5. All questions and claims related to the use of the Service shall be submitted via the feedback form at: https://yoomoney.ru/feedback/.
Published on: December 17, 2020
Previous version of the document dated November 5, 2020