Feature Enablement & Setup

The Unified Card 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 Unified Card API is a 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 is the "Master Template" that acts as the blueprint for your cards, defining all business rules such as spending limits, restricted merchants, and KYC requirements. It is essential to set up because it centralizes these configurations at the Program Manager level, ensuring that every card you issue automatically inherits the correct compliance and operational controls without the need for manual, error-prone setup on individual accounts. This structure serves as the foundation for the Unified API's automated decision-making.

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

Managing your Program

Once the AM team has completed the setup, you gain full visibility and specific control over the program via the API.

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:

Field	Required	Description
`id`	✅ Yes	Unique identifier of the Card Program.
`name`	No	List programs using exact name match.
`status`	No	Status of the Card Program (`ACTIVE`, `INACTIVE`).
`subType`	No	Type of Card Program (`PLASTIC`, `DIGITAL`).
`branding`	No	Branding category of the Card Program (`PRIORITY_BRANDED`, `CO-BRANDED`).

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.
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. You can update various Card Program fields such as:

Field	Required	Description
`cardProgram.id`	✅ Yes	Unique identifier of the card program for which access control is defined.
`accessControl.holderType`	No	The entity type for which access is controlled (`CUSTOMER`, `PARTNER`).
`accessControl.scope`	No	Specifies the scope of access (`SINGLE`, `ALL`).
`accessControl.isAllowed`	No	Indicates whether access is allowed (`TRUE`, `FALSE`).
`accessControl.description`	No	Description or rule definition explaining the access restriction.
`accessControl.customer.id`	No	Identifier of the customer included in the access rule.
`accessControl.customerSubtype`	No	Type of customer included in the access rule (`CORPORATE`, `CONSUMER`).
`accessControl.isDefault`	No	Indicates if this is the default access control rule for the program (`TRUE`, `FALSE`).