Interlace
Guides

Card Issuance Integration for Gateway Mode (Business Use)

• This guide provides the card issuance integration process for Gateway mode (Business use) clients, outlining the key scenario, use case, and corresponding API workflow.
• The card issuance process will differ depending on the client's CaaS integration model (MoR or Gateway) and business model (Business use or 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

In this model, card issuance is facilitated through a Payment Service Provider (PSP), which supports downstream clients (sub-merchants).

Use Case Example

A PSP enables its sub-merchants to issue cards for internal business use, such as managing business expenses or corporate spending.

Workflow

1. Master-Merchant Account Registration

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

2. Sub-Merchant Account Registration

Once the master merchant account is approved, the master merchant can register sub-merchants at https://distributor.interlace.money.

  • The master merchant is responsible for adding downstream sub-merchants and completing KYC and KYB requirements on behalf of them.
  • Only after successful verification can sub-merchants proceed with cardholder and card creation.

3. Deposit Fiat/Crypto to 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.

3.1 Deposit Fiat to Sub-Merchant Infinity Account

If funding a Sub-Merchant Infinity Account with fiat, complete the transfer through your integrated merchant portal.

3.2 Deposit Crypto to Sub-Merchant Infinity Account

If funding a Sub-Merchant 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 Sub-Merchant 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.

  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 an address" API to generate a new one.

  3. Step 3 (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. You may choose to move balances at CryptoConnect Wallet layer (in stablecoins) to collect transaction fees.

  4. Step 4: Deposit crypto to Sub-Merchant Infinity Account
    After receiving the deposit webhook notification from Interlace, use the "Create a 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: Create a transfer (v1)
    • Body parameters: "source": "CRYPTO ASSETS" "destination": "INFINITY SUBACCOUNT"
    • For the type field, use the default value. For the id field, enter the sub-merchant account ID.

  5. Step 5 (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. You may choose to move balances at Infinity Account layer (in USD) to collect transaction fees.

    • Endpoint: Create a transfer (v1)
    • Body parameters: "source": "INFINITY SUBACCOUNT" "destination": "INFINITY ACCOUNT"

4. Create Cardholder

Cardholder creation is mandatory for all card issuance.

Notes:

  • Cardholder approval by the issuing bank is required before proceeding to card issuance.
  • 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.

5. Create Card

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

5.1 Create a Prepaid Card

Use the "Create Infinity Card" API to directly create a prepaid card.

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

5.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 Infinity Card" API.

  1. Step 1: Create a Budget

  2. Step 2: Create a Budget Card

    • Endpoint: Create Infinity Card (v2)
    • Body parameter: "type": "BudgetCard"
    • 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.

  • 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.

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.

Updated about 12 hours ago