Nadcab logo

CARD ISSUING INFRASTRUCTURE

Crypto Card Issuing API for Fintech & Web3 Platforms

Build card issuing capabilities into your wallet, exchange, or fintech application. Connect card creation, card management, transaction events, and operational controls through a structured API integration.

Designed for businesses building branded virtual and physical card experiences through approved issuing and processing partners.

  • ▸Card creation, status, and control operations
  • ▸Transaction and lifecycle events via webhooks
  • ▸Virtual and physical programs, issuer dependent
card-platform · illustrative console201 · request accepted
POST/v1/cardsIllustrative API example
request
{
"customer_id": "cust_8f42…",
"card_type": "virtual",
"program_id": "prog_…",
"idempotency_key": "req_01J…"
}
response
{
"card_id": "card_5d21…",
"status": "pending_issuance",
"card_type": "virtual",
"last4": "•• 4412"
}
VIRTUAL CARD

•••• •••• •••• 4412

CARDHOLDERissuing

Card creation requested — status returns to your backend.

Final issuance outcome is determined by the issuing partner.

CARD NETWORK OPTIONS

Build for the card networks your market supports.

Explore virtual and physical card program options across eligible networks and issuing partners. Network availability, supported regions, and card capabilities depend on the approved program structure.

VIRTUAL · PHYSICAL

•••• 4412

Visa

Visa programs

Card creation, status, controls, and transaction visibility where the program enables them.

Exploratory — confirmed during program design

PROGRAM OPTION

•••• 4412

Mastercard

Mastercard programs

Card creation, status, controls, and transaction visibility where the program enables them.

Exploratory — confirmed during program design

VIRTUAL · PHYSICAL

•••• 4412

Discover

Discover programs

Card creation, status, controls, and transaction visibility where the program enables them.

Exploratory — confirmed during program design

PROGRAM OPTION

•••• 4412

UnionPay

UnionPay programs

Card creation, status, controls, and transaction visibility where the program enables them.

Exploratory — confirmed during program design

Network names are shown for program exploration only. Availability is verified with the issuing partner for your markets before any commitment.

HOW IT WORKS

From your application to an active card.

Your application connects to the card platform through supported APIs. Card creation, lifecycle updates, and transaction events are coordinated through the relevant issuing and processing integrations.

STEP 1 OF 5

Customer Onboarding

Collect the required customer information and complete applicable identity verification before card issuance, according to the approved program requirements.

  • Customer application
  • Verification status
  • Onboarding completion

request direction response / event

your application
customer = collect_application()
verification = check_status(customer)
if verification == "approved":
enable_card_creation(customer)

API ARCHITECTURE

A clear integration between your platform and card infrastructure.

Build your customer-facing experience while connecting the required card operations to approved issuing and processing systems. Keep responsibilities clear across your application, integration services, and regulated program partners.

LAYER A

Your Platform

  • Mobile application
  • Web application
  • Crypto wallet
  • User accounts
  • Your backend services

LAYER B

Nadcab Integration

  • API gateway
  • Card management orchestration
  • Event handling
  • Webhook delivery
  • Operational reporting
  • Integration monitoring

LAYER C

Approved Partners

  • Issuing partner
  • Card processor
  • Applicable verification providers
  • Settlement and program services
Authenticated API requestCard lifecycle responseTransaction eventWebhook notification

Final architecture and responsibilities depend on the selected issuing partner and commercial program arrangement.

INTERACTIVE API EXPLORER

Explore the card operations your application needs.

Understand the typical integration workflows behind card creation, management, and transaction visibility.

Create a card for an eligible customer.

Submit a card creation request after the customer has completed the required onboarding and verification steps. The issuing partner determines the final issuance outcome.

POST/v1/cardsIllustrative API example
ParameterTypeNotes
customer_idstringVerified customer reference from your system.
card_typeenumvirtual or physical, where supported.
program_idstringApproved program configuration to issue under.
idempotency_keystringPrevents duplicate cards on safe retries.
request
{
"customer_id": "cust_8f42…",
"card_type": "virtual",
"program_id": "prog_…",
"idempotency_key": "req_01J…"
}
response
{
"card_id": "card_5d21…",
"status": "pending_issuance",
"card_type": "virtual"
}

Errors & edge cases

Handle validation errors per-field, treat timeouts as unknown outcomes (query status before retrying), and never create a second card for the same idempotency key.

Card lifecycle

none → pending_issuance → active / declined (issuer decision)

CARD LIFECYCLE

One integration. Multiple card experiences.

Support the card experiences your business needs, from digital-first card access to physical card programs, where supported by your issuing arrangement.

YOUR APP

VIRTUALACTIVE

•••• •••• •••• 4412

Coffee ••••$4.80

Transit ••••$2.40

Cloud ••••$19.00

FREEZEDETAILS

Digital cards built for immediate access after issuance.

Offer eligible customers a digital card experience inside your application, with supported card controls, transaction visibility, and account management.

  • Digital card access
  • Card status
  • Spending visibility
  • Supported freeze/unfreeze actions
  • Transaction history

PHYSICAL CARDYOUR BRAND

•••• •••• •••• 4412

CARDHOLDER NAMEVALID ••/••

  1. Ordered — Card produced under the approved program

  2. Dispatched — Delivery status tracked operationally

  3. Delivered — Cardholder confirms receipt

  4. Activated — Activation workflow completed in-app

Extend the experience beyond the screen.

Explore physical card issuance with supported card artwork, delivery workflows, activation processes, and card lifecycle management.

  • Physical card ordering where supported
  • Card artwork
  • Delivery status
  • Activation workflows
  • Replacement and lifecycle controls

SECURITY & TESTING

Build with security and operational control in mind.

Card issuing integrations require careful handling of customer information, authenticated requests, event delivery, and operational permissions. Design your integration around clear access boundaries and robust failure handling.

Request authentication flow

  1. 1 Your backend signs / authenticates the request
  2. 2 Credentials stay server-side — never in the app
  3. 3 Integration layer validates & routes the call
  4. 4 Issuer response recorded against your request ID

Webhook validation flow

  1. 1 Event received at your endpoint
  2. 2 Authenticity verified before trusting payload
  3. 3 event_id stored — duplicates dropped safely
  4. 4 2xx returned fast; processing runs async

Authentication & Access

Protect API access using the authentication methods supported by the integration, secure credential storage, restricted permissions, and controlled backend access.

Sensitive Card Data

Minimize exposure of payment credentials. Use approved tokenization and secure card-data handling mechanisms where required by the issuing arrangement.

Webhook Security

Validate event authenticity, handle retries, prevent duplicate processing, and maintain reliable event delivery records.

Sandbox Testing

Use available test environments to validate card creation, lifecycle updates, transaction handling, error scenarios, and webhook processing before production rollout.

Operational Monitoring

Track integration errors, processing failures, request outcomes, and operational exceptions to support reliable day-to-day management.

CAPABILITIES MATRIX

Understand what your integration can support.

CapabilityTypical use caseIntegration approachAvailability / dependency
Customer onboarding integrationCollect applications inside your appYour UI + verification handoffProgram dependent
Card creationIssue virtual/physical cardsAPI request via integration layerIssuer dependent
Card status retrievalShow live card state to usersAPI read / event syncSupported where enabled
Card freeze / unfreezeUser & operator card controlsControl API actionsIssuer dependent
Virtual card managementDigital-first card accessIn-app card experienceSupported where enabled
Physical card workflowsOrder, deliver, activate cardsFulfilment workflow + API statusProgram dependent
Transaction historySpending views & notificationsAPI reads + webhook eventsSupported where enabled
Webhook notificationsReact to events in real timeSigned event deliveryRequires confirmation
Operational reportingOps visibility & reconciliationReports / admin toolingProgram dependent
Cardholder managementSupport & lifecycle operationsAdmin workflowsSupported where enabled
Funding workflow integrationConnect balances to card spendConversion & settlement arrangementRequires confirmation
Role-based administrationControl team permissionsAdmin roles & audit trailProgram dependent

Availability labels are deliberately conservative: final capability depends on the issuing partner and program configuration confirmed for your business.

USE CASES

Built for businesses adding cards to existing products.

  1. 1Exchange balance↓
  2. 2Funding workflow↓
  3. 3Card account↓
  4. 4Spending activity

Crypto Exchanges

Extend an exchange experience with branded card functionality, subject to supported funding, conversion, and issuing arrangements.

  1. 1Wallet application↓
  2. 2Customer verification↓
  3. 3Card management↓
  4. 4Transaction events

Web3 Wallets

Give wallet users access to supported card experiences through integrated card management and transaction visibility.

  1. 1Fintech backend↓
  2. 2Issuing integration↓
  3. 3Customer card↓
  4. 4Admin monitoring

Fintech Platforms

Add card issuing capabilities to a broader financial application while maintaining a consistent customer interface and operational workflow.

IMPLEMENTATION SUPPORT

Plan your card integration with a technical team.

Discuss your existing application, API requirements, card products, target markets, and operational needs with the Nadcab team.

Talk to an Integration Specialist

What the first technical review covers

  • Your application architecture and backend readiness
  • Card products: virtual, physical, or both
  • Target countries and indicative card volumes
  • Funding methods and conversion requirements
  • Required API operations and webhook events
  • Issuing-partner fit and program dependencies

Crypto Card Issuing API — Frequently Asked Questions

Potentially, yes. Supported APIs can connect card-related functionality to an existing wallet application. The integration scope depends on your wallet architecture, funding workflows, and the selected issuing partner.

READY TO INTEGRATE?

Bring card functionality into your platform.

Tell us what you're building. We'll help you evaluate the available API capabilities, integration requirements, issuing dependencies, and implementation approach.

  • API capability review
  • Technical architecture discussion
  • Issuer-dependent program planning

Explore More Solutions

From launching your own branded cards to integrating issuing APIs and digital payment infrastructure, explore the solutions that help you build and scale your card business.