Credit Solutions
Overview
Our one-stop, centralized solution for Credit 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 Credit Card processing solution, you can easily accept payments from your customers and offer flexible credit options. Our platform supports all major credit card networks, so you can serve customers regardless of their issuing bank.
Activate Credit cards
Users can activate credit cards when they are first issued or after they have been temporarily suspended.
Check Available Credit
Users can check their available credit limit and outstanding balance in real-time or on a scheduled basis.
View Transaction History
Users can view a detailed record of all transactions made with a credit card, including the date, time, amount, and merchant details.
Make Payments
Users can pay their credit card bills through multiple channels, including online transfers, auto-debit, or in-person payments.
Resolve disputes
Users can access a process for resolving disputes or issues that may arise with credit card transactions, ensuring timely resolution and customer satisfaction.
Protect against fraud
Users can access measures to detect and prevent fraudulent activity on credit cards, such as monitoring for suspicious activity, enabling transaction alerts, and requiring additional authentication for high-value transactions.
Manage card accounts
Users can view and manage their credit card accounts, including the ability to set spending limits, view transaction history, update personal information, and manage rewards or loyalty points.
Switch Restrictions
Status:
Production
Version:
V2
Product:
Credit Solutions
Switch Restrictions API
Overview
This API enables customers to quickly and easily switch restrictions on their credit or debit cards, helping them to make changes on the go.
Quick and Easy Access
The Switch Restrictions API provides customers with a simple and intuitive way to access information about their card restrictions. With just a few clicks, customers can change their restrictions.
Customization options
The Switch Restrictions API allows customers to customize the information they view on their restrictions usage summary.
Secure and encrypted
The Switch Restrictions API uses advanced security protocols to protect customer data and ensure the safety of transactions.
How It Works
Once the customer's identity has been verified, the API switch the requested information from the payment processing company's database. This information includes data on the customer's transaction restrictions, approved or declined merchant categories, and countries where their card can be used. Overall, the Switch Restrictions API is a powerful tool that enables payment processing companies to provide their customers with quick and easy access to information about their card restrictions. By leveraging advanced security protocols and customizable features, the API helps to improve customer satisfaction and loyalty, while also streamlining internal operations.
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:
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 | Static Value - REQ_ENABLE_DISABLE_RESTRICTION | |||||||
| 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 | |||||||
| restriction | isAllowed | boolean | 0 | true/false | ||||||
| restriction_type | string | 100 | Restriction Type MOTO - Mail Order Telephone Order INTERNATIONAL - International Transaction ECOM - e-Commerce PERS_RESTR_CONTACTLESS - Contactless Transaction NFC - controls POS transactions only ATM - ATM Transaction ANY - Any Debit Transaction PURCHASE - Purchase Transactions INTERNATIONAL_SPECIFIC_COUNTRIES - to allow specific countries | |||||||
| end_date | string | 10 | End Date | |||||||
| allowed_values | 100 | Allowed values (in case of Restriction-type = INTERNATIONAL_SPECIFIC_COUNTRIES, please input comma seperated list of country codes here) | ||||||||
{
"NISrvRequest": {
"request_enable_disable_restriction": {
"header": {
"msg_id": "236001",
"msg_type": "TRANSACTION",
"msg_function": "REQ_ENABLE_DISABLE_RESTRICTION",
"src_application": "BNK",
"target_application": "CARD_CONTROL",
"timestamp": "2020-07-20T10:49:02.366+04:00",
"bank_id": "NIC"
},
"body": {
"card_identifier_id": "99984100148297467162",
"card_identifier_type": "EXID",
"restriction": [
{
"isAllowed": true,
"restriction_type": "MOTO"
}
]
}
}
}
}
| Node | Child Node | Type | Length | Description | ||||
|---|---|---|---|---|---|---|---|---|
| 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 “REP_ENABLE_DISABLE_RESTRICTION” | |||||||
| 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 | 15 | 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. | |||||||
{
"NISrvResponse": {
"response_enable_disable_restriction": {
"header": {
"msg_id": "236001",
"msg_type": "TRANSACTION",
"msg_function": "REP_ENABLE_DISABLE_RESTRICTION",
"src_application": "BNK",
"target_application": "CARD_CONTROL",
"timestamp": "2020-07-20T06:49:02.366Z",
"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"
}
}
}
}
| 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 |