Reason for operation rejection

The reason for operation rejection describes the circumstances or conditions under which the operation was not successfully completed. This may include user errors (e.g., insufficient funds), verification issues, or restrictions on the part of the payment system or bank.

Field Structure

"fail_reason": {
    "code": 100,
    "message": "Unknown reason, clarification required"
}

The reason for operation rejection is passed as additional parameters in the following methods:

• Payment System Callback​

{
    "project": "Testing",
    "service_code": "70958",
    "external_id": "proident",
    "status_code": "4",
    "status_message": "Transaction was failed",
    "amount": 100.82,
    "datetime": "fugiat sed",
    "username": "enim culpa eiusmod laborum",
    "fail_reason": {
        "code": 100,
        "message": "Unknown reason, clarification required"
    }
    "additional_data": {}
}

• ​Checking the refill status

{    
    "status": true,
    "status_code": 0,
    "message": "Success",
    "result":{
        "error_code" : 0,
        "message": "",
        "data": {
            "status_code": "4",
            "status_message": "Transaction was failed",
            "username": "989898",
            "amount": 100,
            "datetime": "2022-12-01T15:45:00Z",
            "project": "mobile",
            "fail_reason": {
                "code": 100,
                "message": "Unknown reason, clarification required"
            }
            "service_code": "201106",
            "external_id": "200001",
        },
        "additional_data":{}
}

• Check account status

 {
    "status": true,
    "status_code": 0,
    "message": "Success",
    "result": {
        "error_code": 0,
        "message": "This account is inactive",
        "account_status": 0,
        "additional_data": {},
        "fail_reason": {
            "code": 100,
            "message": "Unknown reason, clarification required"
        },
        "info": {
            "parking": {
                "in_date": "2024-08-02T12:24:07+05:00",
                "left_free_time_minutes": 0,
                "sum": 118,
                "current_balance": -1
            }
        }
    }
}

• ​Make a payment is passed when the status is Transaction was failed

{
    "status": true,
    "status_code": 0,
    "message": "Success",
    "result": {
        "error_code": 0,
        "message": "",
        "data": {
             "status_code": "4",
            "status_message": "Transaction was failed",
            "username": "12345",
            "amount": 1000,
            "datetime": "2024-01-01T00:00:00",
            "project": "project",
            "service_code": "service",
            "external_id": "200001",
            "fail_reason": {
                "code": 100,
                "message": "Unknown reason, clarification required"
            },
        },
        "additional_data": {}
    }
}

• Confirmation of funds debit is passed when the status is Transaction was failed

{
    "status": true,
    "status_code": 0,
    "message": "Success",
    "result": {
        "is_success": true,
        "transaction_status_id": "4",
        "external_id": "200001",
        "message": "",
        "otp_status": false,
        "fail_reason": {
            "code": 402,
            "message": "Incorrect confirmation code"
        }
    }
}

code	message
100	Unknown reason, clarification required
101	Error on the service provider side
102	Request validation error
103	A payment with the specified ID already exists in the system
104	Transaction with the specified ID is not found in the system
105	Authorization error
106	Verification via the provider's server is unavailable. You can make a payment if you are confident in the parameters
107	Transaction failed by timeout
200	Insufficient balance
201	Invalid ID format
202	Unverified account
203	Phone number not available for top-up
204	Operation limit exceeded for a user with simplified identification
205	Operation limit exceeded for an identified user
206	Operation limit exceeded for an unidentified user
207	Invoices are not yet generated. The provider may generate new month invoices during a period when they cannot be obtained.
300	The payment amount is too large
301	Limit exceeded
302	Incorrect payment amount
303	The payment amount is less than the minimum value
304	Amount out of acceptable range
400	Receiving two confirmation requests for the same operation with a minimal interval
401	Transaction lifespan expired
402	Incorrect confirmation code
403	The service has already been paid
404	The specified zone does not exist
405	The specified zone is inactive
406	A parameter required for payment is missing
407	Exceeded the number of confirmation code attempts