Terms of Service

1. Operator, acceptance, and scope

These Terms of Service (“Terms”) are provided by the platform operator of ArtCloud Crypto Pay (“Operator”, “we”). Canonical product host: https://pay.artcloud.by.

The Operator is ArtCloud (ООО «АртКлауд»). Full registration details, registered address, and governing law/venue will be published here when finalized with counsel. Until then, these pages remain an operator product shell and are not a jurisdiction-specific contract signed by counsel.

By creating a merchant account, completing registration/invite onboarding (including legal consent), paying platform invoices, or using the merchant cabinet, checkout, APIs, or webhooks, you (“Merchant”, “you”) agree to these Terms and the Privacy Policy.

These Terms govern B2B use of the managed SaaS. They do not replace a Data Processing Agreement (DPA) where one is required, and they are not a substitute for independent legal advice.

2. The service

ArtCloud Crypto Pay is a managed cryptocurrency payment SaaS: a control plane (merchant cabinet, APIs, invoice/payout ledger, subscriptions/billing, webhooks) plus a shared self-hosted payment engine (SHKeeper-compatible) operated as part of the managed product unless a separate merchant-operated arrangement is agreed in writing.

Currently enabled settlement assets on the managed product are Solana-network cryptocurrencies: SOL, SOLANA-USDT, and SOLANA-USDC. By written agreement with the Operator, additional SHKeeper-supported networks and assets may be enabled, including Bitcoin (BTC, BTC-LIGHTNING), Litecoin (LTC), Dogecoin (DOGE), Tron (TRX, USDT, USDC), Ethereum (ETH, ETH-USDT, ETH-USDC, ETH-DAI, ETH-PYUSD), BNB Chain (BNB, BNB-USDT, BNB-USDC), Polygon (MATIC/POL, POLYGON-USDT, POLYGON-USDC), Avalanche (AVAX, AVALANCHE-USDT, AVALANCHE-USDC), Arbitrum (ARBETH, ARB-USDC, ARB-PYUSD), Optimism (OPETH, OP-USDT, OP-USDC), Solana PYUSD (SOLANA-PYUSD), TON/GRAM (TON, TON-USDT), Monero (XMR), XRP, and Firo (FIRO). Fiat/card rails (including Stripe) are not part of the standard offering unless separately agreed.

Merchants may create payment invoices for their buyers, receive status via the cabinet/API/webhooks, configure per-crypto policy (confirmations, under/overpayment handling), and request or automate payouts to merchant-configured destinations.

Buyers who pay an invoice interact with checkout and the public blockchain; the Merchant remains responsible for its relationship with buyers (goods, refunds, taxes, consumer rules).

3. Accounts and access

Access is typically granted via Operator invite (plan/trial) or other onboarding approved by the Operator. You must provide accurate account information, keep credentials confidential, and promptly notify the Operator of suspected unauthorized access.

API keys, webhook secrets, and cabinet sessions are security-sensitive. You are responsible for activity under your account. The Operator may suspend access for security incidents, abuse, or non-payment as described below.

4. Custody and engine model

Managed hosting (default product): deposit and hot-wallet key material for enabled cryptocurrencies lives on infrastructure operated by the Operator (or on a merchant VDS that the Operator administers). Staff with server access may potentially reach key material unless additional controls (HSM, merchant-held decryption keys, or equivalent) are in place. Do not market or treat the managed product as “non-custodial” without those clarifications.

Merchant-operated (only if agreed in writing): the merchant runs the engine on its own servers; the Operator provides software and/or support only; custody and key security remain with the merchant.

Operational access for managed hosting does not mean the Operator guarantees against all loss, theft, or chain-level failure. Merchants should evaluate risk, insurance, and security controls with their own advisors.

5. Invoices, settlement, and autopayout

Invoices are created and tracked in the control plane and settled via the payment engine against supported Solana assets. Confirmation requirements, underpaid/overpaid handling, and related policy follow merchant configuration and product rules.

Autopayout (when enabled) moves merchant balances to merchant-configured destinations subject to thresholds, cooldowns, and Operator policy. Execution is performed by the control-plane autopayout runner—not as a guarantee of timing, success, or chain finality.

You alone are responsible for correct payout destinations and for verifying addresses. Wrong addresses, unsupported assets sent to an address, or buyer payment errors may result in irreversible loss. Network fees and mempool/confirmation timing are chain- and RPC-dependent.

Refunds to buyers, chargebacks (where any off-chain dispute process applies), and commercial disputes between Merchant and buyer are outside the Operator’s payment rails unless separately agreed in writing.

6. Fees, subscriptions, and suspension

Platform fees may include SaaS subscription plan fees and/or percentage fees on paid merchant invoices (as shown in the cabinet, invite/plan assignment, or a written order). Platform invoices for SaaS billing are paid in crypto via the product’s platform-merchant checkout (typically SOLANA-USDT), not via Stripe or other fiat PSP.

Crypto network fees, RPC provider costs borne by the Operator’s infrastructure, and chain congestion are separate from platform SaaS fees and are not controlled by the Operator.

Non-payment, expired trial without an active plan, or exceeding grace periods may move a subscription to past_due or suspended status and may suspend merchant API/cabinet access until resolved. The Operator may also suspend or terminate for security risk or Acceptable Use violations.

7. Acceptable use

You must not use ArtCloud Crypto Pay for activity that is illegal under applicable law or that the Operator prohibits. Representative prohibited categories include (non-exhaustive; counsel should finalize for target markets): sanctions evasion; terrorism financing; fraud/scams; malware/ransomware; trafficking in illegal goods or services; child sexual abuse material; unauthorized sale of controlled substances; and use that materially harms the Operator’s infrastructure or other merchants.

You must not attempt to bypass security, scrape credentials, abuse APIs, or resell the managed service as an unapproved payment intermediary without written permission.

The Operator may investigate suspected violations and suspend or terminate accounts. A market-specific prohibited-categories list may be published when finalized with counsel.

8. Merchant responsibilities

You are responsible for: (a) legality of your business and buyer relationships; (b) tax and reporting obligations; (c) accurate invoice metadata and webhook endpoints you control; (d) safeguarding API keys and payout destinations; (e) content you send through callbacks to your systems (including any personal data of buyers).

If you process personal data of EU/UK (or other) data subjects through invoices/webhooks, you may need a DPA and your own privacy notices. A jurisdiction-specific DPA is not shipped in the product shell—seek counsel.

9. Third-party infrastructure

The service depends on third parties and public networks, including VDS/hosting, databases, and Solana RPC (Alchemy on the pay host for the managed product). The Operator does not control Solana consensus, public mempools, or third-party RPC uptime/policy.

ArtCloud Crypto Pay is not a fiat bank, card acquirer, or money-services franchise by virtue of these Terms alone. Whether local licensing applies to custodial crypto settlement is a question for counsel regarding the Operator’s entity and markets.

10. Intellectual property and engine license

The ArtCloud Crypto Pay control plane, cabinet, checkout branding, and related proprietary materials are owned by the Operator or its licensors. These Terms grant a limited, revocable, non-exclusive right to use the managed SaaS for your lawful business during an active subscription.

Upstream SHKeeper engine components are licensed under GPL-3.0. If on-prem distribution of the engine package is offered, GPL-3.0 source obligations for that package apply separately from the proprietary control-plane product.

11. Disclaimers and limitation of liability

THE SERVICE IS PROVIDED ON AN “AS AVAILABLE” BASIS WITHOUT WARRANTIES OF UNINTERRUPTED AVAILABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR SPECIFIC SETTLEMENT TIMING, TO THE FULLEST EXTENT PERMITTED BY LAW.

To the fullest extent permitted by law, the Operator is not liable for losses from chain reorgs, stuck or failed transactions, third-party RPC or hosting outages, merchant misconfiguration (including wrong payout destinations), buyer payment mistakes, sanctions/compliance actions, or force majeure.

Unless a lower or higher cap is required by mandatory law or agreed in writing, the Operator’s aggregate liability arising from these Terms is limited to the platform fees you paid to the Operator for the managed service in the twelve (12) months before the claim. Nothing in these Terms excludes liability that cannot be excluded under mandatory law.

12. Indemnity, changes, contact

You agree to indemnify and hold the Operator harmless from third-party claims arising from your unlawful use of the service, your products/services sold to buyers, or your misconfiguration of payouts/webhooks, to the extent permitted by law.

We may update these Terms by posting a revised version on https://pay.artcloud.by (cabinet and checkout legal pages). Material changes should be accompanied by notice in the cabinet or by email where practicable. Continued use after the effective date constitutes acceptance, except where mandatory law requires otherwise.

Contact for legal/product notices: admin@artcloud.by. Privacy requests: see the Privacy Policy.

Seek independent counsel for your jurisdiction. These pages are the Operator’s product terms for ArtCloud Crypto Pay and are not a substitute for external legal advice or a jurisdiction-specific DPA.