Status of an order and a transaction
When processing orders with Mercado Pago Point, it’s important to understand how the processing flow works and which status an order and a transaction can take at any given time.
Below, you can view the flow of an order for card payments and then an informative table about each of the possible status, including their respective status_detail.
stateDiagram-v2
[*] --> created
created --> expired: It was not processed within 15 minutes after its creation
created --> canceled: Canceled via API
created --> at_terminal
at_terminal --> canceled: Canceled via terminal
at_terminal --> processed: Processed successfully
at_terminal --> Failed: Payment declined / Payment component failure / EMV reversal
at_terminal --> action_required: After 40s of processing start
processed --> refunded: Full refund via API, activity, or terminal
created: created
expired: expired
canceled: canceled
at_terminal: at_terminal
processed: processed
failed: failed
action_required: action_required
refunded: refunded
Order status
Check the list of status and status_detail that an order can take.
status | status_detail | Description |
created | created | The order was successfully created but has not yet been captured by the terminal. |
processed | processed | The order was successfully processed and the payment was credited. |
action_required | action_required | The transaction associated with the order needs to be confirmed. Check the terminal to verify the final status and make sure to update your system accordingly, as this status will not change. |
at_terminal | at_terminal | The order was captured by the terminal and is ready to be processed. |
failed | failed | The order has failed. This means the transaction was not successful and will not be completed. |
refunded | refunded | The order was refunded. This means the transaction amount was fully returned to the payer. |
expired | expired | The order expired after more than 15 minutes without being paid. If you wish to complete the payment, a new order must be created. |
Transaction status
Check the list of status and status_detail that a transaction can take.
status | status_detail | Description |
created | created | The transaction was successfully created, but it has not yet been processed. This is the initial state of a transaction after it is created. |
processed | accredited | The transaction was successfully processed and the amount has been effectively credited. |
action_required | waiting_payment | The transaction requires an additional action and is waiting for payment. This means the transaction has been initiated, but the payment has not yet been completed. |
action_required | check_on_terminal | The transaction requires confirmation on the terminal to check whether the payment was approved or rejected. |
at_terminal | at_terminal | The transaction was received by the terminal and is ready to be processed. |
expired | expired | The transaction has expired. This means it was not completed within the allowed time and was therefore terminated. |
refunded | refunded | The order has been refunded. This means the amount of the transaction has been fully returned to the payer. |
canceled | canceled | The transaction was canceled and will not be completed. |
canceled | canceled_by_api | The transaction was canceled via the API and will not be completed. |
canceled | canceled_on_terminal | The transaction was canceled from the terminal and will not be completed. |
failed | failed | A failure occurred while processing the order. This may have been caused by incorrect data submission, fraud risk, or rejection by the card issuer. |
failed | bad_filled_card_data | The transaction failed due to incorrectly filled card data. This may include information such as card number, CVV, expiration date, among others. |
failed | high_risk | The transaction failed due to high risk detection. This can happen when the fraud detection system identifies a potential risk in the transaction. |
failed | rejected_by_issuer | The transaction failed due to rejection by the card issuer. |
failed | required_call_for_authorize | The transaction failed because a call for authorization is required. This may occur when the card issuer requires additional verification before approving the transaction. |
failed | max_attempts_exceeded | The transaction failed because the maximum number of attempts was exceeded. This can happen when the number of payment attempts goes beyond the system's allowed limit. |
failed | card_disabled | The transaction failed because the card is disabled. This may occur when the card has been blocked or deactivated by the issuer. |
failed | insufficient_amount | The transaction failed due to insufficient funds. This may happen when the available balance is not enough to cover the transaction amount. |
failed | amount_limit_exceeded | The transaction failed because the amount exceeded the allowed limit. This can happen when the transaction amount surpasses the threshold set by the issuer or the system. |
failed | processing_error | The transaction failed due to a processing error. This may happen when a technical issue or system error prevents completion. If the problem persists, contact support and provide the x-request-id along with details of the operation. |
failed | invalid_installments | The transaction failed due to invalid installments. This can happen when the selected number of installments is not accepted by the card issuer or the system. |
failed | in_review | The transaction failed and its status is unknown or contains sensitive information. |