Security

The controls PayBridgeNP relies on for merchant access, credential handling, and payment integrity, and where merchant-side responsibility still matters. PayBridgeNP does not store or hold customer funds. Report a security concern to support@paybridgenp.com with the subject line Security Issue.

Last updated October 30, 2026

Sign-in and keys

  • Merchants confirm their email address before they can create live API keys.
  • Sign in with email and password, Continue with Google, or a passkey on your device.
  • Optional two-factor authentication with an authenticator app.
  • Sensitive actions, such as creating an API key, removing a passkey, changing team members, or exporting data, ask you to confirm it is you again.
  • Your dashboard settings list every signed-in browser. Sign out any of them, or all of them, in one click.
  • Staff access is separate from merchant access, so a merchant sign-in can never reach internal tools.
  • Secret keys (sk_live_, sk_test_) are for your server only; publishable keys (pk_live_, pk_test_) are safe to use in a browser.
  • AI-agent (MCP) tokens have read or write permissions you choose, and revoking one takes effect immediately.

Data separation

  • Each merchant's data is kept apart from every other merchant's, enforced in the database as well as in the application.
  • Live and sandbox are separate: sandbox keys cannot read live data, and live keys cannot read sandbox data.
  • Staff actions on merchant accounts are recorded in an audit log, with a stated reason for sensitive changes.

Encryption

  • In transit - every PayBridgeNP website, the API, and the hosted checkout use HTTPS (TLS 1.2 or newer).
  • Provider credentials and webhook signing secrets - encrypted at rest. Webhook secrets are shown to you once, when created.
  • Passwords - stored only as a secure hash, never in plain text.

Payment integrity and verification

A payment is marked successful only after PayBridgeNP confirms it with the payment provider, never because of a browser redirect alone. You then see the result in the dashboard, through the API, and in signed webhooks.

  • Signed webhooks - every webhook carries a signature. Check it before you update an order.
  • Safe retries - repeated or out-of-order provider messages are handled once, and refund requests can be retried safely with the same Idempotency-Key.
  • Delivery logs - see whether each webhook was accepted, failed, or is waiting to retry.
  • Buyer-facing pages - receipts and payment pages show only what a buyer needs to recognise a payment, never merchant-internal data.
  • Suspension - a suspended account cannot use its API keys, hosted checkout, payment links, or dashboard.

Abuse controls

  • Rate limits on the public API.
  • Limits on SMS sending, so a mistake cannot flood a customer.
  • Plan limits are enforced on our servers, not in the browser.

Sandbox isolation

Sandbox and live are separate modes that cannot cross. There is one exception you must know about before you test: Fonepay.

  • Sandbox keys can only initiate sandbox checkout sessions; live keys can only initiate live ones. The two cannot cross.
  • Sandbox SMS messages are logged but never sent, so there is no real message and no cost.
  • Fonepay has no test environment. Sandbox eSewa and Khalti use each provider's official test environment, so no real money moves. If you add your own Fonepay credentials to a sandbox project, sandbox Fonepay payments run on the real Fonepay network and move real money, hard-capped at Rs 1,000 per payment and Rs 5,000 per merchant per calendar month. Treat a sandbox Fonepay QR like a live one.
  • Webhooks fire as normal in sandbox so integrators can develop end-to-end before going live.

Custom hostnames

Pro-plan and Enterprise merchants can serve hosted checkout on their own subdomain (e.g. pay.theirstore.com). PayBridgeNP provisions and renews TLS for the hostname; the underlying checkout origin and payment-state handling are unchanged. PayBridgeNP can revoke a merchant's custom hostname at any time (downgrade, suspension, abuse), at which point the merchant's URLs revert to checkout.paybridgenp.com.

Security reviews

We review sign-in, data separation, payment integrity, dependencies, and infrastructure for security issues, and fix what we find in order of risk.

If we ever confirm a personal-data breach that affects you, we will notify affected merchants without undue delay, describe what happened and what data was involved, and tell you the steps we are taking in response.

Merchant responsibilities

Security is shared. Merchants are responsible for protecting their own dashboard accounts, API keys, MCP tokens, webhook endpoints, return URLs, and internal systems that consume PayBridgeNP events.

  • Use strong passwords and enable two-factor authentication for operational accounts.
  • Rotate API keys, MCP tokens, or webhook secrets if you suspect exposure.
  • Verify webhook signatures before updating order state on your side.
  • Keep your integration endpoints, servers, and admin tooling patched and access-controlled.
  • Treat AI-agent MCP tokens as sensitive - don't share between humans, don't paste into untrusted environments.

Reporting a vulnerability

If you believe you have found a vulnerability, exposed credential, or account compromise, contact support@paybridgenp.com as soon as possible. Use the subject line "Security Issue". Include a clear description of the issue, affected URL or project, steps to reproduce, and any relevant request IDs or screenshots.

Please avoid public disclosure before we have had a reasonable chance to investigate and remediate the issue. Good-faith reports are appreciated, and with your permission we will credit you once a fix has shipped.

Good-faith research means: do not access, change, or keep data that is not yours; do not disrupt the service or use social engineering; and stop and report as soon as you can see personal data. We will not pursue legal action against researchers who follow these rules.