| Reviewing | 1. If the acquirer enables the “Transaction Limit Plan” audit task, after the new operation performed through the portal, the status is empty, the reviewing status will be "Reviewing". However, operations performed through the API will not trigger the reviewing status change to “Reviewing”. | No | No | No | No | No | No |
| Rejected | 1. After creation, the status becomes "Reviewing". If the auditor rejects it, the reviewing status changes to "Rejected", and the user can update the information and call the edit API. | Yes | No | No | No | No | No |
| Active | Not Reviewing | 1. When the transaction limit plan is successfully created, its status is set to "Active". | Yes | No | Yes | Yes | Yes | Yes |
| Active | Reviewing | 1. If the acquirer enables the “Transaction Limit Plan” audit task, when the status is "Active", any disable, delete operation performed through the portal will change the reviewing status to “Reviewing” (waiting for approval). However, operations performed through the API will not trigger the reviewing status change to “Reviewing”. | No | No | No | No | No | Yes |
| Disabled | Not Reviewing | 1. When the transaction limit plan is successfully disabled, its status is set to "Disabled". | No | Yes | No | Yes | No | No |
| Disabled | Reviewing | 1. If the acquirer enables the “Transaction Limit Plan” audit task, when the status is "Disabled", any enable, delete operation performed through the portal will change the reviewing status to “Reviewing” (waiting for approval). However, operations performed through the API will not trigger the reviewing status change to “Reviewing”. | No | No | No | No | No | No |
