Sign in at the hub
In the intended flow, you authenticate on the iFastShop Account page—not inside a third-party app.
iFastShopAccount
ONE ACCOUNT · APPROVED APPS
Use your iFastShop Account to sign in to iFastShop and other apps approved by the owner.
Choose a sign-in method that’s ready for this app.
iFastShop Account is the planned sign-in hub for iFastShop and apps approved by the owner. Sign in once at the hub, then choose what profile information each app may receive.
In the intended flow, you authenticate on the iFastShop Account page—not inside a third-party app.
Apps request specific scopes. Only owner-approved fields within those scopes would be returned after consent.
Hosting an app on your own domain? Read the developer integration guidance before requesting access.
YOUR IFastShop ACCOUNT
Sign in or create an account to continue.
Link a new sign-in method only after proving control of this account. Matching email addresses never merge accounts. User authenticator-app TOTP is intended to be optional. Owner TOTP is opt-in. The approved-developer MFA policy defaults to Optional and is owner-controlled; developer sign-in is not live in this local version.
By continuing, you agree to use only apps approved for iFastShop Account.
← Back to iFastShop AccountBuilding an app? Request developer access
Your app can keep its own hosting and domain. Send the owner an access request; every request stays pending until reviewed in the separate console.
Your app may be hosted wherever you choose. When authentication is implemented, the user’s browser will be redirected to the iFastShop Account hub; your app must never ask for, collect, store, or receive the user’s hub password.
http://localhost:3000 or http://127.0.0.1:3000. No wildcard or open-redirect callback is allowed.state, a PKCE verifier, and an S256 code challenge. The hub would verify the exact registered callback and scopes, then ask the user to consent./oauth/authorize currently performs limited boundary checks and returns login-required; it issues no code. /api/oauth/token, OIDC discovery, user sessions, consent, and provider sign-in are not implemented. Do not connect production users yet.More details: Developer integration notes are summarized above.
A separate local console for developer requests and security preferences. Nothing here creates a live account or connects an external service.
Owner authenticator app
Optional. When enabled, owner sign-in asks for a current code or one-use recovery code.
They are shown once. Each code can replace one authenticator code during local owner sign-in.