# MD for: https://www.mercadopago.com.ar/developers/pt/docs/mp-point-v2/resources/status-order-transaction.md

\# 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\`. 


stateDiagram-v2
  [*] --> created

  created --> expired: After its creation, it was not processed within 15 minutes (for PDV mode) or within 15 seconds (for SELF_SERVICE mode)
  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 --> expired: Expired while at terminal

  processed --> refunded: Full refund via API, activity, or terminal

  created: created
  expired: expired
  canceled: canceled
  at_terminal: at_terminal
  processed: processed
  failed: failed
  refunded: refunded

\## Order status Check the list of \`status\` that an order can take. | \`status\` | Description | |-------------------|-------------| | \`created\` | The order was successfully created but has not yet been captured by the terminal. | | \`processed\` | The order was successfully processed and the payment was credited. | | \`at\_terminal\` | The order was captured by the terminal and is ready to be processed. | | \`failed\` | The order has failed. This means the transaction was not successful and will not be completed. | | \`refunded\` | The order was refunded. This means the transaction amount was fully returned to the payer. | | \`expired\` | The order has expired. In \*\*PDV\*\* and \*\*SELF\_SERVICE\*\* operating modes, the default expiration time is 15 minutes without receiving payment. If you wish to complete the transaction, you will need to create a new order. | ## 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. | | \`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. |