Card Services

Overview

Our card services support multiple card types, including Visa, MasterCard, American Express, and Discover, as well as other popular payment methods like Apple Pay and Google Pay. You can also set up recurring payments for your customers, making it easy for them to make regular payments without having to enter their card information every time.Our advanced fraud detection and prevention features use machine learning algorithms to help identify and prevent fraudulent transactions. We also provide detailed reporting and analytics, allowing you to track and analyze payment data and make data-driven decisions.

We also offer multi-currency support, which allows you to accept payments from customers in different parts of the world. And with our 24/7 customer support, you can always count on us to help you resolve any issues related to our card services.Our card services are also fully compliant with all local and international regulations, such as PCI DSS, so you can be confident that you're accepting payments in a secure and compliant manner.

Version

Card Activate

Status:

Production

Version:

V2

Category:

Card Services

Card Activation

Overview

This API enables the activation of cards, allowing them to be used for transactions. New or replaced/renewed cards are initially locked by the system, preventing any transactions from being made with them. Through this API, cardholders can activate their cards, making them fully functional for both online and physical Point of Sale transactions. The API handles all necessary internal processes to activate the card.

How It Works

The Card Activation API is designed to activate a locked card, allowing it to be used for transactions. When a card is first created, its plastic is marked as "Locked" which means that no transactions can be made with it. To use the card, it must first be activated through this API.

To check if a card needs to be activated, the consumer of this API can use the "List of Cards" or "Card Details" API to check the "PLASTIC" status of the card. If the status is "L" (locked), the card can be activated using this API. If the status is "A" (active), then the card has already been activated and does not need to be activated again.

To check if a card needs to be activated, the consumer of this API can use the "List of Cards" or "Card Details" API to check the "PLASTIC" status of the card. If the status is "L" (locked), the card can be activated using this API. If the status is "A" (active), then the card has already been activated and does not need to be activated again.

https://api-sandbox.network.global

Card Activate

Status:

Production

Version:

V2

Category:

Card Services
/SB/CardServices/Transaction/V2/CardActivation
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
headermsg_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 “TRANSACTION”
msg_function* requiredstring50Static Value - REQ_CARD_ACTIVATION
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* requiredstring32This defines the card Identifier Id, this is the sample value please use the newly created card created by card create API? any given card can be actived only once. If we use the same card identifer id multiple times for card activation, the API will be errored out saying - “Card Status Not Allowed for Activation” .
card_identifier_type* requiredstring20CONTRACT_NUMBER is used for clear card number or EXID which is a unique identifier for the card generated by CMS
card_sequence_numberstring2Sample 01,02 etc
card_expiry_datestring4YYMM ex 2310

{
    "NISrvRequest": {
        "request_card_activation": {
            "header": {
                "msg_id": "236001",
                "msg_type": "TRANSACTION",
                "msg_function": "REQ_CARD_ACTIVATION",
                "src_application": "IVR",
                "target_application": "WAY4",
                "timestamp": "2020-07-20T10:49:02.366+04:00",
                "bank_id": "NIC"
            },
            "body": {
                "card_identifier_id": "99984100111514120378",
                "card_identifier_type": "EXID"
            }
        }
    }
}

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

Node TypeTypeLengthDescription
headermsg_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 “TRANSACTION”
msg_function* requiredstring50Static value - REP_CARD_ACTIVATION
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
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* requiredstring20 Application Name
date_time* requiredstring30 Timestamp of the response Format YYYY-MM-DD HH:MM:SS
status* requiredstring1 Status of the request (S/F)
error_code* requiredstring4 EAI Internal Error Code (Check error codes section for the complete list of error codes and error code descriptions)
error_description* requiredstring100 Error Description (Check error codes section for the complete list of error codes and error code descriptions)
transaction_ref_idstring20 The tracking_id sent in the request will be sent back in response in this field.

{
    "NISrvResponse": {
        "response_card_activation": {
            "header": {
                "msg_id": "89854338",
                "msg_type": "TRANSACTION",
                "msg_function": "REP_CARD_ACTIVATION",
                "src_application": "IVR",
                "target_application": "WAY4",
                "timestamp": "2024-02-15T15:39:54.167+04:00",
                "bank_id": "NIC"
            },
            "exception_details": {
                "application_name": "TCC-ADP",
                "date_time": "2024-02-15T15:39:54.167+04:00",
                "status": "S",
                "error_code": "000",
                "error_description": "Success"
            }
        }
    }
}

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.