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   

Bulk Card Create

Status:

Production

Version:

V2

Product:

Debit Solutions

Overview

Bulk Card Create is initiated through the submission of a bulk issuance request. This request can be transmitted either via the bulk file interface or the online API, offering flexibility in how users engage with the system. The primary purpose of this application is to facilitate the mass issuance of pre-embossed cards tailored to specific product parameters. By specifying the desired quantity and product details, users can efficiently generate a large volume of cards, streamlining the card issuance process for various purposes.

How It Works

The Financial Institution will request a consolidated batch of 'x' cards in a single submission, with the flexibility to initiate multiple batches as needed. The maximum allowable card request limit for Financial Institutions is set at 9,999. When 'x' number of cards are requested, they are not immediately created. Instead, a request is generated and queued for backend processing. Creation processes are scheduled between 21:20:00 and 04:35:00. For example, a card requested at 13:00:00 will wait until the scheduled processing time for creation. In the context of the Bulk Card Create API, a unique identifier will be provided from our end. Utilizing this identifier, you can retrieve the list of cards, which will include information indicating either this request is in a waiting status, or if it was processed, we will return the actual list of created cards. You have the option to apply multiple filters to the card list, such as filtering by unique identifier, product, or contract status.

  1. BULK_IN_PROGRESS – The cards are in process of being created (cards were created, but embossing file was not extracted).
  2. BULK_READY – The cards are ready to be used.
  3. BULK_USED – This card has already been associated with a specific client, hence it remains in a used state, preventing further linkage.
  4. BULK_CLOSED – This card can no longer be used due to a specific reason, like it is damaged card.

https://api-sandbox.network.global

Bulk Card Create

Download

Status:

Production

Version:

V2

Product:

Debit Solutions
/V2/BulkCardIssuance/CardCreate
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_createheadermsg_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_BULK_CARD_CREATE”
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_numberstring20Client number/Customer Id or CIF the card will be created under it
product_code* requiredstring50Product code
card_expiry_datestring4Card expiry date format YYMM
number_of_cards* requiredstring4Number of cards needs to be generated
card_design_flagstring2Card design flag
batch_sizestring4batch size is number between 2 and 1000 When this parameter is provided, the generated cards will be split in multiple batches. Suffix '-' will be appended to the batch_idt saved in the cards. Example: 'myfirstbatch-001', 'myfirstbatch-002' etc. If dividing the number_of_cards by batch_size results in more than 999 batches, the request will be declined.
card_name* requiredstring21Embossing name applied to all the cards
company_namestring21Embossing company name applied to all the cards
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.
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_card_create": {
            "header": {
                "msg_id": "567890",
                "msg_type": "TRANSACTION",
                "msg_function": "REQ_BULK_CARD_CREATE",
                "src_application": "BNK",
                "target_application": "WAY4",
                "timestamp": "2020-07-20T10:49:02.366+04:00",
                "bank_id": "NIC"
            },
            "body": {
                "client_number": "112233719988744606",
                "product_code": "982_AED_001_BULK",
                "card_expiry_date": "2803",
                "number_of_cards": "10",
                "card_design_flag": "01",
                "batch_size": "2",
                "card_name": "EMB NAME",
                "company_name": "NI",
                "batch_idt": "BT20240703111111",
                "request_details": [
                    {
                        "src_app_code": "test_app",
                        "src_app_name": "App Name",
                        "ext_user_id": "user1"
                    }
                ]
            }
        }
    }
}

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_BULK_CARD_CREATE”
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.
bodyappl_reg_number* requiredstring60Unique batch code that can be used to query bulk card list to get all cards created as part of this application request 

{
    "NISrvResponse": {
        "response_bulk_card_create": {
            "header": {
                "msg_id": "236001",
                "msg_type": "TRANSACTION",
                "msg_function": "REP_BULK_CARD_CREATE",
                "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": {
                "appl_reg_number": "BULK_ISS_240314020101"
            }
        }
    }
}

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

Code Description
* *