This guide describes the card issuance workflow for clients operating in Gateway mode under Business Use. It outlines the typical business context, applicable cardholder tiers, and the API sequence required to issue cards.
The exact workflow depends on both the integration mode and the intended card usage type. If your integration configuration has not yet been finalized, refer to CaaS Integration Overview for guidance.

Project Background

In this mode, card issuance is facilitated through a Payment Service Provider (PSP), which supports downstream clients (sub-merchants). Cards issued under this mode are used for business-related scenarios by downstream business entities.

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 master merchant must complete account registration and onboarding before any cardholder or card creation can take place. For detailed onboarding steps, refer to Quick Start.

2. Sub-Merchant (Business) Set-up

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. Fund the Infinity Account

All card-related fees and funding operations are processed through the Infinity Account. Ensure the account is sufficiently funded before initiating card issuance. Funding methods including fiat transfer and cryptocurrency transfer. Note that the Infinity Account operates in USD; any cryptocurrency deposits will be converted to USD before being credited to the account.

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 get the wallet addresses. Deposited crypto (e.g., USDC or USDT) will be converted to USD before being credited to the Sub-Merchant Infinity Account.

Step 1: Get Wallet Addresses

See Gateway mode workflow in Generate a Wallet Address for guidance.
Step 2: Deposit Crypto to Infinity Account

See Gateway mode workflow in Deposit Crypto to Infinity Account for guidance.

4. Get Available Card BINs

Before issuing cards, retrieve the list of available card BINs under your account. This step ensures that a valid binId is used when creating cardholders and cards.

Endpoint: List all available card BINs

5. Create a Cardholder

Select the appropriate cardholder tier based on the intended usage scenario. Supported tiers for Gateway - Business Use mode: CORPORATE_MANAGED and NAMED_INDIVIDUAL.

Endpoint: Create a cardholder
Important:
- Choose CORPORATE_MANAGED when the card is issued for business-level use, such as advertising spend, SaaS subscriptions, travel expenses, procurement, or logistics operations.
- Choose NAMED_INDIVIDUAL when the card is assigned to a specific individual, such as an employee, contractor, or other identified person within a business context. NAMED_INDIVIDUAL tier cardholders are required to complete full KYC verification.

Notes:

binIdof the card BIN you intend to use must be included in the request body. Upon successful creation, the response will return all available BIN IDs associated with the cardholder under that card BIN.

After the cardholder is created, approval from the issuing bank is required before card issuance can proceed.

To receive real-time updates on cardholder status changes, subscribe to the webhook notification service.

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

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

6.2 Create a Budget Card

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

Step 1: Create a Budget
- Endpoint: Create a budget
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.