---
url: >-
  https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/technicalterm/FailureFinalState/index.md
description: >-
  Failure Final State is a transaction status flow pattern where the order
  status becomes final after payment failure and cannot be paid again. A new
  order number is required to initiate payment again. Suitable for scenarios
  requiring strict control of duplicate payments. Main states include SUCCESS,
  CLOSED, FAILED, PROCESSING, and INIT.
---
## Transaction Status Flow Pattern

PingPongCheckout provides two transaction idempotency modes:

- Failure Non-Final State (default)
- Failure Final State (requires notification to PingPongCheckout for configuration during integration)

## Failure Non-Final State

`Failure Non-Final State` is the default setting, in this mode:
- `FAILED` status can still continue to be paid until the order expires and is closed. You can initiate payment again without changing the order number.
- Duplicate payments may occur with low probability, which can be handled with manual refunds

| Status                                                            | Description                                                                 | Status Type |
|:------------------------------------------------------------------|:---------------------------------------------------------------------------|:-----------|
| <div><el-tag type="success" effect="dark" >SUCCESS</el-tag></div> | Payment successful, transaction completed successfully                      | Final State |
| <div><el-tag type="danger"  effect="dark">CLOSED</el-tag></div>   | Transaction result due to timeout/closure                                   | Final State |
| <div><el-tag type="danger" effect="dark" >FAILED</el-tag></div>   | Payment failed, user can pay again                                          | Intermediate State |
| <div><el-tag type="info"  effect="dark">PROCESSING</el-tag></div> | Intermediate state, merchant should wait for PingPongCheckout's asynchronous result before processing business. | Intermediate State |
| <div><el-tag type="info"  effect="dark">INIT</el-tag></div>       | Order initialization                                                        | Intermediate State |

## Failure Final State

`Failure Final State` requires manual configuration, in this mode:
- `FAILED` status is final, the payment order status will not change anymore, you need to change the order number to initiate payment again.
- `PROCESSING` initiating payment request again will prompt duplicate transaction

| Status                                                            | Description                                                                 | Status Type |
|:------------------------------------------------------------------|:---------------------------------------------------------------------------|:-----------|
| <div><el-tag type="success" effect="dark" >SUCCESS</el-tag></div> | Payment successful, transaction completed successfully                      | Final State |
| <div><el-tag type="danger"  effect="dark">CLOSED</el-tag></div>   | Transaction result due to timeout/closure                                   | Final State |
| <div><el-tag type="danger" effect="dark" >FAILED</el-tag></div>   | Payment failed, user can pay again                                          | Final State |
| <div><el-tag type="info"  effect="dark">PROCESSING</el-tag></div> | Intermediate state, merchant should wait for PingPongCheckout's asynchronous result before processing business. | Intermediate State |
| <div><el-tag type="info"  effect="dark">INIT</el-tag></div>       | Order initialization                                                        | Intermediate State |