OTP Code Resend

To resend an OTP code via the Partner's website, the check_pan method should be used by sending a request to the server.

Important Information!

Limit on incorrect OTP code entries: The client can enter an incorrect OTP code no more than three times. If this limit is exceeded, the transaction will be canceled, and a new payment registration will be required.

Method check_pan

• URL: https://secure.octo.uz/check_pan
• Method: POST
• Content-type: application/json

Request Example

{
    "pan": "1234123412341234",      // Client's card number
    "expDate": "2601",             // Card expiration date (YYMM)
    "paymentId": "{{payment_id}}"    // Unique payment identifier
}

Request Parameters

Parameter	Type	Required	Description
pan	string	Yes	Client's card number used for the transaction
expDate	string	Yes	Card expiration date in the format YYMM
paymentId	int	Yes	Unique payment identifier

Successful Response Example

{
    "error": 0,
    "errMessage": "",
    "data": {
        "verifyId": 856,
        "phone": "+998** *****33",
        "secondsLeft": 120
    }
}

Successful Response Parameters

Parameter	Type	Required	Description
error	int	Yes	Error code: 0 means no errors
errMessage	string	No	Error message. Empty if no errors
data	object	Yes	Object with details of the verification process
verifyId	int	Yes	Unique identifier of the verification process
phone	string	Yes	Phone number for verification (partially hidden for security)
secondsLeft	int	Yes	Remaining time (in seconds) until the verification expires

---

Unsuccessful Response Example

{
    "error": 17,
    "errMessage": "Maximum number of SMS resend attempts",
    "data": null
}

Unsuccessful Response Parameters

Parameter	Type	Required	Description
error	int	Yes	Error code
errMessage	string	Yes	Error message
data	object	No	Core transaction data (in this case null)