Card Issuance Integration for Gateway Mode (Consumer Use)

Before starting the integration, confirm your operating model: MoR (Merchant of Record) or Gateway Mode. Refer to the official documentation for guidance: Determine Your Integration Model.

Project Background

This model is designed for decentralized wallets or platforms that issue cards to their end users or customers without directly managing customer funds. The service provider uses Interlace's KYC and wallet custody services.

Use Case Example

A decentralized wallet platform issues cards to its users while Interlace handles KYC verification and wallet management.

Workflow

1. Master-Merchant Account Registration (Offline Process)

The decentralized wallet provider (master-merchant) must register at https://distributor.interlace.money and submit KYC and KYB information.

2. End-Customer Account Registration

2.1 Create an account

Use the "Register an Account" API to create an account.

• Endpoint: Register an Account

2.2 Submit KYC for the account

Submit the end-customer's KYC information for verification.

• Endpoint: Submit Account KYC
• Interlace Review: Interlace will handle the KYC review process.
• Note: Once KYC is approved, the end-customer's CryptoConnect wallets and Infinity account will be automatically created.

3. Deposit Fiat/Crypto to Infinity Account

All card-related fees will be deducted from the Infinity Account. Therefore, ensure your end-customer's Infinity Account is funded directly, either via fiat or cryptocurrency. Note that the Infinity Account only supports USD; any crypto deposits will be converted to USD before being credited.

3.1 Deposit Fiat to Infinity Account

If funding an end-customer's Infinity Account with fiat, complete the transfer through your integrated merchant portal.

3.2 Deposit Crypto to End-Customer's Infinity Account

If funding an end-customer's Infinity Account with cryptocurrency, you must first obtain wallet addresses. Deposited crypto (e.g., USDC or USDT) will be converted to USD before being credited to your end-customer's Infinity Account.

1. Step 1: Get a wallet address In Gateway Mode, once KYC is approved, a set of master wallets is provisioned by default. Use the "List all wallets" API to fetch wallet details, including balance and available addresses.

   • Endpoint: List all wallets

2. Step 2 (Optional): Generate an additional address If no address is available, or if you need an address on a different blockchain, use the "Create a blockchain address" API to generate a new one.

   • Endpoint: Create a blockchain address

3. Step 3 (Optional): Transfer between CryptoConnect Wallets Move stablecoins from an End-Customer’s Wallet to the Master Merchant Wallet. This step is optional and provides flexibility in how funds are managed. You may choose to move balances at CryptoConnect Wallet layer (in stablecoins) to collect transaction fees.

   • Endpoint: Cross-account business transfer
   • Body parameters: "from" - "businessType": "2" "to" - "businessType": "2"

4. Step 4: Deposit crypto to End-Customer's Infinity Account After receiving the deposit webhook notification from Interlace, use the "Intra-account business transfer" API to move USDC or USDT from an End-Customer's Wallet to the End-Customer's Infinity Account. The system will convert the crypto to USD before the funds are credited.

   • Endpoint: Intra-account business transfer
   • Body parameters: "from" - "businessType": "2" "to" - "businessType": "0"
   • For the id field, enter the end-customer's account ID.

5. Step 5 (Optional): Transfer between Infinity Accounts Move funds from the End-Customer's Infinity Account to the Master Merchant Infinity Account. This step is optional as well. You may choose to move balances at Infinity Account layer (in USD) to collect transaction fees.

   • Endpoint: Cross-account business transfer
   • Body parameters: "from" - "businessType": "0" "to" - "businessType": "0"

4. Get Available Card BINs

Before issuing cards, you must call the "Get Card BINs" API. This API returns all available card BIN information under your Master Merchant account, including the binId field.

• Endpoint: List all available card BINs

5. Create Cardholder

Cardholder creation is mandatory for all card issuance.

• Endpoint: Create a cardholder
• Body parameter: "programType": "CONSUMER USE - GATEWAY"

Notes:

• binId of the card BIN you intend to use must be included in the request body. Regardless of which binId is specified, upon successful creation, the response will return all available BIN IDs for the cardholder under that card BIN.
• After the cardholder is created, approval from the issuing bank is required before issuing a card.
• To stay informed about cardholder status updates, please subscribe to our webhook. This will ensure you receive real-time notifications whenever a status change occurs.
• OTP (One-Time Password) will be sent to the cardholder for identity verification during sensitive operations such as card activation or transaction authorization.

6. Create Card

First, decide which type of card you want to issue: prepaid card or budget card.

6.1 Create a Prepaid Card

Use the "Create Prepaid Card" API to create a single prepaid card, or use the "Batch Create Prepaid Card" API to create multiple prepaid cards in bulk.

• Endpoint: Create Prepaid Card, Batch Create Prepaid Card

Balance Management: The balance of a prepaid card is controlled by transferring funds between the Infinity Account and the card.

• Transfer funds into the card: Prepaid Card Transfer In API
• Transfer funds out of the card: Prepaid Card Transfer Out API

6.2 Create a Budget Card

To create a budget card, you must first set up a budget using the "Budget" API, and then create cards under that budget with the "Create Budget Card" API or "Batch Create Budget Card" API.

1. Step 1: Create a Budget

   • Endpoint: Create a budget

2. Step 2: Create a Budget Card Use the "Create Budget Card" API to create a single budget card, or use the "Batch Create Budget Card" API to create multiple budget cards in bulk.

   • Endpoint: Create Budget Card, Batch Create Budget Card
   • Required: Include the budgetId in the request body when creating a budget card.

Balance & Spending Control:

• The balance of a budget is managed through transfers between the Infinity Account and the budget.

  • Increase the budget balance API – to allocate funds from the Infinity Account to the budget.
  • Decrease the budget balance API – to return funds from the budget back to the Infinity Account.

• A budget card itself does not hold funds. Its available spending is strictly tied to the budget balance and governed by the velocity control (spending limits) configured for that budget.

  • Endpoint: Velocity Control

Notes:

• Virtual and physical cards must be created separately. Once issued as a virtual card, it cannot be converted into a physical card. For details on physical card issuance, see Issuing Physical Cards.
• This step can only be performed after the cardholder creation has been approved.