Connect the way you already work
A module for WHMCS, a plugin for WooCommerce, a self-hosted app for Shopify, SDKs for TypeScript, PHP and Python, popup checkout and an MCP server. Whichever you use, customers pay on the same hosted checkout, and nothing is marked paid until Paymentsnp has verified the payment.
- Every integration works in test mode
- Packages on npm, Packagist and PyPI
- Plugins from your dashboard
- Integration guide (PDF)
- WHMCS payment gateway v3.0.0
- WooCommerce plugin (WordPress) v1.0.0
- Shopify app (self-hosted) v1.0.0
- TypeScript / JavaScript SDK v1.0.0
- MCP server for AI assistants v0.1.0
For verified owners, administrators and developers
Everything that connects. With the version it ships at.
Nine ways in, all ending at the same hosted checkout and the same verified payment. Each row shows the package name, its current version and where it comes from.
Platform plugins
Install into the billing system or store you already run. Each has a full setup guide.
SDKs and tools
Official clients for the API-key routes, from public package registries.
- TypeScript SDK and CLITyped client with retries and webhook verification, plus a paymentsnp command.
- PHP SDKFor plain PHP and frameworks alike. Works with or without Composer.
- Python SDKStandard library only, typed, with Flask and Django examples.
- MCP serverLets an AI assistant read payments and invoices. Read-only unless you allow writes.
Build it yourself
No package needed: call the API from your server, or open checkout in a popup.
Requirements. Check before you download.
Each integration lists the same thing in its own guide. A connected, ready and enabled gateway in the same environment is needed for all of them.
| Integration | Version | Runs on | Also needs |
|---|---|---|---|
| TypeScript SDK and CLI | 1.0.0 | Node 18+, Bun, Deno and edge runtimes | Zero dependencies; ESM, CommonJS and types |
| PHP SDK | 1.0.0 | PHP 7.4+ | ext-curl and ext-json; works without Composer |
| Python SDK | 1.0.0 | Python 3.9+ | Standard library only |
| MCP server | 0.1.0 | Node 20+ | An MCP client and an API key |
| WHMCS module | 3.0.0 | WHMCS 8.x on PHP 7.4 to 8.3 | A public HTTPS System URL and a running cron |
| WooCommerce plugin | 1.0.0 | WordPress 6.0+, WooCommerce 7.0+, PHP 7.4+ | Store currency set to NPR |
| Shopify app | 1.0.0 | Node 20, self-hosted | A public HTTPS URL and a store in NPR |
| Popup checkout | checkout.js | A script tag on your page | Your domain on the approved embed domains, up to 20 per environment |
Where to get them. Registries for code, the dashboard for plugins.
SDKs and the MCP server
The TypeScript SDK and MCP server are on npm, the PHP SDK on Packagist and the Python SDK on PyPI, under the names shown here.
Plugins, modules and the integration guide
The WHMCS module, WooCommerce plugin, Shopify app, SDK archives and the integration guide PDF are downloaded from Dashboard > Downloads. Downloads are open to verified owner, administrator and developer users of a workspace. There are no public download links.
npm install @paymentsnp/sdkcomposer require paymentsnp/paymentsnp-phppip install paymentsnp# Started by your MCP client; nothing to install
npx -y @paymentsnp/mcp<script src="https://paymentsnp.com/checkout.js"></script>
<script>
// checkoutUrl comes from a checkout session your server created
window.Paymentnp.open({ checkoutUrl, onSuccess, onCancel, onClose });
</script>How every integration confirms a payment. Never from the browser.
A return page or a webhook body is a hint, not proof. Each integration asks the API for the verified payment and checks the order, amount, currency and environment before it marks anything paid.
- Your serverCreates a checkout for the order
- CustomerPays on hosted checkout
- ProvidereSewa, Khalti or Fonepay
- PaymentsnpVerifies and sends a signed webhook
- Your systemFetches the payment, then marks it paid
Questions about integrations.
Is there a plugin for my platform?
Paymentsnp ships a WHMCS module, a WooCommerce plugin and a self-hosted Shopify app. Anything else connects through the REST API, an SDK or popup checkout.
Why are plugins not on a public download page?
They are downloaded from Dashboard > Downloads by verified owner, administrator and developer users of a workspace. The SDKs and MCP server are on public package registries.
Does the Shopify app put eSewa inside Shopify checkout?
No. Shopify only admits approved Payments Partners into its checkout. The app adds a manual payment method and a signed pay link, and marks the order paid after verification.
Which API key scopes do the plugins need?
The WHMCS module, WooCommerce plugin and Shopify app each need checkout:create, checkout:read and payments:read, in the same environment as the plugin.