Terms of Service

Last Updated: September 11, 2026

1. Introduction

These Terms of Service (“Terms”) govern access to and use of the software, applications, APIs, plugins, websites, merchant tools, wallet applications and related services provided under the Coinsnap brand and operated by Onlineshop24 DOO (“Coinsnap”, “we”, “our” or “us”).

By accessing or using Coinsnap, you agree to these Terms.

If you use Coinsnap on behalf of a company, organisation or other legal entity, you represent that you are authorised to accept these Terms on its behalf.

If you do not agree to these Terms, you must not use Coinsnap.

2. Operator Information

Coinsnap is a brand operated by:

Onlineshop24 DOO
Ljubimira Ivkovica Suce 75
11453 Sopot (Ducina)
Serbia

Registration Number / Matični broj: 21579041
Tax ID / PIB: 111945856
D-U-N-S® Number: 679972520

Email: support@coinsnap.io

3. Definitions

For the purposes of these Terms:

“Merchant” means a business, organisation, entrepreneur or other person using Coinsnap to request, accept, monitor, assign, document or reconcile Bitcoin payments.

“Payer” means a person making or intending to make a Bitcoin payment to a Merchant.

“User” means any Merchant or other person using a Coinsnap product or service.

“Bitcoin Payment” means a payment made using Bitcoin, whether on the Bitcoin blockchain or through the Lightning Network.

“Merchant Wallet” means a Bitcoin or Lightning wallet selected by the Merchant for receiving Bitcoin.

“Coinsnap Wallet” means a self-custodial wallet application provided by Coinsnap.

“Third-Party Provider” means an independent external provider whose services may be integrated with or accessible through Coinsnap, including providers of exchange, conversion, banking, brokerage or settlement services.

“Merchant-Provided Payer Data” means information relating to a Merchant’s customer or Payer that the Merchant chooses to submit to Coinsnap in connection with a transaction or functionality.

“Data Processing Addendum” or “DPA” means the Coinsnap Data Processing Addendum incorporated into these Terms to the extent applicable.

4. Nature of the Coinsnap Service

Coinsnap is a software and technology provider.

Coinsnap provides technical tools that enable Merchants to request, detect, assign, document and reconcile Bitcoin Payments.

Depending on the product and configuration selected by the Merchant, Coinsnap may provide:

  • Bitcoin and Lightning payment requests;
  • QR codes and payment pages;
  • payment links and payment buttons;
  • point-of-sale functionality;
  • integrations for online shops and e-commerce systems;
  • plugins and modules;
  • APIs and webhooks;
  • Merchant dashboards;
  • transaction histories;
  • reporting and accounting exports;
  • payment notifications;
  • wallet integrations;
  • self-custodial wallet software; and
  • technical integrations with independent Third-Party Providers.

Coinsnap does not become a party to the underlying commercial transaction between a Merchant and a Payer.

The Merchant remains the seller or service provider in its relationship with the Payer.

5. Standard Self-Custodial Payment Model

Coinsnap is designed around a direct and self-custodial Bitcoin payment model.

For a standard self-custodial Bitcoin Payment:

  1. the Merchant or the Merchant’s system requests payment through the Coinsnap software;
  2. Coinsnap provides the technical information required to present the payment request to the Payer;
  3. the Payer decides whether to make the payment;
  4. the Payer authorises the Bitcoin transaction using the Payer’s own wallet;
  5. Bitcoin is transferred through the Bitcoin or Lightning Network directly to the wallet destination selected by the Merchant; and
  6. Coinsnap detects the payment and provides the Merchant with payment status, attribution, reconciliation and reporting information.

Coinsnap does not receive, hold or take possession of the Bitcoin at any stage of the standard self-custodial payment flow.

Coinsnap does not receive Bitcoin Payments into a custodial Coinsnap account on behalf of the Merchant.

Coinsnap does not control the Payer’s wallet or authorise the Payer’s transaction.

Where the Merchant uses a self-custodial Merchant Wallet, the Merchant retains control over the receiving wallet and its private keys.

The standard Coinsnap payment model can therefore be summarised as:

Payer’s Wallet → Bitcoin / Lightning Network → Merchant-selected Wallet

Coinsnap provides the software layer used to create and monitor the payment request and to associate the resulting transaction information with the Merchant’s business systems.

6. No Custody of Merchant or Payer Funds

Coinsnap does not provide custodial Bitcoin accounts as part of its standard Merchant service.

Coinsnap does not:

  • hold Bitcoin on behalf of Merchants or Payers;
  • take ownership of Bitcoin Payments;
  • receive or take possession of Bitcoin Payments intended for Merchants;
  • control Merchant private keys;
  • control Merchant seed phrases;
  • maintain pooled customer or Merchant Bitcoin balances;
  • determine when a Merchant’s Bitcoin may be transferred; or
  • have unilateral authority to dispose of a Merchant’s Bitcoin.

Users of self-custodial wallets remain responsible for securing their private keys, seed phrases, recovery information, devices and wallet backups.

Coinsnap cannot recover Bitcoin where a User loses access to the relevant private keys or recovery information.

7. Coinsnap Wallet

Coinsnap may provide self-custodial wallet software.

When a User uses the Coinsnap Wallet, the User remains responsible for controlling access to the wallet and for protecting the relevant recovery information.

Coinsnap does not provide the Coinsnap Wallet as a custodial account and does not undertake to hold Bitcoin on behalf of the User.

Transactions initiated through a self-custodial wallet must be authorised by the wallet User.

The availability of the Coinsnap Wallet does not change the nature of the Coinsnap Merchant service and does not make Coinsnap the recipient, owner or custodian of Bitcoin received by a Merchant.

8. No Financial, Exchange or Custodial Services

Coinsnap’s standard service does not include:

  • cryptocurrency exchange services;
  • Bitcoin-to-fiat exchange services;
  • fiat-to-Bitcoin exchange services;
  • brokerage services;
  • investment services;
  • portfolio management;
  • lending;
  • staking;
  • custodial wallet services;
  • banking services;
  • payment accounts;
  • fiat payment accounts;
  • money transmission services; or
  • settlement of fiat funds to a Merchant bank account.

Coinsnap is not engaged by Merchants to take custody of crypto-assets, execute purchases or sales of crypto-assets, or exercise discretionary control over crypto-assets on behalf of Merchants or Payers.

Coinsnap does not represent itself as a bank, payment institution, cryptocurrency exchange, broker, custodian or MiCAR-authorised Crypto-Asset Service Provider.

Coinsnap’s contractual service is the provision of software and technical infrastructure described in these Terms.

Where a functionality would require a separately regulated financial or crypto-asset service, Coinsnap may:

  • not offer the functionality;
  • modify the technical workflow;
  • restrict or discontinue the functionality; or
  • provide a technical integration with an independent Third-Party Provider that performs the regulated service under its own legal and regulatory framework.

9. Third-Party Financial and Settlement Services

Coinsnap may provide technical integrations that allow a Merchant to use services offered by independent Third-Party Providers.

Such services may include:

  • Bitcoin-to-fiat conversion;
  • settlement to a bank account;
  • brokerage or exchange services;
  • banking services; or
  • other independently provided financial services.

These services are not provided by Coinsnap.

The Merchant decides whether to use a Third-Party Provider.

Where a Merchant selects such a service, the Third-Party Provider may become directly involved in the payment, conversion or settlement flow. The standard self-custodial payment flow described in Section 5 may therefore differ for that specific optional service.

The precise transaction flow, custody arrangement, conversion, payout and regulatory treatment of the Third-Party Provider’s service are determined by that provider.

Third-Party Providers operate under their own terms, privacy policies, licences, regulatory framework and compliance procedures.

Coinsnap may provide the technical interface through which information required for the selected service is exchanged.

Coinsnap is not responsible for:

  • acceptance or rejection decisions made by the Third-Party Provider;
  • KYC or KYB requirements imposed by the Third-Party Provider;
  • AML or sanctions checks performed by the Third-Party Provider;
  • information requested by the Third-Party Provider for regulatory purposes;
  • exchange rates offered by the Third-Party Provider;
  • conversion execution;
  • bank settlement;
  • payout delays;
  • bank processing times;
  • account restrictions imposed by the Third-Party Provider; or
  • availability of the Third-Party Provider’s service.

The Merchant’s use of a Third-Party Provider is also governed by that provider’s own contractual terms.

10. Regulatory Separation

Coinsnap’s software is designed so that its standard Merchant service can operate without Coinsnap taking custody of Bitcoin, exchanging Bitcoin, executing crypto-asset transactions on behalf of a Merchant or providing fiat settlement.

Where a feature requires a regulated service, Coinsnap may integrate an independent provider that performs that service under the provider’s own regulatory framework.

Coinsnap may modify, restrict, redesign or discontinue functionality where reasonably necessary to:

  • preserve the separation between Coinsnap’s software services and regulated financial services;
  • comply with applicable law; or
  • avoid Coinsnap performing an activity requiring regulatory authorisation that Coinsnap does not hold.

Nothing in these Terms constitutes a representation that the use of Bitcoin or any particular Coinsnap functionality is lawful or unregulated in every jurisdiction.

Each Merchant remains responsible for determining whether accepting Bitcoin and using Coinsnap is permitted for its particular business and jurisdiction.

11. Merchant Relationship With the Payer

The commercial relationship relating to goods or services purchased by a Payer exists between the Merchant and the Payer.

Coinsnap is not:

  • the seller of the Merchant’s goods or services;
  • the buyer of those goods or services;
  • the Merchant’s commercial agent;
  • the Payer’s payment representative;
  • responsible for product delivery;
  • responsible for product quality;
  • responsible for the Merchant’s pricing;
  • responsible for the Merchant’s invoices; or
  • responsible for disputes between the Merchant and the Payer.

The Merchant is responsible for its own:

  • terms and conditions;
  • customer contracts;
  • refund policy;
  • privacy disclosures;
  • invoicing;
  • pricing;
  • tax treatment;
  • accounting;
  • consumer protection obligations; and
  • other legal obligations applicable to its business.

12. Merchant Responsibility for Payer and Customer Data

The Merchant determines which information about its customers or Payers is collected in connection with the Merchant’s business.

Coinsnap does not require identification of the Payer for a standard self-custodial Bitcoin Payment unless a particular optional functionality or Third-Party Provider expressly requires additional information.

The Merchant is responsible for determining whether it is legally permitted to:

  • collect information from a Payer;
  • associate that information with a Bitcoin Payment;
  • transmit that information to Coinsnap;
  • store that information;
  • export that information to another system; or
  • transmit that information to a Third-Party Provider.

The Merchant is responsible for providing any privacy notices, contractual information, consent mechanisms or other disclosures required under laws applicable to the Merchant and its customers.

Coinsnap does not determine the Merchant’s legal basis for collecting customer or Payer information.

13. Merchant-Provided Payer Data

A Merchant may choose to transmit information relating to a customer or Payer to Coinsnap.

Such information may include, depending on the functionality selected by the Merchant:

  • customer or Payer name;
  • email address;
  • customer reference;
  • order number;
  • invoice number;
  • accounting reference; or
  • other Merchant-defined transaction information.

Coinsnap may process such information in order to provide functionality requested by the Merchant, including:

  • associating a Bitcoin Payment with an order or invoice;
  • displaying information in the Merchant Dashboard;
  • transaction reconciliation;
  • reports;
  • accounting exports;
  • APIs and webhooks;
  • integrations with Merchant systems; and
  • technical transmission to a Third-Party Provider selected by the Merchant.

Merchant-Provided Payer Data is not required merely because a Bitcoin transaction occurs on the Bitcoin or Lightning Network.

The Merchant should not transmit Personal Data to Coinsnap unless such information is required for a Coinsnap functionality that the Merchant has chosen to use.

Further details are provided in the Coinsnap Privacy Policy and Data Processing Addendum.

14. Data Processing Addendum

The Coinsnap Data Processing Addendum (“DPA”) is incorporated into and forms part of these Terms.

The DPA applies automatically to the extent that Coinsnap processes Personal Data on behalf of a Merchant.

By accepting these Terms, the Merchant also accepts the DPA where applicable.

No separate signature, countersignature or individually negotiated data processing agreement is required unless mandatory Applicable Data Protection Law requires otherwise.

Where Coinsnap processes Personal Data for its own purposes and determines the purposes and means of such processing, Coinsnap acts as an independent Controller and such processing is governed by the Coinsnap Privacy Policy rather than the DPA.

The DPA contains further provisions concerning:

  • processing instructions;
  • confidentiality;
  • security;
  • Subprocessors;
  • assistance with individual rights;
  • Personal Data breaches;
  • deletion and retention;
  • international processing; and
  • applicable international transfer mechanisms.

In the event of a conflict between these Terms and the DPA concerning processing for which Coinsnap acts as Processor on behalf of the Merchant, the DPA prevails with respect to that processing.

15. International Data Transfers

Coinsnap is operated by Onlineshop24 DOO in Serbia.

Accordingly, information submitted to Coinsnap may be processed in Serbia and, depending on the services used, in other jurisdictions where Coinsnap’s service providers operate.

The Merchant is responsible for considering whether its transfer of Personal Data to Coinsnap is subject to international data transfer requirements under laws applicable to the Merchant.

Where Applicable Data Protection Law requires a particular safeguard or contractual transfer mechanism, the appropriate mechanism will be determined according to:

  • the jurisdictions involved;
  • the roles of the parties;
  • the nature of the Personal Data;
  • the purpose of the processing; and
  • the Applicable Data Protection Law.

Such mechanisms may include applicable standard contractual clauses or another legally recognised transfer mechanism where appropriate.

No particular transfer mechanism applies automatically to every Merchant, every jurisdiction or every Coinsnap processing activity.

Further information is provided in the Coinsnap Privacy Policy and Data Processing Addendum.

16. Data Required by Third-Party Providers

An independent Third-Party Provider may require information about a Merchant or Payer in order to perform its own services or comply with regulatory requirements applicable to that provider.

Such information may include Payer identification information where required by that provider.

The Third-Party Provider determines which information it requires for its regulated service.

Coinsnap does not independently determine the KYC, AML, customer due diligence, sanctions, banking or similar regulatory information requirements of the Third-Party Provider.

Where instructed by the Merchant and supported by the relevant integration, Coinsnap may technically transmit information supplied by the Merchant to the selected Third-Party Provider.

The Third-Party Provider may process such information for its own purposes and under its own privacy policy and regulatory framework.

17. Merchant Account Registration

Certain Coinsnap services require a Merchant account.

When registering and maintaining an account, the Merchant agrees to provide accurate and current information.

The Merchant must:

  • protect account credentials;
  • use reasonable security measures;
  • restrict access to authorised persons;
  • notify Coinsnap of suspected unauthorised access; and
  • keep relevant business and contact information accurate.

The Merchant is responsible for activities performed through its account by persons authorised by the Merchant.

Coinsnap may record access and security information for purposes such as account protection, fraud prevention, investigation of unauthorised access and system security.

Further details are provided in the Privacy Policy.

18. Location Information, Fees, Taxes and VAT

Coinsnap may use information supplied by the Merchant and limited technical information available during registration to determine the Merchant’s probable country of establishment for administrative and tax purposes.

This may include temporarily processing the IP address used during registration in order to estimate the Merchant’s country.

The registration IP address is not retained solely for that country determination purpose.

The Merchant is responsible for providing correct information concerning its place of establishment, tax status and other information relevant to the tax treatment of Coinsnap’s services.

Fees for Coinsnap services are determined according to the pricing, plan or separate commercial terms applicable to the Merchant.

Applicable VAT or other taxes may be added where required by law.

The Merchant remains responsible for its own taxes arising from the sale of goods or services and from the receipt, holding or disposal of Bitcoin.

Coinsnap does not provide tax advice.

19. Exchange Rate Calculations

Where a Merchant prices goods or services in a fiat currency, Coinsnap may provide a technical calculation of the corresponding Bitcoin amount for the purpose of generating a payment request.

Such calculation does not constitute an exchange transaction by Coinsnap.

Coinsnap does not buy or sell Bitcoin merely by displaying or calculating a Bitcoin equivalent of a fiat-denominated price.

Exchange-rate information may originate from external market data providers and may change rapidly.

A calculation displayed by Coinsnap does not constitute investment, trading or financial advice.

20. Payment Confirmation and Network Conditions

Coinsnap may detect Bitcoin or Lightning transactions and communicate a payment status to the Merchant.

Payment status depends on technical information obtained from the relevant network and infrastructure.

The Merchant remains responsible for determining when it considers a payment sufficiently final for delivery of goods or services.

Bitcoin and Lightning payments may be affected by:

  • network congestion;
  • routing availability;
  • fees;
  • blockchain reorganisations;
  • payment timeouts;
  • node or infrastructure failures;
  • software failures; or
  • other network conditions outside Coinsnap’s control.

Coinsnap does not guarantee that every attempted transaction will be successfully completed.

21. Refunds and Payment Disputes

Bitcoin transactions are generally irreversible after they have been validly transmitted and confirmed according to the applicable network conditions.

Coinsnap cannot reverse a Bitcoin transaction.

Refunds relating to the Merchant’s goods or services are the responsibility of the Merchant.

Where a refund is appropriate, the Merchant is responsible for determining:

  • the refund destination;
  • the amount;
  • the conditions of the refund; and
  • the wallet from which the refund is authorised.

Coinsnap is not responsible for disputes between a Merchant and a Payer concerning goods, services, refunds or the underlying commercial transaction.

22. Merchant Compliance Responsibilities

Merchants are responsible for complying with laws and regulations applicable to:

  • their business;
  • their goods and services;
  • accepting Bitcoin;
  • taxation;
  • accounting;
  • invoicing;
  • consumer protection;
  • privacy and data protection;
  • sanctions;
  • AML obligations where applicable to the Merchant; and
  • any other legal requirements applicable in the Merchant’s jurisdiction.

Coinsnap does not provide legal, regulatory, tax, investment or accounting advice.

The availability of a Coinsnap feature does not mean that its use is legally permitted in every jurisdiction or for every Merchant.

23. Eligibility

Users must have the legal capacity required to enter into these Terms.

Where an individual uses Coinsnap, the individual must be at least 18 years old unless applicable law permits otherwise.

Users must not use Coinsnap where such use is prohibited by applicable law.

Persons acting for a company or organisation represent that they have authority to act for that entity.

24. Acceptable Use

Coinsnap must not be used for unlawful purposes.

Users must not use Coinsnap for activities involving:

  • fraud;
  • theft;
  • money laundering;
  • terrorist financing;
  • sanctions violations;
  • phishing;
  • unauthorised system access;
  • malware distribution;
  • deliberate security attacks;
  • deceptive or fraudulent practices; or
  • goods or services whose sale or payment would violate applicable law.

Users must not use Coinsnap in a manner intended to circumvent legal restrictions applicable to the User or the User’s business.

Coinsnap may restrict or suspend use of the service where reasonably necessary to protect the platform, other Users or Coinsnap, or to comply with applicable law.

25. APIs, Plugins and Developer Tools

Users of Coinsnap APIs, plugins, webhooks and developer tools must:

  • follow applicable technical documentation;
  • protect API credentials;
  • implement reasonable security controls;
  • respect applicable rate limits;
  • avoid abusive automated requests; and
  • avoid actions intended to interfere with Coinsnap’s infrastructure.

The Merchant is responsible for ensuring that its own software implementation does not alter the intended payment flow in a way that misrepresents Coinsnap’s role or creates security risks.

Coinsnap may modify technical interfaces where reasonably necessary for security, compatibility, performance or legal compliance.

26. Open-Source Components

Coinsnap products may include open-source components.

Such components may be subject to separate open-source licence terms.

Nothing in these Terms is intended to restrict rights granted under an applicable open-source licence.

27. Referral and Partner Programs

Coinsnap may offer referral, affiliate or partner programs.

The conditions and commission structure of such programs may be described separately.

Coinsnap may modify or discontinue a referral or partner program subject to applicable contractual commitments.

Referral commissions may be withheld in cases of fraud, abuse or violation of applicable program conditions.

Personal information relating to referred Merchants will not be disclosed to a referring party except where required to administer the referral relationship and permitted under applicable law.

28. Service Availability

Coinsnap aims to provide reliable software but does not guarantee uninterrupted or error-free operation.

Services may be unavailable because of:

  • scheduled or emergency maintenance;
  • software updates;
  • infrastructure failures;
  • internet connectivity;
  • Bitcoin network conditions;
  • Lightning Network conditions;
  • third-party service failures;
  • cybersecurity incidents;
  • force majeure; or
  • circumstances outside Coinsnap’s reasonable control.

Coinsnap may modify technical infrastructure or service functionality where reasonably required to maintain security, reliability, compatibility or legal compliance.

29. Bitcoin and Technology Risks

Users acknowledge that Bitcoin, the Lightning Network and self-custodial wallet technologies involve risks.

These may include:

  • loss of private keys or recovery information;
  • irreversible transactions;
  • incorrect wallet addresses;
  • price volatility;
  • network congestion;
  • routing failures;
  • software defects;
  • protocol changes;
  • forks;
  • third-party infrastructure failures;
  • cybersecurity risks; and
  • changes in legal or regulatory treatment.

Users are responsible for evaluating these risks before using Bitcoin.

Additional information is provided in the Coinsnap Non-Custodial & Risk Disclosure.

30. No Investment or Financial Advice

Coinsnap provides software and technical information.

Nothing provided through Coinsnap constitutes:

  • investment advice;
  • financial advice;
  • trading advice;
  • a recommendation to purchase, sell or hold Bitcoin; or
  • a representation concerning the future value of Bitcoin.

Users make their own decisions concerning the acceptance, use and holding of Bitcoin.

31. Intellectual Property

Except for open-source components and third-party materials, Coinsnap’s trademarks, branding, proprietary software, documentation and content remain the property of Onlineshop24 DOO or its licensors.

Users may not, except where permitted by law or applicable licence terms:

  • copy proprietary Coinsnap software;
  • resell proprietary Coinsnap services without authorisation;
  • misuse Coinsnap trademarks or branding;
  • remove proprietary notices; or
  • falsely represent affiliation with Coinsnap.

32. Privacy and Data Protection

Coinsnap processes Personal Data in accordance with the Coinsnap Privacy Policy, the Data Processing Addendum where applicable and Applicable Data Protection Law.

The Privacy Policy explains, among other things:

  • Merchant Account Data;
  • Merchant access and security information;
  • technical payment information;
  • Merchant-Provided Payer Data;
  • information transmitted to Third-Party Providers;
  • data retention; and
  • international processing.

Where Coinsnap processes Personal Data on behalf of a Merchant, the Data Processing Addendum applies as described in Section 14.

The Merchant remains responsible for its own privacy relationship with its customers and Payers.

33. Security

Coinsnap implements reasonable technical and organisational measures intended to protect its systems and information.

No internet-connected service can guarantee absolute security.

Users are responsible for securing their own:

  • devices;
  • accounts;
  • passwords;
  • API credentials;
  • email accounts;
  • wallets;
  • private keys; and
  • recovery information.

Users must notify Coinsnap promptly if they become aware of unauthorised access to a Coinsnap account or another material security issue affecting the service.

34. Suspension and Termination

Coinsnap may suspend, restrict or terminate access to a service where reasonably necessary because of:

  • violation of these Terms;
  • suspected fraud;
  • unlawful activity;
  • sanctions requirements;
  • security risks;
  • abuse of the platform;
  • material risk to Coinsnap or other Users;
  • requirements imposed by law or a competent authority; or
  • functionality or use that may cause Coinsnap to provide a service requiring regulatory authorisation that Coinsnap does not hold.

Where reasonably possible and legally permitted, Coinsnap may provide notice before material suspension or termination.

Users may discontinue use of Coinsnap at any time.

Termination of a Coinsnap account does not affect the Merchant’s ownership or control of Bitcoin held in the Merchant’s own wallet.

35. Third-Party Services and Dependencies

Coinsnap may depend on or integrate software, infrastructure, market data, blockchain services, Lightning infrastructure or other services provided by third parties.

Coinsnap does not control independent third-party services.

The availability of an integration does not constitute a guarantee or endorsement of the Third-Party Provider’s service.

The use of an independent Third-Party Provider may be subject to separate terms between the User and that provider.

36. No Warranty

To the maximum extent permitted by applicable law, Coinsnap is provided on an “AS IS” and “AS AVAILABLE” basis.

Coinsnap does not warrant that:

  • the service will always be available;
  • the service will be error-free;
  • every payment will be successfully completed;
  • every third-party integration will remain available;
  • every exchange-rate source will always be accurate; or
  • Coinsnap will meet every User’s particular business, legal or regulatory requirements.

Mandatory warranties that cannot legally be excluded remain unaffected.

37. Limitation of Liability

To the maximum extent permitted by applicable law, Coinsnap and Onlineshop24 DOO will not be liable for indirect, incidental, special or consequential losses arising from the use or inability to use Coinsnap.

This includes, where legally permitted:

  • loss of profits;
  • loss of business;
  • business interruption;
  • loss of data;
  • loss of Bitcoin resulting from incorrect wallet information supplied by the User;
  • loss of wallet access;
  • blockchain or Lightning Network failures;
  • third-party service failures;
  • exchange-rate movements; and
  • failures outside Coinsnap’s reasonable control.

Coinsnap’s aggregate liability arising from the services will, to the maximum extent permitted by law, not exceed the fees paid by the affected User to Coinsnap during the twelve months preceding the event giving rise to the claim.

Nothing in these Terms excludes or limits liability where such exclusion or limitation is prohibited by applicable law.

38. Indemnification

To the extent permitted by applicable law, a User agrees to indemnify and hold harmless Onlineshop24 DOO from third-party claims resulting from:

  • unlawful use of Coinsnap by the User;
  • the User’s material violation of these Terms;
  • the User’s infringement of third-party rights;
  • goods or services sold by the Merchant;
  • Personal Data or other information unlawfully supplied by the Merchant to Coinsnap; or
  • the Merchant’s failure to comply with laws applicable to its business.

This provision does not apply to the extent a claim was caused by Coinsnap’s own breach of applicable law or these Terms.

39. Changes to the Services

Coinsnap may improve, modify, replace or discontinue features.

Coinsnap may make changes where necessary for:

  • security;
  • technical development;
  • network compatibility;
  • third-party dependencies;
  • legal compliance; or
  • preservation of Coinsnap’s non-custodial software model.

Where a material change significantly affects a paid service, Coinsnap will provide notice where reasonably possible.

40. Changes to These Terms

Coinsnap may update these Terms from time to time.

The current version and the date of the latest revision will be published on the Coinsnap website.

Where required by applicable law or where a change materially affects the contractual relationship, Coinsnap may provide additional notice.

Continued use of Coinsnap after revised Terms become effective constitutes acceptance of the revised Terms where permitted by applicable law.

Where renewed acceptance is required by applicable law or reasonably necessary because of a material contractual change, Coinsnap may require the User to accept the revised Terms electronically.

41. Governing Law

These Terms are governed by the laws of the Republic of Serbia, excluding its conflict-of-law rules to the extent permitted by law.

Mandatory laws that cannot contractually be excluded remain unaffected.

42. Jurisdiction

Subject to any mandatory jurisdiction rules that apply, disputes arising from these Terms or the use of Coinsnap will be subject to the competent courts of the Republic of Serbia.

Mandatory rights that cannot lawfully be excluded by this provision remain unaffected.

43. Severability

If any provision of these Terms is held to be invalid or unenforceable, the remaining provisions remain in effect.

The invalid or unenforceable provision will be interpreted or replaced, to the extent permitted by law, in a manner that most closely reflects its intended commercial purpose.

44. No Waiver

Failure by Coinsnap to enforce a provision of these Terms does not constitute a waiver of that provision or any other right.

45. Assignment

Users may not assign their contractual relationship with Coinsnap without prior consent where such consent is permitted to be required by law.

Coinsnap may transfer these Terms in connection with a restructuring, sale, merger or transfer of the Coinsnap business, subject to applicable law.

46. Entire Agreement

These Terms, together with:

  • the Coinsnap Data Processing Addendum where applicable;
  • any applicable service-specific conditions; and
  • any other contractual documents expressly incorporated into these Terms,

constitute the agreement between the User and Coinsnap regarding the relevant Coinsnap Services.

The Coinsnap Privacy Policy, Cookie Policy and Non-Custodial & Risk Disclosure provide additional information concerning use of the services.

The Data Processing Addendum forms part of the contractual relationship only to the extent described in Section 14.

47. Contact

Questions regarding these Terms may be sent to:

Coinsnap / Onlineshop24 DOO
Ljubimira Ivkovica Suce 75
11453 Sopot (Ducina)
Serbia

Email: support@coinsnap.io