Issuing Physical Cards
Interlace offers card issuance options depending on your branding needs: customizable white-label cards, blank cards, or Interlace-branded cards.
Physical Card Issuance Process Overview
Scenario 1: Customizable White-Label Cards
If you need a customized card with your branding, follow these steps:
- Design the card front and back.
- Issuing bank approval (~1 business day).
- Card organization approval (1~2 weeks).
- Manufacturing sample cards (2~4 weeks).
- Mass production of cards (8~10 weeks).
- Create a physical card.
- Card shipment.
- Card activation.
- Ready for use (online and offline).
Scenario 2: Blank or Interlace-Branded Cards
If you don’t require customization and prefer blank or Interlace-branded cards:
- Create a physical card.
- Card shipment.
- Card activation.
- Ready for use (online and offline).
API Integration Workflow
💡 Important Notes:
• This workflow applies to Interlace Own HK Visa BIN.
• Applying for a physical card requires full KYC information, for both business and consumer use.
For Interlace Own HK Visa BIN Cards
Step 1: Create a Physical Card
- Use the corresponding Card API and set the
CardMode
field to "PHYSICAL_CARD". - Endpoints: Create Prepaid Card, Batch Create Prepaid Card, Create Budget Card, Batch Create Budget Card
*The card will be in a pending state until activated and cannot be used for any transactions (online or offline).
Step 2: Add Shipping Information
- Use the Bulk Ship API to add shipping details.
- For bulk shipments, include multiple
cardIds
. The maximum number of cards per shipment is 100.
Step 3: Activate the Physical Card
-
If KYC was completed earlier (Consumer Use):
- Use the Card Activation API to activate the card.
cardholderId
must be included in the request.
- Use the Card Activation API to activate the card.
-
If no prior KYC details were submitted (Business Use):
- First, complete KYC verification using the Identity Verification APIs:
- For Mainland Chinese nationals, use Confirm Cardholder Identity API.
- For non-Mainland Chinese nationals, use Generate Cardholder Identity URL API and follow the URL instructions for KYC.
- Once KYC verification is completed, use the Card Activation API to activate the card.
- First, complete KYC verification using the Identity Verification APIs:
Note:
- Each sub-account can create up to 5 physical cards and the total number of physical and virtual cards combined cannot exceed 20.
- The 20-card limit does not apply to MoR Mode (Business Use) and Gateway Mode.
Step 4: Set Card PIN
- Use the Update Physical Card PIN API to set a PIN for the physical card.
- The PIN will be required for ATM withdrawals and in-store transaction verification.
For Instant Issuing
What is Instant Issuing?
Instant issuing refers to the process where cards are issued without specific cardholder details during creation, and real cardholder information is collected and verified at the time of activation.
Supported BIN:
Currently, only the Interlace Own HK Visa BIN supports instant issuing, and it is available exclusively for MOR-mode clients.
Usage Recommendation:
- Instant issuing is ideal for early product launches or large-scale acquisition campaigns, such as marketing events.
- Not recommend for long-term physical card issuance due to operational complexities.
API Workflow for Instant Issuing – Consumer Use Programs
Step 1: Create Physical Cards
- For Consumer use projects, due to the mandatory cardholder KYC requirement, bulk card creation must be performed via the Dashboard (Merchant Portal).
- A single batch can create up to 100 cards at a time.
- During card creation, enter your company name or brand name as the cardholder name.
- Cards will remain in a pending state until activated and cannot be used for any transactions (online or offline).
Step 2: Add Shipping Information
- Use the Dashboard (Merchant Portal) to handle bulk shipping.
- Fill in the mailing addresses for shipments.
- For bulk shipments, you can include up to 100 cards per shipment.
Step 3: Link Physical Cards with Cardholder
This step requires building a custom UI to collect the full physical card number (PAN) from users. Optionally, you can also collect the CVV for additional security. The goal is to match the physical card to the corresponding cardId
in your system and link it to the cardholder’s account.
Why Is This Necessary?
- Transaction Requirements: The
cardId
is needed for recharges, withdrawals, and balance management. - Account Matching: It ensures the physical card is linked to the correct user account in your system.
Steps to Link Card Information
- Collect Card Details: Use your custom UI to securely collect the full card number (and optionally CVV) from your users.
- If PCI DSS LEVEL 1 Certification is Available:
- Use the Get Private Info API to retrieve the full card number (PAN) for each card ID in your system.
- Loop through the card IDs to find a match with the user-provided card number.
- If PCI DSS LEVEL 1 Certification is NOT Available:
- Contact your Relationship Manager to register on the whitelist.
- Use the card information export function to obtain the special encrypted field.
- Import the card ID and the special encrypted field into your backend system.
- Match the full card number to the corresponding card ID and complete the linking.
Notes:
- Avoid Storing Full Card Details: For security reasons, do not store the full card number or CVV. Only retain the
card id
for reference.
Step 4: Activate the Physical Card
-
If KYC was completed earlier:
- Use the Card Activation API to activate the card.
cardholderId
must be included in the request.
- Use the Card Activation API to activate the card.
-
If no prior KYC details were submitted:
- First, complete KYC verification using the Identity Verification APIs:
- For Mainland Chinese nationals, use Confirm Cardholder Identity API.
- For non-Mainland Chinese nationals, use Generate Cardholder Identity URL API and follow the URL instructions for KYC.
- Once KYC verification is completed, use the Card Activation API to activate the card.
- First, complete KYC verification using the Identity Verification APIs:
Updated 24 days ago