Card Issuing API
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.
How does a card issuing API work?
A card issuing API exposes card infrastructure as programmable endpoints. Your application calls the API to create a cardholder, issue a card, set spending rules or freeze a card; the platform executes those instructions against the card networks and returns real-time events — authorizations, declines, settlements — via webhooks. This lets developers embed full card functionality without touching scheme-level integration.
What you can build with the API
Cardholder management
Create and verify cardholders with KYC data collection handled through structured API flows.
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.
Integration in four steps
- 1
Get sandbox keys
Start against test rails with the same endpoints you'll use in production.
- 2
Create a cardholder
POST cardholder data; verification workflows run behind the scenes.
- 3
Issue and control cards
Issue virtual or physical cards and attach spending rules per card.
- 4
Subscribe to webhooks
Consume real-time transaction events to drive balances, notifications and ledgers.
Who it's built for
Frequently asked questions
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.
Related pages
Ready to launch with NetPay?
Tell us what you're building — our team will map the fastest route from scoping to a live program.
Get started