Reloadable or single-load
Support ongoing balances or fixed-value cards for incentives, refunds and campaigns.
No scheme membership. One API. Launched under your brand.
Load-first cards for payouts, benefits, gifting and controlled spending. Prepaid programs run on the same NetPay issuing rails with balance management designed for load-and-spend models.
The product is rarely the hard part. The dependencies are: scheme membership, a sponsor bank, a certified PCI environment and a stack of vendors, each with its own queue.
Going to Visa or Mastercard directly means capital requirements, audits and a sponsor bank before a single card ships.
PCI DSS, KYC, AML monitoring and disputes each need their own people, vendors and audit cycles.
Processor, ledger, KYC and payout providers each bring their own API, contract and failure modes.
Every dependency sits in another team's queue, and you still own the audits.
Same program. One partner, one API and one contract.
Everything here runs on the same NetPay rails, API and dashboard.
Support ongoing balances or fixed-value cards for incentives, refunds and campaigns.
Fund cards via API — one card or thousands in a batch — with instant balance availability.
Category, merchant, country and amount rules keep prepaid funds used exactly as intended.
Deliver prepaid value as an instant virtual card, a branded plastic card, or both.
Real-time balance and transaction events keep your program ledger authoritative.
KYC flows scaled to program type, on PCI DSS Level 1 certified infrastructure.
A guided path. We carry the regulated heavy lifting so your team ships the product.
Reloadable general-purpose, payout cards, or fixed-value incentive cards.
Set load limits, spend rules and expiry that match the use case.
Create cards and push funds through the API, individually or in batches.
Track balances and transactions in real time via webhooks and reporting.

Every option gets you to a live program eventually. The rows show what each one asks of your team.
| Capability | NetPay | Build in-house | Legacy processor |
|---|---|---|---|
| Card scheme membership | Not needed, we sponsor | Required | Usually required |
| PCI DSS scope | On our Level 1 systems | Yours to certify | Shared with you |
| Cards, IBANs and payouts | One platform | Separate vendors | Cards only |
| Integration | One REST API and webhooks | Several vendor APIs | Batch files, legacy APIs |
| Sandbox before launch | Full sandbox | Build your own | Limited |
| Your brand | Every card, app and statement | Yes | Often co-branded |
A debit card draws on a deposit account balance; a prepaid card spends only what has been loaded onto it. Prepaid programs give the business tighter control over funding and are often simpler to distribute for payouts, benefits and incentives.
Yes. Loads are API-driven, so you can schedule recurring funding — like weekly payroll or monthly allowances — or trigger loads from events in your own product.
Cards spend wherever the network is accepted, subject to the country and channel controls you configure for the program.
Tell us what you're building and we'll scope the right program and rails with you.