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.
Bulk List Of Cards
Status:
Production
Version:
V2
Product:
Debit Solutions
Overview
Bulk list of cards can be used for stock management, which lists all generated pre-embossed cards, with the option to request the list 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)
- 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 list of cards, which will include information indicating either this request is in a waiting status, or if it was processed.
There are four statuses for cards:
- appl_resp_code: application response code which will indicate if the request was accepted or not.
- appl_resp_text: application response text which will give a test description about the request.
- appl_posting_status: application posting status which will indicate if the request in waiting status, the expected value if the request is in waiting stats is “Waiting”
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.
Bulk List Of Cards
Status:
Production
Version:
V2
Product:
Debit Solutions
Node | Child Node | Type | Length | Description |
---|---|---|---|---|
Authorization | Bearer xxxx | string | Authorization Header (Bearer Token) | |
Content-Type | application/json | string | Content Type |
Node Type | Type | Length | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
NISrvRequest | request_bulk_card_list | header | msg_id | string | 12 | Message 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 | string | 12 | Message Type – This can have either “TRANSACTION” or “ENQUIRY” As for this API the value expected is “ENQUIRY” | |||||||
msg_function | string | 50 | Message functions: Should be “REQ_LIST_OF_BULK_CARD” | |||||||
src_application | string | 10 | Source 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 | string | 10 | The 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 | string | 30 | Timestamp of the request - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00 | |||||||
bank_id | string | 4 | Bank 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” | |||||||
body | client_number | string | 20 | Client number/Customer Id or CIF linked to the card | ||||||
product_code | string | 50 | Product Code | |||||||
product_code_tgt | string | 50 | Code of the client card-level product for which this bulk card is suitable | |||||||
contr_status_code | string | 32 | Status of the card in the bulk batch | |||||||
appl_reg_number | string | 60 | Unique batch id genereted by NI system | |||||||
batch_idt | string | 60 | batch Idt | |||||||
card_identifier_id | string | 32 | Card Identifier Id | |||||||
card_identifier_type | string | 20 | CONTRACT_NUMBER is used for clear card number or EXID which is a unique identifier for the card generated by CMS |
{
"NISrvRequest": {
"request_bulk_card_list": {
"header": {
"msg_id": "236001",
"msg_type": "ENQUIRY",
"msg_function": "REQ_LIST_OF_BULK_CARD",
"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",
"product_code_tgt": "982_AED_001",
"contr_status_code": "BULK_IN_PROGRESS",
"appl_reg_number": "BULK_ISS_240314020101",
"batch_idt": "BT20240703111111",
"card_identifier_id": "99985101161390700708",
"card_identifier_type": "EXID"
}
}
}
}
Node | Child Node | Type | Length | Description | |
---|---|---|---|---|---|
Node Type | Type | Length | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
NISrvResponse | response_bulk_card_list | header | msg_id | string | 12 | Message 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 | string | 12 | Message Type – This can have either “TRANSACTION” or “ENQUIRY” As for this API the value expected is “ENQUIRY” | |||||||
msg_function | string | 50 | Message functions: Should be “REP_LIST_OF_BULK_CARD” | |||||||
src_application | string | 10 | Source 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 | string | 10 | The 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 | string | 30 | Timestamp of the response - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00 | |||||||
bank_id | string | 4 | Bank 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_details | application_name | string | 20 | Application Name | ||||||
date_time | string | 30 | Timestamp of the response Format “YYYY-MM-DD HH:MM:SS” | |||||||
status | string | 1 | Status of the request (S/F) | |||||||
error_code | string | 4 | EAI Internal Error Code (Check error codes section for the complete list of error codes and error code descriptions) | |||||||
error_description | string | 100 | Error Description (Check error codes section for the complete list of error codes and error code descriptions) | |||||||
transaction_ref_id | string | 20 | The tracking_id sent in the request will be sent back in response in this field. | |||||||
body | clients | client_number | string | 20 | Client number/Customer Id or CIF linked to the card | |||||
client_short_name | string | 255 | Client short name | |||||||
batches | batch_idt | string | 60 | batch Idt | ||||||
cards | card_identifier_id | string | 32 | Card Identifier Id | ||||||
card_identifier_type | string | 20 | CONTRACT_NUMBER is used for clear card number or EXID which is a unique identifier for the card generated by CMS | |||||||
pan | string | 16 | card number | |||||||
product_code | string | 50 | Product code | |||||||
product_name | string | 100 | Product name | |||||||
date_open | string | 10 | Date of card creation | |||||||
date_closed | string | 10 | Date of closing the card | |||||||
contr_status_code | string | 32 | Status of the card in the bulk batch | |||||||
production_status | string | 1 | Card production status, M: Marked for embossing, L: Locked | |||||||
card_expiry_date | string | 4 | Card's expiry date the Format is YYMM | |||||||
card_name | string | 21 | Card embossing name defined on client level should be in Upper case | |||||||
company_name | string | 21 | Embossing company name applied to all the cards | |||||||
appl_resp_code | string | 3 | Application response code | |||||||
appl_resp_text | string | 255 | Application response text | |||||||
appl_posting_status | string | 20 | Application posting status |
{
"NISrvResponse": {
"response_bulk_card_list": {
"header": {
"msg_id": "236001",
"msg_type": "ENQUIRY",
"msg_function": "REP_LIST_OF_BULK_CARD",
"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": {
"clients": [
{
"client_number": "112233719988744606",
"client_short_name": "NI",
"batches": [
{
"batch_idt": "BT20240703111111",
"cards": [
{
"card_identifier_id": "99985101161390700708",
"card_identifier_type": "EXID",
"pan": "9998510116139070",
"product_code": "982_AED_001_BULK",
"product_name": "982-PS AED Visa Classic - Bulk",
"date_open": "2022-01-01",
"date_closed": "2022-01-01",
"contr_status_code": "BULK_IN_PROGRESS",
"production_status": "M",
"card_expiry_date": "0528",
"card_name": "JAMES ROBERT",
"company_name": "NI"
}
]
}
]
}
]
}
}
}
}
Node | Child Node | Type | Length | Description | ||
---|---|---|---|---|---|---|
Node | Child Node | Type | Length | Description | ||
---|---|---|---|---|---|---|