Cardholder management
Create and verify cardholders with KYC data collection handled through structured API flows.
Developers
Card Issuing API
No scheme membership. One API. Launched under your brand.
Create cardholders, issue virtual and physical cards, apply controls and stream transaction events — all from clean REST endpoints designed for product teams that ship fast.
Your program
- Cardholder managementCreate and verify cardholders with KYC data collection handled through structured API flows.
- Instant virtual issuanceGenerate virtual cards in seconds for immediate online use, wallet provisioning or single-use scenarios.
- Physical card ordersTrigger production and fulfilment of branded physical cards from the same endpoints.
- Controls & lifecycleSet limits, merchant rules and channel restrictions; freeze, unfreeze, replace or terminate programmatically.
Launch checklist
- Get sandbox keys
- Create a cardholder
- Issue and control cards
- Subscribe to webhooks
- PCI DSS Level 1 systems
- Visa & Mastercard programs
- 150+ countries
- 35+ currencies
The problem
Launching payments usually means building a bank first.
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.
Scheme membership is a project in itself.
Going to Visa or Mastercard directly means capital requirements, audits and a sponsor bank before a single card ships.
Compliance becomes a second product.
PCI DSS, KYC, AML monitoring and disputes each need their own people, vendors and audit cycles.
Every vendor is another integration.
Processor, ledger, KYC and payout providers each bring their own API, contract and failure modes.
Run it yourself
One program, two ways to launch it.
Launch developers under your brand Ready
Building it with a bankIdle: press Launch the program
- Apply for card scheme membership
- Negotiate a sponsor bank and BIN
- Build and certify a PCI DSS environment
- Integrate processor, KYC and ledger vendors
- Wait for scheme certification
Every dependency sits in another team's queue, and you still own the audits.
Launching it on NetPayIdle: press Launch the program
- Get sandbox keys
- Create a cardholder
- Issue and control cards
- Subscribe to webhooks
Same program. One partner, one API and one contract.
Capabilities
What you can build with the API
Everything here runs on the same NetPay rails, API and dashboard.
Instant virtual issuance
Generate virtual cards in seconds for immediate online use, wallet provisioning or single-use scenarios.
Physical card orders
Trigger production and fulfilment of branded physical cards from the same endpoints.
Controls & lifecycle
Set limits, merchant rules and channel restrictions; freeze, unfreeze, replace or terminate programmatically.
Webhooks for every event
Authorizations, declines, clearing and settlement pushed to your endpoint in real time — no polling, no files.
Sandbox first
A full test environment lets you simulate issuing and spending before any production credentials exist.
How it works
Integration in four steps
A guided path. We carry the regulated heavy lifting so your team ships the product.
Get sandbox keys
Start against test rails with the same endpoints you'll use in production.
Create a cardholder
POST cardholder data; verification workflows run behind the scenes.
Issue and control cards
Issue virtual or physical cards and attach spending rules per card.
Subscribe to webhooks
Consume real-time transaction events to drive balances, notifications and ledgers.
Who it's for
Built for teams that move money.
- Product engineering teams
- Fintech developers
- Expense platforms
- Marketplaces
- SaaS with embedded finance
- Crypto applications
How we compare
How NetPay compares.
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 |
Can card issuing be integrated purely through API?
Yes. Every program operation — cardholder creation, issuance, controls, lifecycle and transaction data — is available through REST endpoints, so you can run a program entirely from your own stack. The dashboard remains available for operations teams.
Is there a sandbox for testing?
Yes. Sandbox access is available so you can integrate and test issuing flows, controls and webhooks before going live.
How do webhooks handle authorization events?
When a cardholder transacts, the authorization event — approved or declined, with amount, merchant and reason data — is pushed to your configured endpoint in real time, followed by clearing and settlement events as they occur.
What does the API documentation cover?
The Distributor Card API documentation covers cardholder creation, card issuance and management with request/response examples you can copy directly.
Launch developers under your brand.
Tell us what you're building and we'll scope the right program and rails with you.