Finance and accounting decision

Nurpay Technologies

A technical user can build the core payment plumbing and a merchant dashboard (and open-source projects exist to accelerate this), but full production-grade payments (PCI, bank relationships, fraud/risk, and operations) make a complete replacement impractical for most single developers.

Visit website

You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off130 h to build

$0/mo6 h/mo upkeep

No published price to break even against.

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Nurpay Technologies alternatives, with the arithmetic →

juspay/hyperswitchOpen source, composable payments platform | PCI compliant | SaaS and Self-host options | Enables connectivity to multiple payment, payout, fraud, vault and tokenization providersOpen on GitHub juspay/hyperswitch-prismOne library | Many payment processors | Scale to multiple processors with few lines of code.Open on GitHub

What a replacement has to do

Accept payments from buyers, route/authorize with payment providers, persist transactions, notify merchants, provide a basic merchant dashboard.

What it still won’t have

PCI-compliant infrastructure and certification
Banking relationships and sponsored merchant accounts
Mature fraud-detection and chargeback handling operations
Brand trust, liability underwriting, and large-scale operational support

What remains hard

Product polish and ongoing maintenance

Read the build prompt

First-year cost

No published price

Nurpay Technologies does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying

—

Subscription price × seats × 12

Build it

—

AI build —APIs + hosting —

Time you would spend

—

What you would spend

Your monthly price$/moAI to build it$ onceAPIs + hosting$/mo

What we assumed

Initial buildhrsMonthly upkeephrsYour rate$/hr

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet

Build a self-hosted payments relay and merchant dashboard using Node.js (Express) + TypeScript, Postgres for data, Redis for jobs, and React for the admin UI. Core features: connect to 2 payment processors (Stripe and PayPal) via their SDKs, implement authorization and capture flows, webhook receiver with idempotency and reconciliation jobs, transaction and merchant schemas with migrations, simple payouts via provider APIs, basic role-based auth for merchants, logging and audit trails, Docker Compose for local dev and production-ready Dockerfiles. Out of scope: attaining PCI Level 1 certification, bank sponsorship/merchant acquiring contracts, advanced fraud/risk underwriting, high-volume horizontal scaling. Include error handling, retries, unit and integration tests for webhooks and payment flows, and infrastructure IaC notes for deploying to a single VPS or small cloud instance.

How we checked3 sources · 3/3 runs agreed · evidence score 64

How the score was reached

Partly verdict base52
An open-source build was found+5
3 cited sources+3
3/3 assessment runs agreed+4
Evidence score64

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 3

Every page the run actually retrieved.

official productNurpay
open sourcejuspay/hyperswitch
open sourcejuspay/hyperswitch-prism

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded