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.
Get Eligible Plans
Status:
Production
Version:
V2
Product:
Prepaid Solutions
Get Eligible Plans
Overview
The 'Get Eligible Plans' API offers personalized plan recommendations based on eligibility criteria, allowing for a seamless and efficient plan selection process. With comprehensive and informative plan details provided, users can make informed decisions about which plan is best for them. Overall, this API streamlines the process of finding the right plan for each user.
Eligibility-based plan recommendations
This API offers personalized plan recommendations based on eligibility criteria, ensuring that customers only see plans that they are eligible for.
Quick and easy plan selection
The 'Get Eligible Plans' API provides a quick and easy way for users to find the best plan for their needs, saving time and effort.
Relevant plan details
The API provides detailed information about the recommended plans, including the plan number, interest rate etc. helping consumers make informed decisions.
How It Works
The 'Get Eligible Plans' API is allows authorized users to retrieve a list of plans that they are eligible for based on certain criteria. To use this API, users must provide information about the card they want to use for the plan, as well as details about the transaction and the type of action they want to perform. The API will then provide a list of eligible plans that match the user's criteria, including details such as the plan name, price, and duration.
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.
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_get_eligible_plans | 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 | Static Value - REQ_GET_ELIGIBLE_PLANS | |||||||
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 | card_identifier_id | string | 32 | card identifier | ||||||
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 | |||||||
trans_id | string | 20 | Transaction Id | |||||||
action | string | 15 | This describes the action for which the elibilge plans should be checked ex - balance_conversion, balance_transfer, loan | |||||||
balance_amount | string | 28 | Balance amount | |||||||
options | key | string | 20 | custom key | ||||||
value | string | 128 | custom value |
{
"NISrvRequest": {
"request_get_eligible_plans": {
"header": {
"msg_id": "236001",
"msg_type": "ENQUIRY",
"msg_function": "REQ_GET_ELIGIBLE_PLANS",
"src_application": "IVR",
"target_application": "CMS",
"timestamp": "2020-07-20T10:49:02.366+04:00",
"bank_id": "NIC"
},
"body": {
"card_identifier_id": "99984100148297467162",
"card_identifier_type": "EXID",
"trans_id": "",
"action": "EXID",
"balance_amount": "EXID"
}
}
}
}
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 | ||||||
msg_type | string | 12 | Request Type Default ENQUIRY | |||||||
msg_function | string | 50 | Function name to be used Default RES_GET_ELIGIBLE_PLANS | |||||||
src_application | string | 10 | Source requesting channel Ex IVR | |||||||
target_application | string | 10 | Target application name Ex PCMS | |||||||
timestamp | string | 30 | Timestamp of the request Format DD/MM/YYYY HH:MM:SS | |||||||
bank_id | string | 4 | Source Bank Id Ex bankID | |||||||
instance_id | string | 10 | InstanceID | |||||||
exception_details | ||||||||||
body | plans | plan_number | string | 5 | Plan number | |||||
number_of_portions | string | 4 | Number of portions | |||||||
interest | string | 3 | Interest |
{
"NISrvResponse": {
"response_get_eligible_plans": {
"header": {
"msg_id": "236001",
"msg_type": "ENQUIRY",
"msg_function": "RES_GET_ELIGIBLE_PLANS",
"src_application": "IVR",
"target_application": "CMS",
"timestamp": "2020-07-20T10:49:02.366+04:00",
"bank_id": "NIC",
"instance_id": "InstanceID"
},
"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": {
"plans": [
{
"plan_number": "",
"number_of_portions": "",
"interest": ""
}
]
}
}
}
}
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 |