Enablement & Configuration

Enable the feature and configure your card program before issuing cards.

Feature Enablement & Setup

The Card Issuance capability is a powerful feature set that is securely locked by default. To start using it, you must follow a guided process.

📘

This feature requires prior enablement and configuration. Please contact the Account Management team to get started.

The Card Issuance configuration-based feature. You cannot activate it solely through API calls. Reach out to your Account Manager (AM) to request the "Unified Card Issuance" feature. They will toggle the necessary settings to unlock the unified workflow for your Program Manager.

Capabilities Unlocked

Once this feature is enabled, you gain access to a powerful suite of operations:

  • Unified Issuance: Issue both Debit and Prepaid cards using a single API endpoint.
  • Lifecycle Management: Self-serve tools to Freeze, Unfreeze, Replace, and Cancel cards.
  • Granular Controls: Set specific spend limits for individual cards.
  • Digital Wallets: Enable Push Provisioning to Apple Pay and Google Pay.
  • Security: Retrieve PCI-compliant card images for secure display.

Card Program Configuration

A Card Program acts as the master template for issuing cards. It defines key business rules such as spending limits, restricted merchants, and KYC requirements. By configuring these controls at the Program Manager level, every card issued under the program automatically inherits the required compliance and operational settings, ensuring consistency and reducing manual setup.

📘

To establish your Card Program template based on your business needs, please contact the Account Management (AM) Team.

Once the AM team has completed the setup, you gain full visibility of the Card Program setup for you by:

  1. You can Retrieve All Card Programs linked to you that meet a requested criterion by using the POST /v1/issuance/cardProgram/list endpoint. You can use this endpoint to sort the Card Programs by createdOn, name, and id of the Card Program set up, and apply these filters:
  2. Similarly, using the GET v1/issuance/cardProgram/id/{id} where “id” will be the Card Program ID, you can fetch the full configuration of a specific Card Program to verify active limits, controls, and settings.
  3. While the core rules are set by the AM (Account Management), you can self-manage who accesses the program. Using the POST v1/issuance/cardProgram endpoint you can restrict or grant access to specific sub-entities (e.g., specific Partners or Customers) without needing AM intervention.

Choose your Card Holder

Before issuing a card, you must ensure the cardholder, whether an individual or a business user, meets the eligibility criteria defined.

  • The cardholder's Customer Identification Program (CIP) checks must be VERIFIED. Issuance requests for unverified or pending customers will be rejected.
  • The mailing address of the cardholder must be set up and must be a physical location. PO Boxes and Lockbox addresses are strictly prohibited for card shipment.
  • Only one physical debit card can be issued to a single Authorized User for a specific Passport account.

To whom can Cards be Issued to ?

  • Business Customer: These are corporate or commercial entities. While the account belongs to the business, the card is issued to a specific person associated with it.

    • Beneficial Owner: The primary individual who owns the business.
    • Authorized Signatory: Individuals with legal authority to manage the account.
  • Individual Customers: These are standard personal accounts managed by a single person. The individual account holder is the only eligible cardholder.


Pending Items


.readme-logo { display: none !important; }