---
page_source: https://juspay.io/in/docs/payv3/web/resources/transaction-status
page_title: Transaction Status
---


## Transaction Status



There are 2 ways to fetch payment status: -

1. **Order Status API** : Juspay provides a server-to-server mechanism of verifying the Order Status. [Click for Detailed API for order status](https://docs.juspay.in/payv3/web/base-integration/order-status-api)

2. **Webhooks** : After the completion of every payment/refund, Juspay will provide direct notification to your server regarding the event. These are called Webhooks. You must configure a valid HTTPS endpoint that is reachable from our servers to consume these notifications. Our servers will push data using HTTP POST calls to your endpoint. [Click for Detailed Webhook Specifications](https://docs.juspay.in/payv3/web/base-integration/webhooks)


#### The following figure is a workflow of how you can handle the order status:




#### The following table lists the transaction status codes that Order Status API returns:




| Status ID | Status | Description | Actionables |
|---|---|---|---|
| 10 | NEW | Newly created order. This is the status if transaction is not triggered for an order | <span style="margin-left:45%; margin-right:45%;">N/A</span> |
| 23 | PENDING_VBV | Authentication is in progress | This is a non-terminal transaction status. Show pending screen to your customers and in background keep polling order-status API till you get Charged or Failed; or till the time your order fulfilment window <i>(a specified duration post which payments will not be accepted against the order)</i> is active. |
| 21 | CHARGED | Successful transaction | Display order confirmation page to the user and fulfill the order. |
| 26 | AUTHENTICATION_FAILED | User did not complete authentication | Display transaction failure status to the user along with the failure reason provided in the order status API response. Allow user to retry payment. |
| 27 | AUTHORIZATION_FAILED | User completed authentication, but the bank refused the transaction. | Display transaction failure status to the user along with the failure reason provided in the order status API response. Allow user to retry payment. |
| 22 | JUSPAY_DECLINED | User input is not accepted by the underlying PG | This scenario is an integration error. Reach out to <a href='mailto:support@juspay.in'>support@juspay.in</a> with order ID details for clarification. |
| 28 | AUTHORIZING | Transaction status is pending from bank | This is a non-terminal transaction status. Show pending screen to your customers and in background keep polling order-status API till you get Charged or Failed; or till the time your order fulfilment window <i>(a specified duration post which payments will not be accepted against the order)</i> is active. |
| 29 | COD INITIATED | COD Initiated Successfully | Display order confirmation page to the user and fulfill the order. |