Debit Solutions

Overview

Our one-stop, centralised solution for Debit Card processing is designed to provide you with a seamless and secure payment experience. Whether you are a small business or a large enterprise, our solution is cost-effective, easily configurable and scalable to meet your specific needs.

With our Debit Card processing solution, you can easily accept payments from your customers and enjoy faster access to your funds. Our platform supports all major debit card networks, so you can accept payments from customers regardless of their bank.

Version

Bulk Move Cards

Status:

Production

Version:

V2

Product:

Credit Solutions

 

Overview

The Bulk Pre-embossed Card Client Move API request is a designed for streamlined processing of large-scale card movements within a client's system. This application operates through an online API, allowing you to move card/list of cards from one client, branch, agent to another.

How It Works

This API facilitates card transfers between clients, such as between two branches. For instance, if branch A has 100 cards and branch B has 10, this API allows you to transfer X number of cards between them according to your business requirements. For instance, if branch B's stock is low or if any branch needs to be closed, you can easily manage card movement between them.

https://api-sandbox.network.global

Bulk Move Cards

Status:

Production

Version:

V2

Product:

Credit Solutions
/V2/BulkCardIssuance/MoveCards
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_bulk_move_cardsheadermsg_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* requiredstring50Message functions: Should be “REQ_MOVE_BULK_CARDS”
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”
bodyclient_number_from* requiredstring20Client number/Customer Id or CIF from which the cards will be moved from
client_number_to* requiredstring20Client number/Customer Id or CIF from which the cards will be moved to
number_of_cards* requiredstring4Number of cards needs to be generated
batch_idtstring60batch id, is an Id managed by FI system and no uniqueness checking on it from our side, if this was not provided, we will generate it.
bulk_preemb_idt_liststring3000Contain comma-separated list of clear card number or EXIDs of the cards to be moved.
bulk_preemb_idt_schemestring20CONTRACT_NUMBER is used for clear card number or EXID which is a unique identifier for the card generated by CMS
request_detailssrc_app_codestring32Free text sent by the you, to identify the calling application. Optimized for machine-readable processing like grouping and filtering.
src_app_namestring64Additional tag, repeating the src_app_code, but with a value optimized for direct display.
ext_user_idstring32Free text sent by the bank, to identify the external system’s user.

{
    "NISrvRequest": {
        "request_bulk_move_cards": {
            "header": {
                "msg_id": "236001",
                "msg_type": "TRANSACTION",
                "msg_function": "REQ_MOVE_BULK_CARDS",
                "src_application": "BNK",
                "target_application": "WAY4",
                "timestamp": "2020-07-20T10:49:02.366+04:00",
                "bank_id": "NIC"
            },
            "body": {
                "client_number_from": "112233719988744606",
                "client_number_to": "112233719988744607",
                "number_of_cards": "10",
                "batch_idt": "BT20240703111111",
                "bulk_preemb_idt_list": "9984100116414979716,99984100129858230678,99984100195464865918",
                "bulk_preemb_idt_scheme": "EXID"
            }
        }
    }
}

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

Node TypeTypeLengthDescription
NISrvResponseresponse_bulk_move_cardsheadermsg_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* requiredstring50Message functions: Should be “REP_MOVE_BULK_CARDS”
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.

{
    "NISrvResponse": {
        "response_bulk_move_cards": {
            "header": {
                "msg_id": "236001",
                "msg_type": "TRANSACTION",
                "msg_function": "REP_MOVE_BULK_CARDS",
                "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"
            }
        }
    }
}

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

Code Description
* *