Debit Solutions

Credit Solutions

Overview

Prepaid card services in NI allow users to access and use prepaid cards in the payment processing system. Prepaid cards are a type of payment card that are loaded with a specific amount of funds, which can be used to make purchases or withdraw cash at locations that accept the card.Users of prepaid card services in a payment processing company can typically:

Activate prepaid cards

Users can activate prepaid cards when they are first issued or after they have been deactivated for any reason.

Check card balances

Users can check the balance on a prepaid card in real-time or on a scheduled basis.

View transaction history

Users can view a detailed record of all transactions made with a prepaid card, including the date, time, amount, and location of each transaction.

 

Reload cards

Users can add funds to a prepaid card, either by transferring money from another account or by purchasing a reload card.

Resolve disputes

Users can access a process for resolving disputes or issues that may arise with prepaid card transactions.

Protect against fraud

Users can access measures to detect and prevent fraudulent activity on prepaid cards, such as monitoring for suspicious activity or requiring additional authentication for certain transactions.

 

Manage card accounts

Users can view and manage their prepaid card accounts, including the ability to set spending limits, view transaction history, and update personal information.

Download
Version
Client Create(Post)

This API is used to create a new cardholder within a financial institution. It can be used to register a new customer and issue them with a card.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Account Create(Post)

The Account Create API allows for the creation of new customer accounts. Parameters include customer ID, card type, branch code, Product code, currency, and custom fields.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Card Create(Post)

A card creation API in a payment processing company allows users to add a credit or debit card to their account on the payment platform.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Card Activate(Post)

This API is used for activating newly issued cards or ones that have been renewed. Enables transactions on a new or replaced card by activating it.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Card Set Pin(Post)

This API enables the setting of a personal identification number (PIN) for a specific card, which can then be used for point of sale or ATM transactions.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Card Pin Verification(Post)

This API is used to check if a PIN provided by the cardholder matches the one associated with the card, in order to confirm the identity of the cardholder.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Card Pin Change(Post)

This API allows a cardholder to change their PIN by verifying their current PIN and setting a new one. The new PIN will be used for Point of Sales or ATM transactions.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Pin Tries Counter Reset(Post)

This API allows to reset the number of attempts a user has made to enter the correct PIN, in case the user has entered the incorrect PIN multiple times.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Get CVV2(Post)

This API allows consumers to retrieve the CVV2 (Card Verification Value 2) for a specific card.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Lookup Card Identifier(Post)

This API allows you to obtain an alternative identifier for a given card by using its identifier as input, the API will then return a different type of identifier such as tokenized card identifier.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Cards List(Post)

This API obtains a comprehensive listing of all the cards linked to a specific cardholder, including prepaid, credit, and debit cards.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Accounts List(Post)

The List of Accounts API is a useful tool for payment processing companies that offer a range of financial products, such as credit cards, debit cards, and bank accounts. This API allows customers to easily view a list of all their accounts with the payment processing company, providing a convenient way to manage their finances and keep track of their spending.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Card Details Enquiry(Post)

This API is used to retrieve information about a specific card such as the primary account number, the product the card is associated with, the status of the card, and any balances associated with the card.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Customer Details(Post)

A customer details enquiry API allows a payment processing company to retrieve information about a customer's account. This could be used, for example, by a merchant to get information about a customer's billing address or by a customer service representative to verify account details.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Card Status Change(Post)

This API is used to change the status of a card or account, such as blocking or unblocking it. It is used primarily for security purposes.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Card Replacement(Post)

This API is used to request a new card to replace a lost, stolen, damaged, or expired card.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Client Update(Post)

A client update API in a payment processing company allows users to update information for an existing client account in the payment processing system.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Account Update(Post)

This API allows for the updating of an existing account for a cardholder.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Card Update(Post)

The API facilitates the modification of an existing card associated with a specific account and cardholder.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
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
Product : Debit Solutions
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
Product : Debit Solutions
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
Product : Debit Solutions
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
Product : Debit Solutions
Try Out   
Bulk Card Create(Post)

Bulk card create can generate a pool of no-name plastic cards ready for instant issuance.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Bulk List Of Cards(Post)

Bulk list of cards can be used to check the status of bulk card create requests or to access the list of pre-embossed cards.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Bulk Card Summary(Post)

Bulk card summary can be used to check summary of the cards available in stock.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Bulk Move Cards(Post)

Bulk move cards can be used to move card/list of cards or batches from one client to another.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
OnlineEmbossing(Post)

This API is used to immediately send a request for card embossing.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Account Status Change(Post)

This API updates block codes on the account level for an account identifier.

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

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

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

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

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

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

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Get Account Transactions(Post)

This API pulls transactions which are authorized, time_based/posted, or statemented to account.

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

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

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Set FXRates(Post)

This service is used by an FI to set FX rates for a currency.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Get FXRates(Post)

This service is used by an FI to get FX rates for a currency.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   
Card Contact Details(Post)

This API allows fetching the customer contact details.

Status :Production
Version :V2
Product : Debit Solutions
Try Out   

Card Update

Status:

Production

Version:

V2

Product:

Debit Solutions

Card Update

Overview

The API provides the capability to update an existing card associated with a specific account and cardholder. This includes updating card information such as the expiration date, card status, etc. The API requires specific information to be provided such as the card identifier in order to update the card. This feature allows businesses to keep their customer's card information updated, ensuring smooth transaction processing and reducing the risk of fraudulent activities. The functionality provided by this API can be useful for updating cards.

Card update

The API allows an update of existing cards by saving time and reducing human error.

Secure card identification

By requiring a card number as input, the API ensures that only authorized individuals or systems can update existing cards, adding an extra layer of security to the card update process.

Accurate account tracking

By requiring the account number as input, the API ensures that the correct account and cardholder is being updated, allowing for accurate tracking and management of the cardholder's account.

How It Works

The Card Update API facilitates the modification of existing card information for a specific account and cardholder. The API requires certain input parameters, such as the card number, account number, and cardholder details, to be provided in order to update the specified card.

Upon receiving the input parameters, the API connects to the card management system and updates the card information with the provided details, such as the expiration date or card status. The updated card remains linked to the same account and cardholder as before and can continue to be utilized for transactions.

Additionally, this API also provides the capability to update multiple cards under a single account. This feature allows businesses to update multiple cards efficiently, reducing the time and effort required for updating individual cards.

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.

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.

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.

https://api-sandbox.network.global

Card Update

Download

Status:

Production

Version:

V2

Product:

Debit Solutions
/SB/CardServices/Transaction/V2/CardUpdate
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* requiredstring50Message functions: Should be “REQ_CARD_UPDATE”
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* requiredstring20Card Identifier Id
card_identifier_type* requiredstring32CONTRACT_NUMBER is used for clear card number or EXID which is a unique identifier for the card generated by CMS
cardbranch_code* requiredstring10Branch Code, if no branches are used, the code must be same as bank_code
card_identifier_id* requiredstring32Card Identifier 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
custom_fieldskeystring20Custom Tag. Ex: CN-CONTRACT_NAME
valuestring128Tag value. Ex: John doe

{
    "NISrvRequest": {
        "request_card_update": {
            "header": {
                "msg_id": "236501",
                "msg_type": "TRANSACTION",
                "msg_function": "REQ_CARD_UPDATE",
                "src_application": "IVR",
                "target_application": "PCMS",
                "timestamp": "2020-07-20T10:49:02.366+04:00",
                "bank_id": "NIC"
            },
            "body": {
                "card_identifier_id": "99984100111514120378",
                "card_identifier_type": "EXID",
                "card": {
                    "branch_code": "982",
                    "card_identifier_id": "99984100111514120378",
                    "card_identifier_type": "EXID",
                    "custom_fields": [
                        {
                            "key": "CN-CONTRACT_NAME",
                            "value": "John doe"
                        }
                    ]
                }
            }
        }
    }
}

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* requiredstring50Message functions: Should be “REP_CARD_UPDATE”
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* 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.
bodycard_identifier_id* requiredstring32card identifier
card_identifier_type* requiredstring20CONTRACT_NUMBER is used for clear card number or EXID which is a unique identifier for the card generated by CMS
custom_fieldskeystring20Custom Tag. Ex: CN-CONTRACT_NAME
valuestring128Tag value. Ex: John doe

{
    "NISrvResponse": {
        "response_card_update": {
            "header": {
                "msg_id": "236501",
                "msg_type": "TRANSACTION",
                "msg_function": "REP_CARD_UPDATE",
                "src_application": "IVR",
                "target_application": "PCMS",
                "timestamp": "2024-02-15T15:03:22.511+04:00",
                "bank_id": "NIC"
            },
            "exception_details": {
                "application_name": "TCC-ADP",
                "date_time": "2024-02-15T15:03:22.511+04:00",
                "status": "S",
                "error_code": "000",
                "error_description": "Success"
            },
            "body": {
                "card_identifier_id": "99984100111514120378",
                "card_identifier_type": "EXID",
                "custom_fields": [
                    {
                        "key": "CN-BC_C1",
                        "value": "_"
                    },
                    {
                        "key": "CN-CARD_DESIGN_FLAG",
                        "value": "00"
                    },
                    {
                        "key": "CN-CONTRACT_NAME",
                        "value": "John doe"
                    },
                    {
                        "key": "CN-DATE_OPEN",
                        "value": "2022-01-01"
                    },
                    {
                        "key": "CN-EXID",
                        "value": "99984100111514120378"
                    },
                    {
                        "key": "CN-NCONTROL_ENROLMENT",
                        "value": "N"
                    }
                ]
            }
        }
    }
}

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