| 400 | mobile-not-eligible | The submitted mobile number entered isn’t valid for the selected service or the account isn’t Active. |
| 400 | email-not-eligible | The submitted email isn’t valid for the selected service or the account isn’t Active. |
| 400 | account-not-found | When checking for the product and associated account, this errors occurs when the account is not found. |
| 400 | invalid-product-code | The product code entered isn’t valid. |
| 400 | product-id-required**** | The product id is missing or not entered. |
| 400 | unsupported-identifier-type**** | The identifier isn’t supported by the account discovery operation. The discovery operation is controlled by the accountDiscovery feature flag , and determines if the process needs to auto-discover the user account(s) or not. |
| 400 | invalid-identifier | The identifier does not belong to the current end user. |
| 400 | NotReusedPassword | The submitted password isn’t allowed because it’s been used previously. The number of times a password can be reused is controlled by the app settings Password. (system.security.passwordHistoricalCheckingCount) |
| 400 | NotEmpty | The password or identifier hasn’t been entered or is missing. |
| 400 | ValidIdentifierType | The authentication identifier (authN ID) isn’t allowed or valid. If the identifier is:- Mobile number, there may be a pattern mismatch such the wrong number of digits. - If identifier is email, the email domain may be blacklisted. |
| 400 | invalid-2fa-method | The selected 2FA option is not in the list of available 2FA methods. |
| 400 | invalid-2fa-setup-option | The selected 2FA method hadn’t been registered yet. |
| 401 | invalid-credential | The user submits the wrong credentials. |
| 401 | invalid-otp | An user enters an incorrect OTP code when registering their 2FA identifier (authN ID). |
| 401 | invalid-code | The user submits an invalid code during TOTP registration or the user submits an invalid OTP during the 2FA AuthnIdentifier registration. |
| 403 | user-profile-locked | The user is locked and can’t proced until their account is unlocked by an admin or care agent. |
| 403 | no-eligibility-data | no eligibility data for specified account |
| 403 | number-is-portable | This field is controlled by the app setting as system.carrier.portURL. |
| 403 | unverified-identifier | The identifier (authN ID) has not been verified and the end user must complete an action. |
| 403 | user-not-activated | The User ID hasn’t been activated in the Storefront Gateway system. |
| 409 | already-exist-email | When a user onboards and submits their email, the identifier (authN ID) already exists in the Storefront Gateway system. |
| 409 | already-exist-phone | When a user logins and submits their mobile number, the identifier (authN ID) already exists in the Storefront Gateway system. |
| 409 | duplicate-identifier | The identifier (authN ID) entered is already associated to a different user. |
| 409 | already-exist-account | The specified account is already associated to a different user or the same user. |
| 409 | duplicate-account-number | There’s already an existing account in the system with the same account number (account attribute). |
| Parent topic:Onboard and Authenticate Process | | |
