Skip to content
Cryptonera

Legal

Terms of service

The agreement between the operator of this installation and the merchants who use it.

Cryptonera Terms of Service

Last updated: 7 October 2026

These Terms govern access to cryptonera.com and its cryptocurrency splitting, billing and related tools. They explain how transactions are instructed, how fees and exceptional payments are handled, and the responsibilities of users and the people operating the platform. Cryptocurrency transfers can be irreversible and can result in loss of the entire amount sent.

1 Who provides the Services

Cryptonera is the name of the website and platform. “Cryptonera”, “we”, “us” and “our” refer to the individual operator or operators identified below (the “Operators”). Use of the name Cryptonera does not represent that the platform is operated by an incorporated company.

Contact: [email protected] or https://cryptonera.com/contact

“Services” means the website, merchant dashboard, Crypto Splitter, Crypto Billing, hosted payment pages, application programming interface (“API”), webhooks, sandbox and related support. “Merchant” means an account holder using these tools to collect or distribute cryptocurrency. A “Payer” sends a payment, and a “Recipient” is designated to receive a distribution. “You” means the person using the relevant Service, including a business represented by an authorised user.

2 Agreement and eligibility

You accept these Terms when you expressly agree to them during registration or activation, or use an account or API after being given notice of the Terms and a reasonable opportunity to review them. If you act for a business or another person, you must have authority to bind them and give the instructions you submit. Keep a copy of the version you accept.

You must be at least 18 and legally able to enter this agreement. You must provide accurate information, keep it current and use the Services only where your use and our provision of them are lawful. Availability is subject to account approval, supported locations and operational readiness. You must not conceal your location or identity to evade a restriction.

A Payer's purchase contract remains with the relevant Merchant. Merely visiting a payment page does not make a Payer responsible for a Merchant's fees, business indemnities or account obligations. Any terms requiring a Payer's agreement must be presented at the relevant point of use. Mandatory consumer rights are preserved throughout these Terms.

3 Products and availability

Crypto Splitter supports percentage distributions through a persistent receiving address or a fresh address allocated to a particular split session. It supports the configured settlement triggers, recipient versions and confirmation rules. Recipient percentages must total 100 percent, and the current recipient limit and other limits are shown in the product or API.

Crypto Billing supports cryptocurrency invoices, payment links, hosted checkout, payment status, receipts and settlement to a specified wallet or compatible saved split. Where enabled, an invoice may be priced in fiat and quoted for payment in cryptocurrency. Refund requests and releases of held balances are subject to the procedures below.

The dashboard, team access, API, webhooks and sandbox support these products. Features depend on the account, asset, network and environment. A feature described in documentation is not available until it is enabled for the relevant use. No service level, uninterrupted availability or settlement deadline is promised unless expressly agreed in writing.

Crypto Card is a proposed future product. No card is currently issued or available through that product. There is no announced issuer, card-scheme or banking partnership, launch date, eligibility commitment or guaranteed fee schedule. Joining the waitlist creates no entitlement to a card, credit, account or financial service. Any launch will require its own disclosures, eligibility checks and terms. Do not send funds or identity documents for the proposed card.

4 Transaction model and external signing

The platform obtains receiving addresses from an external signing provider, observes blockchain activity through external infrastructure, calculates distributions and submits transaction instructions for signing and broadcast. The web application is designed not to store blockchain private keys. The Operators configure the signing relationship and its policies, and transaction execution depends on that arrangement.

An external signer does not by itself mean that you can move funds independently of the Operators or provider. Access, approvals, recovery and transfers can depend on their systems and policies. Descriptions such as “non-custodial key management” describe an aspect of the technical arrangement; they do not determine its legal classification or remove responsibilities imposed by law.

The current splitting and billing products settle in the same asset on the same network. They do not exchange assets, bridge networks or provide fiat settlement. A fiat-denominated invoice is a price quotation, not a fiat account or promise to redeem cryptocurrency at that value. Dashboard balances are accounting records of transaction states, not a bank deposit or an interest-bearing account.

Nothing in these Terms represents that the Operators hold a financial-services authorisation, that a regulator has approved the Services, or that funds benefit from a deposit guarantee or compensation scheme. Any actual authorisation or protection must be expressly identified and verifiable. These Terms do not create an exemption from applicable licensing, safeguarding or other legal requirements.

5 Accounts and security

You are responsible for managing authorised users, team roles, API scopes, wallet details and notification endpoints. Protect passwords, passkeys, recovery methods, API credentials and webhook secrets; use available multifactor authentication; and promptly revoke access that is no longer needed. Do not share credentials with unauthorised persons or place secret credentials in public client code.

Instructions authenticated through your account or credentials may be acted on unless we have reason to question their authority or have received effective notice of compromise. Notify us promptly of suspected unauthorised access and cooperate with reasonable verification. Your responsibility for unauthorised activity remains subject to our own security obligations and any protection required by law.

We may require proportionate checks before sensitive changes, account recovery or releasing funds. We will not ask you to disclose a wallet seed phrase or private key through support. Messages claiming otherwise should be treated as suspicious.

6 Your instructions and recipient details

By activating a split, invoice, payout, refund or release, you authorise the necessary transaction instructions and disclosed fees for that operation. Recurring split configurations authorise settlement of qualifying future deposits under the applicable configuration until paused or closed, subject to instructions already accepted for execution.

Check the asset, exact network, token contract where relevant, receiving and destination addresses, required memo or tag, amount, percentages, expiry and environment before proceeding. Address-format validation does not establish ownership, recipient identity, legality, trustworthiness or compatibility with an exchange's deposit rules. A fresh address is allocated for transaction matching; it is not a promise of anonymity.

Use only addresses and funds that you are authorised to use. You are responsible for instructions you supply incorrectly, including instructions supplied by your authorised team or integration, to the extent the loss is attributable to them. Once a transaction has been signed or broadcast, cancellation or amendment may be impossible. We cannot recall assets that have reached a Recipient's wallet.

7 Splits and configuration snapshots

A split session uses the recipient and fee snapshots recorded when it is accepted. Later edits do not retrospectively change that session. For a persistent splitter, recipient changes create a new version; deposits are assigned using the version applicable when they are observed under the platform's recorded rules. Pending deposits remain tied to their applicable snapshots.

Recipient percentages apply to the distributable amount after the platform commission and any disclosed costs deducted in the same asset. Amounts are rounded to the asset's smallest unit, and rounding remainders are allocated using the recorded settlement calculation. Review the preview and settlement record rather than assuming percentages apply to the gross deposit.

A pause stops new settlements according to the product's operation; it does not disable the blockchain address or reverse instructions already submitted. Deposits can still arrive and be recorded. Threshold and target-amount settings can delay settlement until sufficient confirmed funds exist. Each payout leg is a separate transaction, so some Recipients may be paid while another leg is delayed or fails.

8 Invoices and payment status

Pay only the exact asset and network shown for the selected payment option, within its validity window. Different networks using the same token symbol are not interchangeable. A blockchain transfer being sent or seen, or a browser returning to a success page, does not by itself establish that an invoice is fully paid or its onward settlement completed.

An invoice is fulfilled when one permitted option satisfies its confirmed-amount requirements, subject to any authorised acceptance of an underpayment. Partial payments accumulate under the invoice rules. Payments in different options do not automatically combine into full payment. Excess funds and funds received through another option after fulfilment are handled as held funds.

Where a fiat quote is available, the quotation source, cryptocurrency amount and expiry shown for that option govern its validity. Market changes, stale quotes and payment outside the window can require a new quote or review. A receipt records platform payment information and does not by itself certify tax compliance, delivery of goods or the legality of the underlying transaction.

9 Fees and network resources

The platform commission and calculation basis are disclosed before activation and recorded in the applicable fee snapshot. The current pricing page and any agreed account-specific rate explain the available pricing. Illustrative examples are not a permanent fee offer. A later rate change does not alter a snapshot already applicable to accepted activity.

Network fees are separate from platform commission. Under the current model, token payouts use a separately funded native-asset gas or resource budget. For native-coin payouts, the estimated cost of payout legs is reserved from the deposit as a separate settlement line. Fees and resource needs can change with network conditions. Insufficient resources may delay settlement.

We may deduct only charges authorised for the relevant operation or otherwise lawfully due. Additional recovery or support charges require prior disclosure and agreement. Earned commission on a completed service is generally not refundable merely because the underlying sale is disputed, subject to applicable law and our responsibility for an incorrect charge or failed service. Network charges already incurred may be unrecoverable. You remain responsible for your own taxes and records.

10 Confirmations and supported assets

The supported-assets page and relevant API response identify permitted asset-and-network combinations, minimums and confirmation or finality requirements. Support for a token on one network does not imply support elsewhere. Unsupported contracts, look-alike tokens, bridged variants and assets designated solely for fee funding must not be used as payment options.

Confirmations and finality rules reduce certain risks but cannot guarantee that a blockchain transaction will never be reorganised or invalidated. Detection, indexing, signing and broadcast can be delayed, interrupted or inaccurate. We may correct an erroneous status or record based on reliable evidence, explain a material correction where lawful, and investigate disputed entries. A dashboard or webhook message cannot change the blockchain itself.

We may suspend an asset or change prospective confirmation requirements for security, legal or network reasons. We will provide reasonable notice where practicable and explain the handling of affected pending funds. A suspension does not entitle us to appropriate those funds.

11 Held funds and exceptional payments

Amounts can remain held because they are below minimums, below a settlement threshold, late, excess, sent after closure or cancellation, awaiting resources, affected by a technical incident, disputed, or subject to a lawful restriction. Held balances do not earn interest under these Services. Closure or expiry does not make an address incapable of receiving further transfers.

Held funds are not automatically sent back to the apparent sending address. Exchange, pooled and contract addresses may be unsuitable refund destinations. Release or refund requires an authorised instruction with a verified destination and sufficient usable resources, subject to proportionate security checks and applicable legal obligations.

Where funds are technically recoverable and no lawful restriction prevents it, we will process a valid release instruction within a reasonable time. We may request evidence of authority or entitlement, explain the reason for a material hold where permitted, and provide a support route for review. We cannot guarantee recovery of an unsupported or wrongly routed transfer, but will not describe recoverable funds as forfeited merely because an account closes or an address expires.

12 Refunds and merchant disputes

A refund is a new blockchain payout. It is subject to authorisation, a compatible destination, available funds, network costs and any required approval. A refund request is not confirmation that the refund has been executed. Funds already distributed cannot be recovered from Recipients by reversing the original transaction; the Merchant must arrange any necessary funding.

The Merchant is responsible for its goods or services, customer disclosures, lawful refunds, delivery, taxes and disputes with Payers or Recipients. A hosted checkout or receipt does not make the Operators the seller or guarantor of the underlying purchase. Payers should contact the Merchant about that purchase and contact Cryptonera about suspected platform errors or abuse. Blockchain irreversibility does not eliminate a refund or other remedy that the law requires a responsible party to provide.

13 API and integration responsibilities

Follow the current API requirements, preserve idempotency keys for retries, validate webhook signatures and timestamps, prevent replay, and reconcile transaction states before fulfilling an order. Events may be duplicated, delayed, retried or delivered out of order. Do not rely on an unauthenticated callback, screenshot, redirect or a single webhook as conclusive evidence of completed settlement.

Secure your integration, customer data and webhook endpoints. Send only information needed for the transaction and avoid personal data in public references or blockchain messages. Rate limits, API scopes and security controls must not be bypassed. We may change interfaces with reasonable notice where practicable; urgent security or legal changes may take effect sooner.

14 Lawful use and verification

Do not use the Services for fraud, theft, laundering criminal proceeds, sanctions evasion, prohibited goods or services, unlawful gambling, impersonation or infringement of others' rights. Do not attack the platform, exploit an error, access another user's data, submit malicious code or interfere with security, accounting or confirmation controls. Report a suspected vulnerability privately through support without extracting other users' data.

You must hold any permissions required for your own activity. Where necessary and proportionate for an applicable legal duty or a substantiated security concern, we may seek information about identity, authority, a transaction or source of funds, restrict affected activity, or respond to lawful requests. Any additional personal-data collection must be explained when requested. This clause does not claim that a particular verification programme is currently deployed or transfer our own legal duties to you.

15 Third parties and cryptocurrency risks

The Services depend on signing providers, hosting, email, network infrastructure, indexers and, when used, price sources. Their failures, policy changes, cyberattacks, insolvency or legal restrictions can delay or prevent access and settlement. Third-party terms apply to a relationship you separately enter with that provider; our use of a supplier does not automatically make you a party to its contract.

Cryptocurrency risks include loss of value, stablecoin depegging, issuer freezes, chain forks, reorganisations, congestion, protocol defects, token-contract vulnerabilities, attacks and permanent loss following a mistaken transfer or compromised credential. Stablecoins are not guaranteed to retain their reference value. Forked assets, airdrops and unsupported assets are not automatically credited or supported.

You should assess those risks and keep independent records. Content and support are operational information, not investment, legal, tax or financial advice or a recommendation to transact. No profit, asset value, recovery outcome or continuous access is guaranteed. These risk disclosures do not excuse the Operators from duties or liability that cannot lawfully be excluded.

16 Warranties and service interruptions

To the fullest extent permitted by law, the Services are provided on an “as is” and “as available” basis. We disclaim implied warranties of merchantability, fitness for a particular purpose and non-infringement to the extent they can lawfully be disclaimed. We do not warrant that the Services, external information or integrations will always be uninterrupted, error-free or immune from attack.

We are not responsible for delay or failure caused by events beyond our reasonable control to the extent they could not reasonably have been prevented or mitigated, including public-network failure, natural disaster or government action. We will take reasonable steps to limit the impact. This provision does not excuse failure to apply legally required safeguards or to account for and release funds when legally and technically able to do so.

17 Limitations of liability

The limitations in this section apply only to the extent lawful. Nothing in these Terms excludes or limits liability for fraud or fraudulent misrepresentation, deliberate misconduct, gross negligence, death or personal injury caused by negligence, non-excludable data-protection or financial-services liability, or any other liability that cannot lawfully be excluded or limited.

For business users, and subject to those exceptions, the Operators are not liable for indirect, consequential, special, exemplary or punitive loss, or for loss of profit, revenue, business opportunity, anticipated savings or goodwill, arising from the Services. We are not responsible for losses to the extent caused by incorrect user instructions, a user's security failure, an independent Merchant or Recipient, or an external network or supplier event for which we have no legal responsibility. These exclusions do not apply to the extent the loss results from our breach of a duty that cannot be excluded.

For business users, the aggregate liability of the Operators and the persons protected under this section for all claims arising from the Services is limited to the greater of EUR 100 and the platform fees actually paid by that user in the 12 months immediately preceding the first event giving rise to the claim. The cap applies across contract, tort and other legal grounds to the extent lawful. Cryptocurrency principal and third-party network fees are not platform fees for calculating the cap.

The cap does not limit a duty to account for, return or release crypto-assets belonging to you and remaining under our or our appointed provider's control, refund fees that we are legally required to refund, or satisfy the non-excludable liabilities above. Any mandatory rules governing loss of entrusted assets prevail.

The business exclusions and monetary cap do not apply to you where you act as a consumer. Your statutory remedies, including any right to compensation for loss for which we are legally responsible, remain available. A designation such as “Merchant” or “business account” does not override your legal consumer status.

To the extent permitted by law, the lawful protections in sections 15 to 17 also benefit people acting in connection with the Services as owners, developers, maintainers, personnel, agents or contractors. They do not give anyone immunity for their own non-excludable conduct, create a separate incorporated entity, or prevent a claim against a person who is legally responsible.

18 Business indemnity

If you use the Services for business purposes, you agree to indemnify the Operators and their relevant personnel against third-party claims, reasonable legal costs and damages to the extent caused by your unlawful use, unauthorised transaction instructions, infringement of third-party rights, or material breach of these Terms. This includes claims concerning your underlying goods or services and personal data you supply without authority.

This indemnity does not cover amounts caused by an indemnified person's negligence, breach of these Terms, unlawful conduct or other non-excludable liability. We must give reasonably prompt notice, allow you reasonable participation in the defence and take reasonable steps to reduce the loss. No settlement may impose an admission or non-monetary obligation on you without your consent, not to be unreasonably withheld. This section does not apply to consumers.

19 Suspension and closure

We may proportionately restrict an account, feature or transaction for a material breach, credible security or fraud concern, a legal requirement, unreliable transaction information or an operational incident. We will give reasons and a reasonable opportunity to remedy a remediable breach where lawful and practicable. An urgent restriction may occur without advance notice. Contact support to request review.

You may request account closure through support. We may discontinue a Service or close an account on reasonable notice unless immediate action is justified. Outstanding accepted transactions, lawful fees and valid claims remain to be resolved. Closing an account does not transfer ownership of remaining assets to the Operators or cancel a lawful entitlement to release. Sections 10 to 12 govern pending or held funds, and the Privacy Policy governs retained information.

20 Sandbox and testing

Sandbox activity uses test networks or simulated assets and is separate from live activity. Test balances have no promised monetary value, redemption right or carry-over into live mode. Sandbox data may be reset or removed, and test systems can be less reliable. Use fabricated or otherwise appropriate test data rather than unnecessary personal information.

Never send real assets to a sandbox address, even if its format resembles a live address. Such transfers are not credited as live payments and may be unrecoverable. Live activation requires express enablement and use of the correct environment and credentials. Access to a sandbox is not a commitment to approve live use.

21 Intellectual property and personal data

The Operators and relevant licensors retain their rights in the platform, branding, documentation and other protected materials. You receive a limited, non-exclusive right to use the Services and permitted integration materials for their intended purpose while you comply with these Terms. Open-source components remain subject to their own licences, and statutory rights are not restricted.

You retain rights in content and data you supply and grant only the permissions reasonably needed to process it for the Services. You must have authority to provide it and must give affected people required notices. Our handling of personal data is explained at https://cryptonera.com/privacy. That notice is not a blanket consent to processing. Where we process personal data solely on your behalf and a data-processing agreement is legally required, that agreement must be in place for the relevant processing.

22 Changes and general provisions

We may update these Terms for changes in the Services, risks or law. Material changes will be notified by reasonable means before they take effect, with at least 30 days' notice where practicable. Urgent legal or security changes may take effect sooner with an explanation where permitted. We will obtain renewed agreement where required. Changes do not retrospectively alter accepted fee or recipient snapshots or accrued rights.

If you do not accept a material change, you may stop new activity and close your account, subject to resolving pending matters. A transfer of operation or of this agreement must be lawful, notified where required and must not reduce your accrued or mandatory rights. A new contracting provider must be identified; a change in website branding alone does not silently substitute that provider.

If a provision is unenforceable, the remainder continues where legally possible. A failure to enforce a right immediately is not a waiver. These Terms and any expressly agreed product or account terms form the agreement for the Services. A specific written agreement prevails on a conflict within its scope; mandatory law prevails over all contractual wording. Nothing creates a partnership, employment relationship or authority to bind the other party beyond the transaction instructions expressly covered here.

23 Complaints and applicable law

Send complaints to [email protected] with sufficient information to identify the issue. For a transaction, include its reference or hash and the relevant address, but never private keys or secrets. We will review the complaint and seek a practical resolution. Contacting support does not prevent you from using a regulator, competent court or other remedy available by law.

Unless a valid separate agreement specifies an applicable law or forum, governing law and court jurisdiction are determined by the legal rules applicable to the parties and the dispute. No exclusive foreign forum, compulsory arbitration or class-action waiver is imposed by these Terms. Consumers retain any right to rely on mandatory protections and courts in their place of residence. Where a regulated service requires a specific governing-law clause or complaint procedure, it must be disclosed and agreed before that service is supplied.