Card Control Services

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 Limits(Post)

This API allows customers to easily view a summary of their limit usage, providing a convenient way to keep track of their spending and manage their finances.

Status :Production
Version : V2
Try Out   
Switch Restrictions(Post)

This API allows customers to seamlessly switch restrictions on their credit or debit cards, helping them to make decisions about their spending.

Status :Production
Version : V2
Try Out   
Update Limits(Post)

This API enables customers to quickly and easily view any limits on their credit or debit cards, helping them to make informed decisions about their spending.

Status :Production
Version : V2
Try Out   
Get Companies(Post)

This API enables customers to Get the details of the companies

Status :Production
Version : V2
Try Out   
Get Restrictions(Post)

This API enables customers to quickly and easily view any restrictions on their credit or debit cards, helping them to make informed decisions about their spending.

Status :Production
Version : V2
Try Out   
Switch MCC(Post)

This API enables or disables MCC groups/codes for a card.

Status :Production
Version : V2
Try Out   
Release Pending Authorization(Post)

This API cancels pending authorizations. It will only search for pending authorizations.

Status :Production
Version : V2
Try Out   
Get MCC Controls(Post)

This API retrieves all blocked and/or allowed MCC groups and codes.

Status :Production
Version : V2
Try Out   
Get Dictionaries MCC(Post)

This API retrieves all blocked and/or allowed MCC groups and codes.

Status :Production
Version : V2
Try Out   

Get MCC Controls

Status:

Production

Version:

V2

Category:

Card Control Services

Overview

The Get MCC Controls API is a service used to retrieve information about blocked or allowed Merchant Category Code (MCC) groups and codes within a system. This API provides a convenient method to access and query the status of MCC groups and codes, enabling users to ascertain which categories are permitted or restricted for transactions. By utilizing this service, businesses can effectively manage and monitor MCC controls to ensure compliance and optimize payment processing workflows.

How It Works

The Get MCC Controls API functions by allowing users to retrieve information regarding blocked or allowed Merchant Category Code (MCC) groups and codes stored within a system. Users interact with this API by sending requests to access the current status of MCC categories, enabling them to determine which categories are either permitted or restricted for transactions. This API provides a straightforward method for users to query and analyze MCC controls, which are crucial for ensuring compliance with payment regulations and optimizing payment processing workflows.

The Get MCC Controls API is a service used to retrieve information about blocked or allowed Merchant Category Code (MCC) groups and codes within a system. This API provides a convenient method to access and query the status of MCC groups and codes, enabling users to ascertain which categories are permitted or restricted for transactions. By utilizing this service, businesses can effectively manage and monitor MCC controls to ensure compliance and optimize payment processing workflows.

 

 

How It Works

The Get MCC Controls API functions by allowing users to retrieve information regarding blocked or allowed Merchant Category Code (MCC) groups and codes stored within a system. Users interact with this API by sending requests to access the current status of MCC categories, enabling them to determine which categories are either permitted or restricted for transactions. This API provides a straightforward method for users to query and analyze MCC controls, which are crucial for ensuring compliance with payment regulations and optimizing payment processing workflows.

https://api-sandbox.network.global

Get MCC Controls

Status:

Production

Version:

V2

Category:

Card Control Services
/CardControl/Enquiry/V2/GetMCCControls
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

{
    "NISrvRequest": {
        "request_get_mcc_controls": {
            "header": {
                "msg_id": "236001",
                "msg_type": "ENQUIRY",
                "msg_function": "REQ_GET_MCC_CONTROLS",
                "src_application": "BNK",
                "target_application": "WAY4",
                "timestamp": "2020-07-20T10:49:02.366+04:00",
                "bank_id": "NIC"
            },
            "body": {
                "card_identifier_id": "99984104111610175918",
                "card_identifier_type": "EXID"
            }
        }
    }
}

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

Node TypeTypeLengthDescription
NISrvResponseresponse_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 “REP_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 response - 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”
exception_detailsapplication_name* requiredstring20Application Name
date_time* requiredstring30Timestamp of the response Format “YYYY-MM-DD HH:MM:SS”
status* requiredstring1Status of the request (S/F)
error_code* requiredstring4EAI Internal Error Code (Check error codes section for the complete list of error codes and error code descriptions)
error_description* requiredstring100Error Description (Check error codes section for the complete list of error codes and error code descriptions)
transaction_ref_idstring20The tracking_id sent in the request will be sent back in response in this field.
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
mcc_allowed_group_listcodestring30By specifying this array of codes, only the designated MCC groups will be permitted, while all others will be restricted
mcc_blocked_group_listcodestring30By specifying this array of codes, only the designated MCC groups will be restricted, while all others will be permitted
mcc_allowed_code_listcodestring30By specifying this array of codes, only the designated MCC codes will be permitted, while all others will be restricted
mcc_block_code_listcodestring30By specifying this array of codes, only the designated MCC codes will be restricted, while all others will be permitted

{
    "NISrvResponse": {
        "response_get_mcc_controls": {
            "header": {
                "msg_id": "236001",
                "msg_type": "ENQUIRY",
                "msg_function": "REP_GET_MCC_CONTROLS",
                "src_application": "IVR",
                "target_application": "WAY4",
                "timestamp": "2020-07-20T10:49:02.366+04:00",
                "bank_id": "NIC"
            },
            "exception_details": {
                "application_name": "TCC-ADP",
                "date_time": "2023-02-01T16:39:47.314+04:00",
                "status": "S",
                "error_code": "000",
                "error_description": "Success",
                "transaction_ref_id": "236001"
            },
            "body": {
                "card_identifier_id": "99984104111610175918",
                "card_identifier_type": "EXID",
                "mcc_allowed_group_list": [
                    {
                        "code": ""
                    }
                ],
                "mcc_blocked_group_list": [
                    {
                        "code": ""
                    }
                ],
                "mcc_allowed_code_list": [
                    {
                        "code": ""
                    }
                ],
                "mcc_block_code_list": [
                    {
                        "code": ""
                    }
                ]
            }
        }
    }
}

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.

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.