Card Control Services

Overview

Our card control services allow you to manage your customers' cards with ease, providing an extra layer of security and flexibility. You can set custom limits on transactions for each card, such as daily or weekly limits, and even limit transactions to specific merchant categories or locations.

In the event of a lost or stolen card, our platform allows you to quickly block the card to prevent fraudulent transactions. You can also unblock the card when it's found or issue a replacement card directly through the platform.

With our real-time transaction monitoring, you can track your customers' card usage and receive instant alerts for suspicious or unauthorized transactions. This allows you to take immediate action to prevent fraud and protect your customers' accounts.

Version

Get Dictionaries MCC

Status:

Production

Version:

V2

Category:

Card Control Services

Overview

The Get Dictionaries MCC API is designed to retrieve all available MCC Groups associated with a particular Financial Institution (FI). Users have the option to access related MCC codes within these groups. MCC codes categorize merchants based on the types of goods or services they provide, and they can be organized into groups. This service allows for the retrieval of MCC data tailored to specific FIs, facilitating efficient grouping and management of merchant categories.

How It Works

The API requires the user to specify a particular FI. Once the FI is identified, the API retrieves all the available MCC Groups associated with that specific FI. Within each MCC Group, users have the option to access the individual MCC codes.

The Get Dictionaries MCC API is designed to retrieve all available MCC Groups associated with a particular Financial Institution (FI). Users have the option to access related MCC codes within these groups. MCC codes categorize merchants based on the types of goods or services they provide, and they can be organized into groups. This service allows for the retrieval of MCC data tailored to specific FIs, facilitating efficient grouping and management of merchant categories.

How It Works

 

The API requires the user to specify a particular FI. Once the FI is identified, the API retrieves all the available MCC Groups associated with that specific FI. Within each MCC Group, users have the option to access the individual MCC codes.

/dictionaries/mcc

Get Dictionaries MCC

Status:

Production

Version:

V2

Category:

Card Control Services
/dictionaries/mcc
curl --location --request POST '#{PARAM_URL}' --header 'Authorization: Bearer {{ access_token }}' {custom_headers} --data-raw '#{JSON_PAYLOAD}'
curl --location --request GET 'https://api-sandbox.network.global/v1/tokenkc/generate' \--data-raw '#{JSON_PAYLOAD}'
curl --location --request POST 'https://api-sandbox.network.global/v1/tokenkc/generate' \--data-raw '#{JSON_PAYLOAD}'

Node Child Node Type Length Description
Authorization* requiredBearer xxxx* requiredstringAuthorization Header (Bearer Token)
Content-Type* requiredapplication/json* requiredstringContent Type

Node TypeTypeLengthDescription
NISrvRequestrequest_get_mcc_controlsheadermsg_id* requiredstring12Message ID, this field should be unique id for each Api call. This will be generated from client side. If the same message ID is used the system will decline the API call with Error Description “Duplicate Message ID”
msg_type* requiredstring12Message Type – This can have either “TRANSACTION” or “ENQUIRY” As for this API the value expected is “ENQUIRY”
msg_function* requiredstring50Message functions: Should be “REQ_GET_MCC_CONTROLS”
src_application* requiredstring10Source Application: This is a free Text and the client can populate the source system from where the API is Initiated Example: IVR, IB, MB No Validations of these are kept at Network Systems
target_application* requiredstring10The target_application can hold any value from FI side, this can be used by FI to check the target system of the API call
timestamp* requiredstring30Timestamp of the request - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00
bank_id* requiredstring4Bank Id is Unique Id 4 digit code for each client and the same will be provided once the client setup is completed in our core system. For sandbox testing – Please use “NIC”
bodycard_identifier_id* requiredstring32Card Identifer ID
card_identifier_type* requiredstring20CONTRACT_NUMBER is used for clear card number or EXID which is a unique identifier for the card generated by CMS

Node Child Node Type Length Description
Content-Typeapplication/jsonstringContent Type

Node TypeTypeLengthDescription
dictionaries_mccgroup_namestring50MCC Group Name
group_codestring50MCC Group Code
mcc_listcode* requiredstring4MCC Code
name* requiredstring255MCC Name

{
    "dictionaries_mcc": {
        "group_name": "Entertainment",
        "group_code": "ENTERTAINMENT",
        "mcc_list": [
            {
                "code": "7996",
                "name": "7996 Amusement Parks,circuses"
            }
        ]
    }
}

Code Description
200Sample Description
400Bad Request
401Unauthorized
403Forbidden
500Internal Server Error
502Bad gateway
503Scheduled Maintenance
504Gateway Timeout
596Service Not Found

How It Works

Follow the steps below. For more details, read the Quick Start Guide.