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:

  1. Design the card front and back.
  2. Issuing bank approval (~1 business day).
  3. Card organization approval (1~2 weeks).
  4. Manufacturing sample cards (2~4 weeks).
  5. Mass production of cards (8~10 weeks).
  6. Create a physical card.
  7. Card shipment.
  8. Card activation.
  9. 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:

  1. Create a physical card.
  2. Card shipment.
  3. Card activation.
  4. Ready for use (online and offline).

API Integration Workflow

🔔 Important Notes:
• This workflow applies to US Apple Pay BIN and our Own HK Visa BIN.
• For HK Apple Pay BIN, the process varies. Please contact your tech support team for assistance.

For US Apple Pay BIN Cards

Step 1: Create a Physical Card

  • Use the Card API and set the cardMode field to "Physical Card".

*The card will remain in a pending state and cannot be used for any online or offline transactions until activated.


Step 2: Create a Bulk Shipping Group


Step 3: Add Shipping Information

  • Use the Bulk Ship API to add the shipping address and other required details.
  • Include the bulkShippingGroupId from Step 2.

*Orders must be submitted before 12 PM UTC to be processed on the same day. Orders placed after this time will be included in the next day’s batch.


Step 4: Activate the Physical Card

*This API will be upgraded on May 29th, and new client integrations are not supported until the update is complete.

For activation, follow these guidelines:

  • Gateway Mode: If cardholder KYC was completed during account creation, activate the card using the account id.
  • B2C Mode: If KYC was completed when creating the cardholder, activate the card using the cardholder id.
  • MOR with B2B Mode: If KYC was not submitted earlier, KYC verification must be completed during activation.

KYC Steps:

Note: Each sub-account may create up to 5 physical cards. There is no limit on virtual card issuance.


Once KYC is completed, the card will be activated and ready for online and offline transactions.


For HK Own Visa BIN Cards

Step 1: Create a Physical Card

  • Use the Card API and set the CardMode field to "Physical 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 card ids. The maximum number of cards per shipment is 100.

Step 3: Activate the Physical Card

  • Use the Card Activation API.
  • This API will be upgraded on May 29th, and new client integrations are not supported until the update is complete.

For activation, follow these guidelines:

  • Gateway Mode: Activate the card using the account id if KYC was completed earlier.
  • B2C Mode: Activate the card using the cardholder id if KYC was completed during cardholder creation.
  • MOR with B2B Mode: Complete KYC verification during activation if no prior KYC details were submitted.

KYC Steps:

Note: Each sub-account can create up to 5 physical cards. There’s no limit for virtual cards.


Once KYC is completed, the card will be activated and ready for use.


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 HK Own Visa BIN supports instant issuing, and it is available only for MOR-mode clients.

Usage Recommendation:

  • Instant issuing is ideal for early product launches or large-scale acquisition campaigns, such as marketing events.
  • We do not recommend using this model for long-term physical card issuance.

API Workflow for Instant Issuing

Step 1: Create a Physical Card

  • Use the Card API and set the CardMode field to "Physical Card".
  • When creating the card, enter your company name or brand name as the cardholder name.

*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 provide the mailing address.
  • For bulk shipments, include multiple card ids (maximum 100 cards per shipment).

Step 3: Link Physical Card 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 card id in your system and link it to the cardholder’s account.


Why Is This Necessary?

  • Transaction Requirements: The card id 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

  1. Collect Card Details:
    Use your custom UI to securely collect the full card number (and optionally CVV) from your users.
  2. Find the Matching card id:
    Use the [Get Private Info API] to retrieve the full card number for each card id in your system. Loop through the card ids to find a match with the user-provided card number.
  3. Complete the Link:
    Once a match is found, associate the card id with the cardholder’s account to enable transactions.

Important 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.
  • CVV Validation (Optional): Validate the CVV to enhance security and ensure accurate linking.

Step 4: Activate the Physical Card

Once KYC is completed, the card will be activated and ready for online and offline use.