Unknown macro: {style}

.page-metadata

Unknown macro: {display}

Page tree
Skip to end of metadata
Go to start of metadata

Overview

Following are the possible transaction states that you may come across during payment scenarios:

StateDescription
WAITING_FOR_SOURCETransaction is waiting for user identification vectors. For example, card details, phone number and so on.
WAITING_FOR_CONSENTWaiting to validate users' authenticity via OTP, PIN and so on.
CANCELLEDCancelled by the requester by calling Cancel a transaction API.
CANCELLED_BY_USER_AGENTCancelled by user by clicking on CANCEL option provided on Zeta hosted client pages.
WAITING_FOR_AUTHORIZATIONUser entered the authentication factor get authorized. Transaction in this state should not be considered as authorized, if a transaction is in 'WAITING_FOR_AUTHORIZATION' state for more that 30 seconds. It gets auto-reversed in 3 days, if in case money got debited.
AUTHORIZEDTransaction is authorised by the processor.
UNAUTHORIZEDTransaction is unauthorized by the processor. See Get Transaction Details API response to know the reason for failure under the 'failureReason' field.
REFUND_INITIATEDRefund for transaction in AUTHORIZED or WAITING_FOR_AUTHORIZATION states has been initiated. For transaction in AUTHORIZED state, refund initiation happens when the client calls the Refund a Transaction API. For transaction in WAITING_FOR_AUTHORIZATION state, an 'auto-reversal' of this transaction is attempted which marks the transaction as REFUND_INITIATED
REFUND_FAILEDRefund has failed. This rarely happens, when the transaction stuck in 'WAITING_FOR_AUTHORIZATION' was not authorized by the processor in the initial authorization attempt.
REFUND_COMPLETEDRefund of the transaction is processed successfully.
REFUND_DROPPEDRefund is dropped after fixed automated N number of attempts to get transaction refunded. In rare cases, if refund is required for a valid use-case, it needs to be handled manually.