Clear rules for using the platform.

You may use PayBridgeNP only for lawful business purposes and only in connection with products or services you are authorized to sell or collect payment for. You must provide accurate account details and keep your login, API keys, and provider credentials secure.

Access to the merchant dashboard is available through the merchant dashboard. You are responsible for activity that occurs through your account unless caused by our own breach or misconduct.

• Use only your own valid and authorized provider credentials, bank relationships, and business information for eSewa, Khalti, Fonepay, ConnectIPS, and HamroPay.
• Maintain accurate pricing, refund, fulfilment, and customer support practices for your end users.
• Comply with the rules of eSewa, Khalti, Fonepay, ConnectIPS, HamroPay, banks, regulators, tax authorities, and any other applicable law or policy.
• Ensure your website, checkout context, and webhook endpoints are secure and under your control.
• Respond to disputes, refund requests, and customer complaints related to your goods or services.
• Configure customer-facing notifications (SMS, email, receipts) accurately and on a frequency that respects your customers.

PayBridgeNP is offered in two tiers. The current pricing and feature breakdown is published on the website and inside the dashboard /upgrade page; the rules below describe how the tiers work.

• Free — capped monthly processing volume, one webhook endpoint, one active API key, and a 30-day list-endpoint retention window. Premium-only features are visible but inactive.
• Premium — recurring billing system, advanced analytics, webhook replay, audit logs, customer SMS notifications, embeddable Buy Buttons, Direct-QR API for Fonepay, MCP write access, Shopify Buy Now button, Shopify Draft-order send-link, and unlimited team / webhooks / API keys / retention.
• Plan changes — caps and features may change as the product evolves. Material changes will be presented in the dashboard or via direct notice before they apply to your account.
• Enforcement — Free-tier limits are enforced server-side; once a cap is reached, the related action returns an error until the underlying state changes (volume resets monthly; webhooks and keys can be revoked to free up the slot).

PayBridgeNP publishes a Model Context Protocol server. When you connect an AI assistant (Claude, ChatGPT, Cursor, etc.) using a token issued from your dashboard, you authorise that agent to act on your behalf within the scopes of the token.

• You are responsible for actions an authorised AI agent takes through your token, including refunds, payment-link creation, subscription changes, and any other write operation made available to your plan.
• Tokens can be revoked at any time from /mcp. Revocation is immediate.
• Money-moving actions (refunds, voids, etc.) surface confirmation prompts in the agent's interface, but final responsibility for confirming or denying remains with the merchant operator running the agent.
• Don't share MCP tokens between humans or paste them into untrusted environments. Treat them like API keys.

PayBridgeNP sends transactional SMS and email on your behalf — payment receipts, refund confirmations, payment reminders, and similar transactional messages. By using the platform you agree:

• To use SMS and email only for legitimate transactional communication tied to a real payment relationship with the recipient. No marketing campaigns, broadcast messaging, or unsolicited outreach.
• That PayBridgeNP applies per-merchant rate limits (burst and recipient cooldown) to protect provider relationships and downstream cost. Messages exceeding limits are suppressed and logged.
• That delivery via the SMS provider (bulk.bedbyaspokhrel.com.np) and email provider (Resend) is not guaranteed for any individual message; delivery is best-effort.
• That you will not use the SMS history or email log to harvest customer contact data outside the purpose for which the customer provided it.

PayBridgeNP publishes official integrations for Shopify, WooCommerce, and WHMCS, plus first-party SDKs for TypeScript, PHP, Python, and mobile. Integrations are subject to their own platform rules in addition to these terms.

• Shopify — installation requires accepting the scopes the app declares. Uninstalling triggers Shopify's mandatory data-deletion webhooks, which PayBridgeNP honours.
• WooCommerce — distributed under GPL-2.0-or-later. Updates are delivered through the plugin distribution channel.
• WHMCS — distributed via the WHMCS Marketplace. Updates are delivered through the Marketplace and the official documentation site.
• SDKs — distributed under MIT (TypeScript, PHP, Python). Mobile SDK is distributed under MIT via npm.

We aim for high reliability, but uptime is not guaranteed. Provider outages, bank downtime, network interruptions, or upstream API changes may affect payment processing, callbacks, or reconciliation. Status will be communicated through the dashboard, the website, or direct outreach where appropriate.

We may restrict, suspend, or terminate access if we believe an account presents fraud, abuse, security, legal, or operational risk. Suspension may be triggered by repeated policy violations, misuse of the API, misleading checkout flows, or use in prohibited categories.

• Suspended accounts have API keys returning 403, hosted checkout disabled, and dashboard access read-only with the suspension reason surfaced. The merchant is notified by email.
• You may stop using the service at any time. Some records may still be retained after termination where needed for audit history, fraud prevention, dispute handling, or legal compliance.
• Reinstatement is at PayBridgeNP's discretion and may require remediation of the underlying issue.

PayBridgeNP provides software and operational tooling for payment orchestration. We do not guarantee that every payment will succeed, that a provider will remain available, or that your business use will meet every commercial or regulatory requirement.

To the maximum extent permitted by law, PayBridgeNP is not liable for indirect, incidental, special, consequential, or lost-profit damages, or for losses caused by merchant error, provider actions, customer disputes, bank restrictions, or third-party downtime. Our total liability relating to the service is limited to the amount you paid us for the specific service giving rise to the claim during the three months before the event.