Debit Solutions
Overview
Our one-stop, centralised solution for Debit Card processing is designed to provide you with a seamless and secure payment experience. Whether you are a small business or a large enterprise, our solution is cost-effective, easily configurable and scalable to meet your specific needs.
With our Debit Card processing solution, you can easily accept payments from your customers and enjoy faster access to your funds. Our platform supports all major debit card networks, so you can accept payments from customers regardless of their bank.
Activate Debit cards
Users can activate debit 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 debit card in real-time or on a scheduled basis.
View transaction history
Users can view a detailed record of all transactions made with a debit card, including the date, time, amount, and location of each transaction.
Reload cards
Users can add funds to a debit 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 debit card transactions.
Protect against fraud
Users can access measures to detect and prevent fraudulent activity on debit cards, such as monitoring for suspicious activity or requiring additional authentication for certain transactions.
Manage card accounts
Users can view and manage their debit card accounts, including the ability to set spending limits, view transaction history, and update personal information.
Card Status Change
Status:
Production
Version:
V2
Product:
Credit Solutions
Card Status Change
Overview
This API allows for the change of status of a card or account. It is primarily used for blocking or unblocking a card, in cases where a cardholder has reported their card as lost or stolen, for example. This API can also be used for other status changes such as activating or deactivating a card. The API requires proper authentication and authorization to ensure that only authorized parties are able to make these changes.
Card/Account Status Change
Allows for quick and easy modification of the status of a card or account, such as blocking or unblocking.
Flexible Status Options
The API should be able to integrate with other payment processing systems, such as point-of-sale systems and fraud detection systems, to ensure seamless processing of transactions.
How It Works
This API allows you to change the status of a card or account to a new value. It is primarily used for blocking or unblocking a card. When you want to change the status of a card or account, you can use this API to do so. The API requires you to provide the card or account information, as well as the new status that you want to set. The API will then process your request and update the status of the card or account accordingly. Once the status has been changed, it will be reflected in the system and will be used for all further transactions. If this API not used properly, it could result in account or card being blocked or unblocked which could have significant impact on cardholder's banking experience. Overall, this API allows for quick and efficient management of card or account statuses, making it easy to maintain the security and integrity of your financial 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.
Card Status Change
Status:
Production
Version:
V2
Product:
Credit 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 | 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_CARD_STATUS_CHANGE” | |||||||
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 | |||||||
card_expiry_date | string | 4 | CARD EXPIRY DATE | |||||||
status | type | string | 32 | Status Type | ||||||
value | string | 32 | Status value | |||||||
custom_fields | key | string | 20 | Custom Tag | ||||||
value | string | 128 | Tag value |
{
"NISrvRequest": {
"request_card_status_change": {
"header": {
"msg_id": "56532898",
"msg_type": "TRANSACTION",
"msg_function": "REQ_CARD_STATUS_CHANGE",
"src_application": "CRM",
"target_application": "WAY4",
"timestamp": "2020-07-20T10:49:02.366+04:00",
"bank_id": "NIC"
},
"body": {
"card_identifier_id": "99984100111514120378",
"card_identifier_type": "EXID",
"status": {
"type": "BCC-CARD-982",
"value": "T"
},
"custom_fields": [
{
"key": "bc_channel",
"value": "TIB2"
}
]
}
}
}
}
Node | Child Node | Type | Length | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Content-Type | application/json | string | Content Type |
Node Type | Type | Length | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
header | msg_id | string | 12 | Unique Source Message ID eg ada123456fdsf | ||||||
msg_type | string | 12 | msg_type can hold 2 values TRANSACTION or ENQUIRY, the value must be sent as it is mentioned in the request | |||||||
msg_function | string | 50 | Default REP_CARD_STATUS_CHANGE | |||||||
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” | |||||||
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_card_status_change": {
"header": {
"msg_id": "56532898",
"msg_type": "TRANSACTION",
"msg_function": "REP_CARD_STATUS_CHANGE",
"src_application": "CRM",
"target_application": "WAY4",
"timestamp": "2024-03-19T14:04:23.065+04:00",
"bank_id": "NIC"
},
"exception_details": {
"application_name": "TCC-ADP",
"date_time": "2024-03-19T14:04:23.065+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 |