| On File | 1. This is the initial status. When the store is created and doesn't onboard any payment brand, the store status is "On File". | Yes | No | No | Yes | No |
| Active | 1. There are payment brands that have onboarded successfully, and there is no payment brand that is onboarding or has failed to onboard, then the store status is "Active". | Yes | No | Yes | Yes | Yes |
| Partial Active | 1. One of the payment brand that has onboarded successfully, the store status is "Partial Active". | Yes | No | Yes | Yes | Yes |
| Reviewing | 1. If the acquirer enables the “Store Level Task” audit task, any new operations performed through the portal will change the store status to “Reviewing” (waiting for approval). However, operations performed through the API will not trigger the status change to “Reviewing”. | No | No | No | No | No |
| Rejected | 1. After creation, the status becomes "Reviewing". If the auditor rejects it, the status changes to "Rejected", and the user can update the information and call the edit API. | Yes | No | No | Yes | No |
| PSP Pending | 1. There are payment brands that are onboarding and there is no payment brand that has onboarded successfully, then the store status is "PSP Pending". | No | No | No | No | No |
| PSP Rejected | 1. There are payment brands that have failed to onboard and there is no payment brand that is onboarding or has onboarded successfully, then the store status is "PSP Rejected". | Yes | No | No | Yes | No |
| Disabled | 1. When the store status is "Disabled", the store can’t be used. The transaction can not be performed, and the related user's permissions will be restricted. | No | Yes | No | Yes | No |
