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.
Accounts List
Status:
Production
Version:
V2
Product:
Prepaid Solutions
Account List
Overview
A "list of accounts" API in a payment processing company allows users to retrieve a list of all client accounts in the payment processing system. This API is typically used by merchants or other businesses that want to view a list of all accounts that are registered in the payment processing system, for example, to manage which accounts are eligible for use in transactions or to view the status of a particular account.
Account listing
This feature allows users to retrieve a list of all accounts that are registered in the payment processing system.
Security
This feature ensures that the API has the necessary security measures in place to protect against unauthorized access and ensure the security and integrity of the payment processing system. This may include measures such as authentication and encryption.
How It Works
To utilize the 'account list' API, users must first provide their authentication credentials, such as a client secret and ID, to access the API. Once authenticated, the API retrieves a list of all accounts registered in the NI systems and returns it to the user.
End consumers benefit from using the 'account list' API by having a comprehensive view of all the accounts in the NI card management systems.
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.
Accounts List
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 | |||||||
---|---|---|---|---|---|---|---|---|---|---|
header | msg_id | string | 12 | Unique Source Message ID | ||||||
msg_type | string | 12 | Request Type Default TRANSACTION | |||||||
msg_function | string | 50 | Function name to be used Default REQ_LIST_OF_ACCOUNTS | |||||||
src_application | string | 10 | Source requesting channel Ex IVR | |||||||
target_application | string | 10 | Target application name Ex PCMS | |||||||
timestamp | string | 30 | Timestamp of the response Date u0026 time Format DD/MM/YYYY HH:MM:SS | |||||||
bank_id | string | 4 | Source Bank Id Ex bankID | |||||||
body | customer_id | string | 32 | customer id | ||||||
card_type | string | 20 | PREPAID/CREDIT/DEBIT |
{
"NISrvRequest": {
"request_list_of_accounts": {
"header": {
"msg_id": "236001",
"msg_type": "ENQUIRY",
"msg_function": "REQ_LIST_OF_ACCOUNTS",
"src_application": "IVR",
"target_application": "WAY4",
"timestamp": "2020-07-20T10:49:02.366+0:00",
"bank_id": "NIC"
},
"body": {
"customer_id": "100000027",
"card_type": "CREDIT"
}
}
}
}
Node | Child Node | Type | Length | Description |
---|---|---|---|---|
Content-Type | application/json | string | Content Type |
Node Type | Type | Length | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
header | msg_id | string | 12 | The msg_id sent in the request will be sent back in response in this field Unique Source Message ID eg ada123456fdsf | ||||||
msg_type | string | 12 | msg_type sent in the request will be sent back in response in this field | |||||||
msg_function | string | 50 | Default REP_LIST_OF_ACCOUNTS | |||||||
src_application | string | 10 | The src_application sent in the request will be sent back in response in this field | |||||||
target_application | string | 10 | The target_application sent in the request will be sent back in response in this field | |||||||
timestamp | string | 30 | Timestamp of the response Date u0026 time Format DD/MM/YYYY HH:MM:SS | |||||||
bank_id | string | 4 | The bank_id sent in the request will be sent back in response in this field | |||||||
exception_details | ||||||||||
body | card_identifier_id | string | 32 | Card Identifier Id | ||||||
card_identifier_type | string | 4 | CONTRACT_NUMBER |
{
"NISrvResponse": {
"response_list_of_accounts": {
"header": {
"msg_id": "236001",
"msg_type": "ENQUIRY",
"msg_function": "REP_LIST_OF_ACCOUNTS",
"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"
},
"body": {
"card_identifier_id": "2227230000508669",
"card_identifier_type": "CONTRACT_NUMBER"
}
}
}
}
Code | Description |
---|---|
200 | Sample Description |
400 | Bad Request |
401 | Unauthorized |
403 | Forbidden |
500 | Internal Server Error |
502 | Bad gateway |
503 | Scheduled Maintenance |
504 | Gateway Timeout |
596 | Service Not Found |