Key Terms

Distributor

The primary business entity integrating with Interlace’s API to facilitate card issuance for their downstream clients.

Master Merchant

Master merchants are the distributor’s business clients. They are typically companies or corporate entities and they use the distributor’s API to issue cards to their own customers.

1. Account Setup

• Each master merchant will be provisioned with:
  • A CryptoConnect Wallet for managing on-chain deposits (crypto transactions).
  • An Infinity Account for managing and settling fiat funds.

2. Access and Interaction

• Master merchants do not typically have direct access to Interlace’s dashboard.
• Instead, they operate through the distributor, which manages their integration, credentials, and related services on their behalf.

Sub-Merchant and Cardholder

• Sub-Merchant (Gateway Mode):

  • Onboarded by master merchants as downstream clients.
  • Can be businesses or individuals.
  • Each sub-merchant is provisioned with:
    • CryptoConnect Wallet: For receiving crypto-based deposits.
    • Infinity Account: For managing fiat funds converted or transferred from the CryptoConnect Wallet.

• Cardholder (MoR Mode):

  • End customers of the Master Merchant.
  • Typically individuals or authorized users of businesses.

---

Account Structure

Below is an overview of how accounts are structured within the Interlace ecosystem:

---

Fund Flow Management

1. Sub-Merchant to Own Infinity Account

   • Sub-merchants (e.g. Sub-Merchant A1) can transfer funds from their CryptoConnect Wallet to their own Infinity Account using the "Intra-account business transfer" API. The system will convert the crypto to USD before the funds are credited.
     • Example Use Case: A sub-merchant converts crypto-based funds to fiat for business operations or settlements.
     • Endpoint: Intra-account business transfer
     • Body parameters: "from" - "businessType": "2" "to"- "businessType": "0"
     • For the id field, enter the sub-merchant account ID.

2. Sub-Merchant to Master Merchant

   • Master merchants (e.g. Master Merchant A) can pull funds from a Sub-Merchant's Infinity Account (e.g., Sub-Merchant A1) into their Master Merchant’s Infinity Account using the "Different-account business transfer" API.
     • Example Use Case: A master merchant consolidates funds from its sub-merchants for centralized treasury management or settlements.
     • Endpoint: Different-account business transfer
     • Body parameters: "from" - "businessType": "0" "to"- "businessType": "0"

3. Master Merchant to Sub-Merchant

   • Master merchants (e.g. Master Merchant A) can transfer funds from their Infinity Account to any other sub-merchant’s Infinity Account (e.g. Sub-Merchant B1) using the "Cross-account business transfer" API.
     • Example Use Case: A master merchant redistributes funds to its sub-merchants for payouts, funding, or operational needs.
     • Endpoint: Cross-account business transfer
     • Body parameters: "from" - "businessType": "0" "to"- "businessType": "0"

---

API Workflow

This section outlines the integration process of Interlace's API, to cover the roles of distributors, master merchants, and sub-merchants/end customers.

Distributor Setup

1. Registration and KYC Verification

   • Distributors must register at https://distributor.interlace.money and submit KYC information.
   • Once KYC is approved, please contact your relationship manager to enable access.

2. Facilitate Master Merchant Registration

   • Distributors should add their master merchants in the portal and help them finish their KYC and KYB information.

3. Request Production Credentials

   • Once KYC is approved, distributors can request production environment credentials by contacting Interlace’s Technical Support Team.

4. Configure Webhooks

   • Configure the necessary settings, such as webhook URLs.
   
   

---

Master Merchant Setup

1. Registration and KYB Verification

   • Distributors assist master merchants to register through the portal and are responsible for submitting KYC/KYB information on their behalf via Interlace’s platform.

2. Access Assignment

   • Once KYC is approved, distributors grant master merchants the necessary access.

3. Generate Blockchain Wallet Address (MoR Mode Only)

   • Step 1: Create a new wallet

     Use the "Create a wallet" API to create a new wallet.

     • Endpoint: Create a wallet
     • You may assign a nickname to the wallet.

   • Step 2: Get a wallet address

     Use the "Get a wallet" API to fetch wallet details, including balance and available address.

     • Endpoint: Get a wallet
     • Note: walletId must be included in the request.

   • Step 3 (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

4. Fund Master-Merchant Infinity Account (MoR Mode Only)

   All card-related fees will be deducted from the Infinity Account. Therefore, ensure your Master-Merchant Infinity Accounts are 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.

• 4.1 Deposit Fiat to Infinity Account

  • If funding Master-Merchant Infinity Account with fiat, complete the transfer through master merchant's integrated portal.

• 4.2 Deposit Crypto to Infinity Account

  • If funding Master-Merchant Infinity Account with cryptocurrency, use the "Intra-account business transfer" API to transfer funds. 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"

---

Sub-Merchant Setup (Gateway Mode Only)

1. Create Sub-Merchant Account

   Use the "Register an Account" API to register sub-merchants under the master merchant.

   • Endpoint: Register an Account
   • parentAccountId must be included in the request to specify the associated account ID.

2. Submit Sub-Merchant KYC

   KYC information for sub-merchants must be submitted for verification via the "Submit Account KYC" API.

   • Endpoint: Submit Account KYC
   • The master merchant will review and approve the KYC submission.
   • Note: Once KYC is approved, the sub-merchant's CryptoConnect wallets and Infinity account will be automatically created.

3. Generate Blockchain Wallet Address

   • 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

   • 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

4. Fund Sub-Merchant Infinity Account

   All card-related fees will be deducted from the Infinity Account. Therefore, ensure your Sub-Merchant Infinity Accounts are 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.

   4.1 Deposit Fiat to Sub-Merchant Infinity Account

   • If funding a Sub-Merchant Infinity Account with fiat, complete the transfer through master merchant's integrated portal.

   4.2 Deposit Crypto to Sub-Merchant Infinity Account

   • If funding a Sub-Merchant Infinity Account with cryptocurrency, use the "Transfer" API to transfer funds from the Sub-Merchant CryptoConnect Wallet to the Sub-Merchant Infinity Account. The system will convert the crypto to USD before the funds are credited.

   1. Step 1 (Optional): Transfer between CryptoConnect Wallets

      Move stablecoins from a Sub-Merchant Wallet to the Master Merchant Wallet. This step is optional and provides flexibility in how funds are managed. The master merchant 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"

   2. Step 2: Deposit crypto to Sub-Merchant Infinity Account

      After receiving the deposit webhook notification, use the "Intra-account business transfer" API to move USDC or USDT from a Sub-Merchant Wallet to the Sub-Merchant 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 sub-merchant account ID.

   3. Step 3 (Optional): Transfer between Infinity Accounts

      Move funds from the Sub-Merchant Infinity Account to the Master Merchant Infinity Account. This step is optional as well. The master merchant 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"

---

Card Issuance Process

1. Create KYB Profile (MOR-Business Use Only)
   This step applies to all MoR - Business Use cardholders, including the CORPORATE_MANAGED and NAMED_INDIVIDUAL tiers.

   • Endpoint: Submit account KYB
   • Output: profileId and the review status
   • Requirements:
     • For CORPORATE_MANAGED (cards issued to another business entity), submit the KYB information of the corresponding business entity.
     • For NAMED_INDIVIDUAL (cards used by the MoR entity itself), submit the KYB information of the MoR entity.
     • The referenced profileId must be in PASSED status before proceeding to cardholder creation.
     • Each registrationNumber may only be used once per client. Duplicate submissions will be rejected.
     
     

2. Get Available Card BINs
   Before issuing cards, retrieve the list of available card BINs under the Master Merchant account. This step ensures that a valid binId is used when creating cardholders and cards.

   • Endpoint: List all available card BINs
   
   

3. Create a Cardholder
   Select the appropriate cardholder tier based on the intended usage scenario. Refer to the CaaS Integration Overview to understand the differences and applicable use cases for each cardholder tier.

   • Endpoint: Create a cardholder
   
   

4. Create Cards
   Choose the type of card you want to create: prepaid card or budget card. Please note that 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.

   4.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: Use the Prepaid Card Transfer In API.
     • Transfer funds out of the card: Use the Prepaid Card Transfer Out API.
     
     

   4.2 Create a Budget Card

   To create a budget card, you must first set up a budget, and then create cards under that budget.

   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 Management

   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.
   
   

   Spending Control

   A budget card does not hold funds directly. Instead, all cards under the same budget share a common balance. Spending behavior for each card is controlled through velocity control, which supports configuration of per-transaction limits, periodic limits, and lifetime limits. If the shared budget balance is exhausted, all associated cards will be unable to make further transactions.

   For detailed usage scenarios and limit calculation rules, refer to the Velocity Control Usage Guide.

---

Support and Assistance

For any questions or technical issues during the integration process:

• Contact your Interlace Relationship Manager for business-related support.
• Reach out to the Interlace Technical Support Team for integration and development queries.