TemplateFREE⏱️ 90-120 minutes
Card Issuing Product Spec Template
Free template for specifying card issuing features. Covers physical and virtual card lifecycle, BIN sponsorship, authorization controls, spend limits,...
Updated 2026-03-05
Card Issuing Spec
| # | Item | Category | Priority | Owner | Status | Notes | |
|---|---|---|---|---|---|---|---|
| 1 | |||||||
| 2 | |||||||
| 3 | |||||||
| 4 | |||||||
| 5 |
#1
#2
#3
#4
#5
Edit the values above to try it with your own data. Your changes are saved locally.
Get this template
Choose your preferred format. Google Sheets and Notion are free, no account needed.
Frequently Asked Questions
Should I build on a processor or build the issuing infrastructure myself?+
Use a processor (Marqeta, Lithic, Galileo, Stripe Issuing). Building card issuing infrastructure from scratch requires a direct network membership, PCI-DSS Level 1 certification, and a team of 20+ engineers. Processors abstract the network integration and let you focus on product logic.
Virtual cards or physical cards first?+
Start with virtual cards. They can be issued instantly, cost nothing to produce, and let you validate your authorization logic and user experience without the complexity of card fulfillment and shipping. Add physical cards when user demand justifies the per-card cost.
How fast does my authorization webhook need to respond?+
Under 100ms at P99. Card networks impose strict timeout limits (typically 2-5 seconds end-to-end). Your processor will have its own SLA, but aim for < 100ms to leave room for network latency. If you exceed the timeout, the default action (approve or decline) depends on your processor configuration.
How do I handle recurring payments when a card is replaced?+
Card networks offer token migration services (Visa Account Updater, Mastercard Automatic Billing Updater). When you issue a replacement card, the old PAN-to-token mapping is updated so recurring merchants can continue charging without the cardholder re-entering card details. Ensure your processor supports this.
What fraud rate should I target?+
For card issuing programs, target a fraud basis points (bps) rate under 10 bps (0.10% of transaction volume). Card networks monitor program fraud rates, and programs exceeding thresholds face fines or program termination. Start conservative with tighter spend rules and loosen based on data.
Explore More Templates
Browse our full library of PM templates, or generate a custom version with AI.