1. Service and operator
Zynost Pay is a product of Zynost led by founder Muhammad Umar in Pakistan. It provides a merchant dashboard, payment APIs, hosted checkout and blockchain payment detection. These terms cover Zynost Pay. The Zynost research application and UQX wallet have separate product terms even where accounts or branding are shared.
Creating an account or using the service means you agree to these terms. If you act for a business you must have authority to do so. You must be at least 18 and provide accurate business and contact details. Nothing on this website represents a financial licence or regulatory approval.
2. Merchant-controlled settlement
For supported EVM checkout flows the service derives receive addresses from the merchant's extended public key. Supported Solana payments use the merchant's configured payout address. Merchants retain the corresponding signing keys. A payment made to a merchant is separate from a merchant's payment of Zynost service fees.
Zynost Pay does not ask merchants to deposit customer receipts into a Zynost custodial balance. We cannot recover a lost merchant seed phrase or reverse a confirmed transfer. Merchants must verify their payout configuration and their ability to access derived addresses before accepting customer payments. Changing a payout setting may require verification and review.
3. Checkout and payment status
Use only the token contract, network, destination and amount shown on the current invoice. The same token name on a different chain is not interchangeable. Invoice expiry does not cancel a blockchain transaction. Late, duplicate, partial, excessive or wrong-network transfers may require manual investigation and may be unrecoverable.
A checkout status is our observation of blockchain data. RPC outages, reorganisations, confirmation requirements and delayed indexers can postpone or change a status. Merchants should verify the invoice and network confirmation before fulfilment. A webhook delivery or browser redirect alone is not evidence that a payment is final.
4. API and account security
Protect passwords, API credentials, webhook secrets and wallet access. Enable two-factor authentication where available. Verify webhook signatures and handle repeated events idempotently. Restrict access to your integrations and rotate credentials if compromise is suspected.
Do not put personal secrets or unnecessary customer information in public order references. Report suspicious checkout addresses or account changes promptly. Public keys cannot sign transactions but an xpub can reveal associated addresses and financial activity. Treat it as sensitive business information.
5. Gas sponsorship
Eligible gasless payments use smart-account and paymaster infrastructure on supported networks. Sponsorship is subject to supported wallets, token balances, network conditions, eligibility rules and operational gas limits. It is not an unlimited or permanent promise of free transactions.
The paymaster holds an operational gas deposit separate from merchant receipts. Wallet signing is still required. Review each approval and transaction request. If sponsorship is unavailable a supported standard payment may require native network gas. Do not repeatedly sign unfamiliar requests to bypass a failure.
6. Plans and service fees
The service offers Free, pay-as-you-go and Pro options as shown in the dashboard and pricing section. Pay-as-you-go fees relate to eligible payment volume. Pro is a subscription service. The displayed plan limits, fee basis and billing period apply to the relevant invoice. Blockchain gas is separate unless sponsorship explicitly covers it.
Crypto-funded service plans require renewal payment rather than an automatic debit from a merchant's wallet. A downgrade or expired plan does not reverse earlier customer payments or erase fees already incurred. Check the dashboard for the effective date of a billing-mode change. Material pricing changes should be communicated before they apply to future service periods.
7. Merchant obligations and lawful use
Merchants remain responsible for their products, fulfilment, customer disclosures, tax records and legally required refunds. They must assess the laws and any registration, sanctions, consumer-protection or financial-service requirements that apply to their business and location. A non-custodial design does not by itself establish a regulatory exemption.
Do not use the service for fraud, laundering, prohibited transactions, stolen funds or unauthorised access. Do not manipulate payment detection, evade usage limits, impersonate another merchant or distribute malicious checkout links. We may restrict service access to investigate abuse or comply with applicable legal requirements.
8. Availability and liability
The service depends on external networks, hosting and data providers. We do not guarantee uninterrupted access, a fixed confirmation time, stablecoin redemption or recovery of incorrectly sent funds. Read the risk disclaimer before integrating the service.
To the extent permitted by applicable law the service is provided as available and we exclude liability for indirect or consequential losses. These terms do not exclude liability that cannot lawfully be excluded or remove mandatory consumer rights. A technical limitation does not excuse a legal obligation.
9. Suspension and changes
Suspending API or dashboard access does not give Zynost signing control over merchant-controlled wallets. Keep independent records and wallet recovery material so you can access your own funds if service access ends. Outstanding service fees and obligations that arose before termination remain subject to applicable law.
We may revise these terms as the service changes. The revision date appears above. Material changes will be communicated through an appropriate service channel. Changes are not intended to retrospectively remove rights relating to an existing payment. Contact us before continued use if you do not accept a material revision.
Contact
Account or payment issue: support@zynost.com. Legal or privacy request: legal@zynost.com. Never send a seed phrase or private key.