DornaPal Terms of Service and Merchant Conditions

This is the same text you read and accept when you sign up in the DornaPal panel. Take your time to read it in full before creating an account.

17 articlesArticles

Articles

Preamble

This agreement sets out the conditions for using DornaPal's software services between the Provider and the Merchant. By selecting “Accept the terms and conditions” during sign-up, the Merchant accepts this agreement once, for their entire user account; this acceptance covers all current and future gateways and services on the account, as well as later amendments to the agreement within the framework of Article 14, and the Merchant confirms that they were able to read the full text before accepting it.

Article 1 — Parties and definitions

1.1. DornaPal or the Provider: the software services offered through the dornapal.ir domain, operated by the owner and operator of that domain. The Provider's identity can be established by competent authorities through ownership of the domain and its registration records. Official correspondence with the Provider takes place only through tickets in the user panel.
1.2. Merchant: the individual or legal entity that signs up and uses the services to sell their goods or provide their services.
1.3. End customer: the person who pays the Merchant for a purchase.
1.4. Services: software tools for creating and managing payment requests, reviewing and matching transaction notifications and data against those requests (currently based on the text of bank deposit SMS messages and, in the future, if announced, based on other methods and features the Provider announces), status reporting through the API and webhooks, plugins, and technical documentation.
1.5. Registered card: the bank card (and, under new methods, any other account, address, or payment instrument) that the Merchant registers in the system and into which customers deposit funds directly.
1.6. Service credit (wallet): the Merchant's prepaid credit in the system, used solely for deducting service fees.

Article 2 — Nature and scope of the services

2.1. DornaPal is a software tool that matches transaction notifications and data (currently the text of bank deposit SMS messages that the Merchant provides to the system through the introduced tools) against the Merchant's payment requests and reports the result to the Merchant.
2.2. DornaPal is not a bank, a credit institution, Shaparak, a payment facilitator, or a payment service provider, and this agreement does not grant any banking, payment, or financial licence to either party.
2.3. DornaPal does not receive, hold, transfer, settle, or intermediate any funds for transactions between the Merchant and the customer. The only funds DornaPal receives from the Merchant are the amounts the Merchant pays to top up their service credit; this amount is a prepayment for DornaPal's service fees and is unrelated to the transaction funds between the Merchant and the customer. Transaction funds are deposited directly by the customer into the Merchant's registered card or destination. DornaPal is not a custodian of funds, a payment guarantor, or a party to the transaction between the Merchant and the customer.
2.4. Providing the services does not constitute endorsement of the Merchant's goods, services, licences, or credibility, and the Merchant must not attribute any such claim to DornaPal.
2.5. The services are provided “as is” and within the limits of the announced technical capabilities, and no feature or commitment that has not been expressly announced is assumed or guaranteed.
2.6. One-time, account-wide coverage: This agreement is accepted at the level of the Merchant's user account, and a single acceptance covers all gateways, payment requests, keys, webhooks, plugins, software integrations, and services created or used on that account now or in the future. No separate acceptance is required to create a gateway or use a new service on the same account, and the Merchant cannot release themselves from the obligations of this agreement by creating multiple gateways.
2.7. Future services and features: The Provider may add new services, features, and methods (including other payment or transaction-review methods) to the system in the future. All provisions of this agreement also govern them, and accepting this agreement also constitutes accepting them. The specific conditions of each new service or method (such as pricing and technical requirements) are announced on the website or in the panel when it is offered and supplement this agreement. Using any new service is optional; a Merchant who does not agree must not use it, and their use constitutes acceptance of its specific conditions. The nature of all these services is reviewing and reporting the status of transaction notifications and data, and DornaPal does not receive, hold, or transfer the transaction funds between the Merchant and the customer (receiving service-credit prepayments under Articles 2.3 and 6 is not covered by this statement). The Merchant is responsible for complying with the laws that apply to each method.

Article 3 — Registration and accuracy of information

3.1. The Merchant declares that they are at least 18 years old, have the legal capacity and authority required to accept this agreement, and provide their identity, contact, and business information accurately, completely, and up to date. Forgery, using another person's identity, or providing false information is a violation.
3.2. The Merchant only registers a card or payment destination that belongs to them or that they are legally authorised to use. Registering another person's card or destination without authorisation, or using a rented card, is prohibited.
3.3. The Merchant knowingly and voluntarily allows DornaPal to receive the deposit notifications (currently bank SMS messages) that the Merchant provides to the system, to retain their text, and to provide the matching and payment-status services based on them. The only information DornaPal needs is the transaction amount (and its time). The Merchant must not send DornaPal any password, one-time password, CVV2, account details, or any other financial or security information, and the Merchant is responsible for the content they send. The Merchant sends only notifications related to their registered card and their own activity. The Provider may ignore or delete any additional data.
3.4. Any change to identity details, the card or payment destination, the domain or bot, or the subject of activity must be reported through the panel or a ticket at the earliest reasonable opportunity and within 72 hours at most.
3.5. If the Merchant signs up on behalf of a legal entity or business, they declare that they have the required legal authority; otherwise, they are personally liable.
3.6. The Provider may request reasonable supplementary documents to verify the accuracy of information or the compliance of the activity. Failing to provide them within the announced deadline may result in the services being restricted.

Article 4 — Merchant obligations

4.1. The Merchant is responsible for the legality of their business, goods and services, advertising, licences, taxes, and other legal obligations.
4.2. The Merchant is responsible for the accuracy of the amount, order details, and payment requests, and must clearly inform their customers of the terms of sale, delivery, support, complaints, and refunds. Any dispute between the Merchant and a customer is resolved between them.
4.3. The Merchant is responsible for protecting their user account, password, API key, token, and webhook, and in case of disclosure or misuse must change them immediately and report it through a ticket. Activities carried out with the Merchant's access credentials are attributed to the Merchant. Transferring the account or access to others without the Provider's approval is prohibited.
4.4. The Merchant must not collect or store customers' sensitive banking information (password, CVV2, security code) and must comply with the laws of the Islamic Republic of Iran when retaining customer data.
4.5. The Merchant responds to the Provider's tickets within a reasonable time and cooperates in reviewing suspicious cases.
4.6. The Merchant must not resell the services to third parties, transfer the gateway to others, aggregate other people's funds, or present themselves as a representative or partner of DornaPal.

Article 5 — Nature of status reports and limits of reliance

5.1. A status reported by DornaPal is the result of automated processing of received notifications and data (such as bank SMS text) and matching logic, not a bank confirmation or a guarantee that funds were received.
5.2. Transaction notifications and data may be delayed, duplicated, erroneous, or forged, and DornaPal cannot be absolutely certain of their accuracy. The Merchant is responsible for their own business decisions (delivering goods, activating a service) and, in proportion to the risk and value of the transaction, must also check the balance or transaction details of their account or payment destination.
5.3. A deposit is established conclusively only through the Merchant's account or payment destination. DornaPal is not responsible for funds not actually being deposited, reversals, blocks, or amount discrepancies; in addition, DornaPal reviews and reports status solely on the basis of the notifications and SMS messages that the Merchant provides to the system and is not responsible for the accuracy, completeness, or authenticity of that information; its inaccuracy, forgery, or incompleteness and the resulting consequences are the Merchant's responsibility. DornaPal is liable only to the extent that a direct and proven error in its software caused a loss.

Article 6 — Service credit (wallet) and pricing

6.1. Service pricing is announced in the “Pricing” section, and the Provider may change it for future use. Pricing changes are announced under Article 14, apply from the announced effective date, and do not apply retroactively to services already provided.
6.2. Service fees and charges are deducted from the Merchant's service credit. Service credit is solely prepaid credit for DornaPal's service fees; it is not a bank deposit, earns no interest, cannot be transferred to others, and cannot be withdrawn as cash or refunded at the Merchant's request; the Merchant should top up only as much as they need and use the credit by consuming the services.
6.3. If the credit is insufficient, the Provider may suspend all or part of the services.
6.4. Credit refunds: Topped-up credit is a prepayment for service fees and is used only by consuming the services; an unused balance is not refunded at the Merchant's request. The balance is refunded, after deducting the Provider's documented claims, to a bank account belonging to the same Merchant in only two cases: (a) the Provider terminates the agreement or the services to the Merchant without any violation by the Merchant; (b) the Merchant objects to a material change to the agreement under clause 14.4. In cases of suspension or termination due to the Merchant's violation, the balance is retained up to the Provider's documented claims and damages, and after these are settled and the dispute is resolved, any surplus is refunded to a bank account belonging to the same Merchant. In addition, in case of an erroneous top-up or the Provider's inability to provide the services, the relevant amount is refunded after review.
6.5. Taxes and statutory deductions, where applicable, are applied and announced in accordance with the regulations.

Article 7 — Prohibited activities

7.1. Using the services for any goods, services, or activities that are prohibited or unauthorised under the laws of the Islamic Republic of Iran, or that lack the required licence, is prohibited.
7.2. By way of example and not limitation: fraud, phishing, selling counterfeit or deceptive goods or services, gambling and betting, money laundering and financing criminal activities, pyramid schemes, selling banking or identity information, sham or simulated transactions, and circumventing legal restrictions.
7.3. Determining whether the Merchant's activity conflicts with this article rests with the Provider, provided that it has reasonable grounds. The list above does not limit the Provider from identifying other cases.
7.4. System security: The Merchant has no right to carry out any penetration testing, vulnerability scanning, reverse engineering, attacks (including DoS/DDoS, password and key guessing, injection, or bypassing authentication or rate limits), access to other users' data, or any similar security activity against DornaPal's system, API, webhooks, servers, infrastructure, or data, except with the Provider's prior written permission through a ticket.
7.5. Exploiting software errors: Exploiting any error or technical weakness to create or change a payment status without an actual deposit, manipulating amounts, forging or sending fake deposit notifications, repeating confirmations, or bypassing fees and service credit is prohibited.
7.6. Reporting vulnerabilities: If the Merchant notices a vulnerability or abnormal behaviour in the system, they must report it immediately through a ticket, must not exploit or publish it, must not access data beyond the minimum needed to demonstrate the issue, and must keep the details confidential until it is fixed. A report made in good faith and in accordance with this clause is not in itself considered a violation.
7.7. Consequences of breach: Breaching clauses 7.4 to 7.6 results in immediate suspension or termination of the services, a claim for documented damages and, where necessary, a report to the competent authorities (including the FATA cyber police).

Article 8 — Risk control, restriction, and suspension

8.1. Where there are reasonable grounds for a violation, fraud, false information, a security risk, a breach of the agreement, a justified complaint, or an order from a competent authority, the Provider may restrict or suspend part of the services or all access to the account for as long as necessary.
8.2. In urgent cases, the Provider may act without prior notice and announce the reason through the panel or a ticket within a reasonable time. In other cases, it may ask for an explanation or documents before suspension.
8.3. Lifting a restriction depends on resolving its cause and providing the necessary explanations and documents.
8.4. Upon a lawful request from competent authorities or to protect its own rights, the Provider provides the relevant information and records to those authorities within the limits of the law.

Article 9 — Privacy and data

9.1. The Provider processes and retains the Merchant's data (identity, contact, registered card or destination, the text of deposit notifications such as SMS messages, transaction data, logs, and usage records) solely for providing the service, security, preventing misuse, support, dispute handling, and meeting legal obligations.
9.2. To the extent necessary, the Provider shares information with technical suppliers (such as server and SMS providers) and does not give it to other parties except upon a lawful request from competent authorities or with the Merchant's consent.
9.3. The Provider applies reasonable security measures but does not guarantee absolute security.
9.4. User accounts cannot be deleted; the Merchant can stop using the services at any time. The text of notifications and records related to the services are retained permanently for providing the service, protecting the Provider's rights, security, dispute handling, and enforcing the law, and the Merchant agrees to this by accepting this agreement.

Article 10 — Liability and indemnification

10.1. The Provider is not responsible for the quality of the Merchant's goods and services, the Merchant's disputes with customers, or the Merchant's profitability, sales, or business success.
10.2. The Provider is not responsible for disruptions, delays, or errors caused by the banking network, SMS, the internet, operators, third-party services, restrictions imposed by competent authorities, or factors beyond reasonable control.
10.3. To the extent permitted by law, the Provider is not liable for indirect damages, loss of profit, or loss of opportunity. In any case, the Provider's direct liability, where a legal basis and causation are established, is limited to at most the fees paid by the Merchant in the 1 month preceding the incident.
10.4. The cap and disclaimer in clause 10.3 do not apply to the Provider's wilful misconduct or fraud, or to mandatory statutory liabilities.
10.5. The Merchant is responsible for compensating direct and documented damages arising from their violation, fault, or false information. If, for that reason, a third party brings a claim against the Provider, the Merchant cooperates by providing documents within the limits of their legal liability and, where their liability is established, compensates the damages and the documented and reasonable costs of defence.

Article 11 — Events beyond control

In the event of incidents beyond the Provider's reasonable control, including widespread internet or banking network disruption, outages of third-party services, cyberattacks, natural disasters, orders from competent authorities, or changes in regulations, a delay or interruption of the services is not a breach of contract, and the Provider makes reasonable efforts to reduce its effects.

Article 12 — Intellectual property

DornaPal's software, code, user interface, documentation, name, and logo belong to the Provider. The Merchant has only a non-exclusive, non-transferable right to use the services within the framework of this agreement and must not copy, reverse-engineer, or resell the services or use them for unauthorised access, or use the DornaPal name to claim a relationship that does not exist.

Article 13 — Term and termination

13.1. The agreement begins at the time of electronic acceptance and remains valid until terminated.
13.2. The Merchant cannot delete or close their user account; the Merchant can stop using the services at any time. Stopping use does not extinguish prior obligations and claims, and the status of the credit balance is governed by clause 6.4.
13.3. The Provider may terminate the agreement with 15 days' notice through the panel or a ticket, without needing to give a reason. In case of a material breach of the agreement, fraud, a security risk, prohibited activity, or an order from a competent authority, termination may be immediate and without notice.
13.4. Termination does not extinguish financial obligations, indemnification, confidentiality, other obligations that by their nature survive, or the right to pursue earlier violations.

Article 14 — Amendments to the agreement

14.1. By initially accepting this agreement, the Merchant agrees that the Provider may amend, supplement, or replace all or part of the agreement, pricing, and service conditions due to legal, technical, security, operational, or commercial changes. The initial acceptance also constitutes acceptance of later amendments within this framework.
14.2. The amended text is announced with its effective date on the website and in the user panel (and, where possible, by registered SMS or email). For material changes concerning pricing, liabilities, or the Merchant's rights, notice is given at least 7 days before they take effect, unless there is an urgent legal or security requirement.
14.3. Continuing to use the services after the effective date of the amended text, including creating payment requests or using the API or active gateways, constitutes acceptance of that text, unless the Merchant has objected in accordance with clause 14.4. Providing the services does not depend on re-acceptance; if the Merchant expressly accepts the new text, that acceptance is recorded, but the absence of express acceptance does not prevent the amended text from applying.
14.4. A Merchant who does not agree with a material change must, before the effective date or within 7 days after it at the latest, state their objection through a ticket and stop using the services. In that case, their services end and the credit balance is refunded under clause 6.4. Continuing to use the services without objecting constitutes acceptance of the change.
14.5. The Merchant must follow the contractual notices in the panel and on the website.

Article 15 — Notices and electronic evidence

15.1. The Provider's notices and announcements made through the user panel, tickets, SMS, or other registered communication channels are valid and effective. The Merchant's correspondence with the Provider takes place through panel tickets.
15.2. Records registered in the system (including the accepted text of the agreement, the time of acceptance, technical data, logs, tickets, and any data the system records) can be relied on as electronic evidence within the limits of the law. The Merchant retains the right to raise a legal objection.
15.3. The agreement is accepted by selecting “Accept the terms and conditions” during the sign-up process, and this has the effect of an electronic signature.
15.4. The Merchant is responsible for keeping their contact details up to date, and failing to receive a notice because of incorrect contact details does not invalidate the notice.

Article 16 — Governing law and dispute resolution

16.1. This agreement is governed by the laws of the Islamic Republic of Iran.
16.2. The parties first try to resolve any dispute within 15 days through tickets and negotiation.
16.3. If the dispute is not resolved, it is heard by the competent court of Kermanshah, and the parties choose this city as the local forum, except where mandatory law provides otherwise.
16.4. No provision of this agreement prevents recourse to legal authorities to protect legal rights.

Article 17 — General provisions

17.1. Failure to exercise a right immediately does not mean waiving it.
17.2. If any part of the agreement becomes unenforceable under the law or a ruling of a competent authority, the remaining parts remain valid.
17.3. In case of conflict with mandatory laws or binding orders of competent authorities, those provisions prevail.
17.4. This agreement, together with the pricing, documentation, and notices published in the panel, constitutes the entire agreement between the parties.
17.5. The Merchant cannot assign their rights and obligations to another party without the Provider's written consent. The Provider may transfer its rights and obligations, provided the service level is maintained, to another individual or legal entity (including a company to be established in the future), and the Merchant hereby agrees to this.

Questions?

Have a question about these terms?

Before signing up, find the right channel on the contact page; after signing up, support runs through tickets in the panel.

Create a free account Contact us