Prepaid Solutions
Overview
With our prepaid solution, you can extend prepaid products to customers without constraints such as credit rating, income, or bank account ownership. The solution includes issuer, branch, corporate, or cardholder web-based portals, enabling effortless sales, maintenance, load, and card or customer lifecycle management. These features empower non-banked customers to manage their finances like seasoned professionals, making financial management more accessible and straightforward.
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.
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 Card Summary
Status:
Production
Version:
V2
Product:
Prepaid Solutions
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)
Bulk Card Summary
Status:
Production
Version:
V2
Product:
Prepaid 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_summary | 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_BULK_CARD_SUMMARY” | |||||||
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 | 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 | |||||||
client_number | string | 20 | Client number/Customer Id or CIF the card will be created under it | |||||||
contr_status_code | string | 32 | Status 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-Type | application/json | string | Content Type |
Node Type | Type | Length | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
NISrvResponse | response_bulk_card_summary | 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_BULK_CARD_SUMMARY” | |||||||
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 | summary | product_code | string | 50 | Product code | |||||
product_name | string | 100 | Product name | |||||||
client_number | string | 20 | Client number/Customer Id or CIF linked to the card | |||||||
client_short_name | string | 255 | Client short name | |||||||
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 | |||||||
number_of_cards | string | 4 | Number 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 | ||
---|---|---|---|---|---|---|
Code | Description | |||||
---|---|---|---|---|---|---|