> For the complete documentation index, see [llms.txt](https://docs.rocketfuel.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rocketfuel.inc/developer-guides/api-reference/payins/rocketfuel-ui-integration/transaction-statuses.md).

# Transaction  Statuses

***

This section provides a reference for all possible transaction statuses and how to handle them. You will also receive webhook updates whenever a status changes, and you can consult this guide when using the transaction lookup APIs.

### Status Codes

| Status Code       | Description                                                                                                                                                                                                                 |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 10                | Initial state. No payment detected yet. Transaction is marked as unpaid.                                                                                                                                                    |
| **0**             | Pending transaction. Payment detected but awaiting final confirmation.                                                                                                                                                      |
| **1 / 2 / 3 / 4** | Treated as **Success**. Indicates the payment has been successfully received.                                                                                                                                               |
| **101**           | Partial payment received. The order remains open, and the user can send additional payment to complete it.                                                                                                                  |
| **1011**          | Partial payment closed by the merchant. No further payments are accepted. can be close by this api:[ handling partial cases](/developer-guides/api-reference/payins/rocketfuel-ui-integration/handling-partial-payments.md) |
| **201**           | Payment amount less than order value (**Underpaid**). *Enabled only if the merchant opts into handling such cases. Write us at <contact@rocketfuel.inc> to enable this feature.*                                            |
| **202**           | Payment amount greater than order value (**Overpaid**). *Enabled only if the merchant opts into handling such cases. Write us at <contact@rocketfuel.inc> to enable this feature.*                                          |
| **-1**            | Transaction rejected or failed.                                                                                                                                                                                             |
| 19                | **Timed Out** transaction.                                                                                                                                                                                                  |

***

### Timed Out Transactions

A **Timed Out** transaction occurs when a payment cannot be confirmed within the expected timeframe. This can happen due to network congestion, delays in confirmation, or other technical reasons.

**Key Points:**

* Status code for timed-out transactions: **19**
* These transactions are not marked as successful.
* A **webhook event** is triggered whenever a transaction moves to this status.
* Depending on your system, you can treat this as a failed payment or allow the user to retry the payment.

### Partial Payment Use Cases

1. **Allow Completion of Partial Payment**
   * User makes a partial payment and can send additional payment(s) to complete the order.
   * If the remaining amount is not received within the allowed time, the transaction moves into a final **Partial** state, and a refund can be requested by the shopper.
2. **Do Not Allow Partial Payments**
   * If the first payment is partial, no further payments are accepted.
   * A **Refund** button is displayed to the user immediately. (check the screenshot below)<br>

     <figure><img src="/files/4cSA6ViYCtwpN9CkrzR5" alt=""><figcaption></figcaption></figure>

***

### Force Refund Use Case

To enable this feature, contact us at <_contact@rocketfuel.inc>.\_

* Merchants can trigger a **force refund** to immediately close a transaction and refund the user.
* No further payments are accepted once the refund is initiated.
* This is useful when merchants do not want to handle incomplete or partial payments.