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

Bulk Card Summary

Status:

Production

Version:

V2

Category:

Card Services

Overview

Bulk Card Summary can be used for stock management, this will give you statistics of your stock. For example you will be able to know the number of cards available under a given product.

client_number: client number used in the bulk card create request
product_code: specific product code
countr_status_code: card status (statuses described in bulk card create)
appl_reg_number: Unique request identifier that we will return as part of the card create response.
batch_idt: batch idt used in the bulk card create request
card_identifier_id: option to filter by specific card or EXID

How It Works


You can retrieve the bulk card summary, filtering by.

There are four statuses for cards:

client_number: client number used in the bulk card create request.
product_code: specific product code.
countr_status_code: card status (statuses described in bulk card create)

Overview:

Bulk Card Summary can be used for stock management, this will give you statistics of your stock. For example you will be able to know the number of cards available under a given product.

How it works:

You can retrieve the bulk card summary, filtering by:

  • client_number: client number used in the bulk card create request
  • product_code: specific product code
  • countr_status_code: card status (statuses described in bulk card create)
https://api-sandbox.network.global

Bulk Card Summary

Status:

Production

Version:

V2

Category:

Card Services
/V2/BulkCardIssuance/CardSummary
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_card_summaryheadermsg_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_BULK_CARD_SUMMARY”
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”
bodyproduct_codestring50Product Code
product_code_tgtstring50Code of the client card-level product for which this bulk card is suitable
client_numberstring20Client number/Customer Id or CIF the card will be created under it
contr_status_codestring32Status of the card in the bulk batch

{
    "NISrvRequest": {
        "request_bulk_card_summary": {
            "header": {
                "msg_id": "236001",
                "msg_type": "ENQUIRY",
                "msg_function": "REQ_BULK_CARD_SUMMARY",
                "src_application": "BNK",
                "target_application": "WAY4",
                "timestamp": "2020-07-20T10:49:02.366+04:00",
                "bank_id": "NIC"
            },
            "body": {
                "product_code": "982_AED_001_BULK",
                "product_code_tgt": "982_AED_001",
                "client_number": "112233719988744606",
                "contr_status_code": "BULK_IN_PROGRESS"
            }
        }
    }
}

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

Node TypeTypeLengthDescription
NISrvResponseresponse_bulk_card_summaryheadermsg_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_BULK_CARD_SUMMARY”
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.
bodysummaryproduct_code* requiredstring50Product code
product_name* requiredstring100Product name
client_numberstring20Client number/Customer Id or CIF linked to the card
client_short_namestring255Client short name
contr_status_code* requiredstring32Status of the card in the bulk batch
production_status* requiredstring1Card production status, M: Marked for embossing, L: Locked
number_of_cards* requiredstring4Number of cards

{
    "NISrvResponse": {
        "response_bulk_card_summary": {
            "header": {
                "msg_id": "236001",
                "msg_type": "ENQUIRY",
                "msg_function": "REP_BULK_CARD_SUMMARY",
                "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": {
                "summary": [
                    {
                        "product_code": "982_AED_001_BULK",
                        "product_name": "982-PS AED Visa Classic - Bulk",
                        "client_number": "112233719988744606",
                        "client_short_name": "NI",
                        "contr_status_code": "BULK_IN_PROGRESS",
                        "production_status": "M",
                        "number_of_cards": "10"
                    }
                ]
            }
        }
    }
}

Node Child Node Type Length Description

How It Works

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