Pin Management
Pin Management
Overview
Our PIN Management services provide a secure platform for you to manage and distribute PINs to your customers. With our platform, you can easily generate, distribute and revoke PINs as needed, and track their usage.
Our PIN Management services also include added security features, such as encryption and multi-factor authentication, to ensure that your customers PINs are protected from fraud. Our platform also ensures that your PINs are compliant with all local and international regulations and industry standards, such as PCI DSS, which ensures that your transactions are processed in a secure and compliant manner.
In addition, our PIN Management services provide you with detailed reporting and analytics, which allows you to track and analyze your customers PIN usage, and make data-driven decisions. You can also set up alerts and notifications, which will inform you of any changes to your customers PINs usage or activity.
Get CVV2
Status:
Production
Version:
V2
Category:
Pin Management
Overview
CVV2 is a three or four-digit security code that is printed on the back of a credit or debit card. It is used to verify the authenticity of a card during transactions and is typically required for online or over-the-phone purchases.
The API will connect to the card issuer's systems or network and retrieve the CVV2 associated with the provided card number. The API will then return the CVV2 in its response.
Retrieves CVV2 value
The primary feature of this API is its ability to retrieve the CVV2 value for a specific card. This value is used to verify the authenticity of a card during transactions and is typically required for online or over-the-phone purchases.
Support for multiple card identifiers
The API supports multiple card identifiers, such as the card number, to make it easier for developers to retrieve the CVV2 value they need.
High security
This API uses standard HTTPS protocols to receive the request and return the response, and it also uses the necessary authentication credentials such as an API key, which provides an additional layer of security to protect the cardholder's information.
How It Works
The "Get CVV2" API allows developers to retrieve the Card Verification Value 2 (CVV2) associated with a specific card number. This can be accomplished by making an HTTPS POST request to the API endpoint, which includes the card number as a parameter in the request body.
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
Category:
Pin Management
| 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_GET_CVV2 | |||||||
| src_application | string | 10 | Source requesting channel eg SSP Might change | |||||||
| target_application | string | 10 | Target application name Ex WAY4 | |||||||
| timestamp | string | 30 | Timestamp of the request Format DD/MM/YYYY HH:MM:SS | |||||||
| tracking_id | string | 30 | Transaction Tracking Id | |||||||
| bank_id | string | 4 | Source Bank Id Ex NIC | |||||||
| body | card_identifier_id | string | 32 | card identifier | ||||||
| card_identifier_type | string | 20 | CONTRACT_NUMBER or EXID | |||||||
| expiry_date | string | 4 | YYMM ex: 2310 | |||||||
{
"NISrvRequest": {
"request_get_cvv2": {
"header": {
"msg_id": "223001",
"msg_type": "TRANSACTION",
"msg_function": "REQ_GET_CVV2",
"src_application": "IVR",
"target_application": "WAY4",
"timestamp": "2020-07-20T10:49:02.366+04:00",
"tracking_id": "223001",
"bank_id": "NIC"
},
"body": {
"card_identifier_id": "99984100148297467162",
"card_identifier_type": "EXID",
"expiry_date": "2701"
}
}
}
}| 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 | msg_type sent in the request will be sent back in response in this field | |||||||
| msg_function | string | 50 | Function name to be used default REP_GET_CVV2 | |||||||
| 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 request 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 Eg ABCD | |||||||
| instance_id | string | 10 | InstanceID | |||||||
| exception_details | ||||||||||
| body | card_identifier_id | string | 32 | 454545XXXXXX1234 | ||||||
| card_identifier_type | string | 20 | CONTRACT_NUMBER or EXID | |||||||
| cvv2 | string | |||||||||
| expiry_date | string | |||||||||
{
"NISrvResponse": {
"response_get_cvv2": {
"header": {
"msg_id": "236001",
"msg_type": "TRANSACTION",
"msg_function": "RES_GET_CVV2",
"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": {
"card_identifier_id": "454545XXXXXX1234",
"card_identifier_type": "CONTRACT_NUMBER\/EXID",
"cvv2": "string",
"expiry_date": "string"
}
}
}
}| 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 |
How It Works
Follow the steps below. For more details, read the Quick Start Guide.
1- 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.
2- 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.
3- 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.
4- 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.
5- 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.
