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.
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.
Get Dictionaries MCC
Status:
Production
Version:
V2
Category:
Card Control Services
Node | Child Node | Type | Length | Description |
---|---|---|---|---|
Authorization | Bearer xxxx | string | Authorization Header (Bearer Token) | |
Content-Type | application/json | string | Content Type |
Node Type | Type | Length | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
NISrvRequest | request_get_mcc_controls | header | msg_id | string | 12 | Message 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 | string | 12 | Message Type – This can have either “TRANSACTION” or “ENQUIRY” As for this API the value expected is “ENQUIRY” | |||||||
msg_function | string | 50 | Message functions: Should be “REQ_GET_MCC_CONTROLS” | |||||||
src_application | string | 10 | Source 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 | string | 10 | The 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 | string | 30 | Timestamp of the request - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00 | |||||||
bank_id | string | 4 | Bank 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” | |||||||
body | card_identifier_id | string | 32 | Card Identifer ID | ||||||
card_identifier_type | string | 20 | CONTRACT_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-Type | application/json | string | Content Type |
Node Type | Type | Length | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
dictionaries_mcc | group_name | string | 50 | MCC Group Name | ||||||
group_code | string | 50 | MCC Group Code | |||||||
mcc_list | code | string | 4 | MCC Code | ||||||
name | string | 255 | MCC Name |
{
"dictionaries_mcc": {
"group_name": "Entertainment",
"group_code": "ENTERTAINMENT",
"mcc_list": [
{
"code": "7996",
"name": "7996 Amusement Parks,circuses"
}
]
}
}
Code | Description |
---|---|
200 | Sample Description |
400 | Bad Request |
401 | Unauthorized |
403 | Forbidden |
500 | Internal Server Error |
502 | Bad gateway |
503 | Scheduled Maintenance |
504 | Gateway Timeout |
596 | Service Not Found |
How It Works
Follow the steps below. For more details, read the Quick Start Guide.
1- Process 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.
2- Process 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.
3- Process 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.
4- Process 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.
5- Process 1
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Amet, sed at amet cras fringilla adipiscing nunc, in pulvinar. Sagittis pellentesque leo et proin convallis justo vitae in.