Guides
API Reference

6 - Multi-Benefits

Suggest Edits

Fitbank Multi-Benefits Card API

Overview

The Fitbank Multi-benefits Card API is a comprehensive solution for managing corporate benefits, allowing the configuration of multiple balances on a single prepaid card. The card is internationally flagged by MasterCard and must be used in debit mode. Features include the ability to make contactless payments, ATM withdrawals, and manage different types of benefits.

Key Features

  • Nominal Card Issuance: Directly associated with the employee, with the cardholder's data linked during the request.
  • Non-Nominal Card Issuance: Issued in batches, ideal for mass distribution, without initially linking the cardholder’s data.
  • Multi-benefit Management: Offers different balances for categories such as:
    • Food;
    • Meal;
    • Mobility;
    • Home Office;
    • Entertainment;
    • Education;
    • Pharmacy.

We also provide a flexible balance, which can be used freely in any type of establishment, without specific restrictions on categories like food or transportation. Unlike other benefits with strict usage rules, the flexible balance allows employees to use the funds for a wide variety of purchases, transfers, or even withdrawals, providing more freedom to manage resources according to personal and immediate needs.

Acceptance: The card is accepted at thousands of establishments using the MasterCard (debit) network, making it easy to use across different benefit categories.

Management Features

The product allows the configuration of rules per card, recharges, transfers between balances, as well as real-time control and reporting. Through API integration, companies can manage and automate the allocation of benefits according to internal policies.

Configuration of Card Rules

Overview

In the Multi-benefits Card solution, the configuration of rules per card is essential for controlling where and how the balances available in each wallet can be used.A card can have various rules., and each rule corresponds to a category of MCCs (Merchant Category Codes) enabled for use.

These rules are crucial to ensure that the benefits are used appropriately, respecting the company’s policies and the restrictions of the granted benefit (e.g., food, transportation, health).

How the Rule Configuration Works

  1. Definition of MCC Categories (Merchant Category Codes):
    • Each purchase rule linked to the card defines a specific list of MCCs. MCCs are codes that identify the category of a merchant, such as supermarkets, restaurants, pharmacies, etc.
    • MCCs are used to ensure that funds from a specific wallet can only be spent at merchants compatible with the corresponding purchase rule. For example, a "Food" rule may allow usage only in supermarkets or food establishments.
  2. Limit of Rules per Card:

The rule configuration per card can vary depending on the definition of the business unit (BU). There are two possibilities for setting the limits on rules linked to a card:

  • With configured limit: If the BU has the limit parameter enabled, the system allows between 1 and 5 rules to be linked per card.
  • Without configured limit: If the BU does not have the limit parameter enabled, there is no restriction on the number of rules that can be linked to the card, allowing greater flexibility in the use of multiple benefits.

Regardless of the limit, the card can only be used in accordance with the rules linked to it, and transactions will be permitted based on the available balance in each associated benefit category. This ensures that each benefit is used in a controlled manner, adhering to the rules defined by the company.

  1. Usage Control:
    • Each transaction is checked against the merchant’s MCC. If the merchant falls within one of the rules configured for the card, the transaction is approved.
    • Otherwise, the transaction is denied, even if there is an available balance, as the usage does not align with the permitted category.
  2. Integration of Balance and Rules:
    • Each rule linked to the card corresponds to a specific balance within the multi-benefits wallet. The available balance in each wallet is managed separately.
    • For example, the "Transportation" rule will have its own balance, which cannot be used for "Food," and vice versa.
  3. Configuration Flexibility:
    • Through the API, companies can link rules according to their internal policies and determine which MCC categories should be allowed for each granted benefit
    • The rule configuration can be done during the card creation or changed later if the company wants to modify the types of allowed usage.

Example of Rule Configuration
Let’s consider an example of an employee receiving a Multi-benefits card with three main categories:

  • Meal (For example, MCC 5812 - Restaurants): The balance of this rule can only be used in restaurants, cafes, and similar establishments.
  • Transportation (For example, MCC 4111 - Transportation services): The balance of this rule can only be used with transportation services, such as taxis, buses, or ride-sharing.
  • Pharmacy (For example, MCC 5912 - Pharmacies): The balance of this rule can only be used at pharmacies and drugstores.

Example of Rule Linking Request:

  {  
  "Method": "CreateCardPurchaseRule",  
  "PartnerId": 30326,  
  "BusinessUnitId": 30326,  
  "IdentifierCard": 800015485,  
  "PurchaseRuleId": 1208  
}

In this case, rule 1208 may refer to the Meal category with MCCs such as 5812 (restaurants).

Example of Transaction Verification:

When the employee attempts to make a purchase at a restaurant with MCC 5812, the system checks:

  • Does the card have a rule linked that allows transactions with MCC 5812?
  • Is there an available balance in the meal category?

If both answers are "Yes," the transaction is approved. Otherwise, it will be denied.

Updated about 1 month ago