Agreement

Terms of Service

Last updated:: May 28, 2026
Effective:: May 28, 2026

These Terms govern your use of NoHoldPay ("NoHoldPay", "we", "us", "our"), a non-custodial cryptocurrency payment processor. By creating an account or using the service, you agree to these Terms.

If you do not agree, do not use the service.

1. What NoHoldPay is - and isn't

NoHoldPay is software that helps merchants accept cryptocurrency payments. We are explicit about this because the distinction matters:

Non-custodial. Customer funds are paid to wallet addresses you control. We never custody customer funds. We do not have your private keys and cannot recover, freeze, or reverse on-chain transactions. In optional forwarding or sponsored-payment modes, we may broadcast settlement transactions designed to deliver funds to your registered recipient or treasury wallet; these services are not custody accounts and are not intended to give us discretionary control over the destination.
Not a money transmitter, exchange, or bank. We do not buy, sell, or exchange cryptocurrency on your behalf. We do not convert crypto to fiat. We do not issue accounts that store value.
Not a regulated financial institution. There is no government deposit insurance, no FDIC equivalent, and no central authority that can reverse a confirmed blockchain transaction.

What we provide is:

Address derivation and payment-specific address or reference generation for the chains we support.
A watcher that detects on-chain payments to your addresses and updates payment status.
Hosted checkout pages, payment links, invoices, and a merchant dashboard.
Webhooks and an HTTP API for integrating payment events into your application.
Optional broadcast services, such as forwarder sweeps, gas-sponsored payments, and opted-in HD wallet gap-filler support, that require us to broadcast transactions on your behalf using platform-operated broadcast infrastructure. These services are described below.

2. Eligibility

To use NoHoldPay you must:

Be at least 18 years old (or the age of majority in your jurisdiction).
Have the legal capacity to enter into a binding contract.
If you use the service on behalf of a company or other legal entity, have authority to bind that entity. In that case, "you" includes that entity.
Not be located in, ordinarily resident in, or operating from a country or region subject to comprehensive sanctions.
Not be on any sanctions list (OFAC SDN, UN, EU, UK HMT or equivalent).
Use the service only for businesses and activities permitted under our Acceptable Use Policy.

You are solely responsible for confirming that accepting cryptocurrency payments is legal in your jurisdiction and for the jurisdictions of your customers.

You are also responsible for taxes, invoices, receipts, accounting treatment, reporting obligations, customer disclosures, and any licensing, registration, or compliance obligations that apply to your business.

3. Your account

You create an account using an email address and a password. We protect passwords using industry-standard one-way hashing and never store the plaintext password. You may also sign in with Google, in which case Google verifies your email on our behalf.

You are responsible for:

Keeping your credentials confidential.
Activity that occurs under your account.
Activity using your API keys, webhook secrets, wallets, recovery kit, or connected wallet sessions.
Notifying us via the contact page immediately if you suspect unauthorized access.

We may terminate sessions, disable accounts, or require additional verification if we detect suspicious activity.

4. Your wallets

You provide the wallets used to receive payments. Depending on the chain, this is:

For UTXO chains (BTC, LTC, BCH, DOGE): an extended public key (xpub / zpub / vpub / tpub) matching the script type for that chain. We derive receive addresses from this key; we cannot spend from it because it contains no private-key material.
For Ethereum and EVM-compatible chains (ETH, BASE, MATIC, BSC) - static mode: an Ethereum address you control.
For Ethereum and EVM-compatible chains - CREATE2 mode, where supported: a treasury address you control, plus a control wallet you use to authorize per-payment forwarder contracts. We never see the treasury's private key.
For TRON (TRX) - static mode: a TRON address you control.
For TRON - CREATE2 mode, where supported: a treasury address you control, plus a control key you use to authorize per-payment forwarder contracts.
For Solana - static mode: a Solana address you control.
For Solana - PDA forwarder mode, where supported: a treasury Solana address plus a control key you use to authorize per-payment forwarders.
For XRP: a single XRP classic address you control, with payment-specific destination tags used to match incoming payments.
For Stellar/XLM: a funded Stellar address you control. We generate payment-specific references so incoming XLM payments can be matched to the correct payment or invoice.
For Monero (XMR): your primary address and your private view key. Because of how Monero works, no service can detect incoming Monero payments without the view key. We do not ask for your spend key, and you must not provide it to us. You acknowledge the privacy implications of sharing your view key by checking a mandatory disclosure box when you create a Monero wallet. See the Privacy Policy and Risk Disclosure for full detail.

You warrant that:

You control every wallet you submit.
You have the legal right to use those wallets to receive funds.
You will not submit wallet keys that belong to anyone else.

If you submit an incorrect wallet address, incompatible wallet key, unsupported asset, wrong network, or wallet you do not control, funds may be delayed, unrecoverable, or credited incorrectly. You are responsible for verifying wallet details before using them in production.

Wallet rotation is available for supported static-wallet modes. Rotated wallets remain monitored during a chain-specific grace window, and payments detected during that window are handled under the applicable payment rules. After the grace window, rotated wallets become read-only in your dashboard. HD-derived and forwarder-based wallets use separate add, disable, recovery, or treasury-management flows. Mainnet wallets are subject to a cooling-off period before deletion to reduce the risk of accidental loss of in-flight funds.

5. Payment lifecycle

When a payment is created (via the API, payment link, or invoice), it moves through states roughly as follows:

Awaiting payment -> payment detected on-chain -> confirming -> confirmed.

Other outcomes can include underpayment, overpayment, expiry, cancellation, refund request, refund recorded, reorg-related expiry, or failed settlement. Overpayment is tracked on a confirmed payment rather than treated as a separate settlement state. We describe these in the Risk Disclosure.

Finality is configured per chain. Different blockchains require different confirmation counts or finality signals to be considered final. For example, Bitcoin and similar chains use confirmation depth, Ethereum and Solana use finality / commitment models, XRP uses single-ledger finality, and Monero currently uses a higher confirmation threshold. You should not treat a payment as final until our dashboard or webhook reports it as confirmed. Chain events outside the configured finality and reorg-monitoring windows remain your risk.

For payments where you control the receiving wallet directly, the customer's transaction pays an address you control. Funds become available according to the rules of the relevant blockchain, token, wallet, and any issuer-level controls.

For payments that route through a platform-operated forwarder, funds arrive at your treasury only after a sweep succeeds. Sweeps may be batched for network-fee efficiency and may be delayed by network congestion, operator-wallet balance checks, third-party provider outages, safety checks, issuer restrictions, or failed on-chain execution. For EVM x402 gas-sponsored payments, supported payments can be relayed without requiring the customer to hold that network's native gas token; in static mode, funds settle to your registered recipient, while stacked forwarder modes may also require an automated sweep. If automated settlement fails repeatedly, the payment may require manual recovery from your dashboard using your own wallet. If the platform is unavailable entirely, you can use your downloaded recovery kit with the recovery tooling we provide to re-derive your forwarder addresses where supported. Re-derivation or recovery tooling does not guarantee that funds can be moved. See Section 11.

6. Fees and prepaid balance

Our revenue comes from a platform fee debited from a prepaid balance you fund in advance.

You top up your prepaid balance to a chain-specific top-up address we operate. Once the top-up is confirmed, your balance is credited at the rate captured at confirmation time.
Platform fees are debited automatically when a payment confirms.
The fee rate applicable to your account is shown in your dashboard.
If your prepaid balance is insufficient to cover the fee at confirmation, payment processing for new payments may pause until you top up.

Platform fees are service fees only. They do not include insurance, indemnity, or any guarantee that cryptoassets affected by smart-contract, chain-program, relay, issuer, or settlement-infrastructure issues will be replaced, repaid, or made whole.

You remain responsible for fees, network costs, and other amounts incurred before suspension, termination, or account closure. We may deduct accrued fees, platform-paid network costs, and other amounts owed from your prepaid balance. You acknowledge that prepaid balance is not refundable in cryptocurrency once converted into platform-base accounting. If we offer a manual withdrawal, it is at our discretion and may be subject to verification, minimums, network costs, compliance review, and other operational limits. Treat top-ups as a service prepayment, not a custody deposit.

7. Platform-paid gas and pass-through costs

Some payment modes require us to broadcast transactions on your behalf using platform-operated broadcast infrastructure:

EVM CREATE2 sweep - we broadcast settlement transactions that move funds from per-payment forwarders to your treasury.
EVM x402 gas-sponsored payments - where supported, customers can pay without holding that network's native gas token for transaction fees.
TRON CREATE2 sweep - we broadcast settlement transactions that move funds from per-payment forwarders to your treasury.
Solana PDA sweep - we broadcast settlement transactions that move funds from per-payment forwarders to your treasury.
Solana sponsored transactions - where supported, customers can pay without holding SOL for transaction fees.
Gap-filler service - if you opt in, we may broadcast small payments to unused derived addresses on HD wallets for BTC, BTC testnet, LTC, LTC testnet, BCH, BCH testnet, DOGE, and DOGE testnet. This is used when many checkout addresses are created but left unpaid, causing some wallet software to stop scanning before later paid addresses. Gap-filler is not used for static EVM, TRON, Solana, XRP, Stellar/XLM, or Monero wallets.

Network costs can spike, especially on EVM and TRON networks. For CREATE2, PDA, and gas-sponsored flows, NoHoldPay may need to pay gas, Energy, or other network fees first to sponsor the customer's payment or settle funds to your wallet. You remain responsible for those platform-paid costs: after broadcast or settlement, we deduct the actual cost from your prepaid balance. Any positive prepaid-balance fee debit is rounded up to at least USD 0.01 and to the next cent.

Where customer-facing pass-through is supported, your wallet setting controls whether an estimated network-fee amount is added at checkout so the cost can be shared with the customer:

Smart mode (default). Small estimated costs are not added to the customer payment. Higher estimated costs are shown as an added network-fee amount, so the customer can continue or choose another available network.
Always absorb. The customer sees only the merchant-quoted amount. You cover the network cost from your prepaid balance.
Always pass. The customer is shown an added network-fee amount whenever customer-facing pass-through is supported.

Any added network-fee amount is included in the customer's payment and settles to your wallet or treasury with the rest of the payment. It is not a direct payment to NoHoldPay. Quote-time estimates and actual network costs may differ, and the actual platform-paid cost is still reconciled through your prepaid balance after broadcast or settlement. Customer-facing pass-through is not available for every sponsored or forwarder mode; where it is not available, you cover the platform-paid cost through your prepaid balance. If chain availability, operator-wallet balance, or safety checks fail, we do not broadcast the platform-paid transaction.

If your prepaid balance is insufficient for platform-paid gas, Energy, or network fees, sponsored transactions, sweeps, relays, or gap-filler broadcasts may be delayed, skipped, or paused until your balance is restored.

For TRON, we may use third-party Energy providers. Their cost is handled under the same pass-through model. See the Privacy Policy for the list of third parties.

8. Refunds and disputes

NoHoldPay does not hold customer funds, so we cannot issue a refund on your behalf. All refunds are initiated by you, from your own wallet. Our dashboard provides:

A refund_requested payment state and payment.refund_requested webhook so you can detect customer-initiated refund requests.
A mark refunded action that records a refund transaction hash you submit and notifies the customer.
An "accept underpayment" action that lets you confirm an underpaid payment at the actual received amount (subject to configured shortfall limits).

Disputes between you and your customer are between you and your customer. There is no chargeback mechanism in cryptocurrency, and we have no authority to reverse confirmed transactions. See the Refund and Dispute Policy for the full flow.

You are solely responsible for the goods or services you sell, customer support, refund decisions, consumer-law obligations that apply to your business, and any representations you make to customers about payments, delivery, refunds, or taxes.

9. Reorgs, underpayments, and expiry

Cryptocurrency networks are not deterministic in the way card networks are. Specifically:

A transaction that was confirmed can be reverted if its block is no longer canonical (a reorg). We monitor for reorgs within a per-chain grace window and update the payment status accordingly. After the configured finality and reorg-monitoring windows, we treat the payment as final for platform purposes, and later chain events remain your risk.
A customer may underpay the requested amount. Additional payments to the same payment instructions are counted cumulatively, so the customer can complete the payment by sending the remaining amount before the payment window closes. The customer may also request a refund of the amount already received. We notify you when the cumulative received amount changes; you can accept the partial amount where allowed, or issue and record a refund from your own wallet.
Payments expire after a configured window. A transaction received within a per-chain "late-grace" window after expiry can still revive the payment under the applicable chain and payment rules.

Some assets, especially issuer-managed stablecoins, may include issuer or token-administrator controls. The issuer or token administrator may freeze, blacklist, pause, claw back, or otherwise restrict transfers involving particular addresses, contracts, or users. If this happens, NoHoldPay cannot unfreeze the asset, force the issuer to release it, recover it through our sweep or recovery tools, or reverse the issuer's action. You must resolve issuer-side restrictions directly with the issuer or token administrator.

You acknowledge these properties of public blockchains and agree that NoHoldPay is not liable for losses arising from network reorgs, double-spends finalized within the chain's expected behavior, customer underpayments, or issuer-side restrictions.

See the Risk Disclosure for more detail.

10. Recovery and continuity

Because NoHoldPay is non-custodial, you retain control of wallets and keys you own, even if NoHoldPay is unavailable:

For HD-derived wallets (BTC, LTC, BCH, DOGE), you hold the wallet seed or private keys and can derive addresses with any compliant wallet.
For EVM, TRON, Solana, XRP, Stellar/XLM, and Monero direct-wallet modes, you hold the private keys or spend keys for the receiving wallet.
For CREATE2 / PDA forwarder mode, we provide a recovery kit and recovery tooling that can re-derive your forwarder addresses using public recovery information together with the treasury or control keys you hold.

You are responsible for downloading and securely storing your recovery kit. We cannot regenerate keys you control; we can only provide recovery information that must be combined with your own keys.

11. Webhooks and API

You may configure webhook endpoints to receive payment events. Webhook delivery characteristics:

Each delivery includes a signature header. You should verify the signature before trusting the payload.
Failed deliveries retry with backoff over a limited delivery window.
We apply outbound safety checks and may refuse webhook endpoints that resolve to private, local, or otherwise unsafe network ranges.

Webhooks and dashboard status are operational tools, not a substitute for your own accounting, order-management, or chain reconciliation. You agree that your webhook endpoint will be reachable on the public internet and will return a 2xx response within a reasonable timeout to acknowledge receipt. HTTPS is strongly recommended and may be required for production accounts or future enforcement. We are not responsible for missed, delayed, duplicated, or unverified webhook events caused by your endpoint, network conditions, provider outages, or your failure to verify signatures and reconcile payment state.

API keys are shown to you once at creation and stored securely. Treat API keys as passwords; rotate them if exposed.

12. Suspension and termination

We may suspend or terminate your account if:

You violate these Terms or our Acceptable Use Policy.
We are required to do so by law or by a court / regulatory order.
You materially mislead us about your business or identity.
We have a good-faith reason to believe your account has been compromised.
You repeatedly attempt to receive payments for prohibited categories.

We may act without prior notice where we believe doing so is necessary to protect the service, comply with law, prevent fraud or abuse, manage security risk, or avoid harm to NoHoldPay, other merchants, customers, networks, or third-party providers.

You may request account termination at any time by contacting us. Any prepaid balance withdrawal is subject to reasonable verification and our manual withdrawal process.

We may retain records as needed for security, fraud prevention, tax, accounting, legal, compliance, dispute-resolution, or audit purposes.

Because we are non-custodial, termination affects your access to NoHoldPay, not your control of wallets you own. Subject to chain-level and issuer-level restrictions outside our control, funds already received in wallets you own remain accessible to you through those wallets, regardless of your NoHoldPay account status.

13. Service availability

We make commercially reasonable efforts to keep the service available, but we do not guarantee uptime. Our public status page reports our current view of platform health.

We do not offer a contractual service-level agreement unless one is separately signed.

Some functionality depends on third parties, including blockchain RPC providers, rate providers, email providers, energy marketplaces, and gas-sponsored relay providers. Their availability is outside our control. Where practical, we use fallback providers, retries, or alternate routes, but not every dependency has an equivalent fallback and we cannot guarantee third-party availability.

14. Audit and beta status

Some payment modes are newer or depend on platform-operated settlement infrastructure. These modes may be marked beta in the dashboard or require explicit opt-in.

Beta and platform-operated modes may depend on deployed settlement contracts, chain programs, relays, or broadcast infrastructure. These technologies are experimental and may contain bugs, defects, malfunctions, design limitations, or deployment errors. Those issues may delay settlement, prevent automatic settlement, require manual recovery, or cause partial or total loss of the affected funds. We do not guarantee that an automatic sweep, relay, sponsored settlement, or recovery path will complete by a specific time or succeed at all.

If a settlement issue occurs, we may pause the affected mode, investigate, retry settlement, offer supported merchant-signed recovery, or provide recovery information where available. These steps are technical support measures only. They are not a guarantee of recovery and do not create any obligation for us to replace, repay, insure, or make you whole for funds affected by smart-contract, chain-program, relay, or settlement-infrastructure issues.

For beta features, we may impose lower per-merchant in-flight USD caps and may require explicit opt-in. Use beta features at your own risk, read any in-dashboard advisories, and keep your wallet keys, control keys, and recovery kit secure. Our liability for beta features, settlement delays, and recovery failures remains limited as described in Section 17, except where that limitation is not permitted by law.

15. Intellectual property

We retain all rights in the NoHoldPay software, brand, and documentation. We grant you a non-exclusive, non-transferable, revocable license to use the service for its intended purpose during the term of these Terms.

Open-source components are licensed under their respective open-source licenses, which take precedence within their scope.

You retain all rights in your data, including merchant-controlled keys and any content you upload (logos, business names, etc.).

16. Disclaimers

The service is provided "as-is" and "as-available", without warranties of any kind, express or implied, including (but not limited to) warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, or that the service will be uninterrupted, error-free, or secure.

Cryptocurrency is volatile, irreversible, and subject to network-level and smart-contract risks. Bugs, malfunctions, cyberattacks, forks, issuer actions, contract defects, or settlement-infrastructure failures may result in delayed settlement or partial or total loss of cryptoassets. You accept these risks by using the service. See the Risk Disclosure.

17. Limitation of liability

To the maximum extent permitted by applicable law:

We are not liable for indirect, incidental, special, consequential, exemplary, or punitive damages.
We are not liable for loss of profits, revenue, data, business opportunity, or goodwill.
We are not liable for losses caused by network reorgs, double-spends, customer underpayments, third-party provider outages, unsupported assets, issuer or token-administrator freezes / blacklists / pauses / clawbacks, smart-contract or chain-program bugs, defects, malfunctions, cyberattacks, forks, settlement-infrastructure failures, merchant-controlled wallet issues, or your failure to keep your wallet keys / recovery kit secure.
Our total aggregate liability for any claim relating to the service is limited to the platform fees you paid us in the three (3) months immediately preceding the event giving rise to the claim, and will not exceed USD 100.

If applicable law does not allow a liability limit, that limit applies only to the maximum extent the law allows.

18. Indemnification

You will indemnify and hold harmless NoHoldPay, its personnel, contractors, and affiliates from any claim, loss, liability, or expense (including reasonable legal fees) arising out of:

Your breach of these Terms or our Acceptable Use Policy.
Your access to or use of the service, including your API integration, webhook handling, wallet configuration, customer checkout flow, or connected wallet sessions.
Your violation of any law, regulation, or third-party right.
The goods, services, or content you sell.
Disputes between you and your customers.
Taxes, invoices, receipts, refunds, consumer-law obligations, sanctions obligations, or compliance requirements that apply to your business.
Inaccurate or incomplete information you submit.

19. Changes

We may update this document. Material changes will be announced via email and/or via the dashboard at least 14 days before they take effect when reasonably practical. Changes required for legal, security, risk, chain-support, or urgent operational reasons may take effect sooner. The header of this document reflects the current version.

Your continued use of the service after the effective date constitutes acceptance.

If you do not agree to a change, you should stop using the service before the effective date.

20. Governing law and disputes

These Terms are governed by the laws of [JURISDICTION], without regard to conflict-of-laws rules.

Disputes will be resolved in the courts of [JURISDICTION], unless mandatory law that cannot be waived requires otherwise.

Nothing in this section limits rights or remedies that cannot be waived by contract.

21. Miscellaneous

Entire agreement. These Terms, together with the Privacy Policy, Acceptable Use Policy, Risk Disclosure, Cookie Policy, and Refund and Dispute Policy, are the entire agreement between us regarding the service.
Severability. If any provision is unenforceable, the rest stays in effect.
No waiver. Our failure to enforce a right is not a waiver of that right.
Assignment. You may not assign these Terms without our consent. We may assign them as part of a corporate transaction.
Survival. Sections covering fees owed, network costs, prepaid balance, wallet responsibility, intellectual property, disclaimers, liability limits, indemnification, governing law, and dispute resolution survive termination.

22. Contact

Questions about these Terms? Contact us.