Login
terms of service

Terms of Service

These terms describe the current product position of AGDor Pay as an early-access payment software (SaaS) that orchestrates invoices and confirmation signals around destinations controlled by the merchant.

Definitions
  • "Service", "AGDor Pay", "we", "us" means the AGDor Pay software operated as an early-access product.
  • "Merchant", "you", "user" means the natural person or legal entity that registered an account and connected projects, wallets, and third-party providers.
  • "Payment provider", "third-party provider", "PSP" means any external service that the Merchant connects (for example DonationAlerts, Binance, or a future gateway such as Stripe, YooKassa, CryptoCloud, Cryptomus). These providers are independent third parties and are not part of AGDor Pay.
  • "Payer" means the end customer of the Merchant who performs a payment to a destination configured by the Merchant.
Nature of the Service — software, not a financial institution
  • AGDor Pay is software (SaaS) for orchestrating payment invoices, payment verification signals, and webhook notifications.
  • AGDor Pay is NOT a bank, payment system, money transfer operator, payment agent, electronic money institution, crypto exchange, or any other licensed financial organization.
  • AGDor Pay does NOT accept, hold, store, transfer, custody, withdraw, or otherwise process any funds of the Merchant or the Payer at any point.
  • All payments are made DIRECTLY between the Payer and the destination configured by the Merchant (the Merchant's wallet, the Merchant's account on a third-party provider such as DonationAlerts or Binance).
  • AGDor Pay only transmits technical signals: invoice statuses, transaction matches, and webhook notifications. No money flows through AGDor Pay.
Third-party payment providers
  • When the Merchant connects a third-party provider (DonationAlerts, Binance, or future gateways such as Stripe, YooKassa, CryptoCloud, Cryptomus), the relationship is exclusively between the Merchant and that provider.
  • AGDor Pay is not a party to the agreement between the Merchant and the provider and has no access to the funds, balances, or payouts of that provider.
  • The Merchant is solely responsible for complying with the terms of service of each connected provider, including KYC, withdrawal rules, geographic restrictions, and acceptable-use policies.
  • AGDor Pay is not liable for any blocking, freezing, delay, or refusal by a third-party provider, including DonationAlerts account suspension, Binance withdrawal limits, or bank rejections.
Merchant responsibilities
  • The Merchant is solely responsible for the legality of the goods, services, content, and activities funded through invoices created in AGDor Pay.
  • The Merchant is solely responsible for tax accounting, fiscal reporting, and compliance with applicable laws, including but not limited to anti-money-laundering regulations (e.g. 115-FZ in Russia), counter-terrorism financing, sanctions regimes, consumer protection, and data protection laws (e.g. 152-FZ, GDPR).
  • The Merchant is responsible for the correctness of configured wallet addresses, exchange identifiers, webhook endpoints, API keys, and related project settings. AGDor Pay does not verify whether a destination actually belongs to the Merchant.
  • The Merchant must have a valid account and, where required, a valid contract with each connected third-party provider.
  • Order fulfillment, customer support, refunds, chargebacks, disputes, and internal accounting remain entirely under the Merchant's control.
Prohibited uses
  • The Merchant must not use AGDor Pay to facilitate money laundering, terrorist financing, tax evasion, or sanctions evasion.
  • The Merchant must not use AGDor Pay for cash-out schemes, pyramid structures, unlicensed gambling, unlicensed securities or token offerings, sale of illegal substances, weapons, stolen data, or any activity prohibited by applicable law.
  • The Merchant must not use AGDor Pay to mislead payers, including impersonation, fake charities, or misrepresentation of the payment destination.
  • The Service may restrict, suspend, or disable accounts, projects, wallets, or routes that violate these terms, applicable law, or the acceptable-use policy of a connected provider.
Wallet ownership and operational responsibility
  • The configured merchant wallet or third-party provider account remains the final payment destination and is fully controlled by the Merchant.
  • AGDor Pay is positioned as the invoice and confirmation layer around the configured destination, not as the owner, custodian, or operator of the Merchant's funds.
  • Webhook handling, order-state updates, and downstream business actions triggered by invoice statuses remain under the Merchant's control.
Credentials and access
  • The Merchant grants AGDor Pay the right to store, in encrypted form, the credentials and tokens required to read the configured destinations (for example exchange API keys with read-only scope, or DonationAlerts OAuth tokens).
  • The Merchant may revoke this access at any time by disconnecting the wallet or provider, or by rotating the credentials at the provider side.
  • AGDor Pay applies industry-standard encryption at rest (AES-256-GCM) for stored credentials. The specific encryption details are described in the Privacy Policy.
Early-access service
  • AGDor Pay may change product behavior, supported routes, limits, and interface details while the service remains in early access.
  • Current zero-fee access or pricing conditions may be revised later as the product matures. Any commercial change will be communicated in advance.
  • Some routes, providers, or features described in public materials may be in development and not yet generally available.
Availability and limitations
  • AGDor Pay may depend on external providers, networks, exchanges, and infrastructure services that can delay or affect confirmation flow.
  • No public statement on the landing page or documentation should be interpreted as a guarantee that third-party networks or providers are always available.
  • The Service does not guarantee real-time confirmation and is not liable for missed or delayed confirmations caused by blockchain congestion, provider outages, or payer error (for example wrong network, underpayment, or manual transfer without invoice).
Limitation of liability
  • AGDor Pay is provided "as is" and "as available". To the maximum extent permitted by law, AGDor Pay is not liable for any indirect, incidental, special, or consequential damages, including loss of profit, loss of customers, or business interruption.
  • AGDor Pay is not liable for the actions or omissions of third-party providers, including blocking of accounts, freezing of funds, refusal of payouts, or changes in provider terms.
  • AGDor Pay is not liable for losses arising from incorrect configuration entered by the Merchant, including wrong wallet address, wrong network, or wrong exchange identifier.
  • Any liability of AGDor Pay under these terms is limited to the direct, proven damage caused by a proven gross negligence or willful misconduct of the Service.
Crypto payments — specific terms
  • Cryptocurrency transactions are irreversible. A payment sent to a wrong network, wrong address, or with wrongMemo cannot be reversed by AGDor Pay.
  • AGDor Pay detects incoming on-chain transactions by querying public blockchain infrastructure (e.g. TronGrid, Moralis) and exchange APIs. Detection depends on the availability of those third-party services.
  • AGDor Pay does NOT execute, sign, broadcast, or custody any blockchain transaction. The Service only observes transactions that the Payer makes directly to the Merchant's address.
  • The Merchant is solely responsible for the legal status of accepting cryptocurrency payments in the Merchant's jurisdiction, including any licensing, reporting, or tax obligations.
DonationAlerts — specific terms
  • Connecting a DonationAlerts account is performed via the official DonationAlerts OAuth flow. AGDor Pay stores only the OAuth tokens and public profile fields returned by DonationAlerts.
  • Multiple DonationAlerts accounts can be connected to the same AGDor Pay account. Each account must be authorized separately through the DonationAlerts OAuth flow.
  • DonationAlerts retains full control over the connected account and may suspend, limit, or terminate it according to its own terms. AGDor Pay has no influence over such decisions.
  • AGDor Pay reads donation history through the DonationAlerts API to match donations to invoices. DonationAlerts may change, rate-limit, or deprecate this API at any time.
Updates
  • These terms may be updated as the product expands, adds new asset or provider support, or changes commercial conditions.
  • Material changes will be communicated through the Service interface or by email when available. Continued use after the effective date constitutes acceptance of the updated terms.