1. Acceptance and eligibility
By accessing or using CryptPays, you agree to these Terms and the Privacy Policy. If you use CryptPays for an organization, you represent that you have authority to bind that organization. If you do not agree, do not use the service.
You must have legal capacity to enter a binding agreement and may use CryptPays only where your use is lawful. You are responsible for determining whether accepting or processing cryptocurrency payments is permitted for you, your business, your customers, and the jurisdictions involved.
2. Description of CryptPays
CryptPays provides cryptocurrency payment infrastructure. For an enabled asset, a merchant can configure a callback URL, a payout address, and supported payment settings through the Merchant API. CryptPays can then generate a deposit address, detect qualifying blockchain payments, apply confirmation or finality logic, forward a qualifying payment, and deliver a signed callback.
Normal Merchant API use is keyless and does not require a merchant API key. That technical design does not waive these Terms, remove a merchant's compliance responsibilities, or prevent CryptPays from requesting information or refusing activity where reasonably necessary.
CryptPays is not a bank, deposit account, exchange, broker, investment adviser, or source of investment, tax, or legal advice. Any asset value, conversion, or price metadata is informational and is not a guarantee of value, liquidity, price stability, or execution rate.
3. Payment configuration
You are responsible for supplying an accurate callback URL, payout address_out, canonical asset ticker, network, priority where supported, and other request settings. You must confirm that the payout address is controlled by its intended recipient and is compatible with the selected asset and network before presenting a payment address to a customer.
A generated address_in is tied to its payment configuration. Do not modify, repurpose, or present an address as supporting assets or networks that are not enabled for that address family. Current asset availability and minimums must be obtained from the live metadata endpoints rather than assumed from an old list.
4. Merchant responsibilities
As a merchant, you are responsible for:
- selecting the correct asset, network, payout address, callback URL, and customer-facing payment instructions;
- securing your systems, domains, wallets, credentials, endpoints, and wallet private keys or seed phrases;
- verifying callback signatures and timestamps before trusting callback content;
- validating the expected order, asset, amount, and payment lifecycle in your own records;
- processing repeated or advancing callbacks with persistent, lifecycle-aware idempotency;
- providing your own customer support, refund policy, disclosures, receipts, and dispute handling;
- calculating and paying taxes and keeping records required for your activity; and
- obtaining every licence, registration, consent, authorization, or permission required for your business and the jurisdictions in which you operate.
Normal Merchant API integration does not require you to give CryptPays the private key or seed phrase for your payout wallet. Never send wallet secrets through the contact form or callback endpoint.
5. Payment addresses, forwarding, and blockchain finality
CryptPays is designed around forwarding qualifying payments to the payout address configured by the merchant rather than maintaining a conventional merchant withdrawal balance. Network processing may involve time between deposit detection, finality, forwarding, and callback delivery.
Blockchain transfers may be irreversible. A wrong address, wrong network, unsupported asset, incorrect token, incompatible contract, or other configuration or customer error can cause permanent loss. CryptPays cannot guarantee that an erroneous transfer can be located, reversed, recovered, or refunded.
Numeric-confirmation networks use an effective configured confirmation threshold. Other networks can use chain-specific finality. Confirmation and forwarding times depend on network conditions, fee conditions, block production, protocol behavior, providers, and other factors outside CryptPays’ control. No specific confirmation, forwarding, or completion time is guaranteed.
Forks, reorganizations, protocol changes, validator or miner behavior, network congestion, and smart-contract or token defects can change, delay, invalidate, or otherwise affect a transaction. A configured confirmation policy reduces certain risks but does not eliminate every blockchain risk.
6. Minimum transaction amounts
Current minimum transaction amounts are published through live asset metadata and may vary by asset or network. You must present the applicable minimum clearly to customers and avoid hardcoding a value that can change.
A deposit below the applicable minimum is not forwarded, does not trigger a merchant callback, and is not combined with a later deposit as a top-up. Depending on network economics and technical constraints, a below-minimum amount may be uneconomic or impossible to recover. CryptPays does not promise recovery.
7. Fees and network costs
CryptPays may apply a contracted transaction percentage based on the applicable merchant or domain configuration, including volume-based pricing where configured. Applicable miner, gas, rent, or other network-cost recovery may also contribute to the total coin deduction. Network costs can change with chain conditions.
The confirmed callback reports the actual contracted percentage for that payment in fee and the total coin deduction in fee_coin. The relationship is:
value_coin = value_forwarded_coin + fee_coin
Public /info fee_percent is generic or default metadata and may differ from transaction-specific pricing. CryptPays may change pricing under an applicable agreement or reasonable notice. No numeric public fee or volume threshold is promised by these Terms.
8. Callbacks and merchant systems
You must maintain a reachable HTTPS callback endpoint, preserve the request data needed for verification, verify the RSA-SHA256 signature and timestamp, validate the expected transaction, and return exactly HTTP 200 only after successful processing. A response body does not replace the required status code.
Callback delivery is not exactly once. Failed delivery can be retried under a bounded policy, and a legitimate event may be delivered more than once. When pending notifications are enabled, the same UUID can advance from pending to sent. You must ensure a confirmed result=sent, pending=0 event fulfills an order once.
CryptPays does not guarantee that every callback will arrive without delay or interruption. You should maintain appropriate monitoring and reconciliation instead of treating a single HTTP request as the only record of a payment.
9. Prohibited use
You must not use or assist others in using CryptPays for:
- activity that violates applicable law, sanctions, court orders, or regulatory requirements;
- fraud, deception, money laundering, terrorist financing, sanctions evasion, stolen property or funds, ransomware, extortion, trafficking, child exploitation, illegal weapons, or illegal drugs;
- malware, credential theft, unauthorized access, denial-of-service activity, probing, interference, or attacks on CryptPays or another system;
- misrepresentation of identity, control, location, licensing, ownership, payment purpose, or source of funds;
- infringement of intellectual-property or other legal rights; or
- circumvention of a service restriction, disabled asset, risk control, or information request.
Gambling, gaming, Forex, investment, financial, or other regulated activity is not represented here as universally prohibited or universally accepted. A merchant engaging in such activity must hold all required authorizations, comply with every applicable restriction, and receive any CryptPays risk acceptance that may be required. CryptPays may refuse a sector, merchant, jurisdiction, wallet, or transaction under its risk policy.
10. Restricted jurisdictions and designated parties
You may not use CryptPays from, for, or for the benefit of a jurisdiction, territory, person, entity, wallet, or transaction that CryptPays prohibits under its Restricted Jurisdictions and Parties Policy, applicable law, sanctions obligations, provider restrictions, or reasonable risk controls.
The published country and territory list is not a complete sanctions list. Restrictions can apply to a designated person or entity regardless of location, and legal requirements can change without a website update. You must not evade a restriction through an intermediary, VPN, proxy, nominee, alternate wallet, false information, or routing arrangement.
11. Compliance and information requests
Where reasonably necessary for applicable law, sanctions or compliance obligations, risk controls, provider requirements, suspected fraud or abuse, or investigation of a transaction, CryptPays may request information concerning identity, business, beneficial ownership, licensing, a transaction, source of funds, destination of funds, or related circumstances.
You must provide accurate information within a reasonable period. CryptPays may delay, refuse, restrict, suspend, or terminate access or processing when information is not provided, cannot be reasonably verified, indicates prohibited activity, or the service cannot lawfully or safely proceed. This reservation does not state that routine KYC or KYB currently applies to every normal Merchant API request and is not a promise of permanent anonymous or verification-free access.
12. Third-party and blockchain infrastructure
CryptPays relies on internet, DNS, hosting, communications, blockchain, node or RPC, wallet, network, and other technical infrastructure. Outages, congestion, attacks, protocol changes, forks, reorganizations, validator or miner failures, token defects, and third-party service failures can affect availability or payment processing.
Third-party services and public networks operate under their own terms and risks. CryptPays is not responsible for the design, governance, security, availability, or value of a blockchain, asset, token contract, wallet, merchant system, or independent provider beyond responsibility that cannot lawfully be excluded.
13. Availability, changes, and unsupported assets
CryptPays may maintain, modify, suspend, disable, or discontinue a network, asset, endpoint, feature, or service where reasonably necessary for security, law, risk, provider availability, protocol changes, maintenance, or commercial operation. Runtime metadata, rather than an old integration copy, determines current enabled assets.
The service is not guaranteed to be uninterrupted, error-free, compatible with every system, or available indefinitely. CryptPays will use reasonable efforts to operate the service but does not promise an uptime level, service-level agreement, or continued support for a particular asset unless stated in a separate written agreement.
14. Intellectual property
CryptPays and its licensors retain rights in the service, website, branding, documentation, and software except for rights expressly granted under an applicable licence. Subject to these Terms, you may access the public interfaces and documentation only for lawful integration and evaluation. You may not falsely represent affiliation, remove proprietary notices, or use CryptPays branding in a misleading way.
15. Assumption of payment and asset risks
You understand that digital assets can be volatile and that transactions can be delayed, reorganized, permanently recorded, or irreversible. CryptPays does not guarantee an asset's value, exchange rate, liquidity, legality, availability, or price stability. You are responsible for determining when and on what terms to accept an asset and for communicating those terms to your customer.
16. Disclaimer of warranties
To the maximum extent permitted by applicable law, CryptPays is provided “as is” and “as available.” CryptPays disclaims implied warranties of merchantability, fitness for a particular purpose, title, non-infringement, and warranties arising from course of dealing. CryptPays does not warrant uninterrupted operation, error-free code, recovery of an incorrect transfer, a particular transaction time, or that the service will meet every merchant's requirements.
Nothing in these Terms excludes a warranty or remedy that applicable law does not permit the parties to exclude.
17. Limitation of liability
To the maximum extent permitted by applicable law, CryptPays will not be liable for indirect, incidental, special, exemplary, punitive, or consequential losses, or for lost profit, revenue, business, goodwill, opportunity, data, or anticipated savings arising from use of or inability to use the service.
Any limitation will be interpreted in light of the nature of the service, the parties' applicable written agreement, and mandatory law. These Terms do not state an invented monetary cap and do not exclude or limit liability that cannot lawfully be excluded or limited, including liability where exclusion is prohibited for fraud, fraudulent misrepresentation, wilful misconduct, gross negligence, death, or personal injury.
18. Indemnification
To the extent permitted by applicable law, you will defend or reimburse CryptPays for reasonable third-party claims, losses, and costs arising from your unlawful use of the service, breach of these Terms, infringement of another party's rights, merchant goods or services, customer-facing representations, or failure to meet your tax, licensing, regulatory, or security obligations.
This obligation is subject to reasonable notice and an opportunity to participate in the defense, does not require indemnification for CryptPays’ own misconduct where prohibited by law, and will be interpreted proportionately under applicable law.
19. Force majeure
Neither party is responsible for delay or failure caused by events beyond its reasonable control, such as natural disaster, war, civil unrest, labor disruption, government action, widespread internet or power failure, cyberattack by a third party, provider outage, blockchain halt, fork, congestion, or validator or miner disruption. This section does not excuse payment or other obligations already due where applicable law provides otherwise.
20. Refusal, suspension, and termination
CryptPays may refuse a request or restrict, suspend, or terminate access where reasonably necessary to address a breach, prohibited activity, security threat, legal or provider requirement, elevated risk, misuse, nonpayment, or material harm to the service or another party. Where practicable and lawful, CryptPays may provide notice or an opportunity to address the issue.
Termination does not reverse a public blockchain transaction and does not affect provisions that by their nature should survive, including accrued obligations, risk allocation, intellectual property, liability, and dispute provisions.
21. Changes, governing law, and general provisions
CryptPays may update these Terms to reflect changes in the service, operating entity, law, providers, or risk policy. The date at the top identifies the current website version. Material changes may be communicated through an appropriate service notice where reasonably practicable. Continuing to use the service after an effective update constitutes acceptance where permitted by law.
The governing law and forum for a specific relationship may be identified in an applicable written agreement or a later version of these Terms after the operating entity and legal framework are finalized. These Terms do not currently represent that a Panamanian company exists or that Panama law has been selected. Mandatory laws and courts may apply regardless of a contractual choice.
If a provision is unenforceable, it will be limited to the minimum extent necessary and the remaining provisions will continue. A failure to enforce a term is not a waiver. You may not assign these Terms without CryptPays’ consent, except where applicable law provides otherwise; CryptPays may assign them in connection with an operating-entity change, reorganization, financing, or transfer of the service, subject to applicable law.
22. Contact
Questions about these Terms can be submitted through the CryptPays contact form. Do not include a private key, seed phrase, password, or other secret.