B2B Program - MOR

Project Background

In this model, master merchants issue cards for internal organizational use. These cards are generally not distributed to external users.

Use Case Example

A large retail enterprise issues cards to employees to manage business expenses and corporate purchases.

Workflow

1. Master-Merchant Account Registration (Offline Process)
   The enterprise (master merchant) must be registered before any cardholder or card creation can take place. This step is completed offline.
2. Create Cardholder
   Use the Create Cardholder API.
   Body parameter: "programType": "B2B-MoR"

Notes:

• After the cardholder is created, approval from the issuing bank is required before issuing a card.
• OTP (One-Time Password) will be sent at the cardholder level.

3. Create Card
   Use the Create Infinity Card API.

Notes:

• Cards can be either virtual or physical. A virtual card cannot be upgraded to a physical card.
• This step can only be performed after the creation of the cardholder has been approved.

B2B Program - Gateway

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 (Offline Process)
   The PSP (master-merchant) must be onboarded offline.
2. Sub-Merchant Account Registration (Offline Process)
   Each downstream client (sub-merchant) must also complete offline registration.
3. Create Cardholder
   Use the Create Cardholder API.
   Body parameter: "programType": "B2B-Gateway"

Notes:

• Cardholder approval by the issuing bank is required before proceeding to card issuance.
• OTP will be sent at the cardholder level.

4. Create Card
   Use the Create Infinity Card API.

Notes:

• Cards can be either virtual or physical. A virtual card cannot be upgraded to a physical card.
• This step can only be performed after the creation of the cardholder has been approved.

B2C Program - MOR

Project Background

In this model, licensed digital wallets or similar businesses issue cards directly to their customers. The service provider operates as the Merchant of Record (MOR).

Use Case Example

• A licensed digital wallet issues prepaid cards to their customers for online and in-store purchases.

Workflow

1. Master-Merchant Account Registration (Offline Process)
   The enterprise (master-merchant) must be registered offline.
2. Create Cardholder
   Use the Create Cardholder API.
   Body parameter: "programType": "B2C-MOR"

Notes:

• Cardholder approval by the issuing bank is required before proceeding to card issuance.
• OTP will be sent at the cardholder level.

3. Create Card
   Use the Create Infinity Card API.

Notes:

• Cards can be either virtual or physical. A virtual card cannot be upgraded to a physical card.
• This step can only be performed after the creation of the cardholder has been approved.

B2C Program - Gateway

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 be registered offline.
2. End-Customer Account Registration
   1. To create an account:
      Use the Create Account API
   2. To submit KYC for the account:
      Use the Submit Account KYC API
   3. To initialize the account's settings:
      Use the Account Initialization API to enable crypto wallets and the Infinity account.
3. Create Cardholder
   Use the Create Cardholder API.
   Body parameter: "businessModel": "B2C-Gateway"

Notes:

• Cardholder approval by the issuing bank is required before proceeding to card issuance.
• OTP will be sent at the cardholder level.

4. Create Card
   Use the Create Infinity Card API.

Notes:

• Cards can be either virtual or physical. A virtual card cannot be upgraded to a physical card.
• This step can only be performed after the creation of the cardholder has been approved.

Physical Card Post-Issuance Workflow

The following steps apply to all business models after a physical card has been issued.

1. Physical Card Shipping
   Use the Bulk Ship Physical Cards API.

Notes:

• Currently, only single-card shipments are supported. Each shipment incurs a fee of $85 USD.
• Batch shipping (up to 100 cards per package) will be supported in future updates.

2. Physical Cardholder Identity Confirmation
   Cardholders must upload identification documents:

• Mainland China: National ID. Use the Confirm Cardholder Identity API.
• Other regions: Passport. Use the Generate Cardholder Identity URL.

This step will be optimized for Gateway clients in the future.

3. Card Activation (PIN Setup)
   Use the Set or Update PIN API.

Notes:

• This step is used to set or update the card's cash withdrawal PIN.

4. Logistics Information
   Logistics tracking for physical cards is not currently supported. This feature is under development by the issuing bank.

By following the appropriate workflow based on your project model, you can efficiently integrate US Apple Pay card BINs using Interlace APIs. For detailed implementation guidance, refer to the Interlace API Reference.