Status codes

This section provides a canonical list of valuesstatus, sub_statusand typical valuesstatus_description, which are used in API responses and alerts. The exact set of combinations depends on the product, method and processing scenario.

Basic combinations of status and sub_status

Status Substatus Description

Status	Substatus	Description
`error`		The request was rejected due to a parameter error or processing error.
`processing`	`new`	The application has been created and accepted for processing.
	`requisites`	The selection of a provider, details or preparation of data for payment is carried out.
	`awaiting_confirm`	The client's payment confirmation is expected on the payment page or in the linked payment script.
	`awaiting_3ds_result`	The result of additional verification on the client or provider side is awaited. For scenarios, 3-D Secure is used as an expectation for the authentication result. For Mobile ECOM — OTP is requested from the user.
	`awaiting_redirect_result`	The confirmation result is expected after the user is redirected to the external side of the bank, issuer or provider.
	`sent_verification`	The OTP has been submitted by the user for verification.
	`invalid_verification`	The user sent an incorrect OTP. After three incorrect attempts, the application goes to`decline`.
	`paid`	The client confirmed that he sent the amount to the issued details — an interim confirmation of payment was received, then finalization is expected in`success`or`decline`. For Mobile ECOM — confirmation was received that the OTP was entered correctly.
	`payout_process`	Payment is made using the specified details.
`dispute`	`no_payment`	The client did not complete the payment within the lifetime of the application.
	`different_amount`	An amount received that does not match the stated amount.
	`confirm_timeout`	The confirmation timeout has expired, but the application requires additional review.
	`incorrect_requisites`	Incorrect details received, clarification required.
	`payout_failed`	The payment was not executed; an analysis of the reason is required.
	`payout_timeout`	The payment was not executed before the application's lifetime expired.
`decline`		Final refusal to process the application.
`success`		Final successful completion of the application.

error

The request was rejected due to a parameter error or processing error.

processing

new

The application has been created and accepted for processing.

requisites

The selection of a provider, details or preparation of data for payment is carried out.

awaiting_confirm

The client's payment confirmation is expected on the payment page or in the linked payment script.

awaiting_3ds_result

The result of additional verification on the client or provider side is awaited. For scenarios, 3-D Secure is used as an expectation for the authentication result. For Mobile ECOM — OTP is requested from the user.

awaiting_redirect_result

The confirmation result is expected after the user is redirected to the external side of the bank, issuer or provider.

sent_verification

The OTP has been submitted by the user for verification.

invalid_verification

The user sent an incorrect OTP. After three incorrect attempts, the application goes todecline.

paid

The client confirmed that he sent the amount to the issued details — an interim confirmation of payment was received, then finalization is expected insuccessordecline. For Mobile ECOM — confirmation was received that the OTP was entered correctly.

payout_process

Payment is made using the specified details.

dispute

no_payment

The client did not complete the payment within the lifetime of the application.

different_amount

An amount received that does not match the stated amount.

confirm_timeout

The confirmation timeout has expired, but the application requires additional review.

incorrect_requisites

Incorrect details received, clarification required.

payout_failed

The payment was not executed; an analysis of the reason is required.

payout_timeout

The payment was not executed before the application's lifetime expired.

decline

Final refusal to process the application.

success

Final successful completion of the application.

Typical status_description values

Fieldstatus_descriptionfilled in for errors, failures and other scenarios where a textual explanation is required. Below are commonly used values.

Depending on the value methodstatus_descriptionmay vary. Use product documentation sections and actual integration examples.

Status status_description Description

Status	`status_description`	Description
`decline`	`Canceled by client`	The client canceled the payment.
`decline`	`Declined by anti-fraud`	The anti-fraud system removed the request.
`decline`	`Requisites not found`	Could not find payment details.
`decline`	`Payment general decline`	Generalized final provider failure in mobile commerce (ECOM) scenario.

decline

Canceled by client

The client canceled the payment.

decline

Declined by anti-fraud

The anti-fraud system removed the request.

decline

Requisites not found

Could not find payment details.

decline

Payment general decline

Generalized final provider failure in mobile commerce (ECOM) scenario.