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.

Card Set Pin(Post)

This API enables the setting of a personal identification number (PIN) for a specific card, which can then be used for point of sale or ATM transactions.

Status :Production

Version : V2

Try Out

Card Pin Verification(Post)

This API is used to check if a PIN provided by the cardholder matches the one associated with the card, in order to confirm the identity of the cardholder.

Status :Production

Version : V2

Try Out

Card Pin Change(Post)

This API allows a cardholder to change their PIN by verifying their current PIN and setting a new one. The new PIN will be used for Point of Sales or ATM transactions.

Status :Production

Version : V2

Try Out

Pin Tries Counter Reset(Post)

This API allows to reset the number of attempts a user has made to enter the correct PIN, in case the user has entered the incorrect PIN multiple times.

Status :Production

Version : V2

Try Out

Get CVV2(Post)

This API allows consumers to retrieve the CVV2 (Card Verification Value 2) for a specific card.

Status :Production

Version : V2

Try Out

Card Pin Verification

Status:

Production

Version:

V2

Category:

Pin Management

Card PIN Verification

Overview

The "Pin Verification" API allows financial institutions to verify the identity of a cardholder by comparing a PIN input by the cardholder to the one associated with the card on file. This API can be integrated into various platforms such as online banking, e-commerce, or point-of-sale systems to provide secure cardholder authentication

The API allows for real-time validation of the PIN entered, ensuring that only authorized cardholders have access to restricted information or are able to perform certain actions. It performs the validation of the entered PIN against the card on file to confirm the identity of the cardholder.

Real-time verification

The "Pin Verification" API allows developers to perform real-time verification of a cardholder's identity by comparing a PIN provided by the cardholder to the one associated with the card, ensuring that only authorized cardholders are able to access restricted information or perform certain actions.

Secure authentication

The API uses secure protocols and encryption to protect sensitive information, such as the cardholder's PIN, and ensures that the identity of the cardholder is kept confidential.

Easy integration:

The API is designed to be easy to integrate into existing systems and applications, allowing developers to quickly and easily add cardholder authentication functionality to their projects.

How It Works

The "Card PIN Verification" API allows financial institutions to verify the validity of a cardholder's PIN by comparing it to the one associated with a specific card. The API operates by receiving a request from a financial institution, which includes the card number and the PIN provided by the cardholder as parameters. The API then connects to the card issuer's systems or network to retrieve the PIN associated with the provided card number and compares it to the one provided by the cardholder. The API returns the result of the comparison to the consumer.

The API utilizes standard HTTPS protocols for receiving requests and returning responses. Financial institutions can make an HTTPS POST request to the API endpoint, including necessary parameters such as the card number and the cardholder's PIN 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.

Node	Child Node	Type	Length	Description
Authorization* required	Bearer xxxx* required	string		Authorization Header (Bearer Token)
Content-Type* required	application/json* required	string		Content Type

Node Type				Type	Length	Description
NISrvRequest	request_card_pin_verification	header	msg_id* required	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* required	string	12	Message Type – This can have either “TRANSACTION” or “ENQUIRY” As for this API the value expected is “ENQUIRY”
			msg_function* required	string	50	Message functions: Should be “REQ_CARD_PIN_VERIFICATION”
			src_application* required	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* required	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* required	string	30	Timestamp of the request Date & time Format DD/MM/YYYY HH:MM:SS
			bank_id* required	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* required	string	32	card identifier
			card_identifier_type* required	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	YYMM Ex: 2310
			encrypted_pin* required	string	20	Encrypted Pin block under ZPK Ex: 7B47D3321D4A5F63
			encryption_method	string	20	Encryption Method to be used for the encryption of the pin

{"NISrvRequest":{"request_card_pin_verification":{"header":{"msg_id":"12345","msg_type":"ENQUIRY","msg_function":"REQ_CARD_PIN_VERIFICATION","src_application":"IVR","target_application":"PCMS","timestamp":"2020-05-21T15:13:18.853+04:00","tracking_id":"12345df","bank_id":"NIC"},"body":{"card_identifier_id":"99984100148297467162","card_identifier_type":"EXID","card_expiry_date":"2310","encrypted_pin":"F41AB9C3974FE7B9","encryption_method":"SYMMETRIC_ENC","encryption_key_id":"","encryption_key_type":""}}}}

{
    "NISrvRequest": {
        "request_card_pin_verification": {
            "header": {
                "msg_id": "12345",
                "msg_type": "ENQUIRY",
                "msg_function": "REQ_CARD_PIN_VERIFICATION",
                "src_application": "IVR",
                "target_application": "PCMS",
                "timestamp": "2020-05-21T15:13:18.853+04:00",
                "tracking_id": "12345df",
                "bank_id": "NIC"
            },
            "body": {
                "card_identifier_id": "99984100148297467162",
                "card_identifier_type": "EXID",
                "card_expiry_date": "2310",
                "encrypted_pin": "F41AB9C3974FE7B9",
                "encryption_method": "SYMMETRIC_ENC",
                "encryption_key_id": "",
                "encryption_key_type": ""
            }
        }
    }
}

Node	Child Node		Type	Length	Description
Content-Type	application/json		string		Content Type

Node Type				Type	Length	Description
NISrvResponse	response_card_pin_verification	header	msg_id* required	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* required	string	12	Message Type – This can have either “TRANSACTION” or “ENQUIRY” As for this API the value expected is “ENQUIRY”
			msg_function* required	string	50	Message functions: Should be “RES_CARD_PIN_VERIFICATION”
			src_application* required	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* required	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* required	string	30	Timestamp of the response Date & time Format DD/MM/YYYY HH:MM:SS
			bank_id* required	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* required	string	20	Application Name
			date_time* required	string	30	Timestamp of the response Format “YYYY-MM-DD HH:MM:SS”
			status* required	string	1	Status of the request (S/F)
			error_code* required	string	4	EAI Internal Error Code (Check error codes section for the complete list of error codes and error code descriptions)
			error_description* required	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_pin_verification":{"header":{"msg_id":"236001","msg_type":"ENQUIRY","msg_function":"RES_CARD_PIN_VERIFICATION","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"}}}}

{
    "NISrvResponse": {
        "response_card_pin_verification": {
            "header": {
                "msg_id": "236001",
                "msg_type": "ENQUIRY",
                "msg_function": "RES_CARD_PIN_VERIFICATION",
                "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"
            }
        }
    }
}

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

Pin Management

Pin Management

Overview

Card Set Pin(Post)

Card Pin Verification(Post)

Card Pin Change(Post)

Pin Tries Counter Reset(Post)

Get CVV2(Post)

Card Pin Verification

Status:

Production

Version:

V2

Category:

Pin Management

Card PIN Verification

Overview

Real-time verification

Secure authentication

Easy integration:

How It Works

Process 1

Process 1

Process 1

Card Pin Verification

Status:

Production

Version:

V2

Category:

Pin Management

How It Works

1- Process 1

2- Process 1

3- Process 1

4- Process 1

5- Process 1

Pin Management

Pin Management

Overview

Card Set Pin(Post)

Card Pin Verification(Post)

Card Pin Change(Post)

Pin Tries Counter Reset(Post)

Get CVV2(Post)

Card Pin Verification

Status:

Production

Version:

V2

Category:

Pin Management

Card PIN Verification

Overview

Real-time verification

Secure authentication

Easy integration:

How It Works

Process 1

Process 1

Process 1

Card Pin Verification

Status:

Production

Version:

V2

Category:

Pin Management

Header Request Parameters

Request Parameters

Sample Request

Header Response parameters

Response parameters

Sample Response

Error Code

How It Works

1- Process 1

2- Process 1

3- Process 1

4- Process 1

5- Process 1