Merchant Terms

These Merchant Terms supplement the General Terms. They apply whenever a user creates payment links, requests payments, uses API access, displays a public profile or logo, or registers a settlement wallet.

A merchant can be a natural person, company, association, organisation, or other eligible recipient. Depending on risk, MonaxPay can require additional evidence, restrictions, or manual review.

• Email verification, password/TOTP, and a secure session are required.
• Wallet verification is completed through wallet connection, signature, or comparable control.
• KYC/KYB, sanctions, wallet, adverse-media, and prohibited-use checks can be required before live approval.
• Master Admin and the policy engine can limit countries, assets, industries, volumes, campaigns, API use, or individual merchant profiles.
• A once-approved merchant activity is generally open, but can be restricted if risk, provider requests, complaints, disputes, or policy changes require it.

By default, MonaxPay creates a payment-specific Solana deposit wallet for each payment. The checkout uses that wallet as the destination when the route is approved. MonaxPay may fund that wallet with SOL for network fees from a configured hot wallet.

After provider and onchain confirmation, MonaxPay deducts the configured platform fee from the gross amount and forwards the net amount to the merchant's verified settlement wallet. MonaxPay does not keep pooled merchant balances.

Alternatively, MonaxPay can require prepaid fee credit by admin policy or activate another permitted fee model. The fee rate applied to each link is recorded in the ledger and merchant view.

• The merchant must act lawfully and comply with consumer, tax, advertising, sanctions, and sector rules.
• Offer text, pricing, delivery terms, risks, support, and refund policy must be true and clear.
• Misleading call-center scripts, pressure tactics, hidden terms, fake claims, and chargeback evasion are prohibited.
• Logos, display names, and public descriptions must be lawful and non-misleading.
• The merchant is responsible for support, refunds, taxes, accounting, and evidence.

If a payer disputes a card, bank, or provider payment, the provider may request evidence or action. MonaxPay displays available provider information where lawful and available.

Because crypto may already have been forwarded to a wallet, a refund can require a new merchant transaction or a provider-supported process. The merchant remains economically responsible for valid refunds, chargebacks, provider fees, evidence, and customer communication.

MonaxPay may pause links, reduce limits, request additional evidence, or block further payments while disputes are open.

API access is allowed only through approved scoped credentials. Call-center, CRM, affiliate, or campaign partners must use truthful scripts, clear consent, auditable campaign data, and permitted use cases.

MonaxPay can rotate, suspend, mark as compromised, require IP allowlists, review campaigns, or activate merchant-specific restrictions for API credentials.

The merchant receives dashboard and API data for gross payment, MonaxPay fee, net settlement, wallets, provider status, onchain evidence, receipts, and support/dispute status. These records are operational evidence and can depend on provider or blockchain finality.

The merchant must satisfy its own tax and accounting duties. MonaxPay does not provide tax advice.

MonaxPay may pause or terminate accounts, links, routes, API access, or settlement when there is suspected prohibited use, fraud, sanctions risk, provider breach, security incident, false information, or legal obligation.

Termination does not affect fees, refund, chargeback, tax, evidence, or damages obligations already incurred.