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.
Pin Tries Counter Reset
Status:
Production
Version:
V2
Product:
Prepaid Solutions
PIN Retry Counter Reset
Overview
The "Reset PIN Try Counter" API allows consumers to manually reset the counter that tracks the number of consecutive times a cardholder has entered an incorrect PIN. This API is useful in situations where a cardholder has exceeded the predefined limit of incorrect PIN attempts and is unable to make transactions as a result.
When a cardholder enters an incorrect PIN, the card's PIN Try Counter is incremented by one. Cards have a predefined limit for the number of incorrect PIN attempts before being blocked for transactions. If a cardholder exceeds this threshold and is unable to transact, this API can be utilized to reset the counter and restore the ability for the cardholder to make transactions.
Manually resets the PIN Try Counter
The API allows consumers to manually reset the counter that tracks the number of consecutive times a cardholder has entered an incorrect PIN, thus restoring the ability for cardholders to make transactions.
Card blocking prevention
By resetting the PIN Try Counter, the API prevents cards from being blocked due to a large number of incorrect PIN attempts, thus increasing the availability of cards for transactions.
Security feature
The API requires secure validation of the identity of the cardholder and ensures that the card has not been lost or stolen before allowing a reset of the PIN Try Counter, thus increasing the security of transactions and protecting the cardholder's account.
How It Works
This API allows businesses to easily reset the PIN try counter for a specific card. By utilizing this API, businesses can ensure that authorized cardholders are able to access their account and perform transactions even if they have entered it incorrectly a certain number of times.
To use the API, businesses will need to make an HTTPS POST request to the API endpoint, including the necessary parameters such as the card number in the request body. The API will then process the request and connect to the card issuer's systems or network to retrieve the PIN Try Counter associated with the provided card number and reset it to zero. The API will then generate a response indicating whether the counter has been reset successfully or not, which the API consumers can then use to take the necessary actions.
It is important to note that this API can only be used if the card issuer or the financial institution is using this service provided by the API and the card is active and not blocked. Additionally, it is highly recommended to offer this feature only after securely validating the identity of the cardholder (in-app biometrics, security questions, etc.) and ensuring the card was not lost/stolen for security reasons.
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.
Pin Tries Counter Reset
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_pin_counter_reset | 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 “TRANSACTION” | |||||||
msg_function | string | 50 | Message functions: Should be “REQ_PIN_RETRIES_COUNTER_RESET” | |||||||
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 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_pin_counter_reset": {
"header": {
"msg_id": "1206231104",
"msg_type": "TRANSACTION",
"msg_function": "REQ_PIN_RETRIES_COUNTER_RESET",
"src_application": "BNK",
"target_application": "WAY4",
"timestamp": "2023-06-12T12:01:08.8+04:00",
"bank_id": "NIC"
},
"body": {
"card_identifier_id": "99984100128180710456",
"card_identifier_type": "EXID"
}
}
}
}
Node | Child Node | Type | Length | Description | |
---|---|---|---|---|---|
Content-Type | application/json | string | 12 | Content-Type |
Node Type | Type | Length | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
NISrvResponse | response_pin_counter_reset | 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 “TRANSACTION” | |||||||
msg_function | string | 50 | Message functions: Should be “REP_PIN_RETRIES_COUNTER_RESET” | |||||||
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 Date & time Format DD/MM/YYYY HH:MM:SS | |||||||
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. |
{
"NISrvResponse": {
"response_pin_counter_reset": {
"header": {
"msg_id": "1206231104",
"msg_type": "TRANSACTION",
"msg_function": "REP_PIN_RETRIES_COUNTER_RESET",
"src_application": "BNK",
"target_application": "WAY4",
"timestamp": "2023-06-12T12:01:08.8+04:00",
"bank_id": "NIC"
},
"exception_details": {
"application_name": "TCC-ADP",
"date_time": "2023-06-12T12:01:08.8+04:00",
"status": "S",
"error_code": "000",
"error_description": "Success"
}
}
}
}
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 |