Skip to main content
Learn how to issue virtual and physical cards for your customers using Zentra’s card issuing API. Enable spending, set limits, and manage card lifecycle.
This guide now follows the reviewed public gateway contract. Older SDK examples and older internal docs may still refer to freeze, unfreeze, terminate, or updateLimits. In the reviewed public HTTP contract, those controls map to lock, unlock, and security settings instead.

What You’ll Learn

  • Issue virtual cards instantly
  • Request physical cards
  • Fund and manage cards
  • Set spending limits
  • Handle card transactions
  • Lock, unlock, and secure cards

Prerequisites

  • Zentra API account with card issuing enabled
  • Customer KYC verified
  • Sufficient wallet balance for funding

Card Issuing Flow

Step 1: Create a Virtual Card

Issue a virtual card instantly:
Sensitive card details are card-program specific. Do not assume PAN/CVV retrieval is part of the default reviewed public gateway unless your approved card program explicitly exposes it.

Disposable / Single-Use Virtual Cards

Use single_use: true to issue a virtual card that auto-terminates after its first successful authorization:
This is opt-in per card. Cards without single_use: true remain standard multi-use cards.

Location-Aware Geofencing (Optional)

Geofencing is optional and card-scoped (geofence_enabled: true). When enabled, authorization can auto-decline physical-channel transactions if merchant location and device location are too far apart.

Step 2: Display Card Details Securely

Use the Zentra UI SDK for PCI-compliant card display:

Step 3: Fund a Card

Add funds to an existing card:
Use a stable transaction_reference for client retries and reconciliation; keep it unique per logical funding action. Legacy reference is still accepted for backward compatibility, but it is deprecated for card funding and should be migrated.

Step 4: Update Card Security Controls

Use card security settings to update spending limits and related controls:

Step 5: Handle Card Transactions

Process transaction webhooks:

Step 6: Card Controls

Lock a Card

Temporarily disable a card:

Unlock a Card

Re-enable a locked card:
The reviewed public gateway does not currently expose a dedicated card termination endpoint. Use lock plus security controls for public contract flows, and coordinate permanent closure through your approved operational path if your card program requires it.

Card Types & Features

Supported Networks

Error Handling

Next Steps

Cards API

Full API reference

UI SDK

Secure card display

Webhooks

Handle card events

Going Live

Production checklist