Status

API fields: payment.status, transaction.status

Both the payment and the transaction have a status parameter. The difference between them is that the payment status is obtained after all transactions have been processed. For example, if a payment generated three declined transactions and one approved, the final payment status will be succeeded. The status of each transaction, in turn, represents the response of each communication attempt, if any.

Payment status

The possible statuses for the payment are:

• initiated: the payment was initiated but has not yet been processed by the connector (acquirer, sub-acquirer, or gateway). This is the only status that allows antifraud analysis.
• succeeded: the payment was approved by the connector in at least one of the transactions.
• declined: the payment was declined by the connector.
• blocked: the payment was blocked according to your decision, whether by the fraud probability score or by the traditional antifraud analysis, if any.
• failed: an error occurred while attempting the transaction. Use it in the case of infrastructure or configuration failures, or when the cause of the problem is unknown.

The succeeded and declined statuses require sending the transactions in the same request. The failed and blocked statuses do not, but we recommend sending the transactions whenever there was an attempt.

Transaction status

The possible statuses for the transaction are:

• succeeded: the transaction was successfully approved by the connector.
• declined: the transaction was declined by the connector.
• failed: an error occurred while attempting the transaction. Use it in the case of infrastructure or configuration failures, or when the cause of the problem is unknown.
• canceled: the transaction was canceled before obtaining an approval or decline response from the connector.