Shopify Multipass: customer sign-in and account access
Need one sign-in for your site and Shopify customer accounts? Check Multipass eligibility, account matching and secure access to a shopper’s orders.
- Published
- Last updated
Shopify Multipass signs customers into your store using an identity your external site has already authenticated. It’s limited to eligible Shopify Plus stores already using Multipass. New integrations use a third-party identity provider instead.
The account match decides whose orders the customer can see. Treat a successful redirect as the start of your checks, then confirm the customer identity and private order access.
What Shopify Multipass does
Multipass turns an authenticated external customer into a Shopify customer session through a signed token. Your server creates the token, then the browser follows the sign-in redirect. This is customer access. Staff login and staff Security Assertion Markup Language (SAML) belong to separate Shopify security controls. A storefront password only controls entry to a password-protected store.
For a headless store using current customer accounts, the Multipass grant exchanges a token for Customer Account API access. The client must be a Headless or Hydrogen storefront with that API configured. Its backend calls the token endpoint. A Storefront API customer token and a Customer Account API token aren’t interchangeable.
Customer authentication enables account access. Shopping advice and a support inbox require separate features. A support feature that reads orders also needs permission to read the particular customer’s data.
Check eligibility and the customer-account version
Check the store’s account version and existing Multipass access before choosing an implementation. A Plus subscription alone doesn’t establish eligibility for a new connection.
Shopify’s upgrade guidance says an existing Plus-store Multipass integration continues working after an upgrade. Legacy customer accounts are deprecated. Don’t switch account versions to try to unlock an unavailable integration. If an existing integration’s setting disappears after upgrading, raise that specific issue with Shopify Support.
For a new connection, Shopify Plus stores can connect an OpenID Connect identity provider. OpenID Connect (OIDC) is the authentication standard used for this route. It replaces Shopify’s default customer sign-in experience.
Your provider must meet Shopify’s identity-provider requirements, including verified email and the OAuth 2.0 authorisation code flow. The provider’s ID token must include the required identity claims, including email_verified set to true. This route has its own setup and logout requirements.
Follow Shopify’s connection procedure. Configure the account settings first, then register the callback and sign-out URLs with your provider. Save and test the connection before activation. An Active badge confirms which provider is selected.
Match the customer and protect the sign-in
Match the token’s email to the intended Shopify customer. Verify email ownership first. Use identifier where Shopify requires it, including external usernames. Each Shopify account needs a unique email.
For existing customers, set multipassIdentifier through the Admin API and send its value as identifier. Shopify’s Multipass implementation guide explains the mapping.
Generate encrypted, signed tokens server-side with email and current created_at. Keep the secret in merchant-controlled systems. Exclude browser code and third-party apps.
Redirect over HTTPS using /account/login/multipass/{token} on the store domain or /login/multipass/{token} on the current account domain. Set return_to to your intended store page. Generate tokens on demand. They expire after 15 minutes and work once across URL and grant redemption.
For example, fictional customer Alex has order A-104 and customer Robin has order R-208. Correct: Alex’s verified external identity maps to Alex’s Shopify record. Incorrect: a browser-submitted email overrides Alex’s authenticated identity and selects Robin’s record. Reject that input before issuing a token.
Test account and order access
Test the account identity and visible orders with separate fictional customer records in an eligible test store. Use the following expected outcomes as acceptance checks.
- Sign in as a returning customer. Alex must reach Alex’s record and see A-104. Robin’s R-208 must remain inaccessible, including through a copied order link.
- Sign in with a new verified customer identity. Expect a new customer record when the email has no match. Confirm it has none of Alex’s or Robin’s orders.
- Try an unused token after its validity window. Expect rejection, then generate a fresh token from the authenticated external session and confirm recovery. Also check that replaying a redeemed token fails.
- Sign Alex out, then sign Robin in using the same browser. Reload the account and any connected support panel. Expect Robin’s identity and R-208, with Alex’s cached details cleared.
For an API connection, also inspect the customer returned by an authenticated customer query. The grant’s access token has no refresh token. When it expires, your backend must generate and exchange a new Multipass token.
Test private order support separately from public catalogue answers. A customer name in a greeting doesn’t prove permission to view an order. Attempt another fictional customer’s order number and direct order URL. The support feature must withhold private details throughout that path.
Troubleshoot or replace the connection
Choose the recovery path from the symptom, then repeat the identity and order checks.
| Symptom | Check | Recovery |
|---|---|---|
| Multipass setting missing | Existing access, Plus plan and account version | Existing users affected by an upgrade can contact Shopify Support. New integrations use the identity-provider route. |
Grant returns invalid_assertion | Freshness, previous redemption, payload format and the store secret | Correct token generation and issue a new token. Shopify uses the same error for different token failures. |
Grant returns unsupported_grant_type | Store eligibility, enabled Multipass and client type | Correct the configuration for an eligible Headless or Hydrogen client. |
| Wrong customer or missing expected orders | Authenticated email, customer record and identifier mapping | Stop the affected sign-in flow and correct the mapping before restoring access. |
Keep tokens out of diagnostic logs. Record a correlation reference and safe error details so you can trace failures without retaining sign-in credentials.
Revoke a compromised secret in Shopify admin and generate its replacement. Update your server. Old sign-in URLs become invalid.
External logout leaves Shopify sessions active. Current accounts support backchannel logout, including all-session revocation after compromise. It also revokes grant-issued API tokens. A 204 confirms acceptance only. Verify loss of private access, then repeat the customer-switch test before reopening sign-in.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.